Multinational Information Interoperability Leveraging Multinational Warfighter Consensus for

Multinational Information Interoperability Leveraging Multinational Warfighter Consensus for US Do. D Transformation April 2004 Mr. Richard Lee ADUSD (Interoperability and Network Centric Warfare) ODUSD (Advanced Systems and Concepts) 703 -695 -7938 richard. lee@osd. mil 1

Acknowledgements Portugal Canada United States § DUSD (Advanced Systems and Concepts) – Ms. Sue C. Payton: Vision & Support § Multinational Support: – Three national teams for demonstration and discussions – The Multilateral Interoperability Programme (MIP) community • Portugal, Canada, and US efforts presented today are representative of a larger C 2 community – DISA: • Lt. Gen Raduege, Ms. Dawn Meyerriecks, Mr Bernal Allen and the staff of the Media Center for their assistance in making the demonstrations possible 2

Motivation § Purpose: – The Do. D Net-Centric Data Strategy calls for management of data within Communities of Interest (COI), raising the issue of how to define, organize and govern COIs. – Today’s demonstration shows capabilities resulting from committed Warfighter-led C 2 Community of Interest. – We will demonstrate information interoperability between national C 2 systems from US, Canada and Portugal • Replicating (on a small scale) a 11 -nation interoperability operational test in September 2003 • Showing an implementation consistent with the Do. D Net. Centric Data Strategy (ASD/NII May 2003) – We will share information about the successful multinational interoperability consortium and process, and emerging operational capabilities. – We expect to generate thought and discussion about accelerating the Do. D net-centric transformation by applying the processes and products of the Multilateral Interoperability 3 Programme (MIP) to the GIG.

Agenda § § § Welcome / Overview US Do. D Transformation Context MIP Overview MIP Multinational Demonstration Next Steps - Leveraging MIP Questions/discussion National system presentation / demonstration at the individual workstations after the formal presentations and demonstration MIP: Multilateral Interoperability Programme 4

What this is NOT § A sales pitch for a specific technology or system § A system-centric approach (status quo) § A comparison of national systems, their strengths or weaknesses § A “Silver Bullet” to solve all US Joint interoperability issues § An endorsement or commitment by any US national entity to implement the capabilities you will see, but – within the MIP Community there are commitments between the national system developers regarding planned implementation actions – the C 2 Information Exchange Data Model (C 2 IEDM) that enables information interoperability in the demonstration has been approved by the US in the ratification process for C 2 interoperability under NATO Standardization 5 Agreement (STANAG) 5523.

What you will see today § Multinational information interoperability enabling operational and tactical C 2 capability, improved situational awareness and accelerated decision making § Concrete results from a successful, committed long-term multinational process of Warfighter consensus development and documentation within a Community of Interest § A way to address key aspects of Do. D’s Transformation Challenge – JBMC 2 mandate for C 2 Interoperability by 2008 – Information-centricity required by Do. D strategy and policy – Joint / Multinational / Interagency interoperability across the spectrum of homeland security and homeland defense The MIP process and products can be leveraged for critical information interoperability capability. . . a key transformation enabler for the GIG 6

Global Information Grid GIG will be implemented to provide rapid exploitation of diverse data sources, customized to meet specific Warfighter/mission demands. GIG Applications and Data Net-Centric Enterprise Services GIG IP-based Transport 9 Core Enterprise Services + APIs - Enterprise Systems Management - User Assist - Messaging - IA/Security - Discovery - Mediation - Storage Services - Collaboration - Application Transformational Communications System (TCS) Joint Tactical Radio System (JTRS) Global Information Grid –Bandwidth Expansion (GIG-BE) 7

Global Information Grid The Do. D Net-centric Data Strategy provides guidance about the importance of communities of interest for interoperability and GIG functionality. GIG Applications and Data Net-Centric Enterprise Services GIG IP-based Transport 9 Core Enterprise Services + APIs - Enterprise Systems Management - User Assist - Messaging - IA/Security - Discovery - Mediation - Storage Services Do. D Net-centric - Collaboration - Application Data Strategy Transformational Communications System (TCS) Joint Tactical Radio System (JTRS) Global Information Grid –Bandwidth Expansion (GIG-BE) 8

Global Information Grid C 2 IEDM captures the consensus of a multinational Warfighter Community of Interest. GIG Applications and Data Net-Centric Enterprise Services GIG IP-based Transport 9 Core Enterprise Services + APIs - Enterprise Systems Management - User Assist - Messaging - IA/Security - Discovery - Mediation - Storage Services Do. D Net-centric - Collaboration - Application Data Strategy Transformational Communications System (TCS) Joint Tactical Radio System (JTRS) Global Information Grid –Bandwidth Expansion (GIG-BE) C 2 Information Exchange Data Model: C 2 IEDM MIP 9

Multilateral Interoperability Programme (MIP) COL Stuart Whitehead TPIO- Battle Command Fort Leavenworth, KA Stuart. Whitehead@Leavenworth. Army. mil Mr. Paul Ulrich OPM Ground Combat C 2 Fort Monmouth, NJ Paul. Ulrich@US. Army. mil

MIP TOR • Aim: Achieve international interoperability of Command Control Information Systems (C 2 IS) at all levels: – corps to battalion, or lowest appropriate level – support multinational, combined and joint operations – advance digitization in the international arena including NATO • Scope: – War Ops, Crisis Response Ops, Defence Against Terrorism – Joint, Interagency, Multinational, Non-governmental Organizations – Tactical to Operational and Strategic levels 11

MIP Defined • What it is and what it provides: – Materiel / Combat developer forum to build consensus on how to achieve operational interoperability through information exchange • • Mature process, long-term roadmap Driven by national doctrine and requirements Consensus-based technical specification for national implementation System-independent capability based on information interoperability – Venue for international interoperability testing – Coordinates synchronization of materiel fielding plans • What it is not: – A cooperative development program: • No common funding • No single Program Manager • No common hardware or software development – Organization specific, e. g. , NATO, PFP, ABCA. . . Bottom Line: MIP is a functioning successful C 2 Community of Interest 12

Background QIP 1980 1995 1998 2002 … Long history of collaboration, cooperation, and synchronization 13

Organisation Members / Systems FULL MEMBERS ASSOCIATE MEMBERS CA LFC 2 IS AS JCCS, BCSS RO TBD DA DACCIS AU PHOENIX SI TBD FR SICF, SIR BE SICBEL SW GE HEROS-2/1 CZ GF-TCCS IS MARK SLB IT SIACCON FI TBD TU TKKBS NL ISIS GRHARCCIS NONORTa. C/NORCCIS HU HAVIR SP SIMACET LH ATac. CS/Com. BAT PL SZAFRAN US MCS (L) PO SICCE ACT Bi. SC AIS TBD UK AFNORTH TBD = To be determined 14

Organisation Block 2 MIP Steering Group (MSG) Programme Management Group (PMG) Operational Working Group (OWG) Systems Engineering & Architecture Working Group (SEAWG) Data Modelling Working Party (DMWP) Chair Vice Chair Test & Evaluation Working Group (TEWG) Configuration Control Working Group (CCWG) Chair Deputy Data and Procedural Working Group (DPWG) Technical Working Group (TWG) Multi-Disciplinary Working Parties (MDWPs) 15

Specification Development OWG Information Requirements Data Elements Information Exchange Rules MTIR - MIP Tactical C 2 IS Interoperability Requirements SEAWG Security Policies MSISP MIP System Interconnection Security Policy DPWG MIP Information Resource Dictionary (MIRD) Land C 2 Information Exchange Data Model (LC 2 IEDM) TWG Message Text Format Set (MTF) MIP Contracts MIOP – MIP Interface Operating Procedures Message Exchange Mechanism (MEM) Data Exchange Mechanism (DEM) MTIDP – MIP Technical Interface Design Plan 16

MIP Requirements Roadmap MIP has a long-term plan to deliver capability 17

Block Implementation Plan 01 Block I Analyze Bl 1 02 Design Bl 1 03 IOT&E 04 05 FOT&E 06 07 FOT&E 08 09 Test Bl 1 In-Service Block II Req cap Bl 2 Analyze Bl 2 Design Bl 2 Test Bl 2 In-Service Block III Req cap Bl 3 Analyze Bl 3 Design Bl 3 Test Bl 3 In-Service Today 18

Concept Effective C 2 for international operations Shared tactical picture Automated information exchange National Implementation MCI C 2 IEDM Commander Staff officer DEM MEM C 2 IEDM Common Information Model Staff officer Commander Collaboration Common understanding 19

20

MIP Solution Exchange Services INTERNATIONAL MIP SPECIFICATION (Lingua Franca) MCI LC 2 IEDM NATIONAL MCI LC 2 IEDM CCIS • • System-independent IER IP-based Comm DB-DB Replication Services C 2 Interface 21

IOT&E Objectives • Confirm the operational fieldability of the MEM in accordance with MTIR v. 1. 0 requirements. • Test and evaluate the operational fieldability of the DEM in accordance with the MTIR v. 1. 0. • Test and evaluate coexistence of MEM and DEM implementation of MIP Baseline 1. 0. MTIR = MIP Tactical C 2 IS Interoperability Requirements DEM = Data Exchange Mechanism, MEM = Message Exchange Mechanism 22

23

24

IOT&E Task Organization SHAPE XXX II PO II SP XX XX SP FR FR X X X X NL GE US CA IT UK NO DK 25

Operational Views • IOT&E Presentation of National Command Control Systems • Commander’s Displays (remote views) • Doctrine and Operational Rules set the default views 26

Selected IOT&E Tactical Operation Centers 27

28

Scenario MCS SICCE LFC 2 IS 29

Scenario (cont. ) MCS SICCE LFC 2 IS 30

Scenario (cont. ) MCS SICCE LFC 2 IS 31

Maritime Examples 32

Data Replication Concept MIP Common Interface National C 2 IS Nat. Comms. Nat. DB Ethernet LAN LC 2 IEDM II User Terminal En. Armored Bat in 30 TXM 200123 II PDU {101}A 05{206010001207770023|7|R 05{206010001207770…. User Terminal 33

MIP Block 1 – Information Exchange • Automated C 2 Interface Exchange Mechanism To Support Liaison – Shared Tactical Picture (Position Location) • 176 Information Categories – Exchange Of Orders/Graphics – Holdings/Status Information • e. g. , AD Weapons Control Status • e. g. , Running Status 34

35

36

MIP Path Forward • MIP has established a basic capability for exchange of SA data in Block 1 • MIP has a path forward based upon a defined set of functionality enhancements in a block implementation scheme • We’ve identified the need to define MIP Operating Procedures that need to be incorporated into national unit/TOC SOPs • We’ve begun to realize the impact on ways of doing business/culture • Need to investigate and plan for evolution in warfare in the information age 37

MIP Acceptance NATO Corporate Data Model Bi. SC AIS Land Functional Services NATO C 3 Technical Architecture NATO Force Goal MIP HRF(L) HQ Military Criteria NATO Standardisation Agreement NATO Policy National C 2 IS 38

US Efforts that Leverage MIP • GIG – J 6 I has identified C 2 IEDM / MIP as addressing Key Interface Profile #17 – Identified as applicable to User Defined Operational Picture (UDOP) COI • ABCS – Current US MIP implementation program is Maneuver Control System – Planned software reuse - other ABCS programs • ABCS MIP software can be leveraged by other Service programs • Army Future Combat Systems (FCS) – Coalition Interoperability Requirement. MIP FCS MOA in process. • Shared Tactical Ground Picture (STGP) – US, UK, FR, IT, GE, NO, and CA interoperability project • FIOP FY 04 program initiative – Single Integrated Ground Picture (SIGP) – Situational Awareness Data Interoperability (SADI) • DISA XML Registry: Coalition Namespace – Includes C 2 IEDM Interface Control Document – Authored by Institute for Defense Analysis 39

www. mip-site. org AT&L 40

What You Saw How it fits with the Do. D Vision § What you just saw was a multinational instantiation of information interoperability, coincidentally consistent with Do. D Data Strategy § Shared Warfighter Concepts and Vocabulary: – Net-centric Data Strategy approach to interoperability relies on COI consensus-based information definitions and governance for data and information management – The MIP work, and demonstrated multinational interoperability capability, are proof that we can achieve COI consensusbased information interoperability § Enterprise Services: – MIP has implemented a robust vocabulary and mechanism for Allied Warfighter information exchange – that will need to tie to the GIG – GIG information discovery, exchange, and mediation services, must support Warfighter C 2 concepts and vocabularies. – The MIP multinational C 2 COI standards provide a foundation for Joint capability. 41

Emerging Allied/Coalition Interface Multi-national / Interagency WAN Allies US Joint Core Consultation, Command Control Allies C 2 IEDM CENTRIXS • Core Consultation and C 2 COI • Country, Service, System, Application, Vendor - independent • Query & Replication Services supported over Network Comm • C 2 System Interface and/or Internal 42 DB

Joint Command Control (JC 2) Operational Concept Mission Capability Packages Situational Awareness Air & Space Ops Intelligence Force Projection Joint Fires JC 2 OV-1 Force Protection Force Readiness Core C 2 Services MIP Core C 2 Vocabulary: • Fire Support • IEW • ADA • CSS • Maneuver • A 2 C 2 • NBC • MP • Eng/Terrain • CMO • Weather • Signal • Enemy 43

Opportunities § Operationalize the Data Strategy! – Define, Organize and Govern the US C 2 COI • Create an ongoing Warfighter-led partnership with GIG services and systems developer communities • Leverage MIP processes, methodologies, and products – Embed C 2 COI standards as a component within all other Warfighting COIs § Accelerate achievement of the GIG vision – Next-generation US joint command control systems MUST interoperate with allied MIP-capable systems! – 77% of GWOT partners are MIP participants! § Near term US capability MIP “targets of opportunity”: – Leverage MIP success for JC 2 and CENTRIXS through Warfighter engagement in the COSMOS ACTD (FY 05) – COSMOS ACTD (PACOM sponsored) – DJC 2 coalition interoperability 44 – JC 2 Joint / Interagency / Multinational interoperability

Questions? Comments? Feedback? More Information at: www. mip-site. org 45

You are invited to interact with the National teams and presenters as your schedules allow. To view Speakers’ Notes: (1) Press escape key (2) Click View | Notes Page (3) Press <CTRL><HOME> to begin demo again 46