MOLTP - TEWG MULTILATERAL INTEROPERABILITY PROGRAMME MIP OPERATIONAL LEVEL TEST PLAN (MOLTP) 14 May 2009, Greding Germany This Multilateral Interoperability Programme (MIP) Operational Level Test Plan has been reviewed and is hereby approved by the Heads of Delegation of participating nations. Release of this document to nations or agencies, who are not participants in the Multilateral Interoperability Programme including the media and general public, require the approval of the MIP Steering Group (MSG) in accordance with policy stated in the MIP Communications and Liaison Plan (MCLiP). This document is the property of the MIP participants and the information contained in this document shall not be communicated, either directly or indirectly, to any person or agency not authorised to receive it.
MOLTP - TEWG RECORD OF CHANGES PAGE CP Number Date Entered Responsible individual Remarks 1
TABLE OF CONTENTS MOLTP - TEWG SECTION TITLE PAGE 1 MIP VISION...1 1.1 MIP SCOPE...1 1.2 MIP MISSION...1 1.3 MIP TASKS...1 2 AIM OF MIP OPERATIONAL LEVEL TEST PLAN...2 ANNEX A: GLOSSARY ANNEX B: MIP BASIC TERMINOLOGY 2
MOLTP - TEWG MIP OPERATIONAL LEVEL TEST PLAN (MOLTP) 1 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. 1.1 MIP SCOPE The MIP scope is to deliver a command and control interoperability solution focused on the Land operational user in a Joint environment. 1.2 MIP MISSION MIP is to further develop and improve interface specifications in order to reduce the interoperability gap between different C2IS. 1.3 MIP TASKS Support fielded MIP solutions. Further improve the MIP solution by adopting modern development approaches and standards 1. Harmonise with NATO and leverage other appropriate standards 2. Improve flexibility in using the MIP solution in ad-hoc coalitions. Extend the scope of MIP interoperability. Engage Air, Maritime and other Coalition of Interests to cooperate with MIP. 1 Examples of approaches and standards include the NATO Architectural Framework (NAF), Model Driven Development, Service Orientation and common standards (XML, UML, RDF, etc.). 2 Examples include NNEC, APP-11, APP-6, etc. 1
Examine better ways of structuring the MIP programme. MOLTP - TEWG 2 AIM (insert text) The aim of this document is to provide a covering document for the OLT documentation set. This set of documentation is a stand-alone set of artefacts that will enable an OLT to be managed in accordance with the TEWG direction. Consequently, no further detail will be provided in this (MOLTP) document. 2
MOLTP TEWG Annex A ANNEX A: GLOSSARY See MIP Glossary A-3
MOLTP TEWG ANNEX B: MIP BASIC TERMINOLOGY 1 INTRODUCTION This document explains basic terms which are common to more than one MIP document. 2 S COVERED MIP Product Set MIP Specification MIP Common Interface (MCI) MIP Gateway (MIP GW) MIP Message Exchange Mechanism (MEM) MIP Data Exchange Mechanism (DEM) MIP Information Exchange Data Model (MIP IEDM) MIP Information Resource Dictionary (MIRD) MIP LAN MIP Solution MIP Scope National LAN National C2IS 3 RELATIONSHIPS BETWEEN S The hierarchical relationship between definitions is given below: The full set of MIP documents is known as the MIP Product Set and it includes a subset of documents known as the MIP Specification. B-4
MOLTP TEWG The MIP Specification can be implemented to produce a MIP Gateway which consists of a MIP MEM and a MIP DEM. A MIP DEM can exchange data compliant with a specific MIP IEDM and its associated MIRD. A MIP Gateway provides the point of connection between the MIP LAN and the National LAN which hosts the National C2IS. The information which can be exchanged through a MIP Gateway is defined by the MIP Common Interface. Two or more functioning MIP Gateways which can exchange data over a MIP LAN constitute the MIP Solution, which fulfils the MIP Aim. The MIP Scope is restricted to the definition of the data which can be exchanged in accordance with the MIP Common Interface and the protocols for the exchange of that data. 3.1 MIP PRODUCT SET The MIP Product Set is the total set of documents produced by MIP within a named Baseline Release or Version. The MIP Product Set includes both the MIP Specification (the technical side) and also additional supporting MIP documents (such as the MIP Vision and Scope) which provide amplifying details (the programme management side). Thus there are MIP documents (such as the MIP Campaign Plan and the MPMP) which, whilst essential to the overall achievement of MIP s vision and mission, cannot in any way be considered as specifications 3.2 MIP SPECIFICATION B-5
MOLTP TEWG The MIP Specification is that subset of the total documentation set within a named Baseline Release or Version, which deals with the technical specification of a system and which may be implemented to achieve the MIP mission. The MIP Specification is a term which is widely used and should be understood as those MIP documents which provide the technical specification. It contains specifications for implementation in the form of Data Structures, Data and Message Formats and Functionality, Application Functionality and User Procedures. It also includes a matching set of Test Cases, Procedures and Specifications. The MIP Specification is a coherent set of documents designed to be used in conjunction with one another. 3.3 MIP COMMON INTERFACE (MCI) The MIP Common Interface (MCI) is that subset of a MIP Specification which defines what can be exchanged using the MIP MEM and DEM. It is an interface in that it provides the tangible face of what is otherwise a Black Box. The MCI consists of an agreed set of MEM messages and attachment file types, DEM management messages and DEM data PDUs (Protocol Data Units). The permitted content of these exchange formats is constrained by the MIP Specification (e.g. the content of the DEM data PDUs must be conformant with a specified version of the MIRD). The MIP Specification further constrains the MCI by the definition of protocols and procedures to ensure that the exchanges can take place meaningfully. 3.4 MIP GATEWAY (GW) B-6
MOLTP TEWG A MIP Gateway is an implementation in both software and hardware which conforms to a named version or release of the MIP Specification. It incorporates the functionality of both a MIP MEM (Message Exchange Mechanism) and a MIP DEM (Data Exchange Mechanism). Both MEM and DEM are defined as mechanisms which means that they must be functioning systems. MIP Gateway is a more general term than MEM or DEM. 3.5 MIP MESSAGE EXCHANGE MECHANISM (MEM) A MIP Message Exchange Mechanism (MEM) consists of an ESMTP 3 mailer which is a software implementation of the MEM specification contained in the MTIDP. The ESMTP mailer logically resides within the MIP Gateway. However this is not technically necessary; since the MIP Gateway is providing access between the MIP and National LANs, the mailer could be located on the National LAN. 3.6 MIP DATA EXCHANGE MECHANISM (DEM) A MIP Data Exchange Mechanism (DEM) consists of a replication mechanism which is a software implementation of the DEM specification contained in the MTIDP. The DEM is designed to be used in conjunction with a MIP Information Exchange Data Model schema and its associated MIP Information Resource Dictionary (MIRD). 3 Enhanced Secure Mail Transfer Protocol used for emails and attachments. B-7
MOLTP TEWG The DEM logically resides within the MIP Gateway. 3.7 MIP INFORMATION EXCHANGE DATA MODEL (MIP IEDM) The MIP IEDM is a formally defined data structure designed to encompass the minimal subset of operational data required for multinational exchange in accordance with the MIP V&S and MCP. The term MIP IEDM is a generic term which can be applied to unspecified releases or versions of the MIP Information Exchange Data Model (such as the LC2IEDM, the C2IEDM and the current JC3IEDM). 3.8 MIP INFORMATION RESOURCE DICTIONARY (MIRD) The MIRD is a database schema and an associated data fill which provides a store for metadata describing a specific version of the MIP Information Exchange Data Model. Part of the MIRD is used by the Replication Mechanism as a means of minimising the data exchanged and of ensuring integrity. It has recently been extended to include an encoding of basic business rules designed to ensure semantic integrity which can be used at the application level (i.e. either before data is submitted to the MIP Gateway for transmission or after it has been received from a MIP Gateway but before it is submitted to a national C2IS). 3.9 MIP LAN B-8
MOLTP TEWG The MIP LAN is a limited network which provides connectivity between MIP Gateways. The only protocol used for transport is TCP/IP. The term MIP LAN is required to distinguish the network on the multinational side of a MIP Gateway from that on the national side (which is known as the National LAN). 3.10 MIP SOLUTION The MIP Solution is what exists when two or more MIP Gateways are connected across a MIP LAN. The MIP Solution is the provision of a capability to permit the exchange of actual data, in order to improve common understanding of information. The MIP Solution should be seen as the opposite and concluding end of the spectrum of MIP definitions from the MIP mission. It is that complete thing which enables the MIP mission to be fulfilled. 3.11 MIP SCOPE The MIP scope defines the constraints and limitations that MIP operates within. It identifies the boundaries within which MIP operates. The MIP scope can be broadly understood as the Terms of References for the MIP programme. Importantly it explains where MIP and national responsibilities begin and end. B-9
3.12 NATIONAL LAN MOLTP TEWG A National LAN is a network controlled by a single nation which cannot be accessed by other MIP nations, but which might be connected to a MIP Gateway for purposes of multinational data exchange. The term National LAN is required to distinguish the network on the national side of a MIP Gateway from that on the multinational side (which is known as the MIP LAN). 3.13 NATIONAL C2IS The National C2IS is a Command and Control Information System which resides on a National LAN. The behaviour of the national C2IS is outside the scope of MIP. However it is recognised that in order to ensure international interoperability desired by the MIP mission, a national C2IS should provide a degree of functionality which permits the meaningful interpretation of operational data received from a MIP Gateway. B-10