Skip Ribbon Commands
Skip to main content

Forget your password?
If you have forgotten your password, click here to reset it.
Want to change your password?
If you want to change your password, click here to change it.

 Welcome to MIP

The purpose of this Site is to provide general information about the Multilateral Interoperability Programme (MIP)
Feel free to browse this site in order to learn more about the programme.
Please contact either the Webmaster or any of the member nations to get more detailed information about MIP.

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. 

Key Points

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.

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. 

MIP Mission

MIP is to further develop and improve interface specifications in order to reduce the interoperability gap between different C2IS.

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.

The MIP Data Model

The Joint Consultation, Command & Control Information Exchange Data Model (JC3IEDM) promulgated by NATO as STANAG 5525.

 Background and History

​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.

The MIP History
The MIP history is described below:
Former MIP. The original idea for multilateral interoperabilty.
ATCCIS. A NATO initiative also seeking interoperability!
Enhanced MIP. The MIP as we know it nowadays.
NDAG. NDAG and MIP joined efforts to develop the JC3IEDM in 2004.

Former MIP
The former 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 programmes: Battlefield Interoperability Programme (BIP) and Quadrilateral Interoperability Programme (QIP).
The MIP's 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 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.

MIP remains as the current name of the Programme.

 In June 1976 the the NATO Military Committee approved a military requirement for interoperability between automated data systems at MC 245. This was a visionary statement, which remains valid today, and led to the start of the ATCCIS programme in 1980.
ATCCIS was not a formal NATO programme. It was a voluntary and independent activity by the participant Nations and was sponsored by SHAPE. The Nations and HQs that were active in the ATCCIS programme were BE, CA, CZ, DA, FR, GE, HU, IT, NL, NO, PO, PL, SP, TU, UK, US and RHQ AFNORTH.
The objective was to obtain C2 interoperability at reduced cost by developing and implementing technical standards agreed by Nations and prescribed by NATO. The aim of the programme was to identify the minimum set of specifications, to be included within Command and Control (C2) systems, which allow interoperability of multinational C2 systems. 

Enhanced MIP
 In October 2001, the ATCCIS and MIP members Nations decided to merge the two programmes 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 programme (the MIP name has 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. Battlespace 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 programmes 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:
- Situation awareness.
- Plans and orders.
- Capabilities and status of friendly and enemy forces.
This is the MIP we all know today.

NATO Data Administration Group
In February 2004, MIP and NATO Data Administration Group signed a Memorandum of Agreement stating their intent to collaborate in data modelling efforts to produce a Joint Consultation Command & Control Information Exchange Data Model (JC3IEDM) in 2008.
The NDAG is a multinational working group, responsible to the Information Systems Sub-Committee (ISSC) for the development and maintenance of NATO data management policies for recommendation to the NATO C3 Board, together with guidance on the coherent implementation of data management and administration across NATO. 
The NDAG is composed of a permanent Chairman with voting members and non-voting representatives and experts as follows:

-  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.

 The MIP Organisation

The MIP programme is not a formal NATO programme. It is a voluntary and independent activity by the participating nations and organisations.
Below are more details on its organisation, membership and liaison with external bodies sharing similar goals. 

MIP has a three-tiered structure:  two Management levels and one Task-Execution level. 
The Management levels consist of an oversight Steering group and a Programme Management group. 
In late 2009 the programme structure was reorganised from Multidisciplinary Working Parties into two Integrated Product Teams (IPT).  The first is IPT-3 and it is responsible for the In-Service Support to the MIP3.1 products.  The second team is IPT-4, and it is responsible for the development of a future specification using the latest system architecture concepts.  
Steering level
MIP Steering Group
Management level
Programme Management Group
Execution level
Integrated Product Team – 3
Responsible for In Service Support
Integrated Product Team – 4
Responsible for Future development
The active nations and HQs in the MIP programme are: Australia, Austria, Belgium, Canada, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Italy, The Netherlands, New Zealand, Norway, Poland, Portugal, Romania, Slovak Republic, Slovenia, South Africa, Spain, Sweden, Switzerland, Turkey, United Kingdom, United States and Allied Command Transformation (ACT)
The Programme consists of Full Members (nations only) and Associate Members (including nation and non-nation entities). 

NATO plays its part in the MIP programme through two different entities:
ACT (Allied Command for Transformation) :  Members of SEE (Staff Element Europe), C2DS (Command and control Deployability and Sustainability) attend the MSG and the PMG meetings.  Further details on ACT can be found on their site.
NCIA (NATO Communications and Information Agency) implements the MIP specifications in the framework of the current development and deployment. Further details on NCIA can be found on their site.
Web Accounts
New web accounts may only be submitted via Natoinal Head of Delegation to the Web master via email. 
Information required must at least comprise:
- County;
- Last/First name;
- Email address;
- MIP Orgainsation (MSG/PMG/IPTs) 

 MIP Steering Group (MSG)

The MSG is at the top of the MIP Organisation.
 The MSG members at their meeting in USA in May 2010.

- Aim, Responsibilities & Activities. What is the MSG purpose and foundation?
- Membership & Decision Procedures. Every member is represented by one delegation whose leader is its HoD (Head of Delegation).
- Meetings. How many, where and when MSG meetings are held?
- Chairmanship & Host Nation. MSG meetings take place in different locations volunteered by Member Nations. 

Aim, Responsibilities & Activities
The aim of the MIP Steering Group is to define the strategy for the programme and make overall programme policy decisions.
The MSG defines the overarching Programme objectives, strategy, milestones and Programme phase capstone events. It provides overall guidance and is the decision authority for the Programme. The MSG is the final multinational authority for resolution of Programme issues and risk mitigation. The MSG assigns Member responsibilities and is responsible for the MIP Statement of Intent (MSOI).
The MSG is also the approval authority for the programme of work as presented by the PMG and receives periodic updates by PMG of each meeting concerning work performed, accomplishments to date, current status, future plans, issues and risk areas.
Membership & Decision Procedures
Each MIP Member is to attend MSG meetings with an empowered representative as their national HoD. There can be only one HoD per Member who may attend together with other national representatives if need be.
The Chairmen of the Integrated Product Teams attend the MSG to report on their activities and receive Programme guidance.
All MSG decisions are made by the unanimous agreement of Full Member Nation HoDs. The MSG directs the activities of the PMG and the IPTs, who in turn report back at each MSG meeting.

The MSG meets as required to fulfil MIP objectives. The location and timings for these meetings are to be agreed upon by the MSG.
Each Full Member hosts a MSG meeting in turn and on rotational basis.  Associate Members may host an MSG meeting on voluntary basis.
A Full Member may request meetings other than those formally scheduled. For such a purpose, he has to make a proposal to the other Full Members, including details as location, dates and agenda.

Chairmanship & Host Nation
The designation of the MIP Steering Group Meeting Chairman and Vice Chairman is at MSG's discretion.  The Chairman carries out the following responsibilities in this capacity:
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.
The host Member:
Provide a suitable and convenient location and facilities,
Prepare and distribute administrative and logistics information,
Provide all necessary clerical support for the meeting.

 MIP Programme Management Group (PMG)


Aim, Responsibilities & Activities: What is the PMG purpose and foundation?

Membership & Decision Procedures: HoDs from MIP Members attend.
Meetings & Host Nation: How many, where and when PMG meetings are held? 

Aim, Responsibilities & Activities
The aim of MIP is to ensure that the MIP's strategic goals and objectives are achieved.
The activities of Detailed Planning, Co-ordination, Task Execution Management and Risk Mitigation must be synchronised and complementary within the MIP. These activities are carried out by the Programme Management Group following MSG's policy and guidance.
Strategic planning is predominantly a Programme Management level activity conducted by the MSG, which is concerned with identifying the MIP goals, objectives, milestones and Short and Long Term plans.
Management at the Task Execution level conducted by the PMG is concerned (mostly) with the management of the detailed Short and Long Term plans. The PMG also effects co-ordination between the IPTs to insure that MSG goals are mutually understood.
The primary responabilities of the PMG are to facilitate co-ordination between IPTs, and to make the necessary implementation level decisions to facilitate Programme execution within the framework of the MSG overarching policy and direction. The PMG will be the arbitrator and decision-maker during WG Meeting Sessions.
The specific tasks of the PMG to this end are among others:
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.
* A more comprehensive list may be found in the MPMP (Programme Management Plan)

Membership & Decision Procedures
Heads of Delegation of member nations or their representatives empowered to make decisions, as well as IPT Chairmen, attend the PMG meetings. The MSG designates a Chairman and Vice-chair for the PMG. The PMG establishes a secretariat to support the chair.
All PMG decisions are made by the unanimous agreement of the Full Member's HoDs. The PMG directs the WGs, who in turn report back at each PMG meeting. The PMG approves the Action Item and Decision List of its meetings. 


Meetings & Host Nation


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.

PMG meets four times a year for two weeks each. Germany is the Host Nation and the WTD 81 facilities are located in Greding.
The WG meeting forecast is included in the MIP Schedule (MIPS). 




The designation of PMG Chairman and Vice Chairman is at the discretion of the MSG. The Chairman carries out the following responsibilities:

Chairs meetings of the PMG, providing a neutral viewpoint to facilitate the achievement of MIP aims.
Coordinate with PMG Host Member support organisations to ensure the effective conduct of PMG meetings. This would include coordination related to meeting room requirements, production of minutes of the meeting, et al.
The Vice Chairman supports the Chairman as required.
The PMG is responsible for the day to day management of the MIP Organization.

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

Full Members are Nations that commit to support the collaborative development of succeeding versions of the MIP interoperability solution suitable for fielding.

To be a Full Member, a Nation must agree to meet the requirements listed in the MIP Programme Management Plan. In addition a Full Member must express an intention to field the MIP solution.
Full Members undertake to be represented in all WGs and must be prepared to expend the resources required.  Full Members have voting and access rights at all meetings.


Associate Members


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.   

Application for Membership


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 application must include a statement on the status of involvement in a National C2IS, the nature of interest in the MIP, and an agreement to abide by MSG/PMG decisions.   

Membership Approval
The MSG will, at the next available opportunity, consider the application for membership as presented by the sponsoring member. Subject to a unanimous agreement, the MSG will agree the Membership request and invite the new member to attend the next meeting. 

 Content Editor

 Facts and Figures

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. 

May 2011 


NATO Force Goals (EL2802, Land & ER2802, Marine Forces) reccomend the implementation of the MIP solution by NATO Nations.
The JC3IEDM has been ratified as STANAG 5525.
MIP liaises closely with NATO.
The MIP specification is included in the NATO C3 Technical Architecture.
The NATO Military Criteria for High Readiness Forces (Land) Headquarters requires the use of a MIP-compliant Land Information System.
Many national C2 information systems implement MIP specifications.