MULTILATERAL INTEROPERABILITY … Document Library/99...MULTILATERAL INTEROPERABILITY PROGRAMME MIP IMPLEMENTATION RULES (MIR) 14 May 2009, Greding Germany

MIR – SEAWG Edition: 3.0.9

MULTILATERAL INTEROPERABILITY PROGRAMME

MIP IMPLEMENTATION RULES (MIR)

14 May 2009, 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.

MIR – SEAWG 20090514

Edition: 3.0.9

i

RECORD OF CHANGES PAGE

MIR 3.0.9 (MIP WG-30 14 May 2009)

CP Number

Date Entered

Responsible individual

Remarks

14 May 2009

SEAWG Document version identifier changed from 3.9 to 3.0.9 in preparation for release of MIP baseline 3.0 documentation.

14 May 2009

SEAWG Revised format and content of MIR Main document to conform with MIP Boiler Plate Text 3.0.3

CP-SEAWG-30475-MIR-V2

14 May 2009

SEAWG Rules for semantic encapsulation of OIGs involving ACTION


14 May 2009

SEAWG Recommendations for using context-object-item-association


14 May 2009

SEAWG Distribution of separately managed Annexes/Appendices


14 May 2009

SEAWG Unambiguously specify the size indicator for unit boundaries


14 May 2009

SEAWG Mandate different naming for replacement OIGs


14 May 2009

SEAWG Prevent use of empty string in mandatory text fields


14 May 2009

SEAWG Differences between “Undefined” “Removed” and “End”ing of Locations


14 May 2009

SEAWG Usage of object-item-comment and action-comment


14 May 2009

SEAWG Removing redundant rules from MIR Annex E Appendix 1 - Plans and Orders


14 May 2009

SEAWG Removing a non-OIG context from an OIG

CP-SEAWG-30517-MIR-v1

14 May 2009

SEAWG Cleanup MIR Annex A Glossary terms

CP-SEAWG-30422-SYM-v4

14 May 2009

SYM WP Error in geometry rules for Orchard/Plantation


14 May 2009

SYM WP Mapping issues related to unit symbols based on OWG recommendations


14 May 2009

SYM WP Mapping issues related to UAV unit symbols based on OWG


Edition: 3.0.9

ii

recommendations CP-SEAWG-30470-SYM-v4

14 May 2009

SYM WP MPR#1054: Correct Geometry Mapping for FARP and Holding Line.


14 May 2009

SYM WP CP to handle MPRs that lists editorial errors in MIR Annex G and F.


14 May 2009

SYM WP CP to handle MPRs that addresses missing BR errors in MIR Annex G and F which are similar in nature.


14 May 2009

SYM WP Way Point symbology mapping


14 May 2009

SYM WP Transit Corridor Geometry


14 May 2009

SYM WP Harassing - Correct Geometry


14 May 2009

SYM WP Missing biological and chemical alarm Geometry


14 May 2009

SYM WP Symbology QA


14 May 2009

SYM WP MPR#1054: Correct Geometry Mapping for Holding Line.


14 May 2009

SYM WP MPR 1358: Symbology QA - Part 1


14 May 2009



14 May 2009



14 May 2009

SYM WP Symbol 1.x.3.1.1.7.3.4.2. Artillery target acquisition tracked not supported


14 May 2009

SYM WP MPR 472: Have we been tripped up by the MIL-STD2525B Trip wire?


14 May 2009

SYM WP MPR 1146: TableG2-58 shows wrong geometry for CBRN-EVENT


14 May 2009

SYM WP APP6a Staff Comments modifier to JC3IEDM mapping

MIR 3.8 (MIP WG-29 12 February 2009)

CP Number

Date Entered


Remarks


Edition: 3.0.9

iii


12 Feb 2009

SEAWG New MIP Common Datafill for JC3IEDM 3.1d


12 Feb 2009

SEAWG Clarify Unit Boundary Echelon Indictor


12 Feb 2009

SEAWG Hostility mapping to APP-6A Affiliation Code


12 Feb 2009

SEAWG Representation of Notional Units

12 Feb 2009

SEAWG Updated filename and internal header version of MIR Annex D - Key Management-JC3IEDM from V6 to v3.7 (editorial only, no change to content)

12 Feb 2009

SEAWG Added list of filenames for Annexes F and G (editorial only, no change to content)

MIR 3.7 (MIP WG-28 11 December 2008)

CP Number

Date Entered


Remarks

CP-SEAWG-30336-SYM-V4

11 Dec 2008

SYM WP Establish symbology mappings as MIR Annex G


11 Dec 2008

SYM WP Fix minor errors in UNIT-TYPE symbology mapping


11 Dec 2008

SYM WP MPR 897 Correction of minefield symbology mapping


11 Dec 2008

SEAWG Update key allocation procedure text from MOP to MIR


11 Dec 2008

SEAWG Update Key Management document to reflect new MIP membership


11 Dec 2008

SEAWG Representing IEDs in current Data Model


11 Dec 2008

SYM WP Symbology for IEDs


11 Dec 2008

SYM WP MPR#909: Safe area for evasion: MIR geometry conflicts with business rule


11 Dec 2008

SYM WP MPR#1194: MIR Annex F 5-2-02 Action event geometry rules – radiological-release-event-category-code is not existent


Edition: 3.0.9

iv


11 Dec 2008

SYM WP MPR#1162: Geometry specification for minefields modified unintentionally by 3.6 annex F change


11 Dec 2008

SYM WP MPR#1190: MIR 3.6 annex F Definitions of Generic Geometry Rules


11 Dec 2008

SYM WP MPR#382: Clarify MIR Control Features 2.4f for Weapons Free Zone


11 Dec 2008

SYM WP MPR#891: MIR 3.6 annex F Definitions of Generic Geometry Rule. Need fix in geometry for action-event-category-code Turning and action-task-activity-code Turns


11 Dec 2008

SEAWG Representation of Notional Units


11 Dec 2008

SEAWG Improve layout of MJUR section 3.4 (OIGs and Organisations)

MIR 3.6 (MIP WG-27 18 September 2008)

CP Number

Date Entered


Remarks


18 Sep 2008

SYM WP Remove (move to MIR Annex H) symbology mappings from MIR Annex F


18 Sep 2008

SEAWG Re-generated MIP Common Data Fill for JC3IEDM 3.1c


18 Sep 2008

SEAWG Adding missing exception for PLN_ORDR_DISTR


18 Sep 2008

SEAWG Removal of superfluous context-category-codes from MJUR

MIR 3.5 (MIP WG-26 17 April 2008)

CP Number

Date Entered


Remarks


17 Apr 2008

SEAWG Restriction on Usage of Context-Reporting-Data-Association


Edition: 3.0.9

v


17 Apr 2008

SEAWG Clarification of usage of 'most recent'


17 Apr 2008

SEAWG Add text to empty section 4.5 in MJUR P & O Appendix


17 Apr 2008

SEAWG Corrections of faulty soft links


17 Apr 2008

SEAWG Clarify what soft links are used for


17 Apr 2008

SEAWG Clarify p-relations for COIA and ACTION-CONTEXT


17 Apr 2008

SEAWG Clarify OIG linkage and Soft Link optionality


17 Apr 2008

SEAWG Stop a superseded order


17 Apr 2008

SEAWG Associations between Orders

MIR 3.4 (MIP WG-25 31 January 2008)

CP Number

Date Entered


Remarks


31 Jan 2008

SEAWG Corrections of faulty soft links


31 Jan 2008

SEAWG Rename MIR common data fill annex to permit symbology revisions


31 Jan 2008

SEAWG Representation of Commandpost / Headquarters in JC3IEDM


31 Jan 2008

SEAWG Move rules for non-OIG Contexts from P&O appendix to MJUR


31 Jan 2008

SEAWG Representation of Unit Activity in the JC3IEDM


31 Jan 2008

SEAWG Add usage rules for the candidate-target-list sub-model


31 Jan 2008

SEAWG Specification of data types

MIR 3.3 (MIP WG-24 13 December 2007)

CP Number

Date Entered


Remarks


Edition: 3.0.9

vi


13 Dec 2007

SEAWG Restrict usage for proxy OIGs and transfer of OIG responsibility


13 Dec 2007

SEAWG Remove Open Issues/Limitations section from MIR-Annex E (JC3IEDM Usage Rules) MJUR


13 Dec 2007

SEAWG Align section 3.7.3 and 3.9.3 in MIR-Annex E (JC3IEDM Usage Rules) MJUR


13 Dec 2007

SEAWG Change MIR-Annex E (JC3IEDM Usage Rules) MJUR section 3.3 from a rule to a recommendation


13 Dec 2007

SEAWG Clarify section 4.6.5, use of ‘Is replaced by’ when creating FRAGOs


13 Dec 2007

SEAWG Change section 4.8, Changing the Status of an Order, clarify the intended use of the ORDER-STATUS


13 Dec 2007

SEAWG Restrict the use of CARTESIAN-COORDINATE in MIP Block 3


13 Dec 2007

SEAWG Restrict the use of RELATIVE-COORDINATE-SYSTEM in MIP Block 3


13 Dec 2007

SEAWG Re-generated MIP Common Data Fill


13 Dec 2007

SEAWG Removing a REFERENCE from a Plan Component


13 Dec 2007

SEAWG Allow Replacement OIGs for Error Recovery


13 Dec 2007

SEAWG Correction to the MJUR rule for specifying imprecise datetimes

MIR 3.2 (MIP WG-23 28 September 2007)

CP Number

Date Entered


Remarks


16 Feb 2007

SEAWG Add sections to describe the usage of ACTION-CONTEXT (CP was not fully included in the post-WG-21 release)


28 Sept 2007

SEAWG Editorial corrections to MIR 3.1


28 Sept 2007

SEAWG MIR Annex A Glossary revisions


Edition: 3.0.9

vii


28 Sept 2007

SEAWG MIR revisions


28 Sept 2007

SEAWG Removal of restriction – Plan-Order-Component-Structure


28 Sept 2007

SEAWG Obsolete Semantic Encapsulation Example


28 Sept 2007

SEAWG Handling removal of Plan Components and sub-Components


28 Sept 2007

SEAWG Semantic Encapsulation of OIGs

MIR 3.1 (MIP WG-22 01 June 2007)

CP Number

Date Entered


Remarks


01 June 2007

SEAWG Replace the contents of the MJUR Appendix 3 (Soft Links)


01 June 2007

SEAWG Revise ‘Definition of Most Recent’ section


01 June 2007

SEAWG Add a Business Rule for use of RPTD.ent_cat_code


01 June 2007

SEAWG Updating Common Datafill from C2IEDM to JC3IEDM


01 June 2007

SEAWG Separate FragO


01 June 2007

SEAWG Linking Plans/Orders to OIGs


01 June 2007

SEAWG Rules for Releasing an Order based on a Plan


01 June 2007

SEAWG Update the MJUR Appendix 2 “OIG Content”


01 June 2007

SEAWG OIG Content revision in line with JC3IEDM


01 June 2007

SEAWG Remove MJUR annex with Erwin extracts


01 June 2007

SEAWG Rules changing the status for a plan


01 June 2007

SEAWG Changing the Status of an Order


01 June 2007

SEAWG Superseding Plans and Orders, and Disassociating Plans


01 June 2007

SEAWG Warning Order Usage Rules


Edition: 3.0.9

viii


01 June 2007

SEAWG Prevent orphaned data in PLNORG OIG


01 June 2007

SEAWG Attaching Data to a Plan/Order


01 June 2007

SEAWG Miscellaneous updates to P&O Appendix


01 June 2007

SEAWG Update definition of SoftLinks

CP-SEAWG-30253- SYM-v4

01 June 2007

SYM WP Revision of MIR Annex F Symbology

MIR 3.0.3 (MIP WG-21 16 February 2007)

CP Number

Date Entered


Remarks


16 Feb 2007

SEAWG Editorial corrections to MJUR Main document for Block 3


16 Feb 2007

SEAWG Revise MJUR Introduction


16 Feb 2007

SEAWG Remove references to MTIR and SRS requirements


16 Feb 2007

SEAWG Add a ‘References’ section to the MJUR Introduction


16 Feb 2007

SEAWG OIG naming convention


16 Feb 2007

SEAWG Update the MJUR Appendix 2 OIG Content for Block 3


16 Feb 2007

SEAWG Add sections to describe the usage of ACTION-CONTEXT


16 Feb 2007

SEAWG Adding Plans&Orders Overview Information


16 Feb 2007

SEAWG Usage rule for physical-only update_seqnr


16 Feb 2007

SEAWG Usage rule to ensure consistency in a CONTEXT between REPORTING DATA and operational information being reported

CP-SEAWG-30166-MEM-v2

16 Feb 2007

MEM WP Remove Files from MIR Annex C


16 Feb 2007

SYM WP Initial release of MIR Annex F for Block 3


16 Feb 2007

SYM WP JC3IEDM 3.1a alignment


Edition: 3.0.9

ix


16 Feb 2007

SYM WP Quality Enhancement of MIR Annex F


16 Feb 2007

SYM WP Ordering of points in POLYGON-AREA illustrations

MIR 3.0.2 (MIP WG-20 08 December 2006)

CP Number

Date Entered


Remarks

SEAWG-CAN-2006-11-002-MIR v5

08 Dec 2006

SEAWG Usage Rules for Overlay Contexts

SEAWG-CAN-2006-11-003-MIR v4

08 Dec 2006

SEAWG Plans and Orders Usage Rules

SEAWG-GBR-2006-11-001-MIR v4

08 Dec 2006

SEAWG Add MJUR Business Rule for populating physical-only originating_org_id attribute


08 Dec 2006

SEAWG Update MIR Annex D (Key Management) to JC3IEDM


08 Dec 2006

SEAWG Restructuring MIR Annex E based on Concept CPs: SEAWG-GBR-2006-11-004-MIR v1 SEAWG-GBR-2006-11-005-MIR v1 SEAWG-GBR-2006-11-003-MIR v1 SEAWG-GBR-2006-11-006-MIR v1 SEAWG-GBR-2006-11-002-MIR v1


Edition: 3.0.9

xi

TABLE OF CONTENTS

___________________________________________________________________ SECTION TITLE PAGE ___________________________________________________________________

1 MIP VISION .........................................................................................................................................................1

1.1 MIP SCOPE ...............................................................................................................................................1

1.2 MIP MISSION ............................................................................................................................................1

1.3 MIP TASKS ................................................................................................................................................1

1.4 AIM...............................................................................................................................................................2

1.5 EXECUTIVE SUMMARY ........................................................................................................................2

ANNEX A GLOSSARY..................................................................................................................................... A-1

ANNEX B MIP WORK-AROUND RULE DEFINITIONS............................................................................B-1

ANNEX C NOT CURRENTLY IN USE ......................................................................................................... C-1

ANNEX D KEY MANAGEMENT .................................................................................................................... D-1

ANNEX E JC3IEDM USAGE RULES (MJUR) ............................................................................................E-1

ANNEX F SYMBOLOGY RULES...................................................................................................................F-1

ANNEX G SYMBOLOGY RULES.................................................................................................................. G-1

ANNEX H COMMON DATA FILL .................................................................................................................. H-1


Edition: 3.0.9

1

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 standards1.

− Harmonise with NATO and leverage other appropriate standards2.

− 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.


Edition: 3.0.9

2

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 disparate collection of rules and guidelines for

different implementation areas which have been gathered together in one place for

convenience. 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 edited by the

OWG.


Edition: 3.0.9

3

The diagram below illustrates the relationships between the MIP documents and their

intended users.

MIP Operational Handbook

MIP Operating

Procedures

MTIDP and MIP

Implementation Rules

Commander and Staff Officers

Gateway Operator

Implementer

MIP Gateway Software

MIP Gateway

GUI

Use cases

MIR-Annex A-SEAWG 20090514

Edition: 3.0.9

A-1

ANNEX A GLOSSARY

AOP-38 Allied Ordnance Publication 38

C2 Command and Control

C2IEDM Command and Control Information Exchange Data Model

C2IS Command and Control Information System

DB Database

DEM Data Exchange Mechanism

GW (MIP) Gateway

GUI Graphical User Interface

HQ Headquarters

IED Improvised Explosive Device

JC3IEDM Joint Consultation, Command and Control Information Exchange

Data Model

MCUR MIP C2IEDM Usage Rules

MEM Message Exchange Mechanism

MIP Multilateral Interoperability Programme

MIP GW MIP Gateway

MIR MIP Implementation Rules

MOP MIP Operating Procedures

MJUR MIP JC3IEDM Usage Rules

MSIG MIP Security Information Guidance

MSRS MIP System Requirements Specification

MTIDP MIP Technical Interface Design Plan

MTIR MIP Tactical C2IS Interoperability Requirement

NATO North Atlantic Treaty Organisation

NBC Nuclear, Biological and Chemical

OC Operation Centre

OIG Operational Information Group

OWG (MIP) Operational Working Group

PDU Protocol Data Unit

MIR-Annex B-SEAWG 20090514

Edition: 3.0.9

B-1

ANNEX B MIP WORK-AROUND RULE DEFINITIONS

N.B. This annex has been left empty to permit the reference to individual Annex B

appendices. These should be included in a sub-directory as separate files each

containing a distinct implementation rule. This is necessary because the rules will not

always be closely related. It will prevent the ‘hiding’ of implementation detail in

revised annexes, since each rule will be stored separately and listed below with a

date. Its main purpose is to act as a holding place for those issues which are raised

as CPs (and subsequently accepted), for which there is no suitable annex already

available. In addition, it permits the retention of the same annex lettering as was used

in the MOP for the remaining annexes. However, this annex should not be used as a

‘dumping ground’ for everything; any topic of a substantial nature should be allocated

a new MIR annex of its own.

Implementation rules are documented as appendices to this Annex B of the MIR. The

naming convention is:

MIR-AnnexB-rule name-version

Annex B contains the following files:

Procedure name Version Date Comment

MIR-Annex C-SEAWG 20090514

Edition: 3.0.9

C-1

ANNEX C NOT CURRENTLY IN USE

Annex C is currently empty following a CP to remove the MIP and NATO NBC

Message Definitions. The annex is retained without a subject title to avoid

renaming subsequent annexes.

Annex C contains the following files:

File name Version Date Comment

MIR-Annex D-SEAWG 20090514

Edition: 3.0.9

D-1

ANNEX D KEY MANAGEMENT

Annex D contains the following files:


MIR-Annex D-Key

allocation procedure-

3.0.9.doc

3.0.9 2009-05-14 This file defines a procedure for

the allocation of key range

prefixes.

MIR Annex D – Key

Management-JC3IEDM-

3.0.9.doc

3.0.9 2009-05-14 This file contains the specification

of a set of 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.

MIR-Annex E-SEAWG 20090514

Edition: 3.0.9

E-1

ANNEX E JC3IEDM USAGE RULES (MJUR)

Annex E contains the following files:


MIR Annex E- MIP

JC3IEDM Usage Rules-

3.0.9.doc

3.0.9 2009-05-14 This document captures

additional usage rules of the

Joint Consultation, Command

and Control Information

Exchange Data Model

(JC3IEDM) for implementers of

Command And Control

Information Systems (C2IS) or

mappings between the

JC3IEDM and a national data

store.

MIR-Annex F-SEAWG 20090514

Edition: 3.0.9

F-1

ANNEX F SYMBOLOGY RULES

Annex F contains the following files:

File name Date Comment

MIR Annex F Main.doc MIR Annex F Appendix 2-1 Generic geometry rules change log.doc MIR Annex F Appendix 2-2 Generic geometry rules.doc MIR Annex F Appendix 3-1 Control feature geometry rules change log.doc MIR Annex F Appendix 3-2 Control Feature geometry rules.doc MIR Annex F Appendix 4-1 Facility geometry rules change log.doc MIR Annex F Appendix 4-2 Facility geometry rules.doc MIR Annex F Appendix 5-1-01 Action Task geometry rules change log.doc MIR Annex F Appendix 5-1-02 Action Event geometry rules change log.doc MIR Annex F Appendix 5-2-01 Action Task geometry rules.doc MIR Annex F Appendix 5-2-02 Action Event geometry rules.doc MIR Annex F Appendix 8-1 Convoy geometry rules change log.doc MIR Annex F Appendix 8-2 Convoy geometry rules.doc

2009-05-14

Main document is now v3.0.9

MIR-Annex G-SEAWG 20090514

Edition: 3.0.9

G-1

ANNEX G SYMBOLOGY RULES

Annex G contains the following files:

File name Date Comment

MIR Annex G Main.doc MIR Annex G Appendix 2-1 Symbology Affiliation (Hostility) mapping rules.doc MIR Annex G Appendix 2-2 Symbol modifier field mapping rules.doc MIR Annex G Appendix 3-1 Control Feature symbology mapping rules change log - APP-6A.doc MIR Annex G Appendix 3-2 Control Feature symbology mapping rules - APP-6A.doc MIR Annex G Appendix 3-3 Control Feature symbology mapping rules change log - MIL-STD-2525B.doc MIR Annex G Appendix 3-4 Control Feature symbology mapping rules - MIL-STD-2525B.doc MIR Annex G Appendix 4-1 Facility symbology mapping rules change log - APP-6A.doc MIR Annex G Appendix 4-2 Facility symbology mapping rules - APP-6A.doc MIR Annex G Appendix 4-3 Facility symbology mapping rules change log - MIL-STD-2525B.doc MIR Annex G Appendix 4-4 Facility symbology mapping rules - MIL-STD-2525B.doc MIR Annex G Appendix 5-1-01 Action Task symbology mapping rules change log - APP-6A.doc MIR Annex G Appendix 5-1-02 Action Event symbology mapping rules change log - APP-6A.doc MIR Annex G Appendix 5-2-01 Action Task symbology mapping rules - APP-6A.doc

2009-05-14

Main document is now v3.0.9


Edition: 3.0.9

G-2

MIR Annex G Appendix 5-2-02 Action Event symbology mapping rules - APP-6A.doc MIR Annex G Appendix 5-3-01 Action Task symbology mapping rules change log - MIL-STD-2525B.doc MIR Annex G Appendix 5-3-02 Action Event symbology mapping rules change log - MIL-STD-2525B.doc MIR Annex G Appendix 5-4-01 Action Task symbology mapping rules - MIL-STD-2525B.doc MIR Annex G Appendix 5-4-02 Action Event symbology mapping rules - MIL-STD-2525B.doc MIR Annex G Appendix 6-1 Organisation symbology mapping rules change log - APP-6A.doc MIR Annex G Appendix 6-2 Organisation symbology mapping rules - APP-6A.doc MIR Annex G Appendix 7-1-01 Aircraft equipment symbology mapping rules change log - APP-6A.doc MIR Annex G Appendix 7-1-02 CBRN equipment symbology mapping rules change log - APP-6A.doc MIR Annex G Appendix 7-1-03 Electronic equipment symbology mapping rules change log - APP-6A.doc MIR Annex G Appendix 7-1-04 Engineering equipment symbology mapping rules change log - APP-6A.doc MIR Annex G Appendix 7-1-05 Maritime equipment symbology mapping rules change log - APP-6A.doc MIR Annex G Appendix 7-1-06 Miscellaneous equipment symbology mapping rules change log - APP-6A.doc MIR Annex G Appendix 7-1-07 Railcar equipment symbology mapping rules change log - APP-6A.doc MIR Annex G Appendix 7-1-08 Vehicle equipment symbology mapping rules change log - APP-6A.doc MIR Annex G Appendix 7-1-09 Vessel, other equipment symbology mapping rules change log - APP-6A.doc


Edition: 3.0.9

G-3

MIR Annex G Appendix 7-1-10 Vessel, subsurface equipment symbology mapping rules change log - APP-6A.doc MIR Annex G Appendix 7-1-11 Vessel, surface equipment symbology mapping rules change log - APP-6A.doc MIR Annex G Appendix 7-1-12 Weapon equipment symbology mapping rules change log - APP-6A.doc MIR Annex G Appendix 7-2-01 Aircraft equipment symbology mapping rules - APP-6A.doc MIR Annex G Appendix 7-2-02 CBRN equipment symbology mapping rules - APP-6A.doc MIR Annex G Appendix 7-2-03 Electronic equipment symbology mapping rules - APP-6A.doc MIR Annex G Appendix 7-2-04 Engineering equipment symbology mapping rules - APP-6A.doc MIR Annex G Appendix 7-2-05 Maritime equipment symbology mapping rules - APP-6A.doc MIR Annex G Appendix 7-2-06 Miscellaneous equipment symbology mapping rules - APP-6A.doc MIR Annex G Appendix 7-2-07 Railcar equipment symbology mapping rules - APP-6A.doc MIR Annex G Appendix 7-2-08 Vehicle equipment symbology mapping rules - APP-6A.doc MIR Annex G Appendix 7-2-09 Vessel, other equipment symbology mapping rules - APP-6A.doc MIR Annex G Appendix 7-2-10 Vessel, subsurface equipment symbology mapping rules - APP-6A.doc MIR Annex G Appendix 7-2-11 Vessel, surface equipment symbology mapping rules - APP-6A.doc MIR Annex G Appendix 7-2-12 Weapon equipment symbology mapping rules - APP-6A.doc MIR Annex G Appendix 8-1 Convoy symbology mapping rules change log - APP-6A.doc


Edition: 3.0.9

G-4

MIR Annex G Appendix 8-2 Convoy symbology mapping rules - APP-6A.doc MIR Annex G Appendix 8-3 Convoy symbology mapping rules change log - MIL-STD-2525B.doc MIR Annex G Appendix 8-4 Convoy symbology mapping rules - MIL-STD-2525B.doc MIR Annex G Appendix 9-1 Consumable Materiel Type symbology mapping rules change log - APP-6A.doc MIR Annex G Appendix 9-2 Consumable Materiel Type symbology mapping rules - APP-6A.doc MIR Annex G Appendix 9-3 Consumable Materiel Type symbology mapping rules change log - MIL-STD-2525B.doc MIR Annex G Appendix 9-4 Consumable Materiel Type symbology mapping rules - MIL-STD-2525B.doc

MIR-Annex H-SEAWG 20090514

Edition: 3.0.9

H-1

ANNEX H COMMON DATA FILL

Annex H contains the following files:


MIR Annex H - Common

Data Fill 3.0.9.zip

3.0.9 2009-05-

14

Included as delivered by the

Data Fill Manager – it consists of

two files (SQL and MOU

versions) and has been retained

as a Winzip file to prevent loss of

content.

Documents

MULTILATERAL INTEROPERABILITY … Document Library/99...MULTILATERAL INTEROPERABILITY PROGRAMME MIP IMPLEMENTATION RULES (MIR) 14 May 2009, Greding Germany