MIP Public Home

Last updated on 25^th October 2007
© 2005-2007 MIP
You are the visitor number

Members' Area

Home

History

Organization

Documents

Contact

Miscellaneous

You are at:

> History

Best viewed at
1024 * 768

Interoperability

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.

Commanders require timely and accurate information. Also, supporting command and control (C2) systems need to pass information within and across national and language boundaries. Additionally, forces must interact with non-governmental bodies, and international and national aid organisations.

Information technology will act as a force multiplier to enhance operational effectiveness at each level of command by enabling the sending, receiving, filtering, fusing, and processing of ever-increasing amount of digital information.

Figures

25 Nations plus 1 NATO Headquarters.

MSG meets twice a year for three days.

PMG and the Working Groups meet four times a year for a week. The meetings are usually in Greding (Germany).

There are about 60 people at the MSG, and more than 130 at the PMG and WGs.

MIP scheduled 79 days for testing MIP Baseline 1 and similar amount for Baseline 2.

A rough estimation is that MIP nations spend about $1.2M national effort per annum. There are no transfer of funds.

MIP & NATO

NATO Force Goals (EL2802, Land & ER2802, Marine Forces) calls for the implementation of the MIP solution by NATO Nations.

The JC3IEDM is already the STANAG 5525 currently under ratification. The NATO Corporate Data Model (STANAG 5523 / ADatP-32) does not exist any longer.
*STANAG (Standard Agreement)

MIP liaises closely with NATO, and NATO has a Policy on MIP that allows MIP to easily conveys its specifications into 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 an MIP (ATCCIS) conformant land information system.

Many national C2 information systems implement MIP specifications.

The Bi-SC Automated Information System will use the MIP solution in its Land Functional Services to interface to national C2IS, either in HRF/LRF, CJTF, NRF or other crisis response operation or exercise.

MIP Integrated Operational Test & Evaluation (Sep 03)

Site Map

Home

MIP News

MIP Concept

Nav & Caveats

History

ATCCIS

Block 1

IOT&E

Baseline 2

Organization

MSG

PMG

Operational

Data Model

Engineering

Test & Eval

Conf Control

Documents

XML 1

XML 2

XML 3

Library

Contact

Download here

Acrobat Reader

Contact the

Webmaster

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. Find in this page more details about it.

The MIP History.

Learn about the MIP's history within the following sections:

Former MIP. Do you know who were its ancestors?

ATCCIS. An old NATO initiative seeking for 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 name of the group still today.

Top

ATCCIS.

In June 1976 the MC 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 C3 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.

* Click on here to glace at ATCCIS pages.

Top

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 is 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 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.
		Orders, plans and intentions.
		Capabilities and status of friendly and enemy forces.

This is the MIP we all know today.

Top

NDAG.

On February 04, 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.

*Find more information about by following: NDAG

Top