Center for Army Lessons Learned - Thesaurus
CALL title banner

Multilateral Interoperability Programme

Definition/Scope: The first version of Multilateral Interoperability Programme (MIP) was established in 1998 by the Project Managers of the Army Command and Control Systems of Canada, France, Germany, Italy, the United Kingdom and the United States to replace and enhance two previous programs: Battlefield Interoperability Program (BIP) and Quadrilateral Interoperability Program (QIP). Its objectives were: through the Message Exchange Mechanism (MEM), to have improved structured message (ADatP3) capabilities supporting vertical and horizontal interoperability of C2ISs at all levels from Corps to Battalion, or lowest appropriate echelon which would be fielded by 2003 and Through the Data Exchange Mechanism (DEM), to have a (push) data capability supporting vertical and horizontal interoperability of C2ISs at all levels from Corps to Battalion, or lowest appropriate echelon, and is able to co-exist with the agreed common message capability, with an initial fielding during the period 2003-2005. In October 2001, the ATCCIS and MIP members Nations decided to merge the two programs in order to prevent divergences, to save resources and to foster C3 interoperability in a broader arena. The ATCCIS ethos was passed to the merged program (the MIP name had been retained) and MIP has taken the responsibility of keeping and further developing the specifications that had been produced by ATCCIS. The MIP specification is a managed interface between C2 information systems. When incorporated into a system it enables interoperability of information between any other system that also incorporates the specification. Battle-space data is transferred as information. The meaning and context of the information is preserved across national boundaries precisely and without any ambiguity. The information exchange requirements that MIP inherited from ATCCIS encompasses the spectrum of joint and combined land operations. Thus MIP meets the requirements of the Land Component Commander of Allied Joint Combined Operations (including Article 5 and Crisis Response Operations). Systems may be wholly different from each other and need not necessarily conform to any hardware or software standard. Typically systems will be acquired through national or NATO acquisition program and their architecture will conform to the National or NATO policy prevailing at the time. In a Community of MIP enabled C2 systems Nations, command levels and organizations can share: situational awareness, orders, plans and intentions, capabilities and status of friendly and enemy forces.



Narrower Terms:

Command and Control
contemporary operating environment
Field Artillery and Fire Support Data Interoperability
MIP Communications and Liaison Plan
situational awareness

CALL Homepage >> Thesaurus Last Updated: Sept 17, 2008