multilateral interoperability programme july 2013mip © 2013-20141 multilateral interoperability...

Multilateral Interoperability Programme

July 2013 MIP © 2013-2014 1

Multilateral Interoperability

Programme

Standard Brief


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

July 2013 MIP © 2013-2014


3

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.

July 2013 MIP © 2013-2014


44

What is MIP?

Nat. DB Nat. DB Nat. DB Nat. DB

1

3 3 3 3

4 4 4

2 MIP Specification

Implementation by Nations

Exchange of data between MIP compliant systems

THIS IS MIP

The War Fighter defines the Requirements ...

July 2013 MIP © 2013-2014


55

1980 1990 2000 2010

QIP

5

Merging1998

Merging2001

Agreement(MoA) 2004

Agreement(MoA) 2004

NDAGNATO Data

Administration Group

DMSWGNATO Data ManagementServices Working Group

History of information interoperability between C2I Systems …

History of MIP

July 2013 MIP © 2013-2014


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.

July 2013 MIP © 2013-2014


77

II II II II

x x

Warfighter RequirementsWarfighter Requirements

MIP Vision

Multinational Forum to promote international interoperability

July 2013 MIP © 2013-2014


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 (COIs) in future baselines.

July 2013 MIP © 2013-2014


99

• MIP is not a formal NATO programme, however it is endorsed by NATO- NATO ACT (Allied Command Transformation) participates as an Associate

Member

• 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

What MIP is NOT

July 2013 MIP © 2013-2014


10

FULL MEMBERS

LCSSCAN

ARMY C2ISDNK

SICFFRA

HEROS / FüInfoSysDEU

SIACCON / C2I DifesaITA

ISISNLD

NORTaC/NORCCISNOR

SIMACETESP

TACCISTUR

ComBATGBR

MCSUSA

SWECCIS, SLBSWE

* Country codes according NATO STANAG 1059 Ed 8.

MIP Members

ASSOCIATE MEMBERS

BiSC-AIS-LC2ISACT

JCCS, BCSSAUS

PHOENIXAUT

ISISBEL

GF-TCCSCZE

FINACCISFIN

HARCCISGRC

FIS HECHE

EST BMSEST

July 2013 MIP © 2013-2014

TAVVISLTU

SZAFRAN / C3IS JasminePOL

SICCEPRT

SIAABROU

C2SYSSVK

LC4ISRNZL

ZAF

SITAWARESVN


11

MIP Organisation

MSGMIP Steering Group

PMGProject Management Group

MIP IPT 4Integrated Product Team

MIP IPT 3Integrated Product Team

July 2013 MIP © 2013-2014


12

ObjectiveMaintain and Sustain MIP Baseline 3.1

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

IPT 3 Overview

July 2013 MIP © 2013-2014


13

ObjectiveDesigning the future MIP Baseline

• Optimized (and simplified) Architecture– Separates Information structures from mechanics of information exchange

• Capability-based Approach– Rigorous process for transformation of requirements into specifications– Automated specification generation process

• Modular Specification– Composed of discrete Capability Packages that can be implemented

independently– Use a common Reference Model to maintain alignment between Packages

• Inter-Version Compatibility– Seeks to address a core constraint of the MIP3.1 solution

IPT 4 Overview

July 2013 MIP © 2013-2014


14

MIP Activities

Jan Feb March Apr May June July Aug Sept Oct Nov Dec

Greding

PMG

IPT 3 IPT 4

PMG

IPT 3 IPT 4

PMG

IPT 3 IPT 4

PMG

IPT 3 IPT 4

MSG

Greding Greding Greding

x

II II

CombinedEndeavour

(September)

Standards Standards

MIP Specifications Tests(ad hoc)

TE

ST

ING

SP

EC

IFIC

AT

ION

x

II II

CWIX(June)

July 2013 MIP © 2013-2014


15

MIP Products

STANAGs are NATO standardised agreements. STANAG 5525 establishes a common data model that NATO nations individually ratify and implement in their own C2IS.

[1]

The Joint Consultation, Command & Control Information Exchange Data Model (JC3IEDM) promulgated by NATO as STANAG 5525 [1].

Standards

The programme’s Exchange Mechanism specifications and associated procedures

OperationalDocuments

Standards Standards

TechnicalDocuments

SupportingDocuments

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

July 2013 MIP © 2013-2014


16

National C2IS National C2IS

ConceptData Exchange Mechanism

JC3IEDM JC3IEDM

{101}A05{206010001207770023|7|R05{206010001207770….User Terminal User TerminalEn. Armoured Bn in 30TXM200123

II II

Ethernet LAN

Nat. DB Nat. DB

PDU

En. Armoured Bn in 30TXM200123

MIP Common Interface

Nat. Comms. Nat. Comms.

July 2013 MIP © 2013-2014


17

NNEC Data StrategyEnabling Data & Information Services

TO

DA

YT

OM

OR

RO

W

Shared Space

Nat DB Gateway Nat DBGatewayData exchanged across Engineered, well-defined

interfaces between known Systems

Nat DB Nat DB

Publish/Subscribe of Information between known Systems

Sharing in the Information Sphere

Nat DB

Data & Services

Discovery Catalogs& Service Registry

Metadata Registry

National Systems Publish Data in the Information Sphere

Unanticipated Authorized Users Pull Data from the Information Sphere

NATO NETWORK ENABLED CAPABILITIES (NNEC)

July 2013 MIP © 2013-2014


18

MIP, NATO & NNEC

2007 20??

Semantic Schema for Information Exchange

JC3IEDMSemantic Schema for Information Exchange

JC3IEDMOntology

MIP Data Exchange

Mechanism(DEM)

XML Exchange Web Services

TODAY

Service OrientedArchitecture ?

Object OrientedData Model ?

JC3IEDM

July 2013 MIP © 2013-2014


19

Summary

Multinational Forumto promote international interoperability

PMG

IPT 3 IPT F

Standards

MSG

Common Information Exchange Requirements(IERs)

Organisation

Specification

Development of common Standards

National C2ISs

Nat DB Nat DB Nat DB

Nat DB Nat DB

Tests of fielded Solutions

July 2013 MIP © 2013-2014


20

MIP Websitehttps://mipsite.lsec.dnd.ca/

Open AreaAccess to the official Documents

MIP Website

July 2013 MIP © 2013-2014

https://mipsite.lsec.dnd.ca/

multilateral interoperability programme july 2013mip © 2013-20141 multilateral interoperability...

Documents

mip gateway

mip interface

mip compliant systems

coalition systems mip

future mip baseline

deployed mip implementations

associate member mip

c2i systems history