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.
MIP focuses on interoperability of command and control (C2) systems, which includes the Land view of Joint operations , but encourages contributions from Air, Maritime and other Communities of Interest (CoIs).
MIP specifications are based on operational requirements developed into a fieldable interoperability solution.
MIP assures the quality of the specification through operational and technical testing of national implementations.
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.
MIP is to further develop and improve interface specifications in order to reduce the interoperability gap between different C2IS.
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.
The MIP Data Model
The Joint Consultation, Command & Control Information Exchange Data Model (JC3IEDM) promulgated by NATO as STANAG 5525.
The MIP came about in 2001 by merging two previous separate programmes: The "Army Tactical Command and Control Information System" (ATCCIS) and the former MIP.
- 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 fieldable by 2003.
- 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.
- Situation awareness.
- Plans and orders.
- Capabilities and status of friendly and enemy forces.
- A voting member from each interested NATO Nation and Strategic Command.
- Non-voting representatives from the Partnership for Peace Nations, NATO bodies, Project Offices, Experts from Nations, Strategic Commands, industry or other international data standard bodies and NATO Data Administration (NDA) staff.
Chair MSG meetings providing a neutral viewpoint to facilitate the achievement of MIP's aims and goals.
Coordinate with MSG Host Member support organizations to ensure the effective conduct of MSG meetings. This would include coordination about matters such as meeting room requirements, minutes production, etc.
Provide a suitable and convenient location and facilities,
Prepare and distribute administrative and logistics information,
Provide all necessary clerical support for the meeting.
Aim, Responsibilities & Activities: What is the PMG purpose and foundation?
Develop and maintain the PMG Work Plan.
Effect co-ordination between the MIP WGs and ensure the WP effectiveness.
Make implementation level decisions and perform risk mitigation as necessary.
Develop and maintain several documents such as MPMP, MIPS, MCLiP, MVS, the MIP Standard Briefing as well as others the MSG might decide to.
The PMG meets as required to fulfil MIP objectives. The location and timings of these meetings are to be agreed upon by the MSG. Normally the PMG meets concurrently with the IPTs and at the same location, to facilitate co-ordination work among them.
The designation of PMG Chairman and Vice Chairman is at the discretion of the MSG. The Chairman carries out the following responsibilities:
Chairmanship: Who does chair the meetings?
Membership of the Multilateral Interoperability Programme may be as Full Members or Associate Members. Only Nations are eligible to become Full Members of the Programme.
Full Members are Nations that commit to support the collaborative development of succeeding versions of the MIP interoperability solution suitable for fielding.
Associate Members include Nations and non-Nation entities showing an interest in this Programme that have been granted Associate Member status by the MSG. Associate Members are entitled to have the same rights and privileges as Full Members but do not have the right to vote on decisions within the Programme.
The official request to become a Member shall be made by a formal written proposal to the Chairman of the PMG that must be endorsed by a current MIP Full Member. The Chairman of the PMG will forward the request to all other Full Member MSG HoDs.
The MIP community consists of 29 Nations plus 1 NATO Headquarters.
The MIP Steering Group (MSG) meets once a year for three days.
The Programme Management Group (PMG) and the Integrated Product Teams meet four times a year for a two week session.
The meetings are held in Greding, Germany.
There are about 60 people at the MSG, and more than 130 at the PMG and IPT meetings.
MIP schedules about 90 days for testing MIP Baselines.
All business is conducted in English.
All documents are written in English and based on the Oxford English Dictionary.