Last updated on 9th October 2008
© 2005-2008 MIP
You
are the visitor number
| Home | History | Organization | Documents | Contact |
You are at:
Best
viewed at
1024 *
768
|
Interoperability |
|
|
|
|
|
|
|
MIP & NATO |
|
|
|
|
|
|
|
|
|
|
|
|
|
MIP Integrated Operational Test & Evaluation (Sep 03) |
Interoperability
of information is essential and an assured capability for this is
vital. The successful execution of fast moving operations
needs an accelerated decision-action cycle, increased tempo of
operations, and the ability to conduct operations simultaneously
within combined/multinational formations. That is
precisely what MIP is working for.
NATO
Force Goals (EL2802, Land & ER2802, Marine Forces)
calls for the implementation of the MIP
solution by NATO Nations.
Site Map
|
|
|
|
|
|
|
|
|
|
 |
|
|
|
Download here |
|
Contact the |
What is MIP about ?
The purpose of MIP is summarized in few words: The MIP Aim which reads as follows:
"The aim of the 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, combined and joint operations and the advancement of digitization in the international arena".
MIP goes after interoperability and its solutions lies over two fundamental pieces: The Data Model and the Exchange Mechanism. Get into details through the following sections.
Common Interface.
The Exchange Data Model.
Exchange Mechanism.
How the information exchange takes place.
Interoperability.
MIP and the levels of interoperability.
The common interface is actually defined by a Data Model and comes from the analysis of a wide spectrum of allied information exchange requirements (IERs).
Among its features the most remarkable are:
|
|
It models the information that allied component commanders need to exchange (both vertically and horizontally). | |
|
|
It serves as the common interface specification for the exchange of essential battlespace information. |
System developers incorporate the MIP specification and include a single interface to it. Thereafter no further interfaces are required to interoperate with any other MIP enabled system. The function, implementation and display of the host C2 application is not the concern of MIP.
Initially the DM was completely focus on Land Requirements and the first MIP Baseline of such a Model was called "Land C2 Information Exchange Data Model" (LC2IEDM). In Baseline 2, MIP widened the perspective and started the way to make it Joint. The "L" dropped off its name and it became the "C2 Information Exchange Data Model" (C2IEDM).
But the true step towards jointness roots into the MIP-NDAG agreement to develop the JC3IEDM. The newly added "J" stands for "Joint" precisely. This is the Data Model under development for the Baseline 3 which first version, 3.1, is already available for the public (see documents page). It becomes also NATO STANAG, the 5525, currently under ratification process.
Once the common interface is agreed, a "conveyor" is required to move the data from one physical implementation of the Data Model to the partner one. During MIP Block 1 two different means were designed and implemented for achieving this particular purpose:
|
|
The Message Exchange Mechanism (MEM) consists of a suite of formatted messages that conform to AdatP-3 Part 1 plus procedural guidelines for their use. | |
|
|
The Data Exchange Mechanism (DEM) is an automatic data push mechanism that co-exists with the MEM. When a C2 application changes the state of information that it holds, and which is recognised by the DEM, this information is automatically replicated to all other co-operating systems that have agreed to exchange it. The specification allows users to decide what information, to whom it flows, when and over what communication medium. |
With both exchange mechanisms the meaning and context of the information is preserved and requires no additional processing on receipt to make it useful.
The two mechanism have evolved along the time through out Block 2. DEM has won some more pre-eminence while MEM lost much of it.
Now, as MIP starts Baseline 3, some new avenues align ahead in the shape of emerging technologies that can help make more effective and agile the information exchange. XML is one among them and MIP is currently exploring the possibilities it offers for the improvement of the MIP Exchange Mechanism.
The MIP specifications is a powerful interoperability tools. It enables interoperability at Degree 4.a (DEM) and 2.h (MEM) and functions at NATO Level 5 of System Interconnection.
The Baseline 2 is the product of the MIP Block 2. It has been finished at the end of WG-20 (29th September 2006) and has been released officially at the end of last year (2006). Visit our "Baseline 2" page (History) for additional information about. Nations have already completed the implementation of the MIP Baseline 2 solution into their national C2ISs and after a transition period, will be ready to field such implementations in Coalition exercises or operations. This is know in the MIP Community as "In Service Period" and lasts for two years, until the next Baseline is released and ready to go.
Baseline 3 development is currently under way. The concept continues being very similar although there are many more new operational requirements incorporated, among which a good portion are joint. Baseline 3 will be released mid 2009.
What is MIP about ?
Common Interface.
Exchange Mechanism.
Interoperability.
You are at:
Best
viewed at
1024 *
768
| Home | History | Organization | Documents | Contact |
| Miscellaneous |
Last updated on 9th October 2008
© 2005-2008 MIP
You
are the visitor number