Presentation is loading. Please wait.

Presentation is loading. Please wait.

Multilateral Interoperability Programme September 2012MIP © 20121 Multilateral Interoperability Programme Standard Brief 2012.

Similar presentations


Presentation on theme: "Multilateral Interoperability Programme September 2012MIP © 20121 Multilateral Interoperability Programme Standard Brief 2012."— Presentation transcript:

1 Multilateral Interoperability Programme September 2012MIP © Multilateral Interoperability Programme Standard Brief 2012

2 Multilateral Interoperability Programme September 2012MIP © 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

3 Multilateral Interoperability Programme September 2012MIP © 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.

4 Multilateral Interoperability Programme September 2012MIP © What is MIP? Nat. DB MIP Specification Implementation by Nations Exchange of data between MIP compliant systems THIS IS MIP War Fighters define the Requirements...

5 Multilateral Interoperability Programme September 2012MIP © QIP 5 Merging 1998 Merging 2001 Agreement (MoA) 2004 NDAG NATO Data Administration Group DMSWG NATO Data Management Services Working Group History of information interoperability between C2I Systems … History of MIP

6 Multilateral Interoperability Programme September 2012MIP © 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.

7 Multilateral Interoperability Programme September 2012MIP © II xx War Fighters Requirements MIP Vision Multinational Forum to promote international interoperability

8 Multilateral Interoperability Programme September 2012MIP © 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.

9 Multilateral Interoperability Programme September 2012MIP © 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 What MIP is NOT

10 Multilateral Interoperability Programme September 2012MIP © FULL MEMBERS LCSSCAN ARMY C2ISDNK SICFFRA HEROS / FüInfoSysDEU SIACCON / C2I Difesa ITA ISISNLD NORTaC/NORCCISNOR SIMACETESP TACCISTUR ComBATGBR MCSUSA SWECCIS, SLBSWE * Country codes according NATO STANAG 1059 Ed 8. MIP Members ASSOCIATE MEMBERS CAFHRV TAVVISLTU SZAFRAN / C3IS Jasmine POL SICCEPRT SIAABROU C2SYSSVK LC4ISR NZL ZAF BiSC-AIS-LC2ISACT JCCS, BCSSAUS PHOENIXAUT ISISBEL GF-TCCSCZE FINACCISFIN HARCCISGRC FIS HECHE EST BMSEST

11 Multilateral Interoperability Programme September 2012MIP © MIP OrganisationMSG MIP Steering GroupMSG PMG Project Management Group MIP IPT 4 Integrated Product Team MIP IPT 4 Integrated Product Team MIP IPT 3 Integrated Product Team MIP IPT 3 Integrated Product Team

12 Multilateral Interoperability Programme September 2012MIP © Objective Maintain and Sustain MIP Baselines 2.0 and 3.1 and any further 3.X BaselinesPurpose 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

13 Multilateral Interoperability Programme September 2012MIP © 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 IPT 4 Overview

14 Multilateral Interoperability Programme September 2012MIP © MIP Activities JanFebMarchAprMayJuneJulyAugSeptOctNovDec Greding PMG IPT 3 IPT 4 PMG IPT 3 IPT 4 PMG IPT 3 IPT 4 PMG IPT 3 IPT 4 MSG (MSG) Greding x II Combined Endeavour (September) Standards DM Tests (ad hoc) TESTING SPECIFICATION x II CWIX (June)

15 Multilateral Interoperability Programme September 2012MIP © 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]. [1] Standards The programme’s Exchange Mechanism specifications and associated procedures Operational Documents Standards 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.

16 Multilateral Interoperability Programme September 2012MIP © National C2IS Concept Data Exchange Mechanism JC3IEDM {101}A05{ |7|R05{ …. User Terminal En. Armoured Bn in 30TXM II Ethernet LAN Nat. DB PDU En. Armoured Bn in 30TXM MIP Common Interface Nat. Comms.

17 Multilateral Interoperability Programme September 2012MIP © NNEC Data Strategy Enabling Data & Information Services TODAY TOMORROW Shared Space Nat DB Gateway Nat DB Gateway Data exchanged across Engineered, well-defined interfaces between known Users Nat DB Publish/Subscribe of Information between known Systems Sharing of information in the Information sphere Nat DB Data & Services Discovery Catalogs & Service Registry Metadata Registry Nat. System Publish Data in the Info Sphere Unanticipated Authorized User Pull Data from the Info Sphere NATO NETWORK ENABLED CAPABILITIES (NNEC)

18 Multilateral Interoperability Programme September 2012MIP © MIP, NATO & NNEC ?? Semantic Schema for Information Exchange JC3IEDM Semantic Schema for Information Exchange JC3IEDM Ontology MIP Exchange Mechanisms (DEM & MEM) XML ExchangeWeb Services TODAY Service Oriented Architecture ? Object Oriented Data Model ? JC3IEDM

19 Multilateral Interoperability Programme September 2012MIP © Summary Multinational Forum to 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 Tests of fielded Solutions

20 Multilateral Interoperability Programme September 2012MIP © MIP Website https://mipsite.lsec.dnd.ca/ https://mipsite.lsec.dnd.ca/ Open Area Access to the official Documents MIP Website

21 Multilateral Interoperability Programme September 2012MIP © Questions


Download ppt "Multilateral Interoperability Programme September 2012MIP © 20121 Multilateral Interoperability Programme Standard Brief 2012."

Similar presentations


Ads by Google