1. Multilateral Interoperability Programme Standard Brief 2012
September 2012
MIP © 2012
Unclassified
Page 1

2. Outline What is MIP MIP History MIP Vision MIP Scope What MIP is NOT
MIP Members
MIP Organisation
MIP Activities
Working Groups Overview
IPT3
IPT4
The future – MIP, NATO and NNEC
September 2012
MIP © 2012
Unclassified
Page 2

3. MIP is an interoperability organisation established:
What is MIP?
MIP is an interoperability organisation established:
by national C2IS system stakeholders
with expectations / requirements to share relevant C2 information in a multinational/coalition environment.
Stakeholders are the users, sponsors, developers, etc.
Users have expectations "to share and understand relevant C2 information...".
Systems have requirements "to share or exchange understandable relevant C2 information...".
Then the developers have the duty to deliver such systems and the operational users have the duty to operate them in a consistent way.
September 2012
MIP © 2012
Unclassified
Page 3

4. What is MIP? War Fighters define the Requirements ... THIS IS MIP 1 2
MIP Specification
Implementation by Nations
The War Fighter defines the Requirements definition
The requirements result in the MIP Specification
Nation/organisations implement nationally their MIP Specification → no MIP responsibility
Nation/organisations can exchange the C2-data via the national implemented Data Exchange Mechanism (DEM) → no MIP responsibility 3 3 3 3
Nat. DB
Nat. DB
Nat. DB
Nat. DB 4 4 4
Exchange of data between MIP compliant systems
September 2012
MIP © 2012 4
Unclassified
Page 4
Unclassified
Page 4

5. Services Working Group
History of MIP
History of information interoperability between C2I Systems …
1980
1990
2000
2010
Merging 2001
Merging 1998
QIP
The “Enhanced MIP” is the result of a long history of “merges”. Different initiatives in search for information interoperability between C2ISs have appeared along the last 20 years. Precursors of the current MIP are showed in this slide. QIP, BIP and ATCCIS are the foundations of MIP as it is known today. “Enhanced MIP” has inherited their background and experience.
Note: more detailed information about the MIP history you can find in the public area on the MIP web site:
Army Tactical Command and Control Information System (ATTCIS)
Formed in 1980
Land C2 Information and Exchange Data Model (LC2IEDM)
ATCCIS Replication Model (ARM)
Study project for data exchange
Battlefield Interoperability Programme for Lower Echelon Command and Control Systems (BIP)
Formed in 1995
Message oriented information exchange
Quadrilateral Interoperability Programme (QIP)
Formed in 1998
Multilateral Interoperability Programme (MIP)
Formed in 1998 in Calgary by Project Managers of CAN, DEU, FRA, GBR, ITA and USA.
NATO Date Administration Group (NDAG)
Memorandum of Agreement (MoA) in 2004 with MIP to combine all data modeling activities
Results in 2008 in Joint/Combined Consultation,Command & Control Information Exchange Data Model (JC3IEDM) as STANAG 5525
NDAG changed into Database Management System Working Group (DMSWG).
Agreement (MoA) 2004
NDAG
NATO Data
Administration Group
DMSWG
NATO Data Management
Services Working Group
September 2012
MIP © 2012 5 5
Unclassified
Page 5
Unclassified
Page 5

6. MIP Vision
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.
September 2012
MIP © 2012
Unclassified
Page 6

7. War Fighters Requirements
MIP Vision
Multinational Forum to promote international interoperability
War Fighters Requirements x x II II II II
September 2012
MIP © 2012 7
Unclassified
Page 7

8. MIP Scope
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.
September 2012
MIP © 2012
Unclassified
Page 8

9. What MIP is NOT
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, , chat, etc) to support C2
September 2012
MIP © 2012 9
Unclassified
Page 9

10. MIP Members FULL MEMBERS ASSOCIATE MEMBERS LCSS CAN BiSC-AIS-LC2IS ACT
JCCS, BCSS
AUS
PHOENIX
AUT
ISIS
BEL
GF-TCCS
CZE
FINACCIS
FIN
HARCCIS
GRC
FIS HE
CHE
EST BMS
EST
CAF
HRV
HEROS / FüInfoSys
DEU
TAVVIS
LTU
ARMY C2IS
DNK
SIMACET
ESP
LC4ISR
NZL
SICF
FRA
SZAFRAN /
C3IS Jasmine
POL
ComBAT
GBR
SICCE
PRT
SIACCON / C2I Difesa
ITA
ISIS
NLD
SIAAB
ROU
NORTaC/NORCCIS
NOR
The MIP programme is not a formal NATO programme. Rather it is a voluntary and independent activity by the participating nations and organizations. The nations and HQs that are active in the MIP programme are shown on the slide. Currently, the MIP consists of 12 Full Members (nations only) and 17 Associate Members (nation and non-nation entities).
Full Members:
Are nations that commit to support the collaborative development of succeeding versions of the MIP interoperability solution suitable for fielding. They must express intention to field that solution. Full Members have signed the MIP Statement of Intent (SOI) regarding their participation in MIP.
They undertake to be represented in PMG and IPT’s with at least 3 members and must be prepared to expend the resources required to develop and sustain the solution.
They must be involved in and contribute actively to the decision-making process throughout the specification and development cycle.
and have voting and access rights at all meetings.
Associate Members include nations and non-nation entities such as military agencies and formations, showing an interest in this programme. This status is granted by the MIP Steering Group (MSG). They enjoy all the rights and privileges of a Full Member, except they do not have any voting rights at meetings. Associate members do not need to support all MSG, PMG and WG meetings. They have to accept, of course, the terms of the Statement of Intent.
C2SYS
SVK
SWECCIS, SLB
SWE
ZAF
TACCIS
TUR
MCS
USA
* Country codes according NATO STANAG 1059 Ed 8.
September 2012
MIP © 2012
Unclassified
Page 10

11. MIP Organisation MSG PMG MIP IPT 3 MIP IPT 4 Unclassified Unclassified
MIP Steering Group
PMG
Project Management Group
MIP IPT 3
Integrated Product Team
MIP IPT 4
Integrated Product Team
A rough estimation is that MIP nations spend between $1-2M national effort per annum. There is no multilateral transfer of funds.
Currently, the MIP Structure is under revision as part of the MIP Campaign Plan and the MIP Programme Management Plan.
MIP Steering Group (MSG)
Its aim is to define the overall strategy for the Programme and make overall Programme Policy Decisions
Meets ones a year for three days (approximately 70 persons)
Project Management Group (PMG)
Its aim is to ensure that strategic goals and objectives of the MIP are achieved
MIP Integrated Product Team (IPT) 3:
Focused on the maintenance and sustainment of the fielded MIP Baselines (“in-Service Support”)
Reacts on ‘the feedback from the field’
MIP Integrated Product Team Future:
Meets the need of the stakeholders
operational view (C2, etc.)
semantic view (NATO DMSWG, etc)
Overcome limits of Baseline 3
Improve information management
Better tailored exchange
Be more responsive
Provide backward compatibility
September 2012
MIP © 2012
Unclassified
Page 11
Unclassified
Page 11 11

12. IPT 3 Overview Objective Purpose
Maintain and Sustain MIP Baselines 2.0 and 3.1 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
September 2012
MIP © 2012
Unclassified
Page 12

13. Designing the future MIP Baseline
IPT 4 Overview
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
September 2012
MIP © 2012
Unclassified
Page 13

14. MIP Activities SPECIFICATION TESTING CWIX Combined Endeavour DM Tests
Jan
Feb
March
Apr
May
June
July
Aug
Sept
Oct
Nov
Dec
MSG
(MSG)
Greding
Greding
Greding
Greding
SPECIFICATION
PMG
IPT 3
IPT 4
PMG
IPT 3
IPT 4
PMG
IPT 3
IPT 4
PMG
IPT 3
IPT 4
MIP Steering Group
Meets once a year
Project Management Group and IPT’s
Meet 4 times a year in Greding
Testing
Ad hoc in MIP community depending the development cycle
National MIP implementations test in international test events like Combined Endeavour (CE) and Coalition Warrior Interoperability eXercise-eXamine-eXperiment-eXplore (CWIX) x II
CWIX
(June) x II
Combined
Endeavour
(September)
Standards
DM Tests
(ad hoc)
TESTING
September 2012
MIP © 2012
Unclassified
Page 14
Unclassified
Page 14 14

15. MIP Products
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
Documents
Technical
Documents
Supporting
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.
STANAGs are NATO standardised agreements. STANAG 5525 establishes a common data model that NATO nations individually ratify and implement in their own C2IS.
[1]
September 2012
MIP © 2012
Unclassified
Page 15

16. Concept Data Exchange Mechanism
MIP Common Interface
National C2IS
National C2IS
Nat. Comms.
Nat. Comms.
Ethernet LAN
Nat. DB
Nat. DB
JC3IEDM
JC3IEDM
For the requirements of information exchange by pushing data, MIP has continued the development of the data exchange mechanism (DEM), as shown in the slide. II II
PDU
User Terminal
{101}A05{ |7|R05{ ….
User Terminal
En. Armoured Bn in 30TXM200123
En. Armoured Bn in 30TXM200123
September 2012
MIP © 2012
Unclassified
Page 16

17. NNEC Data Strategy Enabling Data & Information Services
Nat DB
Gateway
Data exchanged across Engineered, well-defined interfaces between known Users
Gateway
Nat DB
Publish/Subscribe of Information between known Systems
TODAY
NATO NETWORK ENABLED CAPABILITIES (NNEC)
Nat DB
Nat DB
Sharing of information in the Information sphere
Data & Services
The biggest change will be the change from the information exchange approach to the information sharing paradigm.
We will move from an information exchange from as we see today, where information is pushed from system to system, into a shared space, where it is possible to pull or subscribe to relevant information.
TOMORROW
Nat. System Publish Data in the Info Sphere
Metadata Registry
Discovery Catalogs
& Service Registry
Unanticipated Authorized User Pull Data from the Info Sphere
Nat DB
Shared Space 
September 2012
MIP © 2012
Unclassified
Page 17
Unclassified
Page 17

18. MIP, NATO & NNEC JC3IEDM JC3IEDM JC3IEDM MIP Exchange Mechanisms
Object Oriented
Data Model ?
Semantic Schema for Information Exchange
Semantic Schema for Information Exchange
Ontology
MIP Exchange
Mechanisms
(DEM & MEM)
Seen from a NATO perspective, this is the way I see the evolution of the data model and the exchange mechanisms.
The most stable standard is the JC3IEDM, which is XML enabled currently. Possibly, the model may be transformed into an object oriented model. The next stage will then be to move the data model towards the “JC3IEDM Ontology” – leading to more advanced and efficient decision making support.
NNEC will be based on the Service Oriented Architecture concept and JC3IEDM should be able to expose information in this environment.
Even JC3IEDM and the MIP solution are well appreciated, MIP has appointed Working Parties (MIP System and Architecture Design + Model Driven Architecture) to analyse and recommend the future development in MIP. NATO is supporting this initiative and sees it as a strong contribution to next level of information sharing and understanding.
XML Exchange
Service Oriented
Architecture ?
Web Services ??
TODAY
September 2012
MIP © 2012
Unclassified
Page 18
Unclassified
Page 18

19. Summary Organisation Specification National C2ISs Unclassified
MSG
PMG
IPT 3
IPT F
Common Information Exchange Requirements
(IERs)
Multinational Forum
to promote international interoperability
Organisation
MIP should be understood in the context of its 3 integrated components:
Organisation, as an international military data interoperability organisation that meets to define common information exchange requirements (IERs), which can be exchanged between different national C2IS.
Specifications since by delivering an assured capability for interoperability of information, MIP facilitates interoperability through defining and developing common technical standards and associated documentation. MIP intends to further develop and improve interoperability standards in order to support understanding in a common working environment.
National C2IS System development,
as a forum for national implementers to synchronise their MIP C2IS materiel fielding plans; and
as an organisation that assists in testing national C2IS in accordance with MIP specifications, which is focused on fielded solutions and iterative development.
Specification
National C2ISs
Nat DB
Nat DB
Nat DB
Standards
Nat DB
Nat DB
Development of common Standards
Tests of fielded Solutions
September 2012
MIP © 2012
Unclassified
Page 19
Unclassified
Page 19

20. MIP Website https://mipsite.lsec.dnd.ca/
You can access the MIP Website at which contains all the latest information relevant to MIP and all the baseline documentation. Access to certain areas is restricted to MIP members.
More details about the way of working in MIP you can find in the MIP Programme Management Plan (MPMP) on the MIP Website.
MIP Website
Open Area
Access to the official Documents
September 2012
MIP © 2012
Unclassified
Page 20
Unclassified
Page 20

21. Questions Unclassified Unclassified September 2012 MIP © 2012 Page 21