AIS-AIMSG/8-SN/14 - Attachment A
International Civil Aviation Organization
WORKING PAPER
IFPP WG/12-2-IP/xx
15/10/2013
Rev 0
Working Group 12-1
Montréal, Canada, 14 to 18 October 2013
Agenda Item: Integration
Aeronautical Data and Information Scope and Collection
DATA CENTRIC FOCUS OF ANNEX 15 IN CHAPTER 4 & PANS-AIM
SERVICES IN CHAPER 6
(Presented by Peter Rudolph, CANSO Member, Rapporteur of the Ad-Hoc
Group on Aeronautical Charting)
SUMMARY
This working paper presents a short overview about activities of the AIS-
AIMSG in relation to define an Aeronautical Information and Data Scope, and major planned concept changes in Chapter 4, 5, and 6 of Annex 15, and the introduction of the new PANS-AIM.
The working paper aims to inform IFPP about this activity.
Action by the IFPP WG/12-2 is at paragraph 4.
1.
INTRODUCTION
1.1
Since its 7 th Meeting, 14 – 18 January, 2013, in Montreal, the AIS to AIM Study
Group (AIS-AIMSG/7) advanced the work on introducing a well defined Aeronautical Data and
Information Scope in Annex 15. The detailed Feature and Attribute description will be introduced in the new PANS- AIM (Aeronautical Information Management).
1.2
follows:
The group agreed upon the alignment of the Annex 15 chapters and content as
Chapter 4 - Data and information scope
(6 pages)

IFPP WG/12-2-IP/xx - 2 -
Chapter 5 - Temporality and distribution
Chapter 6 – Information services
1.3
The Ad-hoc Group considered the need for a minimum data set or scope to support digital data exchange requirements such as in the use of the Aeronautical Information Exchange
Model (AIXM). Additionally, in consideration of extensive textual information in the current
Aeronautical Information Publications (AIP) such as for regulatory, procedural and restriction information the group determined the need to also define an information scope.
1.4
It was noted that the current Chapter 4 of Annex 15 would be revised to provide the required performance requirements for the AIM data and information scope and that a more detailed description would be provided in the PANS-AIM document.
2.
DISCUSSION
2.1
The full move into the data centric environment, as Amendment 38 to Annex 15 and
PANS-AIM is planning to do will require the definition of the data and information scope for all data as follows: a) terrain data (terrain feature types), b) cultural data (cultural feature types, c) aeronautical data (aeronautical feature types), and d) obstacle data (obstacle feature types) to make them available in form of (electronic or digital) structured data sets (features, attributes, domain values).
2.2
Data sets shall become the primary mean of data publication in order to allow verification of correctness of received data sets at the next intended user and to support further electronic processing without any future human intervention.
2.3
That verification of correctness of received data sets at the next intended user shall also be possible at AIS Offices to minimise the necessity of human intervention at AIS Offices. This is also necessary as the number of features and the level of detail of those data will increase. This requires provisions in Annex 15, Chapter 4, for data handling throughout the aeronautical data chain.
Current provisions for Originators and Users are covered by various Annexes and PANS.
2.4
Those Annexes and PANS need to be identified and the relation between the contents
of the changed Chapter 4 of Annex 15 must be updated as well. Figure 1 shows an initial approach in
showing Annexes which are valid for Originators and how the new general process could look like when introducing electronic data sets as main mean of publication.

- 3 - IFPP WG/12-2-IP/xx
Rules
•Properties
•Parameters
•Models
•Features
•…
Products
Annex 4
Thematic
Data Sets
Paper Chart
Source
• Annex 2, 3, 9
•
Annex 10, 11,
• Annex 12, 14
•
PANS-OPS
•
Others
(y)
(x)
F(x:y)
Electronic Chart
Data Sub-sets
Tables
Data Sub-sets
Books
Text
(electronic form)
Text
Products
Next
Intended
User
Origination
Whole
Data
Set
Data Management
Annex 15
PANS-AIM
Data
Super Sets v3.3
Figure 1: Data Centric Approach and Data Originator (Sources)
2.5
The introduction of a State AIS Office as AIM Authority in the AIM Operational
Concept 1 includes also the clearer introduction of “Accredited Provider(s) of AIM Information” also referred to as “Originators” or “Sources”, and “Consumers of AIM Information” also referred to as
“Users” or “User Organisations”. Figure 2 shows this process by introducing:
a) Upstream for the part of the process which refers to the Data Originators, b) Processing for the part of the process which refers to AIS Offices (Single AIM
Authoritative Source), c) Downstream for the part of the process which refers to the Users or User
Organisations.
1 As provided as Version 0.9 at the Ad-Hoc Meeting of AIM Development/8 in Brussels, 13 – 17.02.2012

IFPP WG/12-2-IP/xx - 4 - t
Figure 2: AIM Process
2.6
To raise the importance of Data Origination at Sources the different groups of
Originators shall be mentioned in Annex 15, Chapter 4, by referencing into the Annexes which are applicable to Originators already. A good example is Annex 14, which contains basically all SARPs for Aerodromes which includes SARPs for aeronautical data publication. Important here is to show clearly the relation between “Originator Annexes” and Annex 15. The Originator Annex shall define the provision for an Originator and Annex 15, on high level, and PANS-AIM, on detailed level, describes the contents.
2.7
Initially the Data Originator Groups, called “Accredited Providers of AIM
Information” in Figure 2 could be used. These are:
a) Air Navigation Services Providers (ANSPs), b) Aerodromes, c) Surveying (Terrain, Obstacle), d) Airspace Design, e) Procedure Design, f) Others.
2.8
The Ad-Hoc Group on AIM Development and the Ad-Hoc Group on Aeronautical
Charting met 1 to 5 July, 2013, in Friedrichshafen/Meersburg, Germany, and agreed that the “what” is to be collected by the State will be maintained in Annex 15, Chapter 4, while those which focus on
“how to” will be addressed in the PANS-AIM.

- 5 - IFPP WG/12-2-IP/xx
2.9
The group noted that in drafting the guidance in Chapter 4, the use of the words
“States shall ensure …” or “shall be provided” would not be appropriate because it is supposed to describe the scope of the data. A better term would be “This information shall include …” followed by a list of bullet points.
2.10
On the Downstream, Annex 15, Chapter 6 (Information Services) the group continued to define three services that would form the basis for Chapter 6 provisions: g) Service 1 = “legacy” (existing products), h) Service 2 = “data sets” (complete or thematic), i)
Service 3 = “added-value” (out of scope).
2.11
This ensures that the transition process, both, the currents services and the new services, are covered by the Annex. This is very important as the transition will take several years and the “old” and “new” system will exist in parallel.
2.12
The group discussed a key idea that if a State provides data sets under Service 2 for elements such as eAIP and certain Chart (TBD) then the State may be exempted by providing the same information as part of Service 1. The list of elements will progressively grow over subsequent
Amendment cycles. The aim is that at the end, Service 1 becomes only an option, except for the rulebook (text).
2.13
The group noted in Service 2, data stets would be categorized according to the following thematic data sets (provisionally): a) Terrain, b) Obstacle, c) Aerodrome data (general and geometry – aerodrome mapping), d) En-route, e) Instrument flight procedures.
2.14
The group recognized that updating these data sets would be critical and recommended that States shall provide updates to the issued data set by implementing an update service for operationally significant changes that allows for immediate issuance to operational users and by implementing an update to their data set according to a fixed schedule that would be described in Chapter 5 - Temporality and Distribution.
3.
CONCLUSION
3.1
This Working Paper aim to provide an overview about the approach so far taken by the AIS-AIMSG and intended for collection and provision of the data and information. The plan is to included this into Amendment 38 of Annex 15, with date of applicability 10 November 2016. The whole work shall be finalised until middle/end 2014 to support a possible AIM Divisional Meeting in
2015.
3.2
A further discussion will be held in the AIS-AIMSG about the introduction of terms like: “mandatory”, “optional”, or similar.

IFPP WG/12-2-IP/xx - 6 -
3.3
A further discussion will be held in the AIS-AIMSG about the data provision in cases where a data integrity level or a data resolution can not be met by a particular Originator but the data requirement is “mandatory”. In those cases an Originator shall provide the data supplemented by the integrity level and/or resolution valid for the data provided, if known.
3.4
The Ad-Hoc Group on AIM Development of the AIS-AIMSG felt that the IFPP
Integration Working Group (IWG) shall formally be tasked with the development of the required
Instrument Flight Procedure Data requirements.
3.5
The AIS-AIMSG aims that Features and Attributes (Baseline) completeness must be checked against other user requirements (e.g. ARINC 424, 424A, 816, 829) too.
4.
4.1
ACTION BY THE IFPP WG 12-1
The IFPP WG 12-1is invited to: a) review the approach and concept described in this WP, b) agree that the IWG shall liaise with the AIS-AIMSG, namely with the Ad-Hoc
Group on AIM Development, c)
initiate a Job Card for the tasked mentioned in 3.4, if needed,
d) note that the AIS-AIMSG/8 Meeting is scheduled 4-8 November, 2013,
Montreal, Canada, e) note that the next (winter) IWG meeting is normally scheduled in the last week of
January, in Phoenix, Az., USA, f) both meeting in d) and e) above can be used for further coordination between.
-- END --