Multinational Information Interoperability Leveraging Multinational Warfighter Consensus for US DoD Transformation April 2004

1
Multinational Information Interoperability
Leveraging Multinational Warfighter
ConsensusforUS DoD TransformationApril 2004
Mr. Richard Lee ADUSD (Interoperability and
Network Centric Warfare) ODUSD (Advanced Systems
and Concepts) 703-695-7938 richard.lee_at_osd.mil
2
Acknowledgements

• 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 C2 community
• DISA
• LtGen Raduege, Ms. Dawn Meyerriecks, Mr Bernal
  Allen and the staff of the Media Center for their
  assistance in making the demonstrations possible

3
Motivation

• 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.
• Todays 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.

4
Agenda

• Welcome / Overview
• US DoD 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
5
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 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.

6
What you will see today

• 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 DoDs
  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
. . . a key transformation enabler for the GIG
7
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
9 Core Enterprise Services APIs
- Enterprise Systems Management - Messaging
- Discovery - Mediation - Collaboration -
User Assist - IA/Security - Storage
Services - Application
GIG IP-based Transport
Transformational Communications System (TCS)
Joint Tactical Radio System (JTRS) Global
Information Grid Bandwidth Expansion (GIG-BE)
8
Global Information Grid
The DoD Net-centric Data Strategy provides
guidance about the importance of communities of
interest for interoperability and GIG
functionality.
GIG Applications and Data
DoD Net-centric Data Strategy
Net-Centric Enterprise Services
9 Core Enterprise Services APIs
- Enterprise Systems Management - Messaging
- Discovery - Mediation - Collaboration -
User Assist - IA/Security - Storage
Services - Application
GIG IP-based Transport
Transformational Communications System (TCS)
Joint Tactical Radio System (JTRS) Global
Information Grid Bandwidth Expansion (GIG-BE)
9
Global Information Grid
C2IEDM captures the consensus of a multinational
Warfighter Community of Interest.
GIG Applications and Data
DoD Net-centric Data Strategy
Net-Centric Enterprise Services
9 Core Enterprise Services APIs
- Enterprise Systems Management - Messaging
- Discovery - Mediation - Collaboration -
User Assist - IA/Security - Storage
Services - Application
GIG IP-based Transport
Transformational Communications System (TCS)
Joint Tactical Radio System (JTRS) Global
Information Grid Bandwidth Expansion (GIG-BE)
C2 Information Exchange Data Model C2IEDM
MIP
10
Multilateral Interoperability Programme(MIP)
COL Stuart Whitehead TPIO- Battle Command Fort
Leavenworth, KA Stuart.Whitehead_at_Leavenworth.Army.
mil
Mr. Paul Ulrich OPM Ground Combat C2 Fort
Monmouth, NJ Paul.Ulrich_at_US.Army.mil
11
MIP TOR

• 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
• Organization specific, e.g., NATO, PFP, ABCA . .
  .

Bottom Line MIP is a functioning successful C2
Community of Interest
13
Background
QIP
1980 1995 1998 2002
Long history of collaboration, cooperation, and
synchronization
14
OrganisationMembers / Systems

• FULL MEMBERS
• CA LFC2IS
• DA DACCIS
• FR SICF, SIR
• GE HEROS-2/1
• IT SIACCON
• NL ISIS
• NO NORTaC/NORCCIS
• SP SIMACET
• UK ATacCS/ComBAT
• US MCS (L)

ASSOCIATE MEMBERS AS JCCS, BCSS AU PHOENIX BE S
ICBEL CZ GF-TCCS FI TBD GR HARCCIS HU HAVIR LH
TBD PL SZAFRAN PO SICCE
RO TBD SI TBD SW IS MARK SLB TU TKKBS AFNORT
H ACT BiSC AIS
TBD To be determined
15
OrganisationBlock 2
MIP Steering Group (MSG)
Chair Vice Chair
Programme Management Group (PMG)
Chair Vice Chair
Operational Working Group (OWG)
Systems Engineering Architecture Working
Group (SEAWG)
Test Evaluation Working Group (TEWG)
Configuration Control Working Group (CCWG)
Data Modelling Working Party (DMWP)
Chair Deputy
Technical Working Group (TWG)
Data and Procedural Working Group (DPWG)
Chair Deputy
Multi-Disciplinary Working Parties (MDWPs)
16
SpecificationDevelopment
OWG
TWG
DPWG
Message Text Format Set (MTF)
Message Exchange Mechanism(MEM)
MIP Information Resource Dictionary(MIRD) Land
C2 Information Exchange Data Model (LC2IEDM)
Information RequirementsData Elements
Information Exchange Rules
DataExchangeMechanism(DEM)
MIP Contracts
MTIR - MIPTactical C2IS Interoperability Requirem
ents
MTIDP MIP Technical Interface Design Plan
MIOP MIP Interface Operating Procedures
SEAWG
Security Policies
MSISP MIP System Interconnection Security Policy
17
MIP RequirementsRoadmap
MIP has a long-term plan to deliver capability
18
Block Implementation Plan
IOTE
FOTE
FOTE
Analyze Bl 1
Block I
DesignBl 1
TestBl 1
Bl 1 In-Service
Req cap Bl 2
Block II
Analyze Bl 2
DesignBl 2
TestBl 2
Bl 2 In-Service
Req cap Bl 3
Block III
Analyze Bl 3
DesignBl 3
TestBl 3
Bl 3 In-Service
Today
19
Concept
Effective C2 for international operations
Shared tactical picture
Automated information exchange
National Implementation
MCI
MCI
Common Information Model
DEM MEM
Commander
Commander
Staff officer
Staff officer
Collaboration
Common understanding
20
(No Transcript)
21
MIP Solution -Exchange Services
INTERNATIONAL
NATIONAL
NATIONAL
MIP SPECIFICATION (Lingua Franca)
MCI
MCI
LC2IEDM
LC2IEDM
NATIONAL CCIS

• System-independent IER
• IP-based Comm
• DB-DB Replication Services
• C2 Interface

22
IOTE 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 C2IS Interoperability
Requirements DEM Data Exchange Mechanism, MEM
Message Exchange Mechanism
23
(No Transcript)
24
(No Transcript)
25
IOTE Task Organization
SHAPE
XXX
II
PO
II
FR
SP
XX
XX
FR
SP
X
X
X
X
X
X
X
X
UK
IT
CA
DK
US
NL
NO
GE
26
Operational Views

• IOTE Presentation of National Command and
  Control Systems
• Commanders Displays (remote views)
• Doctrine and Operational Rules set the default
  views

27
Selected IOTE Tactical Operation Centers
28
(No Transcript)
29
Scenario
30
Scenario (cont.)
31
Scenario (cont.)
32
Maritime Examples
33
Data Replication Concept
MIP Common Interface
National C2IS
National C2IS

Nat. DB
Nat. DB
Ethernet LAN
LC2IEDM
LC2IEDM
User Terminal
User Terminal
34
MIP Block 1 Information Exchange

• Automated C2 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

35
(No Transcript)
36
(No Transcript)
37
MIPPath 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
• Weve identified the need to define MIP Operating
  Procedures that need to be incorporated into
  national unit/TOC SOPs
• Weve begun to realize the impact on ways of
  doing business/culture
• Need to investigate and plan for evolution in
  warfare in the information age

38
MIP Acceptance
NATO Corporate Data Model
BiSC AIS Land Functional Services
NATO C3 Technical Architecture
NATO Force Goal
HRF(L) HQ Military Criteria
MIP
NATO Standardisation Agreement
NATO Policy
National C2IS
39
US Efforts that Leverage MIP

• 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
ATL
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.

42
Emerging Allied/Coalition Interface
Multi-national / Interagency WAN
Core Consultation, Command and Control
Allies
Allies
CENTRIXS

• Core Consultation and C2 COI
• Country, Service, System, Application, Vendor -
  independent
• Query Replication Services supported over
  Network Comm
• C2 System Interface and/or Internal DB

43
Joint Command and Control (JC2)Operational
Concept
Mission Capability Packages
Situational Awareness
Air Space Ops
Intelligence
Force Projection
Joint Fires
Force Protection
JC2 OV-1
Force Readiness
44
Opportunities

• Operationalize the Data Strategy!
• Define, Organize and Govern the US C2 COI
• Create an ongoing Warfighter-led partnership with
  GIG services and systems developer communities
• Leverage MIP processes, methodologies, and
  products
• Embed C2 COI standards as a component within all
  other Warfighting COIs
• Accelerate achievement of the GIG vision
• Next-generation US joint command and 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 JC2 and CENTRIXS through
  Warfighter engagement in the COSMOS ACTD (FY05)
• COSMOS ACTD (PACOM sponsored)
• DJC2 coalition interoperability
• JC2 Joint / Interagency / Multinational
  interoperability

45

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

46

• You are invited to interact with the National
  teams and presenters as your schedules allow.
• To view Speakers Notes
• Press escape key
• Click View Notes Page
• Press ltCTRLgtltHOMEgt to begin demo again