MULTILATERAL INTEROPERABILITY PROGRAMME MIP IMPLEMENTATION RULES (MIR)

Transcription

1 MIR MULTILATERAL INTEROPERABILITY PROGRAMME MIP IMPLEMENTATION RULES (MIR) 17 February 2012, Greding Germany This Multilateral Interoperability Programme (MIP) Implementation Rules (MIR) 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, requires approval of the MIP Steering Group (MSG) in accordance with the 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.

2 RECORD OF CHANGES PAGE CP Identifier CP v1 CP v7 CP v2 CP v1 Description Changed in v3.1.5 (WG-41 - February 2012) Annex F Appendix 3-2: Changed geometry rule for Air Axis of Advance to support multi-point. Annex F Appendix 3-2: Changed geometry rule for Final Protective Fire from CORRIDOR-AREA to 2-point LINE. Section 3: Updated text to clarify MIR is implementation rules and not guidance. Updated diagram to include JC3IEDM and MIG. Annex E and Annex E Appendix 2: updated references to MTIR/JC3IEDM/MSRS/MTIDP from MIP3.0 to MIP3.1 [MPR#1600]. Annex F Main: removed list of appendices (as these are already listed in MIR Main). Annex F Appendix 2-2: removed duplicate entry for GEN_FEAT_POINT. Annex F Appendix : Added text GEN_FANAREA to all symbols using FAN-AREA as their geometry. Multiple typo corrections. No change to content. Annex F Appendix : Added text GEN_FANAREA to all symbols using FAN-AREA as their geometry. Multiple typo corrections. No change to content. Annex F Appendix 4-2: Corrected geometry for 'GEN_LINE_CORRIDORAREA' to 'Surface' for 'Wall' and Waste Pile. Corrected Volume business rule for Abatis to be 'GEN_VOL_POLYAREA' [MPR#1587]. Changed in v3.1.4 (WG-40 - December 2011) Annex F Appendix : Added entry for Extortion. Note this editorial omission was actually corrected in MIR3.1.3 but was not reflected in the Record of Changes.[MPR#1558] Removed Annexes G, H, and I. These annexes are now part of the MIG (MIP Implementation Guidance) v3.1.4 as Annexes B, C, and D. Note: WG40 CPs processed against these former MIR annexes are recorded in the MIG Record of Changes. Updated Annex B to clearly state Not Used. Annex A: Added MIG to Glossary. Moved Annex A to separate file (to follow same pattern as other annexes). Removed placeholder pages for all annexes (in main document) and replaced by a single Annex File List table. Annex F: reduced Annex F main document to a single page, including a listing of Annex F appendices. Annex F Appendix 3-2: re-ordered some entries to follow correct alphanumeric order. No change to content. Annex F Appendix 4-2: re-ordered some entries to follow correct i

3 CP Identifier CP v1 CP v5 CP v1 CP v2 CP v4 CP v1 CP v1 CP v2 CP v2 Description alphanumeric order. No change to content. Annex F Appendix : re-ordered some entries to follow correct alphanumeric order. Fixed some spelling errors. No change to content. Annex F Appendix : re-ordered some entries to follow correct alphanumeric order. Fixed some spelling errors. Changed in v3.1.3 (WG-39 - September 2011) Annex E Appendix 3: renamed Excel spreadsheet as Annex E Appendix 4 JC3IEDM Soft Links, in order to differentiate from the Word Document (which remains as Annex E Appendix 3 Soft Links Overview. Annex F Appendix 3-2: Corrected geometry business rule for Transit Corridor. [MPR#1326] Annex E Appendix 1: updated section 3.5 to clarify how is superseded by relationship applies to PLANs. [MPR#1459] Annex E Appendix 1: added section to clarify a superseded PLAN does not affect an associated ORDER. [MPR#1457] Annex E Appendix 4: corrected soft-links for *-COMMENT structure. Removed cardinality relationship tab. Annex E Appendix 1: removed sections and footnote 2. Added new section to clarify rules for independence of a Frago ORDER. [MPR#1493] Annex E Appendix 1: updated section to clarify rules for converting a separately-managed annex from plan to order. [MPR#1504] Annex E Appendix 1: added section to clarify a superseded PLAN does not affect an associated ORDER. [MPR#1457] Annex E: updated sections and to clarify interpretation of context-object-item-association-status-effective-datetime. [MPR#1501] Annex E Appendix 1: updated section to improve clarity. Annex E Appendix 1: standardized capitalization of Order and Plan throughout document. Annex E Appendix 3: removal of reference to C2IEDM. Annex F Appendix 2-2: Clarified that the generic rules apply to ACTIONs as well as OBJECT-ITEMs. [MPR#1549] Annex F Appendix 4-2: Corrected graphic for Crossing, railway/river. [MPR#1550] Annex F Appendix : Corrected graphic for Counter Attack. [MPR#1551] Annex F Appendix : Corrected graphic for Counter Attack. [MPR#1551] Annex G Appendix : Added missing entry (no content) for Extortion. Annex G Appendix : Added footnote to Anti-Tank entry. [MPR#1506] Changed in v3.1.2 (WG-38 - May 2011) ii

4 CP Identifier CP v3 CP v8 CP v1 MPR#1494 (partial) MPR#1527 (partial) CP v3 CP v3 CP v3 CP v2 CP v3 CP v3 CP v3 CP v2 CP v2 CP v2 CP v3 CP v2 CP v3 CP v3 CP v1 Description Annex E: Updated section 6.12 to reflect changes to OBJECT-ITEM- COMMENT and ACTION-COMMENT structures Annex E: Completely replaced section 3.18 with new rules for representing TaskOrg/ORBAT structures Annex G Appendix 2-2: renamed short-text to symbol-annotationtext Annex G Appendix 3-2: corrected hierarchy-code for Attack Position to be 2.X instead of 2.X Annex E: corrected reference in section 1.3 to remove URL of deprecated MIP website. Annex H: Generated new MIP Common Datafill MOU and SQL file, based on JC3IEDM MIRD Changed in v3.1.1 (WG-37 - February 2011) MIR v3.1.1 evolved from MIR v Detailed change history for MIR versions prior to v3.1.1 can be found in MIR v3.0.9 Annex E: removed section 6.9 (IED Usage Rules). Annex D Appendix 2: added key prefix for EST Annex D Appendix 1: updated key allocation procedure to distribute one key instead of ten Annex D Appendix 2: added key prefix for NZL Annex G Appendix : IA updates to Action-Event App-6A Annex G Appendix : IA updates to Action-Event 2525B Annex G Appendix 3-2: IA updates to Control-Feature App-6A Annex G Appendix 3-4: IA updates to Control-Feature 2525B Annex G Appendix 4-2: IA updates to Facility App-6A symbology mappings Annex G Appendix 4-4: IA updates to Facility 2525B symbology mappings Annex G Appendix : IA updates to Electronic-Equipment App- 6A Annex G Appendix : IA updates to Miscellaneous-Equipment App-6A Annex G Appendix : IA updates to Vehicle-Equipment App- 6A Annex G Appendix : IA updates to Weapon-Equipment App- 6A Annex F Appendix 4-2: IED updates to Facility geometry rules Annex G Appendix 4-2: IED updates to Facility App-6A symbology mappings Annex G Appendix 4-4: IED updates to Facility 2525B symbology mappings {note: the update to this Appendix was not explicitly iii

5 CP Identifier CP v1 CP v2 CP v3 CP v1 CP v1 CP v1 CP v2 CP v1 CP v1 CP v1 CP v1 CP v1 CP v1 CP v1 CP v1 Description mentioned in the approved CP, however it was deemed to be an editorial omission, and applied as a Custodian correction} Annex D Appendix 2: added key prefix for ZAF Annex I: added new Annex I, including Appendix 1 (IA Mapping Guidelines) Annex F Appendix : IA updates to Action-Event geometry rules Annex F Appendix 3-2: IA updates to Control-Feature geometry rules Annex F Appendix 4-2: IA updates to Facility geometry rules Annex F Appendix : IED updates to Action-Event geometry rules Annex G Appendix : IED updates to Action-Event App-6A Annex G Appendix : IED updates to Action-Event 2525B Annex G Appendix : New Appendix to hold 2525C symbology mappings Annex G Appendix 3-4: Corrections (MPR#1494) to Control-Feature 2525B Annex F Appendix 3-2: Corrections (MPR#1494) to Control-Feature geometry rules Annex G Appendix : Corrections (MPR#1494) to Maritime- Equipment App-6A Annex G Appendix 3-2: Corrections (MPR#1494) to Control-Feature App-6A Annex G Appendix : Corrections (MPR#1494) to Action-Event App-6A Annex G Appendix : Corrections (MPR#1494) to Action-Event 2525B {note: the update to this Appendix was not explicitly mentioned in the approved CP, however it was deemed to be an editorial omission, and applied as a Custodian correction} Annex F Appendix : Corrections (MPR#1494) to Action-Event geometry rules Annex G Appendix : Removed App-6A mapping for Electronic Warfare Annex G Appendix : Corrected typo for Air Superiority in Action-Task mappings to App-6A Annex G Appendix : Corrected typo for Air Superiority in Action-Task mappings to 2525B Annex G Appendix 6-2: Corrections to Organisation App-6A Clarified Annex G filenames to use Symbology Mappings instead of iv

6 CP Identifier Description Symbology Mapping Rules (as Annex G is guidelines for national C2 mappings, not information exchange rules) v

7

8 TABLE OF CONTENTS SECTION TITLE PAGE 1 MIP VISION MIP SCOPE MIP MISSION MIP TASKS AIM EXECUTIVE SUMMARY... 2 vii

9 MIP IMPLEMENTATION RULES (MIR) 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. Examine better ways of structuring the MIP programme. 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

10 2 AIM 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 running. The MIP Implementation Rules (MIR) document is a counterpart to the MOP in that it deals with those procedures or rules which can be implemented in a computer system and should not be the responsibility of a human operator. 3 EXECUTIVE SUMMARY This MIR document contains a collection of rules to support the implementation of system interfaces in accordance with the overall MIP specification. These rules do not constitute part of the technical design, nor are they operating procedures for the MIP Gateway user. This document therefore defines implementation rules which are not included in either the MTIDP or the JC3IEDM; however, conformance to these rules is necessary to ensure effective interoperability. There are defined within MIP two kinds of procedures, one of which loosely may be termed connection procedures and the other which loosely may be termed information procedures. Information procedures are the ones that are needed in order for the information in the system to be correct and understandable. Information procedures typically are documented as rules to follow. These are mostly to be found in this MIR document. There are Standard Operating Procedures for staff officers (operators) in a MIP enabled force. These are described in the MIP Operational Handbook. 2

11 The diagram below illustrates the relationships between the MIP documents and their intended users. Use cases MIP Operational Handbook MIP Operating Procedures MIP Gateway Software Specification: MTIDP / JC3IEDM / MIR Guidance: MIG Commander and Staff Officers Gateway Operator MIP Gateway GUI Implementer 3

12 Annex File List File Version Description Annex A Glossary Annex A - Glossary Abbreviations used in the MIR Annex B Not Used Annex C Not Used Appendix 1 - Key Allocation Procedure Appendix 2 - Key Management Rules Annex D Key Management Defines the procedure for the allocation of key range prefixes Rules for the management of record identifications (keys) and the unambiguous specification of those keys for all operational data within the distributed environment of the community of interest. Annex E - MIP JC3IEDM Usage Rules Appendix 1 Plans and Orders Usage Rules Appendix 2 OIG Content Appendix 3 Soft Links Overview Appendix 4 JC3IEDM Soft Links List Annex F Main Appendix 2-2 Generic Geometry Rules Appendix 3-2 Control Feature Geometry Rules Appendix 4-2 Facility Geometry Rules Appendix Action Task Geometry Rules Appendix Action Event Geometry Rules Appendix 8-2 Convoy Geometry Rules Annex E Usage Rules Usage Rules describing how to use the JC3IEDM to unambiguously represent data structures and functionality specific to Command and Control Usage Rules defining how to use the Plans and Orders structures in the JC3IEDM Description of expected content for each OIG type Overview explanation of JC3IEDM Soft Links List of JC3IEDM Soft Links (Excel spreadsheet). Annex F Geometry Rules 4