MIP Public Home

Block 2 finished at the end of 2006. The Baseline 2 documentation release took place at the end of WG-19 (Sep 06). This page gathers all relevant documents comprised into that Baseline as well as some definitions and miscellaneous information.

Supporting Documents. Some complementary documents that may help to understand how MIP works internally.

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 baselined documents there are supporting documents. Although being under configuration control management, they are not actually required to build a MIP Common Interface.

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 technical and operational 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.

The MIP Solution has evolved throughout Block 2 to address additional IERs as well as improvements in the technical solution.

The following table shows the MIP Baseline 2 Documentation. It depicts the end state of baseline documents as of WG 20 (Dec 06), the moment it was finished and therefore released. Every document is placed in a folder that you may browse by clicking on its name. Some times there is a unique file containing both the main body and the annexes. In other cases, main body and annexes are placed in different files. For more detailed information on a particular document, click on the hyperlink associated to its name on the table beneath.

WG	Documents
CCWG	MIP Glossary 2.4
CCWG	This document shall explain all the abbreviations and define important terms used within the MIP documents.
OWG	MTIR 2.3 (MIP Tactical C2 Interoperability Requirements)
	It marks the starting point of the whole engineering process. The IERs (Information Exchange Requirements) define the operational needs of exchanging and sharing information between different Operational Commanders. The OWG issues this document at the very beginning of every baseline.
	MOH 2.3 (MIP Operational Handbook)
	The MOH and its content target the operational audience and intend to give to the operational community a clear understanding of the MIP solution and its use in operational environment.
SEAWG	MSRS 2.1 (MIP System Requirement Specification)
	The MSRS (MIP System Requirement Specification) is the next step after the MTIR towards the completion of the technical solution. Going into detail in the technical specification of the MIP solution requires a "translation" of the IERs into technical terms prior to. That is the MSRS's aim. The purpose of this document is to specify the requirements for the MIP Communication interface as well as the required capabilities of a national C2IS in order to function in the MIP context.
	MTIDP 2.6 (MIP Technical Interconnection Design Plan)
	The MTIDP marks the last milestone prior to the material implementation starts. It defines and specifies the IEM (Information Exchange Mechanism). Therefore is a key piece in the whole MIP specification jigsaw puzzle. The MIP technical functions described in this document shall meet the requirements as stated in the document “MIP System Requirement Specification” (MSRS) and ultimately the requirements stated in the “MIP Tactical C2IS Interoperability Requirements” (MTIR).
	MOP 2.6 (MIP Operational Procedures)
	MIP requirements are fulfilled either by machine procedures implemented in computers or by human procedures executed by system operators and staff personnel. The MIP Operating Procedures (MOP) defines part of the human procedures needed to operate in a MIP environment. The MOP defines the procedures executed by gateway operators and information system personnel in order to “keep the system up and running”.
	MIR 2.8 (MIP Implementation Rules)
	The MIP Implementation Rules (MIR) document is a counterpart to the MOP and deals with those procedures or rules which can be implemented in a computer system and should not be the responsibility of a human operator.
DMWG	C2IEDM 6.1.5e (Command and Control Information Exchange Data Model)
DMWG	The Data Model is one of the two key pieces of the MIP solution. It gives room to the whole list of requirements undertaken by MIP to be implemented at every Baseline. The current Data Model is the outcome of a long evolution starting with the first instance of the GH series (ATCCIS). Obviously the DM keeps evolving as MIP improves its solution, since it is part of that solution. (take a look at JC3IEDM too)
TEWG	MTEMP 2.2 (MIP Test and Evaluation Master Plan)
	Its purpose is to define the overall test approach to be carried out within the Multilateral Interoperability Programme with the aim 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.
	MSLTP (MIP System Level Test Plan, SLT 1, 2 & 3)
	The MIP System Level Test Plan (MSLTP) 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.
	MOLTP (MIP Operational Level Test Plan)
	The MIP Operational Level Test Plan (MOLTP) describes the Operational tests to be carried out within the Multilateral Interoperability Programme to prove the MIP solution meets the operational requirements specified in the MTIR. It culminates and concludes the Test Process for the baseline.

*Most of the documents requires a PDF reader to be opened. You may download and install Acrobat Reader by clicking on the hyperlink "Acrobat Reader".

WG	Documents
PMG & CCWG	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.

*The MCLiP resides in Members' Area and requires proper MIP Website user and password to be seen

*Most of the documents requires a PDF reader to be opened. You may download and install Acrobat Reader by clicking on the hyperlink "Acrobat Reader".