428. Interoperability standards for COI services will have to be determined based on commonly agreed Mission Threads such as Battlespace Awareness, Joint Fires, Joint ISR or Medical Evacuation.
| ID:Purpose | Standard | Implementation Guidance |
|---|---|---|
| 1:General definition for the Representation of Dates and Times. | Mandatory:
ISO 8601:2004 - Data elements and interchange formats -- Information interchange -- Representation of dates and times |
Implementation of the W3C profile of ISO 8601:2004 (W3CDTF profile) is recommended. |
| 2:General definition of letter codes for Geographical Entities | Mandatory:
Agreed alpha-3 (three-letter codes) . The following alpha-3 codes shall be used to identify international organizations and their sub-ordinated entities:
|
Whenever possible, alpha-3 (three-letter codes) should be used.
Alpha-3 codes “XXA”, “XXB”, “XXC”, “XXX” shall not be used to avoid potential conflicts with ISO/IEC 7501-1. |
| 3:General definition of letter codes for identifying Nationality of a person | Conditional:
When 3-letter codes are being used for identifying nationality, code extensions such as XXA, XXB, XXC, XXX for special machine-readable passports as defined in
are to be used. |
ISO/IEC 7501-1 for special machine-readable passports |
| 4:General definition of geospatial coverage areas in discovery metadata | Mandatory:
NIMA Technical Report 8350.2 Third Edition Amendment 1+2: 23 June 2004, Department of Defense World Geodetic System 1984 Its Definition and Relationships with Local Geodetic Systems.
Recommended:
|
ISO 19139 provides encoding guidance for ISO 19115
STANAG 2586 includes the mandatory ISO standards, but concretizes and extends it to cope with the NATO geospatial policy. |
| 5:General definition of geospatial coverage areas in discovery metadata | World Geodetic System (WGS) 84, ISO 19115 and ISO 19136 (for point references) | ISO 19139 provides encoding guidance for ISO 19115 |
| ID:Service/Purpose | Standard | Implementation Guidance |
|---|---|---|
| 1:Expressing digital geographic annotation and visualization on, two-dimensional maps and three dimensional globes | Mandatory:
Emerging (2014):
|
NVG shall be used as the standard Protocol and Data Format for encoding and sharing of information layers
NVG and KML are both XML based language schemas for expressing geographic annotations. |
| 2:Formatted military message exchange in support of:
SOA Platform Services/ Message-oriented Middleware Services Enterprise Support Services/ Unified Communication and Collaboration Services/ Text-based Collaboration Services |
Mandatory:
STANAG 5500 Ed.7:2010, Concept of NATO Message Text Formatting System (CONFORMETS) / ADatP-03 Ed. (A) Ver. 1: December 2009. |
This change does not have any impact on existing implementations ADatP-03(A) contains two different equivalent presentations
of data: one as "classic" message or alternatively as XML-MTF instance.
|
| 3:Formatted military message exchange in in low bandwidth environments | Mandatory:
STANAG 7149 Ed. 5 NATO Message Catalogue APP-11(C) Change 1.
Minimum set of messages supported on a FMN Option A Network Element:
Emerging (2015)[a]:
|
The following message that is not compliant with STANAG 7149 Ed 5. could be accepted by a NATO FMN Network Element:
|
| 4:Exchange of digital Friendly Force Information such as positional tracking information between systems hosted on a Mission Network and mobile tactical systems. | Mandatory:AC/322-D(2006)0066 Interim NATO Friendly Force Information (FFI) Standard for Interoperability of Force Tracking Systems
(FFTS).
Emerging (2015): STANAG 5527 Ed: 1 Friendly Force Tracking Systems Interoperability / ADatP-36 Ed. A Ver. 1. |
All positional information of friendly ground forces (e.g. ground forces of Troop Contributing Nations or commercial transport companies working in support of FMN Forces) shall be as a minimum made available in a format that can be translated into the NFFI V1.3 format. |
| 5:Mediation Services: Mediate between the TDL and MN to provide weapon delivery assets with Situational Awareness on friendly forces. | Emerging (2016):
|
|
| 6:Real time automated data exchange such as radar tracking information between TDL networks and MN
Message exchange Over Tactical Data Links |
Mandatory:
In combination with:
|
STANAG 5516, Ed.5 is under ratification.
Link-16 data is disseminated via JREAP and ad-hoc (i.e. NACT) protocols in ISAF. The transition to a full JREAP based dissemination needs to be implemented in close coordination with FMN OPT. |
| 7:Exchanging information on Incident and Event information to support information exploitation. | Operational Incident Report (OIR) – 1.2, Sep 2011
Emerging (2014): Draft EVENTEXPLOITREP XML schema. |
This schema will be used to exchange rich and structured incident/ event information between C2 and Exploitation systems like JOCWatch and CIDNE. National capability developers are invited to contribute to the development of the final EVENTEXPLOITREP XML Schema[b]. |
| 8:Military Symbology interoperability | Mandatory:
STANAG 2019, Ed.6:2011, Joint Symbology APP-6(C). Recommended:MIL-STD-2525C, Common Warfighting Symbology, November 2008. |
Note that the different standards are not fully compatible with each other and may require mapping services. |
| 9:Digital exchange of semantically rich information about Battlespace Objects | Mandatory:
Emerging (2018):
|
Within MIP Baseline 3.1 the implementation of ADEM is optional. The FMN Service Strategy adopts a service based approach
employing loose coupling, therefore the implementation of the ADEM Pub/Sub Exchange pattern with the following schema constructs
are mandatory for the FMN:
The following schema constructs are expected to be used in Milestone 2 and an early implementation is recommended:
|
|
[a] APP-11(C) Change 2, which is satisfying urgent operational requirement and contains new message formats designed for ISAF and similar operations, was not promulgated in 2012. Their promulgation is now forecasted for 2014 with APP-11(D) (1). [b] See http://tide.act.nato.int/tidepedia/index.php?title=TP_112:_Event_Exploitation_Reports_(EVENTEXPLOITREP) |
||
429. The NATO Intelligence, Surveillance, and Reconnaissance Interoperability Architecture (NIIA) [AEDP-2, Ed.1:2005] provides the basis for the technical aspects of an architecture that provides interoperability between NATO nations' ISR systems. AEDP-2 provides the technical and management guidance for implementing the NIIA in ISR systems.
| ID:Service/Purpose | Standard | Implementation Guidance |
|---|---|---|
| 1:Storing and exchanging of images and associated data | Mandatory:
STANAG 4545, Ed. Amendment 1: 2000, NATO Secondary Imagery Format (NSIF) |
AEDP-4, Ed. 1, NATO Secondary Imagery Format Implementation Guide, 15 Jun 07, NU |
| 2:Providing a standard software interface for searching and retrieving for ISR products. | Mandatory:
STANAG 4559, Ed. 3: 2010, NATO Standard ISR Library Interface (NSILI) Emerging (2016): STANAG 4559, Ed. 4, NATO Standard ISR Library Interface (NSILI). |
AEDP-5, Ed. 1, NATO Standard Imagery Library Interface Implementation Guide, TBS, NU
STANAG 4559, Ed.2 and Ed.3 are NOT compatible with each other (No backwards compatibility). The CSD on NATO provided Network elements only implements Ed.3:2010). |
| 3:Exchange of ground moving target indicator radar data | Recommended: NATO Ground Moving Target Indicator (GMTI) Format STANAG 4607, Ed.3:2010 | AEDP-7, Ed. 1, NATO Ground Moving Target Indication (GMTI) Format Implementation Guide, TBS, NU |
| 4:Provision of common methods for exchanging of Motion Imagery (MI)across systems | Mandatory:
NATO Digital Motion Imagery Standard STANAG 4609, Ed. 3:2009. |
AEDP-8, Ed. 2, Implementation Guide For STANAG 4609NDMI , June 2007, NU |
| 5:Exchange of unstructured data (documents, jpeg imagery) | Recommended:
IPIWIG V4 Metadata Specification:2009, Intelligence Projects Integration Working Group (IPIWG), Definition of metadata for unstructured Intelligence. |