2007•Defense Technical Information Center (DTIC)Requires access

Current and Future MIP Capabilities for Coalition Interoperability

M.G. van der Meijden

Open publisher page 0 citations

Abstract

The aim of the Multilateral Interoperability Programme (MIP) is to achieve international interoperability of Command and Control Information Systems (C2IS) at all levels from corps to the lowest appropriate level, in order to support combined and joint operations; and pursue the advancement of digitization in the international arena, including NATO. The MIP programme is tightly focused on delivering capability in an incremental manner based upon a rolling 2-year delivery cycle, while in parallel the previous baselines are sustained, new operational requirements are analyzed, new capabilities are agreed, and emerging technologies are explored. The MIP is an operational requirement driven programme with a schedule constraint. The overall MIP Calendar is divided into 'Blocks' or evolutionary solutions, each block will take three years of developing and will remain 'in-service' for two years. The first MIP solution (block I) became available at the end of 2003, after the Integrated Operational Test & Evaluation (IOT&E). This will be the interoperability solution for allied armies in 2004 and 2005. Meanwhile, the second iteration of the MIP solution is under developed and will become 'in-service' in 2006 and 2007, and so on.

About this research paper

What this paper is about

The aim of the Multilateral Interoperability Programme (MIP) is to achieve international interoperability of Command and Control Information Systems (C2IS) at all levels from corps to the lowest appropriate level, in order to support combined and joint operations; and pursue the advancement of digitization in the international arena, including NATO. The MIP programme is tightly focused on delivering capability in an incremental manner based upon a rolling 2-year delivery cycle, while in parallel the previous baselines are sustained, new operational requirements are analyzed, new capabilities are agreed, and emerging technologies are explored. The MIP is an operational requirement driven programme with a schedule constraint. The overall MIP Calendar is divided into 'Blocks' or evolutionary solutions, each block will take three years of developing and will remain 'in-service' for two years. The first MIP solution (block I) became available at the end of 2003, after the Integrated Operational Test & Evaluation (IOT&E). This will be the interoperability solution for allied armies in 2004 and 2005. Meanwhile, the second iteration of the MIP solution is under developed and will become 'in-service' in 2006 and 2007, and so on.

Why it matters

A significance statement is not available in the OpenAlex record.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

The aim of the Multilateral Interoperability Programme (MIP) is to achieve international interoperability of Command and Control Information Systems (C2IS) at all levels from corps to the lowest appropriate level, in order to support combined and joint operations; and pursue the advancement of digitization in the international arena, including NATO. The MIP programme is tightly focused on delivering capability in an incremental manner based upon a rolling 2-year delivery cycle, while in parallel the previous baselines are sustained, new operational requirements are analyzed, new capabilities are agreed, and emerging technologies are explored. The MIP is an operational requirement driven programme with a schedule constraint. The overall MIP Calendar is divided into 'Blocks' or evolutionary solutions, each block will take three years of developing and will remain 'in-service' for two years. The first MIP solution (block I) became available at the end of 2003, after the Integrated Operational Test & Evaluation (IOT&E). This will be the interoperability solution for allied armies in 2004 and 2005. Meanwhile, the second iteration of the MIP solution is under developed and will become 'in-service' in 2006 and 2007, and so on.

Key concepts: Interoperability, Digitization, Joint (building), Command and control, Order (exchange), Control (management), Cross-domain interoperability, Computer science

Related papers

Back to paper searchBrowse research topicsOriginal source
Current and Future MIP Capabilities for Coalition Interoperability — Research Paper | ScholarLens