multilateral interoperability programme date: 8 dec 06 unclassified mip @ 1999-20071 mip standard...

Date: 8 Dec 06Unclassified

MIP @ 1999-2007 1

Multilateral Interoperability Programme

MIP Standard Briefing

8 Dec 2006www.mip-site.org

This Multilateral Interoperability Programme (MIP) Standard Briefing been reviewed and is hereby “Approved” by the Heads of Delegation of participating members. The information contained herein remains the property of the MIP Participants; as such, its release to nations or agencies, who are not themselves participants in the Multilateral

Interoperability Programme, including the media and general public is agreed however, unauthorised amendment of the information is not permitted. Use of MIP information, from this or any other MIP document, is entirely at the Users risk. Furthermore, if information contained within this document is used, appropriate acknowledgement to the MIP should

be made.

Unclassified MIP © 1999-2007 2

Multilateral Interoperability ProgrammeOutline

• Introduction• Aim• MIP Defined• The MIP Concept • MIP Baseline Phases & fielding plan• Organisation • Integrated Operational Test & Evaluation• MIP Specification Implementation, Adoption &

Stability• Summary of Programme.


Multilateral Interoperability ProgrammeIntroduction (1)

• Looking for a “Common Understanding” of the Battlespace.

• “Interoperability of information” is essential.

• Information across national and language boundaries.

• From tactical to operational and strategic levels.

• Interaction with NGO.


Multilateral Interoperability ProgrammeIntroduction (2)

• The “Shared Awareness” implies “Shared Information”.

• A common language.• AIM: Deliver an assured

capability for interoperability of information

• Combined joint operations• C2IEDM & JC3IEDM

(STANAG 5525).• Covers War, CRO and DAT.


Multilateral Interoperability ProgrammeAim

• “The aim of the Multilateral Interoperability Programme (MIP) is to achieve international interoperability of Command and Control Information Systems (C2IS) at all levels from corps to battalion, or lowest appropriate level, in order to support multinational (including NATO), combined and joint operations and the advancement of digitization in the international arena.”


Multilateral Interoperability ProgrammeMIP Defined (1)

• What it is and what it provides:

– Materiel / Combat developer forum.

– Mature Process. – Consensus-based Technical

Specs.– Venue for international

interoperability testing– Coordinates synchronization of

materiel fielding plans– System-independent capability

based on information interoperability


Multilateral Interoperability ProgrammeMIP Defined (2)

• What it is not:– A typical cooperative

development program:• No common funding• No single Program

Manager• No common hardware or

software development

– Organization specific, e.g., NATO, PFP, ABCA . . .



ConceptEnd-State

Effective C2 for international operationsEffective C2 for international operations

Shared Tactical Picture

NationalImplementation

(Nation A)

NationalImplementation

(Nation A)

NationalImplementation(Nation B)

NationalImplementation(Nation B)

AutomaticExchange Mechanism

CommonData

Model

CommonData

Model

StaffOfficers(Nation B)

StaffOfficers(Nation A)

Commander(Nation A)

Commander(Nation B)

COLLABORATION

COMMON UNDERSTANDING



NATIONAL A

NATIONAL

C2IS (A)

ODB

ConceptMIP Solution

MCIC2IEDMC2IEDM

NATIONAL

C2IS (B)

ODB

INTERNATIONALMIP SOLUTION(Lingua Franca)

NATIONAL B

Specifications

SOPsDocuments

(MIP)

MAPPING MAPPING



ConceptFoundationsNATIONAL A INTERNATIONAL

MCI

NATIONAL B

C2IEDMC2IEDM

C2IEDMC2IS (A)ODB

C2IEDM C2IS (B)ODB

C2IS (D)ODB

C2IS (C)ODB

NATIONAL C NATIONAL DMIP SOLUTION (Lingua Franca)

UNIQUE COMMON PICTURE

COMMON UNDERSTANDING



National C2IS(Nation B)

National C2IS(Nation B)

National C2IS(Nation A)

National C2IS(Nation A)

Concept MCI(co-located)

Router

Switch

MEM

DEM

Router

Switch

MEM

DEM

Implementation (A) Implementation (B)



ConceptSecurity

COMMS (Nation A)

COMMS (Nation A)

COMMS(Nation B)

COMMS(Nation B)

SECURE AREA

MCI(A)

Imple.(C)

Imple.

C2IS (A)C2IS (A) C2IS (C)C2IS (C)

COMMS (Nation C)COMMS (Nation C)

C2IS (B)C2IS (B)

Z Z

Z

‘Red’Area

‘Black’Runs

(B)

Imple.



National C2IS National C2IS

ConceptData Replication

C2IEDM C2IEDM

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

II II

Ethernet LAN

Nat. DB Nat. DB

PDU

En. Armored Bat in 30TXM200123

MIP Common Interface

Nat. Comms. Nat. Comms.



MIP BaselinePhases (1)

Y1 Y2 Y3 Y4 Y5

Inception

Elaboration

Construction

Integration

FO

CT

ran

siti

on

In service period

Baseline Release



MIP BaselinePhases (2)

1103 04 05 06 07 08 09 10

Baseline 3Inception

Elaboration

Construction

Integration FO

CT

ran

siti

on

In service period

Baseline Release

Baseline 4Inception

Elaboration

Construction

Integration FO

CT

ran

siti

on

In service p.

B4 Release

Today

Baseline 2Inception

Elaboration

Construction

Integration

FO

C

Tra

nsi

tio

n

In service period

Baseline Release



ConceptOp. Requirements• Hierarchy and Prioritisation.



ConceptC2IEDM

VERTICAL-DISTANCE

REFERENCE

GROUP-CHARACTERISTIC

COORDINATE-SYSTEM

AFFILIATION ADDRESS

ACTION

CONTEXT

OBJECT-ITEMOBJECT-TYPE LOCATION

REPORTING-DATA

RULE-OF-ENGAGEMENT

CAPABILITY

CANDIDATE-TARGET-LIST

• GH – LC2IEDM – C2IEDM – JC3IEDM

• Automated C2 Interface Exchange Mechanism To Support Liaison and Automation– Exchange Of Orders/Graphics– Holdings/Status Information

• e.g., AD Weapons Control & Running Status

• Operational exchange standards use a common vocabulary consisting of 176 information categories that include over 1500 content elements.

• Information Exchange Data Model• Serves as a Hub for functional areas• CRO & Joint IERs



Concept Baseline 1

NATO DEGREE 2.H INTEROPERABILITY

NATO LEVEL 5 INTERCONNECTIVITYNATO DEGREE 4.A INTEROPERABILITY

NATO LEVEL 4 INTERCONNECTIVITY

C2IEDM

C2IEDM

NATIONAL

C2IS (A)

ODB

C2IEDM

C2IEDM

NATIONAL

C2IS (A)

ODBMIP Agreed Standard for DEM

DATA EXCHANGEMECHANISM

MIP Agreed Standard for MEM

MESSAGE EXCHANGEMECHANISMMIP

MTFMIP MTF

Translation andformatting

mechanism


mechanism


mechanism


mechanism



Concept Baseline 2

NATO DEGREE 2.H INTEROPERABILITY

NATO LEVEL 5 INTERCONNECTIVITYNATO DEGREE 4.A INTEROPERABILITY

NATO LEVEL 4 INTERCONNECTIVITY

C2IEDM

NATIONAL

C2IS (A)

ODB C2IEDM

NATIONAL

C2IS (A)

ODBMIP Agreed Standard for DEM

DATA EXCHANGEMECHANISM


mechanism


mechanism

MIP Agreed Standard for MEM

MESSAGE EXCHANGEMECHANISM

eSMTP eSMTP

MTA MTAMMHS MMHS



ASSOCIATE MEMBERS

AUS JCCS, BCSS LTU TAVVIS

AUT PHOENIX POL SZAFRAN

BEL ISIS PRT SICCE

BUL FICIS ROU SIAAB

CZE GF-TCCS SVN SITAWARE

FIN FINACCIS SWE ISMARK,SLB

GRC HARCCIS ACT BiSC - AIS

HUN HAVIR JFC

FULL MEMBERS

CAN TacC2IS

DNK DACCIS

FRA SICF, SIR

DEU HEROS-2/1

ITA SIACCON

NLD ISIS

NOR NORTaC/

NORCCIS

ESP SIMACET

TUR TACCIS

GBR ATacCS/

ComBAT

USA MCS

OrganisationMembers

*Country codes according NATO STANAG 1059 Ed 8.



Enhanced MIP History

QIPQIP

1980 1990 2000

MERGING (SOI) 2001

MERGING 1998

NDAG: NATO Data Administration Group

NDAG

MoA 2004


Multilateral Interoperability ProgrammeOrganisation

MIP Steering Group(MSG)

Programme Management Group(PMG)

Systems Engineering& ArchitectureWorking Group

(SEAWG)

ConfigurationControl

Working Group

(CCWG)

NDAG

Data ModellingWorking Group

(DMWG)

Multi-Disciplinary Working Parties (MDWPs)

Chair

Deputy

OperationalWorking Group

(OWG)

Test & Evaluation

Working Group

(TEWG)

Chair Vice Chair

Chair Vice Chair


Multilateral Interoperability ProgrammeIOT&E

• Confirm the operational fieldability of the MEM and DEM in accordance with MTIR v. 1.0 requirements.

• EDE (NL), Sep ’03• 11 nations, 13 TOCs,

550 visitors, 394 participants.



IOT&E ORBAT and C2ISs

POSICCE

POSICCE

XXX

SPSIMACET

SPSIMACET

XXFR

SICF

FRSICF

XXSPSIMACET

SPSIMACET

IIFRSIR

FRSIR

II

DKDACCIS

DKDACCIS

XIT

SIACCON

ITSIACCON

XUK ATacCS

/ComBAT

UK ATacCS/ComBAT

XNO

NACCIS

NONACCIS

XXGE

Heros

GEHeros

NLISISNL

ISIS

XUS

MCS

USMCS

XCA

LFCSCA

LFCS

X

SHAPELCCIS

SHAPELCCIS

National Link

MEM & DEMMEM & DEM

DEMDEM


Multilateral Interoperability ProgrammeIOT&E Findings

• The MIP Interface performed well and supported the exchange of data necessary to establish the COP

• Emerging results indicate further development is required in certain areas

• Current implementations are planned for use in future exercises and can provide an initial operational capability if required.



SpecificationSchedule

• Dec 2003 - Release of the MIP Baseline 1

• Feb 2004 - MOA with NDAG

• Oct 2004 - Baseline 2 Tests start

• Oct 2005. Feb & April 2006 - Operational Level Test & Assessment

• Dec 2006 - Release of the MIP Baseline 2



MIP Adoption & Stability

National C2ISNational C2IS

NATOCorporate Data Model

NATOCorporate Data Model

NATO Force Goal

NATO Force Goal

NATO Standardisation

Agreement

NATO Standardisation

Agreement

BiSC AISLand Functional

Services

BiSC AISLand Functional

Services

NATOC3 TechnicalArchitecture

NATOC3 TechnicalArchitecture

NATO PolicyNATO Policy

HRF(L) / NRFHRF(L) / NRF


Multilateral Interoperability ProgrammeSummary

• Firm Foundations– Proven Concept

• NATO Buy-in (NDAG MoA)• National Commitment Clear Roadmap to the Future• Return of investment by:

– Manageability– Legacy-tolerant– Evolutionary– Standard


Multilateral Interoperability ProgrammeMIP Website

www.mip-site.org

multilateral interoperability programme date: 8 dec 06 unclassified mip @ 1999-20071 mip standard...

Documents

mip information

mip participants

mip document

unclassified mip

shared information

outline introduction

common language

common hardware