Multilateral Interoperability Programme: Difference between revisions

Content deleted Content added
Monkbot (talk | contribs)
m top: Task 11: cs1|2 maint: multiple authors/editors fixes;
Reasons for establishing MIP: Removed an incorrect apostrophe (')
Tags: Mobile edit Mobile web edit
 
(30 intermediate revisions by 21 users not shown)
Line 1:
{{Short description|NATO-centred military coordination organization}}
{{ad|date=May 2015}}
{{Multiple issues|
{{refimprove|date=February 2016}}
{{adadvert|date=May 2015}}
[[File:Multilateral Interoperability Programme Logo.png|250px|right]]The '''Multilateral Interoperability Programme (MIP)''' is an effort to deliver an assured capability for interoperability of information to support multinational, combined and joint operations. The MIP goal is to support all levels from corps to battalion. MIP's focus is on [[command and control]] systems. MIP is a consortium of 29 [[NATO]] and Non-NATO nations that meet quarterly to define interoperability specifications for the exchange information between their national Command and Control systems. <ref>{{cite news|last1=Bistarkey|first1=Devon|title=Network interoperability key to common operating picture|url=http://www.army.mil/article/161317/Network_interoperability_key_to_common_operating_picture/|accessdate=2 March 2016|agency=US Army|date=January 22, 2016}}</ref><ref>{{cite book|author1=Babak Akhgar |author2=Gregory B. Saathoff |author3=Hamid R. Arabnia |author4=Richard Hill |author5=Andrew Staniforth |author6=Petra Saskia Bayerl |title=Application of Big Data for National Security|date=19 February 2015|publisher=Butterworth-Heinemann|isbn=9780128019733|url=https://books.google.com/?id=ZPOcBAAAQBAJ&pg=PA183&dq=Multilateral+Interoperability+Programme+(MIP)#v=onepage&q=Multilateral%20Interoperability%20Programme%20(MIP)&f=false}}</ref>
{{refimprovemore citations needed|date=February 2016}}
}}
 
[[File:Multilateral Interoperability Programme Logo.png|250px|right]]The '''Multilateral Interoperability Programme''' ('''MIP''') is an effort to deliver an assured capability for information interoperability to support multinational, combined and joint military operations. The goal of the Programm is to support all levels from corps to battalion and focuses on [[command and control]] (C2) systems. MIP is a consortium of 27 [[NATO]] and Non-NATO nations that meet quarterly to work on the next iteration of its Products. It has standing collaborations with the [[Allied Command Transformation|NATO Allied Command Transformation]] (ACT) and the [[European Defence Agency|European Defense Agency]] (EDA).<sup>[1][2]</sup>
==Overview==
The Multilateral Interoperability Programme referred to as MIP, is an interoperability organisation established by national Command and Control Information Systems (C2IS) developers with a requirement to share relevant Command and Control information in a multinational or coalition environment.
As a result of collaboration within the programme, MIP produces a set of specifications which when implemented by the nations, provide the required interoperability capability.
MIP provides a venue for system level interoperability testing of national MIP implementations as well as providing a forum for exchanging information relevant to national implementation and fielding plans to enable synchronization.
MIP is NOT empowered to direct how nations develop their own C2IS.
 
== Overview ==
'''MIP Vision:''' The vision for the Multilateral Interoperability Programme (MIP) is to become the principal operator-led multinational forum to promote international interoperability of Command and Control Information Systems (C2IS) at all levels of command.
The Multilateral Interoperability Programme referred to as MIP, is an interoperability standard consortium, established by national C2IS developers, with a requirement to share relevant C2 information in a multinational or coalition environment. As a result of collaboration within the programme, MIP produces a set of specifications which, when implemented by the nations, provide the required interoperability capability. MIP provides a venue for system level interoperability testing of national MIP implementations as well as providing a forum for exchanging information relevant to national implementation and fielding plans to enable synchronisation. MIP is NOT empowered to direct how nations develop their own C2IS.
 
[[NATO]] and MIP share a common interest in building, testing, verifying and improving information exchange Models and derived specifications.
'''MIP Mission:''' MIP is to further develop and improve interface specifications in order to reduce the interoperability gap between different C2IS.
 
== Reasons for establishing MIP ==
'''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 in future baselines.
Interoperability among allied armed forces is more important today, than it ever was. Warfare, and the need for timely information exchange between allies, has changed tremendously over the last 100 years. If technology, terminology and command structures are not harmonized, a joint force is neither able to act fast, nor as one unit.
 
To improve Interoperability alliances around the globe, such as [[NATO]], [[European Union|EU]] and [[United Nations|UN]], are continuously working on standardizing their command and control information systems. MIP works outside their bureaucratic frameworks to spearhead and test solutions. Many of MIP's efforts end up being covered by NATO in [[Standardization agreement|STANAG]]s.
The MIP meetings are held in [[Greding]], [[Bavaria]], [[Germany]].
 
== History ==
The [[NATO]] Data Administration Group (NDAG) cooperates with the MIP in building the [[JC3IEDM|Joint Consultation, Command and Control Information Exchange Data Model (JC3IEDM)]].
The need for Interoperability between command and control information systems became readily apparent toward the end of the 20th century. MIP as we know it today is the result of 3 separate C2 initiatives:
 
- Army Tactical Command and Control Information System (ATTCIS, 1980)
==C2IEDM==
The C2IEDM (the predecessor to the [[JC3IEDM]]), or '''Command and Control Information Exchange Data Model''', is a [[data model]] that is managed by the Multilateral Interoperability Programme (MIP). It originated with experts from various [[NATO]] partners and from the [[Partnership for Peace]] nations. This data model is in the process of being submitted to [[Object Management Group]] (OMG) for consideration as the standard for [[Information exchange]]. It falls under the shared operational picture exchange service.
 
- Battlefield Interoperability Programme for Lower Echelon Command and Control Systems (BIP, 1995)
==JC3IEDM==
The '''Joint Command, Control and Consultation Information Exchange Data Model''' is first and foremost an information exchange data model. The model can also serve as a coherent basis for other information exchange mechanisms, such as message formats, currently lacking a unified information structure. It is the most current evolution in a long line of data model as far back as the Generic Hub '''GH'''. '''JC3IEDM''' is intended to represent the core of the data identified for exchange across multiple functional areas and multiple views of the requirements. Toward that end, it lays down a common approach to describing the information to be exchanged in a command and control (C2) environment. The '''JC3IEDM''' has recently been updated to include [[Improvised explosive device|Improvised Explosive Devices (IED)]] and '''Irregular Actors (IA)'''.
 
- Quadrilateral Interoperability Programme (QIP, 1998)
==MIP Full and Associated Members==
 
The MIP was formed in 1998 by project managers of Canada, Germany, France, Great Britain, Italy and the US, as a merge between BIP and QIP. In 2004 it went on to combine all data modeling activities, including the ATTCIS. Among the successes of the MIP are the C2IEDM and the [[JC3IEDM#:~:text=JC3IEDM, or Joint Consultation, Command,and Control (C2) information.|JC3IEDM]]. Both are covered in [[Standardization agreement|NATO STANAG]] and both are predecessors to the MIM.
The active nations and HQs in the MIP programme are: [[Australia]], [[Austria]], [[Belgium]], [[Canada]], [[Croatia]], [[Czech Republic]], [[Denmark]], [[Estonia]], [[Finland]], [[France]], [[Germany]], [[Greece]], [[Italy]], [[Netherlands]], [[New Zealand]], [[Norway]], [[Poland]], [[Portugal]], [[Romania]], [[Slovak Republic]], [[Slovenia]], [[South Africa]], [[Spain]], [[Switzerland]], [[Turkey]], [[United Kingdom]], [[United States]] and [[Allied Command Transformation]] (ACT)
 
== Products ==
 
=== NATO STANAG 5523 (C2IEDM) ===
The '''Command and Control Information Exchange Data Model''' (C2IEDM, predecessor to the [[JC3IEDM]]) is a [[data model]] that is managed by the MIP. It originated with experts from various [[NATO]] partners and from the [[Partnership for Peace]] nations.
 
=== NATO STANAG 5525 (JC3IEDM) ===
The '''Joint Command, Control and Consultation Information Exchange Data Model''' ([[JC3IEDM#:~:text=JC3IEDM, or Joint Consultation, Command,and Control (C2) information.|JC3IEDM]]) is first and foremost an information exchange data model. The model can also serve as a coherent basis for other information exchange mechanisms, such as message formats, currently lacking a unified information structure. It supports data exchange over [[XML#:~:text=Extensible Markup Language (XML) is,-readable and machine-readable.|XML]] and is the most currentsuccessful evolution in a long line of data model as far back as the Generic Hub '''GH'''models. '''JC3IEDM''' is intended to represent the core of the data identified for exchange across multiple functional areas and multiple views of the requirements. Toward that end, it lays down a common approach to describing the information to be exchanged in a command and control (C2) environment. The '''JC3IEDM''' has recently been updated to include [[Improvised explosive device|Improvised Explosive Devices (IED)]] and '''Irregular Actors (IA)'''.
 
=== MIM - MIP Information Model ===
MIM is a reference model that provides the taxonomic and semantic foundation for information exchange in the C2 ___domain. The goal is to harmonize current information exchange concepts and create a common ontology tailored to the needs of joint/combined military operations. MIP has submitted a proposal to cover its information model in the [[Standardization agreement|STANAG]] 5643 to the NATO Digital Policy Committee (DPC) (formerly known as [[NC3O|C3 Board]]). MIM is the baseline for the MIP 4.4 Information Exchange Specification (MIP4.4-IES), which offers a service oriented architecture and expands on the data exchange capabilities of its predecessor JC3IEDM. Current Version of MIM is 5.2 which was released in July 2023.
 
=== MIP IES – MIP Information Exchange Specification ===
The IES is the actual product of MIP to be implemented in C2 systems. MIP 4.4 IES is the newest released Version (released in Oct 2023) and part of the Federated Mission Network (FMN) Spiral 4 and 5. Implementation guidance and Documentation is available through member nations. MIP 4.5 IES is scheduled to be released Sep 2025.
 
== MIP Members ==
'''The Full members are:'''<sup>[3]</sup>
 
[[France]], [[Germany]], the [[Netherlands]], [[Spain]], [[Turkey|Türkiye]], the [[United Kingdom]], the [[United States|United States of America]].
 
'''The Associated members are:'''
 
[[Canada]], [[Denmark]], [[Austria]], [[Belgium]], the [[Czech Republic]], [[Greece]], [[Hungary]], [[Lithuania]], [[Norway]], [[New Zealand]], [[Poland]], [[Romania]], [[Switzerland]], [[Ukraine]]<sup>[4]</sup> as well as [[Allied Command Transformation]].
 
Full members commit to support the collaborative development of MIP solutions (with at least 3 Persons) and must express intention to field those solutions.
 
Associated members can take part in the development process (with at least 1 Person) and fielding of MIP solutions, but have no voting rights at meetings.
 
==References==
Line 33 ⟶ 59:
 
==External links==
*[https://tide.act.nato.int/mediawiki/tidepedia/index.php/Multilateral_Interoperability_Programme]
*[https://mipsite.lsec.dnd.ca/ MIP Public Home (new site)]
*[https://www.mimworld.org/portal/projects/welcome/wiki/Welcome/ Website MIM]
 
{{authority control}}
 
[[Category:NATO standardisation]]