Multinational Information Interoperability Leveraging Multinational Warfighter Consensus for US DoD Transformation April 2004 . Richard Lee USD (Interoperability and Network Centric Warfare) USD (Advanced Systems and Concepts) 3-695-7938 [email protected]
46
Embed
Multinational Information Interoperability Leveraging Multinational Warfighter Consensus for US DoD Transformation April 2004 Mr. Richard Lee ADUSD (Interoperability.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Multinational Information Interoperability
Leveraging Multinational Warfighter Consensusfor
US DoD Transformation
April 2004
Mr. Richard LeeADUSD (Interoperability and Network Centric Warfare)ODUSD (Advanced Systems and Concepts) [email protected]
Purpose: – The DoD 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 C2 Community of Interest.
– We will demonstrate information interoperability between national C2 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 DoD 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 DoD net-centric transformation by applying the processes and products of the Multilateral Interoperability Programme (MIP) to the GIG.
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 C2 Information Exchange Data Model (C2IEDM) that enables information interoperability in the demonstration has been approved by the US in the ratification process for C2 interoperability under NATO Standardization Agreement (STANAG) 5523.
Multinational information interoperability enabling operational and tactical C2 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 DoD’s Transformation Challenge– JBMC2 mandate for C2 Interoperability by 2008– Information-centricity required by DoD 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 . . .
• Aim: Achieve international interoperability of Command and Control Information Systems (C2IS) 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
12
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
• GIG– J6I has identified C2IEDM / 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 FY04 program initiative– Single Integrated Ground Picture (SIGP)– Situational Awareness Data Interoperability (SADI)
• DISA XML Registry: Coalition Namespace– Includes C2IEDM Interface Control Document– Authored by Institute for Defense Analysis
40
www.mip-site.org
AT&L
41
What You SawHow it fits with the DoD Vision
What you just saw was a multinational instantiation of information interoperability, coincidentally consistent with DoD 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 consensus-based 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 C2 concepts and vocabularies.
– The MIP multinational C2 COI standards provide a foundation for Joint capability.