AIS To AIM Roadmap Explained 1 of 17 27 November 2014
AIS To AIM Roadmap Explained 1 of 17 27 November 2014
AIS To AIM Roadmap Explained 1 of 17 27 November 2014
Roadmap
Explained
Version 1.0
Terms
Aeronautical information. Information resulting from the assembly, analysis and formatting of
aeronautical data.
¹Database. A usually large collection of data stored in structured digital format so that appropriate
applications may quickly retrieve and update it.
Note.— This primarily refers to digital data (accessed by computers) rather than files of physical
records.
¹Information management (IM). The processes defined to ensure the collection, utilisation and
transmission of quality data that are tailored to the needs of each component of the air traffic
management system.
¹Interoperability. The capacity for diverse systems and organisations to exchange information by
transferring data and requesting remote services in a manner that requires the client system to have
little or no knowledge of the unique characteristics of the server system.
Note. — This is usually achieved by common understanding of the semantics, the syntax and the
protocols for the exchange of data.
¹Metadata. A structured description of the content, quality, condition or other characteristics of data.
____________________________________________
¹ - Not an official ICAO definition (used in the context of this document only).
IM Information Management
IP Internet Protocol
INTRODUCTION
1. This document serves to assist states in interpreting and implementing the requirements as
listed by the 21 steps of the ICAO AIS to AIM transition roadmap.
2. It should be noted that the 21 steps are linked to one another and failing to implement steps
might adversely.
3. The linkages between the steps are similar to those defined in the Aviation System Block
Upgrades (ASBU)
1. The phases of the roadmap is not required to be implemented in sequence as some of these
elements needs to be implemented in line with others
Phase 3
Phase 2
Phase 1
1. Each of the 21 positioning steps from the ICAO AIS to AIM Roadmap is furthermore described
below:
Description:
Data quality monitoring is the monitoring of data to ensure it meets the ICAO annex publication
resolution and integrity requirements. A quality management system should be implemented to
define all activities relating to processing and publication of aeronautical information in
procedures and processes.
Aeronautical data has 2 components, a static component (information that does not change
often, for example AIPs, charts, etc) and a dynamic component (information that changes
often, for example NOTAM).
The quality of data contained in these components can be measured by the implementation of
SLA’s (Service Level Agreements) between data originators and Aeronautical Information
Service providers, to track the quality of data and to measure it against the ICAO Annex
requirements.
This can only be enforced by the states regulating authority if adequate national regulations are
implemented to ensure accountability for the quality and integrity of aeronautical data.
For Dynamic data, Eurocontrol has created guidelines contained in OPADD (Operating
Procedures for AIS Dynamic Data) to ensure that NOTAM is issued in a standardised way and
to complement the ICAO Standards and Recommended Practices (SARPS) defined in Annex
15 to the International Convention on Civil Aviation and in the Aeronautical Information
Services Manual (Doc8126).
Description:
Data integrity monitoring is the monitoring of the data from originator, through the data process
chain, to eventual publication. Data integrity monitoring can be facilitated by the implementation
of processes like CHAIN (Controlled and Harmonised Aeronautical Information Network)
CHAIN is used to improve the accuracy and quality of the originated aeronautical data and its
management from the point of origination to the point of publication and to subsequently enable
enhanced processing throughout the entire aeronautical data chain.
Description:
As defined in Annex 15, AIRAC defines a series of common dates and an associated standard
aeronautical information publication procedure for States. This is to allow for the updating of
information in electronic systems like Flight Management Systems (FMS) and Air Traffic
Control (ATC) Systems.
It is essential, for both efficiency and safety, that Pilots, Air Traffic Controllers, Air Traffic Flow
Managers, Flight Management Systems and Aviation Charts all have the same data set.
AIRAC adherence can also be facilitated through the creation of multifunctional teams (Airport
companies, ANSP’s, CAA’s, Airlines, General Aviation, etc) in the planning, design and
implementation of airspace, routes, airports, etc.
Description:
Differences to ICAO SARP’s need to be clearly defined in the AIP of the state under GEN 1.7
as defined in ICAO Doc 8126, chapter 5, section 5.8.
Description:
WGS-84 standard with respect to international civil aviation must be defined in each states
national regulation to ensure compliance.
The requirement to use a common horizontal, vertical and temporal reference system is
essential to facilitate the exchange of data between different systems.
Therefore the expression of all coordinates in the AIP and charts using WGS-84 is important
and should be enforced by the implementation of national regulations.
Description:
This database must be able to exchange information based on the Aeronautical Information
Exchange Model (AIXM) with other aeronautical databases.
Description:
Data, received by AIS, should receive a unique identifier when the data is processed and
stored in the AIS database. Data should already receive a unique identifier when the
aeronautical data is entered in the data chain by the original data provider, e.g. surveyor,
PANS-OPS designer, etc. That unique identifier shall then be carried through all subsequent
processes.
The Aeronautical database should be able to use the cyclic redundancy check (CRC)
mechanism as defined in ICAO Annex 15 during the transfer of data to guarantee that the
unique identifiers are not corrupted during the process.
New information requirements coming from the Global Air Traffic Management Operational
Concept will be analysed and modelled if needed (e.g. airspace sectors, or information related
to airspace and route traffic restrictions, or generic information related to aircraft performance,
or information related to airline operators’ callsigns).
Description:
The Aeronautical Information Conceptual Model, also known as "AICM", provides a formal
description of the aeronautical information items, using a standard data modelling language.
This standard data model enables the automated processing of aeronautical information by the
end users. Automated processing of data limits the occurrence of human induced errors.
AICM forms the basis of the Aeronautical Information Exchange Model (AIXM).
P-09 — Aeronautical data exchange
Defining the syntax of the aeronautical data to be exchanged in terms of field names and types
is essential for introducing interoperability.
The exchange of data and the mechanisms to exchange or access the new digital products or
services will be defined by an exchange model. The content of the model will be driven by the
aeronautical information conceptual model (top-down) and by requirements coming from
technological choices (bottom-up); the evolution of the model will be coordinated in order to
balance the need for innovation with the need for protecting investments.
The use of the Internet as a communication media is, for example, one important bottom-up
driver in the definition of the model. The use of well-established, geographic information
standards also applied in non-aeronautical domains is another important technological choice.
Description:
The Aeronautical Information Exchange Model (AIXM) is a specification designed to enable the
encoding and the distribution in digital format of the aeronautical information, which has to be
supplied by the national AIS providers in accordance with the ICAO Convention.
A standard for an aeronautical data exchange model will ensure standardised interfaces
between the computers of both providers and users of data.
Description:
Networks utilising Internet protocol for the transmission and dissemination of aeronautical data
and information should be implemented.
This would also ensure the safety and security of information through the establishment of
network security mechanisms and firewalls.
The electronic version of the AIP will be defined in two forms: a printable document and one
that can be viewed by web browsers. Guidance material will be required to help States
implementing the web browser form of the electronic AIP in order to avoid the proliferation of
different presentations of AIP information over the Internet.
Description:
The Electronic AIP (eAIP) is a HTML version of the AIP which consists of a set of XML files. (It
is not a PDF version of the AIP. The applications used to create the eAIP must be able to
create it in accordance with the eAIP specification.
P-12 — Aeronautical information briefing
Fine tuning of the current NOTAM format by introduction of new selection criteria is needed to
improve the selectivity of the information presented to pilots in the pre-flight information bulletin.
(This can be done in Phase 1.)The combination of graphical and textual information in a digital
net-centric environment will be used to better respond to the airspace users requirements for
aeronautical information in all phases of flight when the new digital data products are specified
and made available (in Phase 3).
Description:
This entails digitalising the traditional paper based pre-flight NOTAM briefing and expanding it
to include other aeronautical information/ data elements such as charts and other graphical
products as well as metrological data and charts. This also includes using systems that have
the capability to filter data to meet specific client product requirements.
Description:
States must establish a national digital elevation model (DTM) or digital surface model (DSM)
which meets the ICAO Annex 15 requirements for terrain data.
The establishment of national regulations would ensure compliance to the terrain data
specifications in terms of accuracy, quality and resolution.
P-14 — Obstacles
The compilation and provision of obstacle data sets is an integral part of the transition to AIM.
Description:
States must establish national regulations for the controlling and monitoring of obstacles in the
vicinity of an aerodrome. These regulations should also indicate the four areas (Areas 1, 2, 3
and 4) as specified in Annex 15, chapter 10 and clearly define the process of approval of the
obstacle through the Civil Aviation Authority of the state.
P-15 — Aerodrome mapping
There is a new requirement emerging from industry for traditional aerodrome charts to be
complemented by structured aerodrome mapping data that can be imported into electronic
displays.
Description:
As all the information should already be available in AIXM, the GIS system employed by the
state should be able to display this information visually.
P-16 — Training
The training of personnel will be adapted to the new requirements on skill and competencies
introduced by the transition to AIM.A new training manual will be developed to reflect the new
competencies required.
Description:
Training requirements for AIS staff must be expanded to include the new requirements of
databases, AIXM, XML, HTML, etc.
Description:
States must implement national regulation on the requirement for all organisation involved in
aeronautical data processing and publication, to have a Quality Management System in place,
which shall manage the safety of all their services.
Description:
Agreements with data originators are usually made up in the form of Service level agreements
(SLA's). The SLA package is a series of interrelated elements to facilitate the establishment of
agreements between aeronautical data originators and Aeronautical Information Services
(AIS).
The SLA requirement must also be included into the national regulations to ensure compliance.
Now that the bandwidth of telecommunication links and space for digital storage devices are no
longer limiting factors, the move towards net-centric and system-wide information management
is becoming feasible for the wider distribution of meteorological forecast data from the world
area forecast centres in a format that will not require considerable effort for the learning and
configuration of decoding software, thereby ensuring true interoperability.
Meteorological information is essential in the compilation of pilot briefings. The transition to AIM
will include activities at both the standardisation and the implementation level to find solutions
for the interoperability of meteorological data products with the new AIM data products.
The established and implementation of an exchange model like WXXM would ensure that data
in products like METAR/SPECI/TAF/SIGMET is exchange in digital form in accordance with a
globally interoperable information exchange model which will use extensible mark-up language
(XML) and geography mark-up language (GML).
Description:
A dataset of GML and XML aeronautical, terrain and obstacle data that can be interpreted by
systems to produce a graphical representation of the applicable data
The digital NOTAM will be defined as a data set that contains information included in a NOTAM
in a structured format that can be fully interpreted by a computer system for accurate and
reliable updates of the aeronautical environment representation both for automated information
equipment and for aviation personnel.
Description:
A dataset of AIXM / XML encoded NOTAM that can be exchanged through multiple media and
with multiple systems for the updating (temporarily or permanent) of “published”/stored data.