Introduction to AIXM The purpose of this briefing is to present the evolution of AIXM from a specification intended to support AIS automation and static data exchange in Europe, to a global standard, covering the full scope of the aeronautical information, both permanent and temporary. During this evolution, AIXM has always tried to adapt and use the latest relevant standards, starting from entity-relationship and XML to UML, ISO 19100 and GML.

Topics Criticality of AIS information AIM – a “data centric” approach Worldwide interoperability AIXM mission Related developments In this briefing I will cover the following topics: Highlight the criticality of the aeronautical information in the current and future aviation domain AIS to AIM. An introduction to the transition from providing traditional AIS to supporting a range of user requirements through AIM (Aeronautical Information Management). Worldwide implementation of AIS interoperability. The mission that AIXM wants to accomplish, by supporting the “AIM Concept” Related activities, such as the AIS Data Link and the NDBX industry committees AIM = Aeronautical Information Management AIS = Aeronautical Information Services AIXM = Aeronautical Information eXchange Model

Aeronautical information criticality Data quality? Information provided by AIS is used for air navigation, ATC, ATM and other related services, which are essential to the safe movement of aircraft on the ground and in the air. It has been identified many years ago that: “The role and importance of aeronautical information/data changed significantly with the implementation of area navigation (RNAV), required navigation performance (RNP) and airborne computer based navigation systems. Corrupt or erroneous aeronautical information/data can potentially affect the safety of air Navigation” [ICAO Annex 15]. On the ground and in the air, the quality and certification of aeronautical information shall be comparable with the quality and certification levels of physical aircraft components, spare parts, fuel, etc..

Aeronautical Information Management State 2 AIP, charts, etc. State 1 Data management NOTAM bulk data upload data update services AIP, charts, etc. Data management NOTAM ARO NOTAM Briefing eAIP, iPIB Applications Data Service Provider AIP State 3 AIP, charts, etc. NOTAM Standards AIXM Regional database In order to ensure the quality of the aeronautical information originated by the States and also to improve cost-efficiency, automation started being introduced in the AIS world, in two directions: inside AIS – database based products – charts, AIP, NOTAM, etc. [Islands of data management] inter-AIS – Interoperability through data exchange/sharing [system wide perspective on information management] When we look at a simplified picture of the data chain, information flows are increasingly complex and involve many actors. Aeronautical information is complex with multiple suppliers and consumers, interconnected systems and the need for real time information. High quality, easy access to aeronautical data, based on world-wide agreed standards is needed if we want to ensure: the quality of the aeronautical information required by modern air navigation and ATC systems the efficiency and the cost effectiveness of the system AIXM, the main subject of this presentation, has emerged from the need of the European States to implement regional AIS interoperability. DATA AFTN (low bandwidth) AIP Surface mail

Role of models in AIM AIM System Classical AIS AIP - manage data - publish traditional and new products - accurate and fast exchange Classical AIS - publish documents SUP, NOTAM, AIC AIP Document content and format is described by: - ICAO Annex 15, Appendix 1 – AIP Content - ICAO Annex 15, Appendix 6 – NOTAM format - ICAO Annex 4, Aeronautical Charts - FAA forms Data managed in the system is described by models: - ARINC 424 - Aeronautical Information Exchange Model (AIXM) - Electronic AIP (eAIP) Specification - Airport Mapping Database (AMDB) - Terrain and Obstacle Database - New products… The world today: business processes and computer systems Moving from paper-based system ==> electronic based one will help all actors in the data chain reference the same data in the same format, promoting accurate and fast exchange Paper products are based on checklists. AIM is based on models and data formats. ARINC 424, AMDB, terrain & obstacle databases are limited in scope – focused on a particular application, a particular product or a data category. The aim of AIXM is to be applicable to a wide range of applications, with an exhaustive coverage of the aeronautical information domain. It is a data management specification, which can improve the internal and the external processes.

Purpose of AIM Improve internal processes Streamline data management and product maintenance Model aeronautical information as a whole Create AIS products from a single data source Ability to integrate workflow and configuration management AIS Office Inside an AIS organisation, the AIM goal is to improve aeronautical data quality and make it quicker and easier to provide data and products to users. By using the same data source to provide information for all products, they become more accurate and consistent allowing AIS operations to become more efficient. The AIM data source meets internal and external needs and streamlines data management and product production. Static and temporary data can be managed seamlessly and product creation engines can be used to create products from a single data source. Products Data management Product Creation Engines

Purpose of AIM Improve external processes AIP AIP NOTAM NOTAM Now, let’s look from another angle at the complex picture presented in a previous slide. If we consider the 3 basic roles in the aeronautical information chain: the data originator (airport in this image) the AIS office (issuing the ‘official’ information - AIP, NOTAM) the service provider (combining the ‘official’ data from different geographical sources and providing services to end users (pre-flight briefing, flight planning, flight manuals, navigation charts, etc.). Note that the service provider could be a commercial company, the briefing office of the Air Navigation Service Provider organisation, etc. It is just a role, not an actor. Traditionally, the information exchange between the 3 roles was through (paper) documents. With the introduction of the automation and databases, the content of these documents is imported/managed/exported at every step, in and out product-oriented databases. Even more recently, these databases have started to become data oriented, organisation-wide. But the exchange between the roles remains through documents/products. This is inefficient and error-prone. The complete “AIM” solution is to do the data exchange inside the digital data layer and not outside it. This is the AIXM role: to enable exchanging the full scope of aeronautical data, both permanent and temporary, in a single exchange format, which can be used to automate both the internal and the external processes. “data layer”

Data modeling is important Role of data models To represent real world concepts as a theoretical construct which can be represented and understood by automated systems To standardise the conceptual understanding of aeronautical data by all actors - “speak the same language" To provide a basis for logical data structures used during the software implementation To provide basis for formal ‘contracts’ between interoperable systems – example: “use the same format" The success of AIM depends directly on the correctness and completeness of the model used to represent aeronautical data.

AIXM – the first versions Sources AIP 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

AIXM - Internationalization Complete Data Model (Military/Civilian) Global Requirements Standards (ISO) The internationalization of AIXM really began in 2003 after the release of version 3.3. Set-up of the AIXM Change Control Board (ACCB) with international participation (States and industry) The United States Federal Aviation Administration, United States National Geospatial Intelligence Agency and EUROCONTROL began to collaborate on expanding AIXM to cover global civilian and military aviation needs. Major early activities included assessing AIXM model coverage and updating lists of values. In SEP 2005 AIXM 4.5 was released. This was the first release that incorporated suggestions from the international community and was a good test of consensus based configuration management.

AIXM 5 - Global Standard AIXM We think the future of AIXM as the global standard for aeronautical data is very promising. States outside Europe, such as Japan, Canada, United States have decided to base their new AIM systems on AIXM. The Global AIS Congress, which took place in June 2007 and gathered representatives from more than 90 States world-wide, has adopted a number of recommendations. The first one asks: “ICAO adopt the AICM/AIXM as the standard aeronautical information conceptual model and the standard aeronautical information exchange model, and develop appropriate means of compliance, and global mechanisms to manage and develop the AICM/AIXM” In order to match the expectations of the global AIS community, an AIXM Design Team, organised in cooperation between EUROCONTROL and FAA, with the support of the international community, is developing the next AIXM version 5. This shall fully satisfy the global AIM needs.

Mission Based on global aeronautical data requirements ICAO standards and practices Industry requirements Modular and extensible Support current and future AIM information system requirements Digital AIPs Automated charting and publications Integrated digital NOTAMs Aerodrome Mapping Databases and applications Situational displays Etc. 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. These applications include: Automated production of Aeronautical Information Publications (AIPs) Automated aeronautical chart creation and publication systems Integrated NOTAMs (e.g., xNOTAM) Aerodrome Mapping Databases (AMDBs) and related applications Electronic Flight Bag data requirements Cockpit situational displays and Flight Management System (FMS) data requirement

AIXM components Conceptual (content) Model Exchange format specification AIXM support AIM in two ways: The AIXM conceptual model describes the features in the aeronautical domain and can be used as the logical basis for AIM databases. Does this mean that your AIS database must copy the AIXM UML model? No, but the class definitions are derived from ICAO and industry requirements so your system should have similar aeronautical features and properties. By ensuring that your systems can map to the conceptual model, you are making it easier for your system to communicate using AIXM. The AIXM XML Schema is an exchange format specification for aeronautical data, which can be used to electronically transmit aeronautical data to others. It is positioned as an international standard for aeronautical data exchange between systems. In version 3 and 4, the conceptual model was using entity-relationship methodology. This has now been replaced by UML in version 5. The encoding was always based on XML, but in version 5 it also becomes compliant with the Geography Markup Language (GML).

Scope Aerodromes Routes Airspace Procedures NAVAIDS & Fixes Obstacles EnRoute Airspace Route Terminal Fix Procedures Service Airport/Runway Airport/Runway Aerodromes Airspace NAVAIDS & Fixes Routes Procedures Obstacles Organizations & Services The AIXM conceptual model contains the definition of the features that are part of the aeronautical information domain. This includes: Aerodromes, runways, taxiways, aprons, facilities, ground services, etc. Airspace structures and their usages Navaids and points used for air navigation Routes Arrivals, Departures and Approach Procedures Obstacles Organisations and Services The intention is to cover the complete content of the Aeronautical Information Publications (AIP), their Supplements but also NOTAM information

Temporal scope AIXM 3.3 The aeronautical information is traditionally and conceptually split into static (permanent) and dynamic (temporary). The versions 3 & 4 of AIXM have covered the static data part. This enables digital charting, digital AIP production. The big step forward in version 5 is the coverage for temporary data. This enables the creation of digital NOTAM. Consequently, this can greatly improve the means by which the pilots and the controllers are made aware of the latest status of the environment in which they operate. This slide presents the proposed deployment of version 5 in the European region.

Why digital NOTAM TWY closure Today, published as NOTAM A0874/03 NOTAMN Q) EBBU/QMXLC/IV/M/A/000/999/5054N00429E005 A) EBBR B) 0308250500 C) 0310271600 E) TAXIWAYS OUTER 7 AND E6 CLSD Not possible for a computer to identify automatically which TWY is closed NOTAM is intended to be read and understood by humans, not by machines; unreliable to ask a computer to interpret the free text field <OK for computers> <not OK for computers> Just as an appetizer for the second day of the conference, which will be largely dedicated to the digital NOTAM concept, the next few slides briefly present the AIXM solution for computer interpretable temporary data. At every moment, there are some 18 000 international NOTAM in force around the world. In one hour, another 20-25 NOTAM will be issued, replaced or cancelled. What kinds of information do NOTAM contain: Runway closure (the most common type of NOTAM) Other situation affecting a runway Danger Area activation Various situation affecting an aerodrome Taxiway closure etc. Obviously, NOTAM are essential, indeed critical, for the safety, regularity and efficiency of international air navigation. The NOTAM system was designed more than 50 years ago and the messages are intended to be read and interpreted by humans (briefing officers, pilots, air traffic controllers, flight dispatchers, etc.). Since their introduction, the ICAO efforts to improve the system have been oriented towards adding codes that allow better storage and selection of NOTAM messages. However, the most meaningful part of the NOTAM information has remained free text, a loosely structured message.

AMDB/xNOTAM Study Gap Analysis ED-99A – AIXM and Prototype AIXM 5 schema Validation of AIXM temporal model Validation of results in real scenario in flight simulator Use AIXM 5 message to announce temporary change Visualise change information on cockpit display “static” database When NOTAM information is available in digital format and may be processed by computers, this enables advanced applications, such as updating the on-board electronic aerodrome maps with temporary information (obstacles erected, taxiway closed, etc.). A simulation of such an application was executed for EUROCONTROL by the Technical University of Darmstadt in 2006. This will be presented in mode detail during the second day of the Conference. Digital NOTAM Digital NOTAM Decoder

WG-76/SC-206 Industry requirements for AIS Data Link Objective EUROCAE WG 76 jointly with RTCA SC 206 Objective Identify AIS and MET Data-Link services that are envisaged to be implemented within the next decade in both Europe and USA Develop the Operational Service and Environment Definition (OSED) document, Safety and Performance Requirements (SPR) and Interoperability Requirements (INTEROP) Related to the concept of digital and graphical NOTAM, on the end user side of the aeronautical information data chain, the industry is working on defining specifications for new services and products, that will benefit from the digital data output of the States. For example, the industry is defining standards for new on-board services, via data link: Upload of “graphical NOTAM” Upload of MET information Etc.

ARINC NDBX AIXM(XML) The Navigation Data Base Open Standard (NDBX) Subcommittee has been set-up by ARINC in order to develop a new standard for Flight Management System (FMS) data upload, as a successor to the aging ARINC 424 Specification. More information about this initiative is available on the ARINC Web site: http://www.arinc.com/aeec/projects/ndbx. The new NDBX standard and its interface with AIXM could greatly simplify and increase the robustness of the data process, as shown in the diagram at the bottom.

Conclusion SC-206 Service Provider AIXM AIXM NDBX, ARINC - 816 AIS Data Link services SC-206 Ground upload NDBX, ARINC - 816 AIP AIP NOTAM NOTAM Service Provider All these emerging standards must be correlated, so that they create a harmonious concept of operations. AIXM AIXM

Conclusion AIXM provides international standardization Content model: UML class definitions for features, attributes, data types, associations & business rules Exchange format: XML/GML encoding Enables transition from AIS to AIM New services and products (e.g., digital NOTAM, NDBX) AIXM is flexible and extensible AIXM working to satisfy industry requirements To conclude, AIS Data Standardization is required if we are going to improve and integrate the aviation system. AIXM provides international data standardization. Using AIXM will reduce development costs and reduce quality assurance costs. Using a common format for data can improve safety because all systems have a clear understanding of the data. If we can provide a conceptual model that represent real world concepts and standardize the understanding about a domain, we stand to gain several benefits: Improved safety: Reduced data inconsistencies. Computer interpretable means fewer errors for pilots and other aviation system users. Reduced costs: eliminating redundancies and rework. By enabling digital input and output, we can reduce data quality checking and data integration costs.