Transcript Slide 1

Multinational Information Interoperability
Leveraging Multinational Warfighter Consensus
for
US DoD Transformation
April 2004
Mr. Richard Lee
ADUSD (Interoperability and Network Centric Warfare)
ODUSD (Advanced Systems and Concepts)
703-695-7938
[email protected]
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 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
2
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.
– 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 NetCentric 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
3
Programme (MIP) to the GIG.
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
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 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
5
Agreement (STANAG) 5523.
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 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 . . .
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 DoD 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
DoD
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
C2IEDM 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
DoD
Net-centric
- Collaboration
- Application
Data Strategy
Transformational Communications System (TCS)
Joint Tactical Radio System (JTRS)
Global Information Grid –Bandwidth Expansion (GIG-BE)
C2 Information Exchange Data Model: C2IEDM
MIP
9
Multilateral Interoperability
Programme
(MIP)
COL Stuart Whitehead
TPIO- Battle Command
Fort Leavenworth, KA
[email protected]
Mr. Paul Ulrich
OPM Ground Combat C2
Fort Monmouth, NJ
[email protected]
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
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 C2 Community of Interest
12
Background
QIP
1980
1995
1998
2002 …
13
Long history of collaboration, cooperation, and synchronization
Organisation
Members / Systems
FULL MEMBERS
ASSOCIATE MEMBERS
CA
LFC2IS
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
GR
HARCCIS
NO
NORTaC/NORCCIS
HU
HAVIR
SP
SIMACET
LH
TBD
UK
ATacCS/ComBAT
PL
SZAFRAN
US
MCS (L)
PO
SICCE
AFNORTH
ACT BiSC AIS
TBD = To be determined
14
Organisation
Block 2
MIP
Steering Group
(MSG)
Chair
Vice Chair
Chair
Vice Chair
Programme
Management Group
(PMG)
Operational
Working Group
(OWG)
Systems Engineering
& Architecture
Working Group
(SEAWG)
Data Modelling
Working Party
(DMWP)
Test &
Evaluation
Working Group
(TEWG)
Configuration
Control
Working Group
(CCWG)
Chair
Deputy
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 C2IS
Interoperability
Requirements
SEAWG
Security Policies
MSISP MIP System
Interconnection
Security Policy
DPWG
MIP
Information
Resource
Dictionary
(MIRD)
Land C2
Information
Exchange
Data Model
(LC2IEDM)
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
03
IOT&E
04
05
FOT&E
06
07
FOT&E
08
09
Design
Bl 1
Test
Bl 1
Bl 1 In-Service
Block II
Req cap
Bl 2
Analyze
Bl 2
Design
Bl 2
Test
Bl 2
Bl 2 In-Service
Block III
Req cap
Bl 3
Analyze
Bl 3
Design
Bl 3
Test
Bl 3
Bl 3 In-Service
Today
18
Concept
Effective C2 for international operations
Shared tactical picture
Automated information
exchange
National
Implementation
MCI
MCI
C2IEDM
Commander
Staff
officer
DEM
MEM
C2IEDM
Common
Information Model
Staff
officer
Commander
Collaboration
Common understanding
19
20
MIP Solution Exchange Services
INTERNATIONAL
NATIONAL
NATIONAL
MIP SPECIFICATION
(Lingua Franca)
MCI
LC2IEDM
NATIONAL
MCI
LC2IEDM
CCIS
•
•
•
•
System-independent IER
IP-based Comm
DB-DB Replication Services
C2 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 C2IS Interoperability Requirements
DEM = Data Exchange Mechanism, MEM = Message Exchange Mechanism
22
23
24
IOT&E Task
Organization
SHAPE
XXX
II
PO
II
FR
SP
XX
XX
SP
FR
X
X
X
X
X
X
X
X
NL
GE
US
CA
IT
UK
NO
DK
25
Operational Views
• IOT&E Presentation of National Command and Control
Systems
• Commander’s Displays (remote views)
• Doctrine and Operational Rules set the default views
26
Selected IOT&E Tactical Operation Centers
28
Scenario
MCS
SICCE
LFC2IS
29
Scenario (cont.)
MCS
SICCE
LFC2IS
30
Scenario (cont.)
MCS
SICCE
LFC2IS
31
Maritime
Examples
32
Data Replication
Concept
MIP Common Interface
National C2IS
Nat.
Comms.
National C2IS
Nat.
Comms.
Nat. DB
Nat. DB
Ethernet LAN
LC2IEDM
LC2IEDM
II
User Terminal
En. Armored Bat in 30TXM200123
II
PDU
{101}A05{206010001207770023|7|R05{206010001207770….
User Terminal
33
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
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
BiSC AIS
Land Functional
Services
NATO C3
Technical
Architecture
NATO
Force Goal
MIP
HRF(L) HQ
Military Criteria
NATO
Standardisation
Agreement
NATO Policy
National C2IS
38
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
39
www.mip-site.org
AT&L
40
What You Saw
How 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 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 C2 concepts and vocabularies.
– The MIP multinational C2 COI standards provide a foundation
for Joint capability.
41
Emerging
Allied/Coalition Interface
Multi-national / Interagency WAN
Allies
US Joint
Core Consultation, Command and
Control
Allies
C2IEDM
C2IEDM
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 42
DB
Joint Command and Control (JC2)
Operational Concept
Mission Capability Packages
Situational Awareness
Air & Space Ops
Intelligence
Force
Projection
Joint Fires
JC2 OV-1
Force Protection
Force Readiness
Core C2 Services
MIP Core C2
Vocabulary:
• Fire Support
• IEW
• ADA
• CSS
• Maneuver
• A2C2
• NBC
• MP
• Eng/Terrain
• CMO
• Weather
• Signal
• Enemy
43
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
44
– JC2 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