Review of 2007 South and Central America AIXM workshop

1. Review of 2007 South and Central America AIXM workshop AIXM Seminar at ICAO Tegucigalpa, Honduras Federal Aviation Administration May 2009

2. Agenda • A need for AIXM • Global AIM community • History of AIXM • AIXM5 concepts • Case studies

3. A Need for AIXM • Current AIS information exchange was based on procedures and needs for the teletype era. • Error prone (both human and computer) as well as inefficiencies • The goal for AIXM 5 is to provide an extensible, modular aeronautical information exchange standard that can be used to satisfy information exchange requirements for current and future aeronautical information applications

4. Global AIM community • Global recognition that AIS is the key to global interoperability • Global recognition that aeronautical information is crucial to realize a safe and efficient air traffic system • Adopt the Aeronautical Information Exchange Model • Examples are: FAA, EUROCONTROL, NAVCANADA, etc.

5. History of AIXM AIXM is a standard for aeronautical information dissemination that has been based on: • ICAO Annex 15 “data to support international air navigation” • Industry standards like ARINC 424 (for encoding terminal procedures) • Other standards and best practices • Real world aeronautical information publications It also took into consideration aspects that are not subject to formal requirements: • Examples: route usage restrictions, declared distances from runway/taxiway intersections, airspace aggregations, fuel types, etc. • AICM (the conceptual part of AIXM) - Started by Eurocontrol in 1996 • AIXM – started in 1997 • First attempt “SQL based” • Move to XML in 1999 • EAD operational since 2003 – All European States are expected to have joined the EAD by end 2008

6. AIXM5 concepts Technical Design Decisions • AIXM5 design decisions are based on the adoption of a number of international standards: • Use GML (Geography Markup Language) for encoding geographical information – positions, areas, routes, etc. • As opposed to the custom geometry encodings used in the current AIXM 4.5 • Use the ISO19100 series of geospatial information standards as data modeling framework • This would maximize the chances of cross-domain interoperability • Use UML (Unified Modeling Language) for developing AIXM 5 Conceptual Model • Closely linked to the ISO 19100 modelling framework, the requirement for exhaustive metadata incorporation into the model has been identified ISO19100series UML GML 3.2 Metadata Integrity Data Quality Mandates

7. Case studies • A number of case studies were presented in Lima • EUROCONTROL presented xNOTAMS • In 2007, the project was in the “initiation” phase, which was going to be followed by an evaluation of the feasibility and a planning phase, and start implementation by 2011-2012. • FAA D-NOTAMS • The initial POC for D-NOTAMS was presented in the conference. An initial formulation of the AIXM protocol was discussed within the context • AIXM Viewer • An AIXM viewer developed by the University of Maryland was demoed to show how to interpret the model in a geospacial environment