1. AIXM and AIRM Analysis
Results Summary

2. XM and AIRM Analysis
The Exchange Model (XM) and Air Traffic Information Reference Model (AIRM) Analysis:
Analyzes the semantic agreement of the ICAO XMs (AIXM, FIXM, IWXXM) with the AIRM
Uses the AIRM to identify gaps in the XMs
Provides recommendations to align the XMs with the AIRM and fill gaps in the XMs
In some cases, recommendations are made to change the AIRM instead of the XMs.

3. Methodology
The AIRM was mapped to each XM separately and the XMs were analyzed independently:
Base Infrastructure
Air Traffic Operations
Flight
Meteorology
Stakeholders
Airspace Infrastructure
Aircraft
Surveillance
Common
AIXM
IWXXM
FIXM
AIRM

4. Methodology
Analysis was broken-down into levels based on the AIRM element type:
Level 1
Mapping of the AIRM entities and objects
Level 2
Mapping of the AIRM attributes and relationships
Level 3
Mapping of the AIRM code lists and data types

5. Results Summary
Percentage of AIRM entities and objects captured by AIXM, FIXM, and IWXXM, by subject area:

6. Methodology
Based on the mappings, recommendations were made to update the XMs based on the following premises:
XM definitions should not contradict the AIRM definitions
XM definitions should read clearly, preventing interpretations that could contradict the AIRM definitions
AIRM elements that are potentially in-scope for the XMs, but not captured by them, are subject to evaluation
XM elements should be fully-captured within AIRM*
In a few instances, when the XM and AIRM definitions disagree, recommendations are made to update the AIRM.
*Since the analysis mapped the AIRM elements to XM elements, not all XM elements were considered. However based on this matching, instances where the matched XM concept is broader than the matched AIRM element were captured.

7. AIXM Recommendation Areas
Definition
Total
Improve Clarity
Changes to AIXM definitions or terminology to improve clarity, especially when compared to AIRM. 57
Model Discrepancies
Differences between AIRM and AIXM that are recommended for resolution through changes to AIXM. 15
Missing AI
AI elements in AIRM that overlap the current AIXM scope, but are not captured in AIXM. 68
Airport Mapping Data
AIRM elements related to airport mapping that are not captured in AIXM. ICAO Annex 15 recommends providing airport mapping data digitally, yet there is no current ICAO standard to capture it. 65
Flow Data
AIRM elements related to flow that are not captured in AIXM. Currently flow data is partially captured via extensions to AIXM. 3

8. AIXM Recommendations

9. Missing AI Example
AIRM
Element Name
Element Type
Element Definition
Radio Navigation Service: authority: Organisation
relationship
The authority responsible for the service.
AIXM
missing
In AIXM, Navaid Equipment has an associated Organisation Authority which represents the authority for the navaid equipment. However, the Navaid service does not have an associated Organisation Authority. The owner of a Navaid equipment and service can be designated differently in two FAA systems (FSEP and NASR). For example, the ownership of a VOR and TACAN are designated separately in FSEP, while the VORTAC service has an owner in NASR. Recommend adding a relationship from Navaid to Organisation Authority in AIXM.

10. Airport Mapping Data Example
AIRM
Element Name
Element Type
Element Definition
Runway Protect Area: name
attribute
The name of the Runway Protection Area.
AIXM
missing
The name of a runway protect area can be defined in an FAA system (AGIS) for airport mapping and is captured in the FAA AIT AIXM extensions, but is not captured in the AIXM core model. Currently, the FAA captures select airport mapping data via AIXM extensions. Recommend evaluating the use of airport mapping extensions against the inclusion of airport mapping data in the AIXM core model or the implementation of an airport mapping exchange model.

11. Elements Missing from AIXM
The Missing AI and Airport Mapping Data recommendation areas both consider AIRM elements that are missing from AIXM

12. Model Discrepancies Example
AIRM
Element Name
Element Type
Element Definition
Aircraft: ICAO Aircraft Category
attribute
Classification of aircraft according to specified basic characteristics, e.g. aeroplane, helicopter, glider, free balloon.
AIXM
Aircraft Characteristic: type
An indication of the type of aircraft.
The AIRM and AIXM attributes both capture the same concept, but use different terminology. The AIRM attribute uses "category" to define this concept, which is consistent with ICAO Annex 1. AIXM uses "type" which can be misleading when compared to aircraft type designators which are a different concept. Recommend changing the AIXM attribute to "category" to be consistent with ICAO nomenclature.

13. Improve Clarity Example
AIRM
Element Name
Element Type
Element Definition
Unplanned Holding
Entity
A specific holding procedure requested at an en-route fix on airway or route radials, bearings, or courses.
AIXM
Feature
First time a point is established in Enroute environment at a navaid, all radials are checked for holding; 360 deg. (A circle is used for assessment) If the point is a designated point, holding along the course guidance radial is checked. If no restrictions are found, holding on any radial (unplanned) is approved. If restrictions are found, holding restrictions may be noted or holding may be restricted to defined holding patterns.
The AIXM definition for Unplanned Holding reads like a set of instructions for unplanned holding instead of a definition like the AIRM representation. The AIXM definition is also generally unclear. Recommend changing the AIXM definition to the AIRM definition for unplanned holding.

14. AIRM Elements Mapped to AIXM
The Improve Clarity and Model Discrepancies recommendation areas both consider recommendations based on AIRM elements mapped to AIXM

15. Flow Data Example
AIRM
Element Name
Element Type
Element Definition
Airport Slot
Entity
The scheduled time of arrival or departure available for allocation by, or as allocated by, a coordinator for an aircraft movement on a specific date at a coordinated airport. For scheduling purposes, the slot is the scheduled time of arrival or departure at the terminal, not the time of landing or take-off from the runway. An allocated slot will take account of all the coordination parameters at the airport e.g. runway(s), taxiways, aircraft parking stands, gates, terminal capacity (e.g. check-in and baggage delivery), environmental constraints e.g. night restrictions etc.
AIXM
missing
Airport Slot is flow data not captured in core AIXM. Currently, the FAA captures select flow data via AIXM extensions. Airport slot data is currently captured in the AIXM Traffic Management Initiative (TMI) extension. Recommend evaluating the continued use of flow extensions against the inclusion of flow data in the AIXM core model or the implementation of a flow data exchange model.