Multilateral Interoperability Programme
Multilateral
Interoperability
Programme
Standard Brief
2010
February 2011
MIP © 2011
1
Outline
Multilateral Interoperability Programme
•
•
•
•
•
•
•
•
•
What is MIP
MIP History
MIP Vision
MIP Scope
What MIP is NOT
MIP Members
MIP Organisation
MIP Activities
Working Groups Overview
– IPT3
– IPT Future
• The future – MIP, NATO and NNEC
February 2011
MIP © 2011
2
What is MIP?
Multilateral Interoperability Programme
MIP is an interoperability organisation
established:
• by national C2IS system stakeholders
• with expectations / requirements to
share relevant C2 information in a
multinational/coalition environment.
February 2011
MIP © 2011
3
What is MIP?
1
Multilateral Interoperability Programme
War Fighters define the Requirements ...
MIP Specification
2
THIS IS MIP
Implementation by Nations
3
3
Nat. DB
Nat. DB
4
3
3
Nat. DB
4
Nat. DB
4
Exchange of data between MIP compliant systems
February 2011
MIP © 2011
4
History of MIP
Multilateral Interoperability Programme
History of information interoperability between C2I Systems …
1980
1990
2000
2010
Merging
2001
Merging
1998
Agreement
(MoA) 2004
QIP
February 2011
NDAG
DMSWG
NATO Data
Administration Group
NATO Data Management
Services Working Group
MIP © 2011
5
MIP Vision
Multilateral Interoperability Programme
The vision for the Multilateral
Interoperability Programme (MIP) is to
become the principal war fighter-led
multinational forum to promote
international interoperability of
Command and Control Information
Systems (C2IS) at all levels of
command.
February 2011
MIP © 2011
6
MIP Vision
Multilateral Interoperability Programme
Multinational Forum to promote international interoperability
War Fighters Requirements
x
II
February 2011
x
II
II
MIP © 2011
II
7
MIP Scope
Multilateral Interoperability Programme
The MIP scope is to deliver a command
and control (C2) interoperability solution in
a net-centric environment focused initially
on the Land operational user in a Joint
environment, with a growing emphasis on
the requirements of Maritime and Air
communities and other Communities of
Interest (COI’s) in future baselines.
February 2011
MIP © 2011
8
What MIP is NOT
Multilateral Interoperability Programme
• MIP is not a formal NATO programme, however it is endorsed by NATO
- NATO ACT (Allied Command Transformation) participates as an Associate
Member
- NATO DMSWG cooperates to the MIP development
• MIP is not a ‘system’
− C2 systems need to build a MIP interface (often called a ‘MIP Gateway’) to
connect to other Coalition systems
− MIP defines the interface that the Gateway shall respect, not how the Gateway
shall be built
• MIP is not the complete interoperability solution
− Still require other communication interfaces (voice, email, chat, etc) to support C2
February 2011
MIP © 2011
9
MIP Members
Multilateral Interoperability Programme
FULL MEMBERS
CAN
LCSS
DEU
HEROS / FüInfoSys
DNK
ARMY C2IS
ESP
FRA
GBR
ASSOCIATE MEMBERS
ACT
BiSC-AIS-LC2IS
HRV
CAF
AUS
JCCS, BCSS
LTU
TAVVIS
SIMACET
AUT
PHOENIX
NZL
LC4ISR
SICF
ComBAT
BEL
ISIS
POL
SZAFRAN /
C3IS Jasmine
CHE
FIS HE
PRT
SICCE
CZE
GF-TCCS
ROU
SIAAB
EST
EST BMS
SVK
C2SYS
FIN
FINACCIS
SVN
SITAWARE
GRC
HARCCIS
ZAF
ITA
SIACCON / C2I Difesa
NLD
ISIS
NOR
NORTaC/NORCCIS
SWE
SWECCIS, SLB
TUR
TACCIS
USA
MCS
* Country codes according NATO STANAG 1059 Ed 8.
February 2011
MIP © 2011
10
MIP Organisation
Multilateral Interoperability Programme
MSG
MIP Steering Group
PMG
Project Management Group
MIP IPT 3
MIP IPT Future
Integrated Product Team
Integrated Product Team
February 2011
MIP © 2011
11
IPT 3 Overview
Multilateral Interoperability Programme
Objective
Maintain and Sustain MIP Baselines 2.0 and 3.0 and any further 3.X
Baselines
Purpose
• Provide support to the deployed MIP Implementations by capturing,
assessing, categorizing, prioritizing and acting upon feedback from
use:
– Deployed in Real World Operations
– MRE/MRX (Mission Rehearsal Ex - pre-deployment tests)
• Specific tests as preparation for certain operations/ big exercises
– FTX/CPX (Field Training Exercise/Command Post Exercise) - involve “staffs”
– Exercises/Tests/Demonstrations, e.g., CWIX, CE…
• Maintain relevance of the MIP specifications while implementations
are deployed
February 2011
MIP © 2011
12
IPT Future Overview
Multilateral Interoperability Programme
Objective
Designing the future MIP Baseline
• Future Solution Architecture
– Exploit advances in emerging technology
• Capability Requirements
– Operational
– Semantics
• Management Processes
– Task driven approach
• Coordination
– Identification of Work Packages
– Prioritisation of Packages
– De-confliction between Packages
• Initial Specification for a future product
February 2011
MIP © 2011
13
MIP Activities
Jan
Feb
March
Apr
Multilateral Interoperability Programme
May
June
July
TESTING
SPECIFICATION
MSG
IPT 3
Aug
Sept
Oct
Nov
Dec
(MSG)
Greding
Greding
Greding
Greding
PMG
PMG
PMG
PMG
IPT F
IPT 3
x
IPT 3
IPT F
Standards
CWIX
(June)
II
II
DM Tests
(ad hoc)
IPT F
x
Standards
II
II
IPT 3
IPT F
Combined
Endeavour
(September)
February 2011
MIP © 2011
14
MIP Products
Multilateral Interoperability Programme
Standards
The Joint Consultation, Command & Control Information Exchange Data
Model (JC3IEDM) promulgated by NATO as STANAG 5525 [1].
Standards
Standards
The programme’s Exchange Mechanism specifications and associated
procedures
Operational
Technical
Supporting
Documents
Documents
Documents
• Instructions on how to use the MIP
solution.
• Record of incorporated Information
Exchange Requirements.
• Guidance for nations and
Communities Of Interest (CoIs) on
how to implement the MIP
specification within the context of
their national C2IS.
• Procedures for testing the
MIP specification.
[1] STANAGs are NATO standardised agreements. STANAG 5525 establishes a common data model that NATO nations individually ratify and
implement in their own C2IS.
February 2011
MIP © 2011
15
Concept
Data Exchange Mechanism
Multilateral Interoperability Programme
MIP Common Interface
National C2IS
National C2IS
Nat. Comms.
Nat. Comms.
Ethernet LAN
Nat. DB
Nat. DB
JC3IEDM
JC3IEDM
II
II
PDU
User Terminal
{101}A05{206010001207770023|7|R05{206010001207770….
En. Armoured Bn in 30TXM200123
February 2011
User Terminal
En. Armoured Bn in 30TXM200123
MIP © 2011
16
NNEC Data Strategy
TODAY
Enabling Data & Information Services
Nat DB
Gateway
Multilateral Interoperability Programme
Data exchanged across
Engineered, well-defined
interfaces between known Users
Gateway
Nat DB
Publish/Subscribe
of Information
between known
Systems
NATO NETWORK ENABLED CAPABILITIES (NNEC)
Nat DB
Nat DB
Sharing of
information in the
Information sphere
TOMORROW
Data & Services
Nat. System
Publish Data in the
Info Sphere
Metadata Registry
Discovery Catalogs
& Service Registry
Nat DB
Unanticipated
Authorized User
Pull Data from the
Info Sphere
Shared Space
February 2011
MIP © 2011
17
MIP, NATO & NNEC
JC3IEDM
Semantic Schema for
Information Exchange
MIP Exchange
Mechanisms
Multilateral Interoperability Programme
JC3IEDM
Object Oriented
Data Model ?
Semantic Schema for
Information Exchange
Service Oriented
Architecture ?
XML Exchange
JC3IEDM
Ontology
Web Services
(DEM & MEM)
2007
20??
TODAY
February 2011
MIP © 2011
18
Summary
Multilateral Interoperability Programme
MSG
PMG
IPT 3
Multinational Forum
to promote international interoperability
IPT F
Common Information Exchange Requirements
(IERs)
Organisation
Specification
National C2ISs
Nat DB
Nat DB
Nat DB
Standards
Nat DB
Development of common Standards
February 2011
MIP © 2011
Nat DB
Tests of fielded Solutions
19
MIP Website
Open Area
Access to the official Documents
February 2011
Multilateral Interoperability Programme
MIP Website
https://mipsite.lsec.dnd.ca/
MIP © 2011
20
Questions
February 2011
Multilateral Interoperability Programme
MIP © 2011
21