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

Members' Area

You are at:

Best viewed at 
1024 * 768

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

Block and Baseline 1

Block 1 finished at the end of 2003 after the IOT&E. Then Baseline 1 documentation release took place. This page gathers all relevant documents comprised into that Baseline as well as some definitions and miscellaneous information.

The MIP Baseline 1.

Learn about Baseline 1 in the following sections:

Definition. Do you know what a MIP baseline is?

MIP Solution and Network Configuration. See what it consists on.

Baselined Documents. Find the most fundamental documents in this charter.

Supporting Documents. Some complementary documents.

A MIP baseline is a specification of an interoperability solution that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development, and can be changed only through formal change control procedures. 

The Baseline specification consists of the coherent minimum set of documents needed to build and test a MIP Common Interface (MCI). Once the baseline is successfully tested it becomes an approved baseline.

In addition to the Baseline there are supporting documents. These are documents that are under configuration control management but are not needed to build a MIP Common Interface.

The Baseline 1.0 is in service from January 2004 to December 2005.

The MIP Solution is a set of items delivered by the MIP programme at the end of each block. It includes the MIP specifications, Standard Operation Procedures and other documentation which is required for implementation of the specifications and for use of the MCI.  

The MIP Common Interface is a logical description of the configuration of two or more implementations (in Soft and/or Hardware) of the MIP specifications that enables information exchange between two or more C2IS from different nations.

Block 1 limitations dictated that the MIP Common Interface was likely to be co-located within a secure area (e.g. Command Post) and to be linked by a LAN, in the course of which the number of MIP Implementations within a LAN was not limited.  The communications between a nation’s C2IS and the MIP Implementation and its associated security is always a national responsibility. There are two other different configurations (de-centralized and hybrid).

Operational Documents.

MTIR, MIP Tactical C2 Interoperability Requirements: which purpose  is to state the user requirements for the exchange of information between national army C2IS.

MCONOPS, MIP Concepts of Operations: which purpose is to provide a harmonised concept of deployment for the fielding of the international interoperability capability developed within MIP, both nationally and within the MIP community. This will ensure that the proposed MIP technical implementation solutions are viewed within an agreed deployed operational framework.

Technical & Procedural Documents.

MSISP, MIP System Interconnections Security Policy: which purpose is to define the policy for ensuring that the interconnection of the individual nation’s army C2IS via the MIP Solutions (MS) does not compromise their security as defined by national policy. This is to ensure that suitable security standards are in place to allow individual MIP Nations, who are responsible for the accreditation of their own national C2IS, to include the MS in that accreditation. NATO security rules have been chosen as the common standard.

MIOP, MIP Interface Operating Procedures (includes the LC2IEDM): which purpose is to provide data specification to support the use of MIP message text formats, and database replication and procedures for establishing, maintaining, and closing MIP Interfaces between national C2ISs for MIP Block I.

MTIDP, MIP Technical Interface Design Plan (includes the WP14-3 ARM): The MTIDP describes and specifies the functions which are necessary to secure the technical interoperability between the C2ISs.

Operational Documents.

MTEMP, MIP Test and Evaluation Master Plan: which purpose is to define the overall test approach to be carried out within the Multilateral Interoperability Programme to prove interoperability between the C2IS of the participating MIP nations by means of physical connectivity, data exchange and procedures. It provides the overall framework for testing, evaluation, and qualification in order to prove that fielded national implementations meet the minimum level of C2IS interoperability as defined by MIP.

MTP, MIP Test Plan: describes the tests to be carried out within the Multilateral Interoperability Programme to prove interoperability between the C2IS of the participating MIP nations by means of physical and logical interfaces.

MEDP, MIP Exercise and Demonstration Plan: which purpose is to define the planning and coordination details necessary to enable field experiments, demonstrations, exercises or other such activities.

Miscelaneous.

MEB1R, MIP End of Block 1 Report: The purpose of the MIP End of Block 1 Report is to identify the work completed in MIP Block 1.

MIP Glos, MIP Glossary: This document shall explain all the abbreviations and define important terms used within the MIP documents.

Management.

MPMP, MIP Programme Management Plan: The purpose of the MIP Programme Management Plan (MPMP) is to define the procedures and structures to be used in the management of the MIP. This plan also provides guidelines detailing the authority and responsibilities for all WGs within MIP. It also establishes procedures for membership. 

MCMP, MIP Configuration Management Plan: The purpose of the MIP Configuration Management Plan (MCMP) is to define the configuration control procedures to be used in the management of documents within the Programme, particularly: monitoring the status of the baseline documents and supporting documents, co-ordinating documentation change, processing Change Proposals (CPs), recording and reporting the status of CPs, issuing Change Notices (CNs), recording and reporting the status of CNs, monitoring and processing Requests for Waiver (RFWs) and Requests for Deviation (RFDs) and recording and reporting the status of RFWs and RFDs.

Miscelaneous.

MCLiP, MIP Communications and Liaison Plan: The purpose of the MIP Communications and Liaison Plan (MCLiP) is to define the internal communication processes and the external liaisons.

The documents here above hyperlinked are old versions valid for the Baseline 1 exclusively. They have evolved since to adopt the new program needs. To view the latest go to Documents.

Block and Baseline 1

Definition. MIP Solution and Network Configuration. Baselined Documents. Supporting Documents.

You are at:

Best viewed at 
1024 * 768

Members' Area

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