AIS-AIM Study Group Working StatusICAO Seminar on Transition to AIM –Phases 1‐3 • the re‐development of chapters 4 to 11 with the objective of restructuring the annex and creating

International Civil Aviation Organization

AIS-AIM Study GroupWorking Status

Roberta LuccioliTO/AIM

ICAO Seminar on Transition to AIM – Phases 1‐3Seminario de la OACI sobre la Transicion al AIM – Fases 1‐3

2

Outline

ICAO Seminar on Transition to AIM – Phases 1‐3

• Development and Implementation of AIS‐AIM Transition

• AIM Operational Concept

• Annex 15 and PANS‐AIM Development

• AIM Domain Functions

• AIM Quality, Data Integrity

• Aerodrome Mapping Database (AMDB)

• Notam

• Summary

• Charting

3

Development and Implementation of AIS‐AIM Transition (Agenda item 1.2)


NEED FOR AN AIM OPERATIONAL CONCEPT

The current Roadmap for Transition from AIS to AIM had an intended implantation horizonof 2016. Moreover, it was noted that the activities associated with the current roadmap fallshort of a full AIM capability, instead providing a path to digital provision of current AISproducts and services. It was emphasized that the articulation of any new roadmapshould serve as an extension to the current roadmap and that it was not to represent achange in direction. In this connection, the current roadmap serves as the evolutionarybeginning of an eventual full transition to an AIM service fully integrated with other ATMservices and functions.

4

AIM Operational Concept


Aeronautical information:

• is digital • is safe, secure and quality‐assured • is part of the network‐centric environment (e.g., SWIM) • can be digitally stored, managed, and displayed (in textual and/or graphical format) • can be digitally disseminated (via ground network and various data links) • is integrated and readily integrate‐able with other information domains • is increasingly harmonized (including data definitions, data models, data formats, etc)

the closer we get to the aircraft • has temporality (Planning and Reference, Pre‐flight, In‐flight and Post‐flight) • supports the needs of the ATM community, and the AIM actors in particular • is adequate for its intended multiple uses, including operational decision making • is usable by automated Decision Support Tools and Expert Systems

KEY PRINCIPLES…

As an operational concept it represents a view of future functions, benefits and operatingmodalities.

5ICAO Seminar on Transition to AIM – Phases 1‐3

• AIM actors are controller, pilot, dispatcher• Objective is to achieve shared situational

awareness for collaborative decision making• AIM is user‐centric and focused on

(trajectory‐based) operations• AIM temporalities include Planning and

Reference, Pre‐flight, In‐flight, and Post‐flight

KEY AIM CONCEPTS…

• In‐flight use requires near‐real time updates for operational decision making • AIM for post‐flight phase to extend current AIS paradigm (improving data integrity) to

Performance Based Methodology (closing the loop) • AIM extends AIS and builds foundation for Knowledge Management • Notion of Single Authoritative Source (SAS) to help avoid potential data duplication and

fragmentation • AIM as part of a network‐centric environment



• The current AIM OPERATIONAL CONCEPT document does not include a transition plan.Transition in part would be covered by the application of the Aviation System BlockUpgrades (ASBU);

• the AISAIMSG/6 agreed that the transition considerations will be incorporated once theconcept is considered mature and that the transition would extend from the end of thecurrent roadmap and be in coordination with the ASBUs;

• need to fully articulate the scope of the AIM information and data domain, the role that AIMis intended to fulfill, and the functions that AIM is required to perform;

• the document should be able to give the reader a fuller understanding of the change thatwould be in place once a change to AIM is in place;

• need to show AIM functions showing the relationship to other entities (e.g. informationsources); the “arrows” providing a functional connection between entities and representingprocesses and procedures connecting the data and information flows are processes that areessentially part of AIM.

NEED TO IMPROVE…


7

Annex 15 and PANS‐AIM Development(Agenda Item 2.2)


• the re‐development of chapters 4 to 11 with the objective of restructuring the annex and creating the structure to accept new material.

• Chapter 4 ‐ Data and Information Scope • Chapter 5 ‐ Temporality and Distribution • Chapter 6 ‐ Information Services

• What is the Scope of AIM ? • What is the role of AIM ? • What are the functions of AIM ? • What are the Products and Services of AIM ? • What is the future of messaging and operational reporting? • What is the future of the AIRAC cycle?

After Amendment 37, the focus on Annex 15 will be…

Big questions to be addressed to complete the evolution of Annex 15 …

The provisions contained in the Annex become more performance oriented while the moretechnical specifications, to the extent that they are needed would be found in otherdocuments..


Minimum data Ad‐hoc sub‐group dedicated to the development of a draft general text describing the minimum data scope to be specified for provision by annex 15.

TemporalityAd‐hoc sub‐group dedicated to investigate thefactors and aspects concerning temporality ofaeronautical information and data and develop anapproach to guide the development of provisionsfor Annex 15 and the draft PANS‐AIM.

AIM servicesAd‐hoc sub‐group dedicated to develop a draft listof AIM services that will be considered forinclusion in Annex 15 Amendment 38.

Annex 15 and PANS‐AIM Development(Agenda Item 2.2)

9

AIM Domain Functions (Agenda Item 3.1)


• The concern is that the phrase “receive and/or originate” incorporated inparagraph 3.1.7 could infer an obligation on AIS to acquire information directly,for example by aerodrome survey, if it was not in “receipt” of such information.

• There was concern that removal of the term could also generate undesirableconsequences. Specifically, it was expressed that if “originate” was not included inthe list of AIS functions, it could be interpreted in some States that functionsassigned to an AIS could not include origination and that this could be problematicin some States.

ANNEX 17 – AMD 37: “and/or originate” taken out

On going discussion about the AIM FUNCTIONS:

• “and/or originate” in conjunction with “receive”.

Note.— An Aeronautical Information Service may include origination functions.

10

AIM Quality (Agenda Item 4.1)


Why AIM Quality is important…

•For all States which have been embracing the shiftfrom AIS to AIM, it is considered fundamental to theevolution, that phase 1 of the Roadmap for theTransition from AIS to AIM be fully implemented. Inparticular, it is observed that AIRAC compliance,WGS‐84 implementation, and the implementation ofquality management systems are elements that stillpersist in some states as requiring attention. Theimplementation of these changes is fundamentaland required for the migration of AIS to AIM.

•


• the expense involved in implementing a recognised QMS system particularly one requiring external registration and certification authorities and auditors as required by ISO 9000.

• many states have difficulty assigning the resources necessary to implement QMS. This wasattributed to the lack of support from Senior and executive management in Civil AviationAdministrations and provider organizations.

AIM Quality (Agenda Item 4.1)Problems in implementing a QMS…

• Importance of the quality management guidance and evolving to the need to assist someStates in implementing quality management systems;

• Implement QMS with greatly reduced cost. QMS implementation is not restricted to ISO9000. Some states may benefit from taking a “home grown” approach or throughcollaboration and sharing of resources with neighbouring states;

• AIS Quality checklist (Eurocontrol) that could serve as an entry point for States to implementa QMS capability. The checklist will be incorporated into the Quality Manual;

• ICAO might outreach to States in order to encourage the implementation of an organizedQMS system.

Recommendations…


• Discussion on the definitions of validationand verification in Annex 15 and theproposed development of procedures forthe correct application of validation andverification processes throughout AIMoperations.

• The AISAIM SG affirms the importance ofvalidation and verification procedures and thecentral role they play in quality managementsystems. The group expressed the need forguidance with respect to validation andverification procedures and the relevancewithin a quality management system.

AIM Quality (Agenda Item 4.1)

VALIDATION AND VERIFICATION PROCEDURES


• Numerical Values Deleted

• The deletion of the numeric values associatedwith data integrity would still leave the integrityclassifications of “routine, essential, and critical”.

• The integrity classifications assigned to datafeatures would need to be accompanied by processand procedure requirements appropriate to dataand information handling for each classification.The development of these procedures would be animportant feature of the new PANS‐AIM and wouldalso require guidance in Doc 8126.

Data Integrity (Agenda Item 4.2)


• The draft criteria introduced in Annex 15 represented a considerable investment of work and contained a thorough list of aerodrome Operational factors.

• One aspect missing is an assessment of equipment and applications that could use the data and an estimate of safety benefits to be achieved after availability of the data and at the percentage of estimated users.

• As the criteria matured, it should be incorporated in the eTOD manual or a futureeTOD/AMDB manual

Aerodrome Mapping Database (AMDB) –Agenda Item 5.2

15

Numerical Requirements (Agenda Item 5.3)


• Need of revisions to the World Geodetic System 1984 (WGS 84) Manual (Doc 9674) to provide guidance on the use of vertical reference systems. The issue of vertical reference is of increasing relevance, especially considering requirements such as eTOD. • The WGS‐84 manual is out of date in several areas but none so immediately relevant as vertical reference

• Changes should be made to the provisions concerning vertical reference systems in amendment 38 to Annex 15. The draft proposals for amendment should be developed in consultation with someone with the requisite expertise in geodetics. CANSO should be approached with the objective of locating such expertise. Additionally it was suggested that ICAO approach the United States NGA with the same objective.

16

NOTAM ISSUES (Agenda Item 1.6)


• NOTAM proliferation issue. Various provisions which govern NOTAM issuance have beenreviewed, as well as an analysis that indicated that the number of international NOTAMdistributed annually between 2000 and 2011 has tripled and is predicted to continuallyincrease.

• NOTAM selection code is an early response to the proliferation issue and the developmentof Digital NOTAM will improve the ability to parse and select only those NOTAM ofimmediate relevance.

• NOTAM issues formes one aspect of an extended group of issues that encompasses global reporting format (for runway condition reporting), response to volcanic ash events, SNOWTAM, and others that were all being looked at selectively by other groups.

• Sequential numbering system used for NOTAM and the “rollover” effect that is caused byreaching the end of a 4 digit series.

• Development of a NOTAM template for the reporting of volcanic ash events to be included in Doc 8126.

17

Charting : Agenda Item 1.6.3


• Electronic version of the Aeronautical Chart Manual (Doc 8697)

• Availability of an updated manual is foreseen to improve it’s distribution as well as having a document that is more easily maintained.

• A new series of chart formats would likely be soon available as a consequence of the work of the Instrument Flight Procedures Panel (IFPP) and that a timely method to make them available is necessary.

It is possible that Annex 15 would evolve to an AIM focus, concerned primarily with theacquisition of information from accountable sources, verifying and validating theinformation and managing it’s availability for other users. In this concept, a primary focuswould be the provision of information made available through a SWIM network forintegration with information from other domains. However, not all users of informationwould access information through SWIM and that there will be a continuing need for dataand information that is assembled into AIS/AIM specific products. Certain segments of theaeronautical community would still require aeronautical charts. It is considered that apotential evolution for Annex 4 could focus on the specification of AIS/AIM products and aswell as charts Annex 4 could outline the specification for data sets assembled for specificpurposes.

18

Integration with other services (Agenda Item 1.6.7)


SWIM

Development of a paper outlining the features of a Global SWIM Concept for presentationto the 12th Air Navigation Conference. The paper has been developed in consultation withthe primary organizations in the FAA and Europe concerning SWIM development and isintended as a catalyst for further development of a globally applicable SWIM Concept.

METRTCA SC206 has developed a draft concept of use for AIS/MET datalink services that couldsubsequently be used to derive corresponding (data) specifications

FIXMFIXM development: Version 1 is intended to be releasedduring the upcoming Air Transportation Information ExchangeConference (ATIEC) to be held in Silver Spring, Maryland,United States from 28 to 30 August 2012. The work isprogressing on the integration of AIXM /WXXM / FIXM usingGML and UML.

19

Location Indicators Problem (Agenda Item 1.8)


• Current scheme of 4 letters with the first 2 normally applied as a country code only left anominal 676 codes available for most countries;

• Many States adopt other, State specific schemes, which often use a combined alphanumeric description and frequently do not result in unique identifiers.

• Problem accessing information for relevant airports and potential confusion

• Growing integration of international and State domestic ATM systems as well as thegrowth in numbers of IFR capable aerodromes the system is not providing enoughpossibilities.

• Relevant to data based procedures such as PBN and the desirability of matching theprocedure data to a unique identifier.

• No consensus reached so far

20

Summary


• GLOBAL PROGRESS UPDATE: Need to be informed of the progress of work toimplement AIM in the various regions.

• NEED FOR GUIDANCE MATERIAL:• There is a need for more guidance from ICAO;• Doc 8126, the quality manual, the training manual, and the eTOD manual are

intended to be issued by 3rd quarter of this year

• ANNEX15, AMD37:• The actual date of applicability could be influenced by other factors, including

ANC schedule, and ultimately would be set by the ANC. The group expressed itshope that a State letter may be available by late July 2012.


THANK YOU!

Documents

AIS-AIM Study Group Working StatusICAO Seminar on Transition to AIM –Phases 1‐3 • the re‐development of chapters 4 to 11 with the objective of restructuring the annex and creating