AERONAUTICAL INFORMATION SERVICES-AERONAUTICAL INFORMATION MANAGEMENT STUDY GROUP (AIS-AIMSG)

Transcription

1 AIS-AIMSG/9-SoD 25/04/14 AERONAUTICAL INFORMATION SERVICES-AERONAUTICAL INFORMATION MANAGEMENT STUDY GROUP (AIS-AIMSG) NINTH MEETING Tokyo, 21 to 25 April 2014 SUMMARY OF DISCUSSIONS 1. HISTORICAL 1.1 The ninth meeting of the Aeronautical Information Services to Aeronautical Information Management Study Group (AIS-AIMSG) was held at Ministry of Land, Infrastructure, Transport and Tourism (MLIT) Annex located at Kasumigaseki, Chiyoda-ku, Tokyo, Japan, from 21 to 25 April The meeting was opened by Paul Bosman, the member nominated by EUROCONTROL. He thanked the group for their valuable work and continued support. 1.3 The meeting welcomed Mr. Park Chun-sik as advisor from South-Korea and Mr. Chris Criswell replacing, this meeting, Mr. Greg Pray from FAA. 1.4 On the occasion of the meeting taking place in Tokyo Japan, the meeting was attended by Mr. Takashi Hatta (KSS), Mr. Yoshiyuki Mikuni (AIS Center Japan) and Mr. Yasushi Iwasawa (Tokyo Regional Civil Aviation Bureau) as advisors to Mr. Tomoya Miyoshi. 1.5 The meeting was notified that Mr. Gregory Pray, Mrs. Ai-min Meng, and Ms. Elena Stepanova, had forwarded their regrets for not being able to attend the meeting. 1.6 Mr. Paul Bosman, acted as Chairman of the meeting in accordance with his appointment established at AIS-AIMSG/ The names and addresses of the participants are listed in AIS-AIMSG/9 - Appendix A Participants. 1.8 After considering the list of papers to be presented and the provisional agenda outlined in AIS-AIMSG/9-SN/1, the meeting adopted the following agenda:

2 AIS-AIMSG/9-SoD -2- Opening of the meeting Working arrangements Agenda Item 1: Review and status of current work 1.1 Status of the work programme and review of follow-up action items Agenda Item 2: Development and implementation of AIS-AIM transition Agenda Item 3: AIM processes and requirements 3.1 Annex 15 material 3.2 PANS-AIM material Agenda Item 4: Aeronautical data and information scope and collection 4.1 Annex 15 Chapter 4 development 4.2 Development of Material for Inclusion in the PANS-AIM 4.3 etod and AMDB 4.4 Numerical requirements (including accuracy and resolution) Agenda Item 5: Information Services 5.1 Annex 15 Chapter 5 development 5.2 Development of Material for Inclusion in the PANS-AIM Agenda Item 6: Temporality and Distribution 6.1 Annex 15 Chapter 6 development 6.2 Development of Material 6.3 NOTAM proliferation Agenda Item 7: Other Business Agenda Item 8: Future work and activities Review of draft summary of discussions Next meetings 1.9 A list of study notes, information papers, presentations and flimsies issued for the meeting is given at AIS-AIMSG/9 - Appendix B - Documentation and are available on the AIM website at The group agreed that the working hours would be from 0930 and 1730 hours with a break of 1 hour for lunch.

3 -3- AIS-AIMSG/9-SoD AGENDA ITEMS: OPENING OF THE MEETING; WORKING ARRANGEMENTS 1.1 The agenda items, opening of the meeting and working arrangements are covered under Section 1: Historical The Chairman provided an overview of the AIS-AIM Study Group activities emphasizing all the results achieved to date. After contributing deliverables for the Amendment 36 to Annex15, the AIS to AIM Roadmap and a lot of guidance material, the next major milestone was the finalization of the Amendment 37 through the publication of the 14th edition of Annex 15 applicable since the 14th of November, The Chairman also noted that a corrigendum has been issued in relation to the following topics: Restoring the use of the use of the O qualifier in conjunction B and NB and removing instances of numeric integrity values that were not completely deleted in Appendix Recent different contacts between Study Group members and the ICAO secretariat indicated that guidance material is being delivered soon to the ICAO editorial section, for review, for the AIS Manual (Doc 8126), the Quality Manual (Doc 9839), the Training Manual (Doc 9991) and the Aeronautical Chart manual (Doc 8697). The Training Manual is currently being extended with additional information from other sources Further updates stemming from AIS-AIMSG proposals to etod/amdb Guidance (Doc 9881), WGS84 Manual (Doc 9674), Public Usage of Internet (Doc 9855) and PANS-ABC (Doc8400) are still being worked upon. AGENDA ITEM 1: REVIEW AND STATUS OF CURRENT WORK 2. AGENDA ITEM 1.1: STATUS OF WORK PROGRAMME AND REVIEW OF FOLLOW-UP ACTION ITEMS 2.1 The meeting noted that through State letter AN 2/2.3-14/20 States had been informed of the adoption of amendment 38 to Annex 15 with a planned application date of November Amendment 38 arises from the work of the Instrument Flight Procedures Panel (IFPP) relating to procedure design criteria and charting requirements to support performance-based navigation (PBN) as well as helicopter point-in-space (PinS) approach and departure operations. The objective of the amendment to the Standards and Recommended Practices (SARPs) relates to improving safety of PBN routes, improved clarification of SBAS and GBAS information as well as associated publication resolution and integrity classification values. 2.3 The changes to Annex 15 are in the sections Appendix 1 ENR3.3 Area Navigation Routes, AD Radio navigation and landing aids and Appendix 7 Table A7-2. Elevation/altitude/height. 2.4 It was noted that the amendment 38 does not contain in Table A7-2 the inclusion of the resolution and integrity classification of GBAS reference point ellipsoid height and LTP/FTP ellipsoid height. In an earlier correspondence between the Chairman and the Secretary indicated that this could be handled during the PANS-AIM drafting.

4 AIS-AIMSG/9-SoD -4- Action agreed 9/1 Integrate the missing resolution and integrity classifications of the Annex 15 Amendment 38 That Ruedi integrate the resolution and integrity classification of GBAS reference point ellipsoid height and LTP/FTP ellipsoid height in Chapter 4 Data Catalogue. 2.5 All outstanding actions from AIS-AIMSG/8 - Appendix C - Action items were reviewed and an up to date list is available as AIS-AIMSG/9 - Appendix C - Action items. 3. AGENDA ITEM 2: DEVELOPMENT AND IMPLEMENTATION OF AIS-AIM TRANSITION 3.1 The meeting was informed of the forthcoming Global AIM congress 2014 (Dubai, May 2014), co-organised by the International Federation of Aeronautical Information Management Associations (IFAIMA) and EUROCONTROL, hosted by Dubai Air Navigation Services and to be moderated by Michael Hohm from ICAO. 3.2 So far more than 250 participants from over 70 countries have registered with a number of people from countries not seen so far at the Global AIM IFAIMA events. Theme this year will be Implementing AIM The next generation Aeronautical Information Professionals. AGENDA ITEM 3: AIM PROCESSES AND REQUIREMENTS 4. AGENDA ITEM 3.1: ANNEX 15 MATERIAL 4.1 In response to Action Agreed 8/12 Safety Management System, the meeting was presented with AIS-AIMSG/9-SN/2 dealing with texts proposed for Chapter 3 describing Metadata and Safety Management. 4.2 It was observed that Metadata requirements currently appear in Chapter 3 and Chapter 11 of Annex 15 and a proposal was made to consolidate current references with the objective of simplifying current multiple instances. 4.3 On the proposal it was agreed that the use of the term Aerodrome Mapping data in the proposed was too specific, that the note in should be retained in the Annex 15, that the proposed section text be removed from the Annex 15 and that the items a/b/c be transferred to PANS-AIM. 4.4 Further a new section on Safety Management was proposed for inclusion in the Annex 15. The group was informed that the subject had been discussed at length at the Ad-Hoc Group on AIM Development Meeting/10, Washington, DC, USA, 4 6 February 2014 and that the source of the proposed text was as a result of information from various sources, including direct input from an Annex 19 Panel member and further input and direction from the Secretary. 4.5 To a question if the Annex 11 safety statements could be used to support the work done, it was replied that the proposed text is considered to be aligned. It was agreed to avoid the use of the term

5 -5- AIS-AIMSG/9-SoD Safety Management System (SMS) with a preference to provide safety management activities in the Annex 15 (and PANS-AIM). It was also agreed not to place the requirement in the text to a specific organisation or State. Further it was agreed to remove the two occurrences of the term as far as reasonably practicable as deemed too vague potentially leading to implementing any change and to merge the sections & Finally the terms identify/detect/assess were aligned within the proposed section and the reference to Doc 8126 was removed from Note More detail will be provided in the PANS-AIM, and the relationship between a SMS and a QMS will be looked at. Action agreed 9/2 Guidance on SMS/QMS relationship That George consults the draft Quality Manual to identify if the section on the relationship between SMS and QMS is sufficient or whether more text is required in either PANS-AIM or Quality Manual. 4.7 In response to Action Agreed 8/14 Annex 15 Chapter 9 proposal, the meeting was presented with AIS-AIMSG/9-SN/5 dealing with telecommunication requirements which currently appear in Annex 15, Chapters 2 and 9, and with a proposal to consolidate texts and move information to both the Annex and PANS-AIM as appropriate. 4.8 After a discussion it was agreed by the group that the current Annex 15 Chapter 9 shall be removed and that only the first paragraph shall be retained in the Annex (Chapter 5 Services, the exact place to be determined). The other elements will go to the PANS-AIM Chapter 5 (reference to Annex 15 Chapter 8 to be revisited). 4.9 In response to Action Agreed 8/16 Clarification of the terms Integrated Aeronautical Information Package and AIS Product, the meeting was presented with AIS-AIMSG/9-SN/6 dealing with the use of the terms Integrated Aeronautical Information Package (IAIP) and Aeronautical Information Products (AI products) and with proposals for the new Annex 15 and PANS-AIM It was noted that today, in the draft of the new Annex 15 and of the PANS-AIM, the situation with regards to the use of Integrated Aeronautical Information Package (IAIP) and Aeronautical Information Service Product (AIS product) is subjective. Moreover, none of these terms refer to digital aeronautical data and information, which is unfortunate in the framework of the transition to AIM. It was observed further that the notion of the IAIP as a package does not really fit in an AIM environment anymore It was proposed not to use IAIP anymore in the new Annex 15 and PANS-AIM and to define AI products so that they include the different elements of the IAIP as well as the digital data sets that are further described in the product related chapters of Annex 15 and PANS-AIM The meeting noted that the removal of the definition of IAIP would have an impact on many national regulations which use this term. Notwithstanding, in consideration of the whole transition from AIS to AIM, which is the purpose of the work of the AIS to AIM study group, will have a number of similar impacts.

6 AIS-AIMSG/9-SoD It was also observed that a clarification might be needed between what is digital and what is electronic once these terms start to be used in front of the term aeronautical product As a conclusion, the group members agreed to implement the option 2 described in the study note for the main reasons that it is clearer, straighter to the point, and fits well in the transition to AIM. The group agreed on the following definition of AI product : Aeronautical data and aeronautical information provided either as digital data sets or as a standardized package of predefined presentation in paper or electronic media. Aeronautical information products include: Aeronautical Information Publication (AIP), including Amendments and Supplements Aeronautical Information Circulars (AIC) Aeronautical charts NOTAM Monthly plain-language list [later deleted, see Agenda Item 5.1] Digital data sets The subgroup will work on the implementation of option 2 and on the replacement of the existing term IAIP in Annex 15 and PANS-AIM and report back identified issues (if any). 5. AGENDA ITEM 3.2: PANS-AIM MATERIAL 5.1 In response to Action Agreed 8/4 Service Level Agreement (SLA), the meeting was presented with AIS-AIMSG/9-SN/8 concerning Agreements for the Provision of Aeronautical Data and Aeronautical Information. The Study note amplified the requirement for formal arrangement for the provision of aeronautical data and aeronautical information. The paper presented the objective of such agreements and proposed some of the elements to be addressed by the formal arrangement. 5.2 A number of points as follows, were discussed and agreed to be covered by an updated version of the text. a) The general statement in the para of the study note constrained the formal arrangements to signing of agreements while the same objective could be met through the establishment of a legal framework. Therefore an introductory statement under general needed to be redrafted to create an understanding of being able to meet the formal arrangement objective through agreements and / or regulation; b) The para introduced constrains by requiring the formal arrangement be made within a legal framework while the same objective can be met outside a legal framework and the para is therefore to be removed; c) The element on Scope needed to be explicit that it was about the data scope as provided in Annex 15 chapter 4 while the quality requirements would go into the service levels; d) Under (d), a better term needed to be introduced to avoid possible confusion on aeronautical service and the service between data originator and AIS;

7 -7- AIS-AIMSG/9-SoD e) The explanations on each of the element were considered to be too brief and needed more descriptive sentences to promote clarity; f) The term change management could be interpreted as a change of systems and therefore is better named change control or modification management to the agreement; g) An element affected parties of the agreement needed to be added after Scope ; and h) For later, it is to be considered if this PANS-AIM Chapter 2 is perhaps better integrated into PANS-AIM Chapter 3 as this chapter is already dealing with processes. 5.3 In response to the Actions Agreed 8/5 AIM Principles, 8/6 Data and information acquisition, verification and validation, 8/7 Handling procedures and processes, and 8/8 Metadata processes, the meeting was presented with AIS-AIMSG/9-SN/13 containing a proposal for the PANS- AIM Chapter The study note addressed aeronautical information management processes and procedures, concentrating on the activities used to ensure quality and integrity is maintained throughout the data and information chain. A new provision concerning safety management activities was introduced with the aim of ensuring that safety considerations are addressed when transitioning from an analogue, product centric to a digital, service centric environment. 5.5 It was considered that new provisions (so not provisions moved from Annex 15) need to be carefully looked at. As a rule of thumb, it was considered that new provisions not already sourced from existing Annex 15 specifications, should be initiated as recommendations (using the operative verb should ) unless the need for a globally harmonised approach is considered essential. The same care needs to be taken before lifting material from guidance documentation to the PANS. 5.6 It was also agreed that material moved from Annex15 to PANS-AIM needed to be marked for traceability and with the corresponding part of the Annex 15 earmarked for amendment. Annex 15 Chapter 3 was uploaded on the shared working environment for maintaining such traceability. The justification of why the material needed to be moved to PANS-AIM from the Annex would be recorded in the traceability table. 5.7 It was agreed that the provisions in the PANS-AIM should be as much as possible exclusive to AIM and lengthy and generic (e.g. QMS) provisions are to be avoided as not seen to be of added value. 5.8 Taking into consideration the observations in plenary, during the break out session, Annex 15 Chapter 3 was reviewed section by section in comparison with the study note in order to create the PANS-AIM material. 5.9 Passages in Annex 15 considered as high level requirements remained in the Annex, while passages considered as a means of compliance or references to guidance material were moved to the PANS-AIM. The PANS-AIM material was then directly mapped to the Annex resulting in a one for one sequential numbering between the two documents (at least at the level of the first paragraph subdivision e.g. x.y). This one for one sequential numbering was thought to be essential for at least the cross-verification and would have to be reconsidered before final publication of the Annex 15 and the PANS-AIM.

8 AIS-AIMSG/9-SoD The study note material was then reviewed against the result of the mapping procedure in 4.9. Study note material considered as already adequately described in the Annex 15 or having no added value was not included in the PANS-AIM. Material considered as having added value was then combined with the Annex material considered as means of compliance (noted in 4.9) to create the PANS- AIM. Post meeting Secretary Note. It will be important to understand that a PANS is not a means of compliance for Annex provisions. PANS provisions are in addition to, and sometimes supplement or standalone from Annex provisions where they provide procedures, practices, instructions, and formats that by necessity, are intended to be globally harmonised. The notion of providing information on possible means of compliance is the role of guidance material The proposed new Annex 15 provisions with respect to safety management remained largely unchanged from the study note. However, the proposed new PANS-AIM material, which is intended to be a means of compliance, was edited so not to include overly prescriptive language. Post meeting Secretary Note. The PANS material if required should be of a nature to amplify the basic requirement in the Annex. Material that is not intended to be overly prescriptive and intended to provide a means (as opposed to the means) of compliance is most likely more appropriate as guidance The proposed material concerning quality management was assumed as being an extract of the upcoming AIM Quality Manual and may not be necessary for inclusion in the PANS-AIM. However, since the document is not yet published, the group decided to keep the material in place for the time being The proposed PANS-AIM material concerning the relationship between quality management and safety management was considered too detailed and redrafted. The redraft describes the notion that safety considerations are a part of quality management, resulting in a high level description of the relationship. However, since the upcoming quality manual is not yet published and is planned to contain a description of this relationship, the redraft may not be necessary for inclusion in the PANS- AIM. Post meeting Secretary Note. Safety considerations are not necessarily a part of quality management. There is a distinct relationship between the two but also considerable overlap when implemented in their respective management systems. It will be essential to clearly convey, what elements of Safety Management are considered to be implemented within a QMS and, perhaps more importantly, those that are not.

9 -9- AIS-AIMSG/9-SoD 5.14 The meeting recalled the brief overview provided by the Secretary during AIS-AIMSG/8 of the Air Navigation Commission Amendment 37 review issues with respect to CRC The meeting also recalled the following from the AIS-AIMSG/8 Summary of Discussions: CRC. The CRC specifications should be deleted from Annex 15. However, while doing this two different aspects need to be analysed: if other Annexes are affected by the withdrawal including consequential changes that may be necessary; and when taking out the CRC from the Annex, is it necessary to replace it with something else? 5.16 The meeting noted that at least Annexes 4, 10 (volume 1), 11, 14 (volumes 1 and 2) and Doc 8168 refer to CRC (non-exhaustive list). If the modification of Annex 15 proposed here below is undertaken, they will have to be updated accordingly. It has to be noted, this will be one amongst other many impacts the transition from AIS to AIM will have on ICAO documentation A high level statement was developed for the Annex 15 and more detailed text for the PANS-AIM. The following text has been added to Annex 15 instead of 3.5.2: Aeronautical digital data sets shall be protected against loss or alteration of data by the application of a data integrity protection mechanism. This shall apply to the protection of the integrity classification of data set as specified in 1.1 Definitions at "Integrity classification (aeronautical data) The following text has been added to the PANS-AIM: The data protection mechanism for digital data sets shall offer, at the minimum, an equivalent level of protection as a 32-bit cyclic redundancy check (CRC). Note - Guidance on the use of a 32-bit CRC algorithm to implement a protection of aeronautical digital data sets is contained in the Aeronautical Information Services Manual (Doc 8126). Post meeting Secretary Note. With respect to CRCs, it should be considered that while the term 32-bit cyclic redundancy check has been used, it has not been clear whether the original intention was to implement CRC-32 which is a common implementation of CRCs with a 33 bit polynomial length or whether it was really intended to implement a relatively uncommon CRC of 32 bits polynomial length. In determining an equivalent level of protection it must be established what levels are largely implemented and what might be feasible on a global basis. Moreover although the removal of CRCs will by necessity impose consequential amendments to other annexes, it should be considered imperative to engage other experts in State ANS providers and regulators as to what the appropriate level of protection should be.

10 AIS-AIMSG/9-SoD -10- AGENDA ITEM 4: AND COLLECTION AERONAUTICAL DATA AND INFORMATION SCOPE 6. AGENDA ITEM 4.1: ANNEX 15 CHAPTER 4 DEVELOPMENT 6.1 The meeting was presented with AIS-AIMSG/9-SN/12 and attachment The SN/12 summarised, that a quick research of PANS-OPS (Doc 8168), Volume II, by IFPP/IWG showed ambiguous wording for data origination requirements. PANS-OPS uses the word promulgate for providing data from the Procedure Designer to the AIS Organisation. IWG will further review this in the Summer Meeting, Paris, France, 7 11 July Peter searched all Annexes (1 to 19) for the words AIP, Chart, publish, promulgate, Annex 4, and Annex 15, to identify an indication whether any reference exists in the Annexes which might imply an provision for data promulgation to AIS according to Annex 4 or 15. The PANS 2 have not been searched so far. The search revealed that the 19 Annexes consist of 25 volumes and 21 of them are dealing in one way or the other with data origination/promulgation requirements to the AIS Organisation. In this regard it was observed that some Annexes deal in only very general terms with origination/promulgation requirements through stating that differences to the ICAO SARPs and PANS shall be published according to Annex 15. A few other Annexes, for example Annex 14 Aerodromes, deal with very detailed origination/promulgation requirements. 6.4 The discussion resulted that a detailed list of data origination/promulgation from the Annexes and PANS is needed to link them to Origination Groups and to enhance consistency between Annex 4, Annex 15 and Data Origination Annexes. Post meeting Secretary Note. The Study Group will need to examine whether the relationship between an origination Annex, vis-a-vis Annex 14, and the provisions in Annex 15 is made redundant considering the new implementation of paragraph made applicable with amendment 37. As the meeting observed, there is not an exclusive relationship between those origination domains that have related provisions for information to be forwarded to AIS (e.g. Annexes 11 and 14), and those other domains with significant obligations for information to be conveyed to the AIS provider. To provide a consistent approach, it will need to be considered whether the past practice is still necessary, and therefore will need to be expanded in those Annexes and PANS where it is possible (not catching all AIS information) or whether paragraph can be used as a more allencompassing approach. The use of origination specifications also carries the obligation ensure that concurrent changes are always made between annexes of relevant specifications. 6.5 The meeting was then presented with an updated sketch from AIS-AIMSG/7-SN/11 showing the relations between Data Originators, the AIS Organisation, and Data Users as follows: 1 The attachment is a copy of IFPP 12-3-IP/2 and can be found under the Other documents portion of the AIS-AIMSG/9 meeting documentation on the website. 2 PANS-OPS (Doc 8168), Volume I, PANS-TRG (Doc 9868), PANS-SUPPS (Doc 7030), PANS-ABC (Doc 8400), PANS-ATM (Doc 4444), Annex 10 Volume II.

11 -11- AIS-AIMSG/9-SoD Source Annex 2, 3, 4, 5, 7, 9, 10v1, 10v2, 10v3, 10v5, 11, 12, 13, 14v1, 14v2, 15, 16v1, 16v2, 17, 18, 19 PANS-OPS Origination v3.5 Rules Properties Parameters Models Features Products, Applications, Services Super Set (y) Def F(x:y) (x) Data Whole Data Set Products Annex 4 (Amd 59) Paper Chart Electronic Chart Data Sub-sets Tables Data Sub-sets Books Text (electronic form) Text Data Management Annex 15 (Amd 40) PANS-AIM (new) Thematic Data Sets Products Data Next Intended User 6.6 It was noted in the discussion that EUROCAE WG44/RTCA SC217 have now agreed on a definition of Authoritative Source being A state authority organisation or an organisation formally recognised by a State Authority to originate or publish data which meets specified data quality requirements. It is recognised that this definition allows for one piece of data to have more than one authoritative source however it is considered that the definition is linked to the relaxing of the validation requirements downstream. 6.7 Consensus was reached on the use of the following terms for usage in Annex 15 and PANS-AIM. The relationship of the terms is outlined in the following diagram (contained in AIS- AIMSG/9-Flimsy/1 to SN/12).

12 AIS-AIMSG/9-SoD -12- Originator Air Navigation Service Providers Aerodrome Operators Surveyor Airspace & Procedure Design Other Sources Collect AIS Organisation AIS Organisation Provide Next Intended User User (AIM Actor) User (ATM Community) User (Source Providers) User (Data Integrators) User (Others) t = Data Exchange Points (Formal Arrangments) a) The main actors in the aeronautical data chain are Data Originator, AIS Organisation and Next Intended User. b) The Data originators (only for usage in Data Catalogue) at the high level further break down to ANSPs, Aerodrome Operators, Surveyors, Airspace/Procedure Designers and Others. c) Overall an AIS organisation Provides data and information. This is further broken down as Publish for Paper and/or Electronic products AND Provide for Digital data sets. Further the terms Distribute (for when the AIS Organisation provides the product itself) or Made available (for when reference is made to through a service or by another organisation e.g. for Terrain data) are used. d) The term promulgate will not be further used in Annex 15 and PANS-AIM. The term collect is to be used for the process getting data from data originators. Post meeting Secretary Note. The term promulgate is used frequently in ICAO documentation. Further discussion and guidance as to it s appropriate use is required.

13 -13- AIS-AIMSG/9-SoD e) Data exchange points are the points where data is exchanged between Data originators and AIS Organisation or between an AIS Organisation and the Next Intended User. f) The terms Downstream and Upstream were not considered required for usage in the Annex and/or PANS-AIM. g) The term Authoritative Source is considered to be useful when describing overall aeronautical data chain processes and procedures. However, in the Annex 15 document the term is not considered to be required. It is proposed to include a reference from the PANS- AIM formal arrangements section to EUROCAE/RTCA documentation further detailing the Authoritative Source. 6.8 The meeting noted that while amendment 37 to Annex 15 provided strengthened provisions on data origination to AIS (e.g , and 3.2), additional provisions are considered required for Annex 15 Chapter 2 and PANS-AIM Chapter 3 (e.g. para 3.2). These provisions will specify that AIS not change data unless informing the data originators and also include statements (building from existing 2.2.6) on what to do when the data originator cannot be contacted and/or data cannot be verified/validated. It is also considered that a definition of the term Data Originator would be useful for inclusion in the Annex 15. Post meeting Secretary Note. While the intent of the new provisions is recognised, it will be important to specify the difference between a data value change versus a nominal change in resolution (deprecation only). The notion that data cannot be changed at all will be problematic considering different requirements for resolution by end users and could lead to the interpretation that differing entries for the same attribute might need to be sourced, stored and maintained in accordance with differing needs for resolution. Action agreed 9/3 Propose new provisions in order to strengthen the relationship between data originators and AIS organisations That Stephane, Arnaud (rapporteur), Peter, Bill, Fernando, Greg/Chris propose new provisions in order to strengthen the relationship between data originators and AIS organisations, especially with regards to the actions to be carried out when an erroneous data is detected. A definition of data originator will also be determined. 7. AGENDA ITEM 4.2: DEVELOPMENT OF MATERIAL FOR INCLUSION IN THE PANS-AIM 7.1 The meeting was presented with AIS-AIMSG/9-SN/11 concerning the Data Catalogue for aeronautical data and information as intended to be part of PANS-AIM data and information scope requirements. Based on the table provided by James in the Ad-hoc Group Meeting in Washington DC, USA, 4 6 February, the analysis of ICAO Annex 15, Appendix 1, ICAO AIS Manual (Doc 8126), AIXM 5.1, AIPs of different States, and the Instrument Flight Procedure Data Set provided by IFPP/IWG (cf. SN/14 discussion in para 5.5) a first draft of the Data Catalogue was provided to the meeting with respect to the following categories:

14 AIS-AIMSG/9-SoD Aerodromes - Airspaces - Navigation Aids - Instrument Flight Procedures (from IFPP/IWG) - ATS Route 7.2 The scope and format of the Data Catalogue was discussed. It was noted that the tables are 80-90% complete and that the missing details include descriptions of attributes and reference to the source Annex. 7.3 The exact meaning of the Obligation column was discussed. It was discussed that this was not to be seen as a SHALL provision, it is just a reference whether it is already in the AIP or not. Only the current tables in Appendix 8 for terrain and obstacle data have the notion of Mandatory/Optional attributes. And although this would be further discussed in the Ad-Hoc Group Meeting on AIM Development, Lisbon, Portugal, 30 June to 4 July It was agreed that for the moment the column Obligation would be dropped from the Data Catalogue and that there would be columns added to the Data Catalogue defining in which dataset a data element is to be provided. 7.4 Concerns were raised that to that accuracy requirements for data origination should not be duplicated across the source Annex (e.g. 4, 11 or 14) and in the PANS-AIM Data Catalogue and that therefore they should be handled through a reference. It was however also considered that for an easy handling and to establish a data exchange procedure between AIS Organisations and Data Originators it would be an advantage to have a central location of all Accuracy and Integrity requirements in one location in the ICAO Annex and PANS documentation. 7.5 It was agreed that publication requirements were to be added (to the Data Catalogue or in a separate table). For data elements for which there are no data origination quality requirements the publication requirements stay undefined. 7.6 It was discussed that the consequence would be that the PANS-AIM was not a standalone document and one would still need to go to other Annex and PANS documents (as is the situation today from the Annex 15). Ultimately the objective would be to have origination and publication requirements in one place (i.e. the Data Catalogue). It was considered that if agreement can already be found now with corresponding origination area (e.g. IFPP/IWG) then the agreement should be reflected in the Data Catalogue. 7.7 Further it was agreed that the features listed in the Annex 15 Chapter 4 paragraphs should correspond to the Feature column of the Data Catalogue and that the Data Catalogue as a whole would be a table in the PANS-AIM document. Finally it was also agreed that the feature column of the Data Catalogue would be the same as the Annex 15 Chapter 4 paragraphs.

15 -15- AIS-AIMSG/9-SoD 7.8 The meeting was presented with AIS-AIMSG/9-SN/14 which summarised the status of the common work with the IFPP/IWG and reviewed the summary of discussions 3 of the 1 st joint Meeting of IFPP integration working Group (IWG) and Sub-Group of AIS-AIMSG IFPP/IWG. 7.9 It was noted that the IWG table supports the PANS-AIM Chapter 4 developments and that ideally a similar approach should be planned towards other data originator Panels and Study Groups to harmonise ICAO documents in the area of originator data and to minimise double entries. This would also support safety in handling these data The meeting discussed how to deal with Aerodrome Mapping Data vs. current Aerodrome Data. The notion was expressed that it would be best to incorporate AMDB Data features into the Data Catalogue The meeting agreed that: a) The IWG table contents are to be included in the Data Catalogue; b) The AMDB Data features would be included into the Data Catalogue by the Ad-Hoc Group on AIM Development Meeting in Lisbon; and c) The Data Catalogue would be made available to IFPP/IWG for the next IWG Summer Meeting, Paris, France, 7 11 July Further coordination was planned for the IFPP WGWHL, Montreal, Canada, 22 September 3 October Action agreed 9/4 Further AIS-AIMSG IFPP/IWG cooperation That Peter further cooperates with the IFPP/IWG on the subject of the Data Catalogue The meeting was presented with AIS-AIMSG/9-SN7 concerning new developments on Chapter 4 of PANS-AIM: Collection of Aeronautical Data and Aeronautical Information. The Study note contained additional material developed to complement Chapter 4 of Annex 15. The new material presented as appendices also included various tables developed to ensure data collected was complete in terms of attributes and other metadata The Appendices presented included: Appendix A1: Aeronautical Data Attributes and Meta Data with a table that was developed by extracting attributes and metadata requirements based on chapter 2 of Annex 14. Appendix A2: Terrain and Obstacle Data Coverage Areas which contained the data collection coverage areas as is currently covered in Annex 15 appendix 8 3 The Summary of Discussions of the 1 st joint Meeting of IFPP/IWG and Sub-Group of AIS-AIMSG IFPP/IWG Cooperation, Phoenix, AZ, USA, January 2014 can be found under Other documents on the AIS-AIMSG/9 meeting documentation ICAO public website.

16 AIS-AIMSG/9-SoD -16- excluding the numerical data requirements and attributes. The e-tod numerical requirement and attributes were covered under Appendix 3. Appendix A3: Data Quality and Integrity Requirements which was based on previous compilation by Steven and updated for other data quality requirements currently in the Annex 15. Appendix A4: Publication and Charting Resolution which was a result of separating the publication and charting resolution from the data quality table previously compiled by Steven The meeting noted that the tables developed addressed the same objective as the Data Catalogue presented by Ruedi hence needed to be integrated with the catalogue for complementing each other in terms of the data coverage It was also noted that Roy had updated the data quality table on resolution values that are currently missing from the Annex and this needed to be integrated as well with the appendix It was agreed that the material in Chapter 4 of PANS-AIM needed to be chronologically arranged to parallel chapter 4 of the Annex Further it was noted that during AIS-AIMSG/8 it was concluded that the publication and charting resolutions will be accommodated in one table with origination accuracies and integrity requirements separated in columns but not necessarily presented as different tables It was therefore agreed that the Ad hoc group on data collection would consolidate all data covered by the Data Catalogue, table from IFPP IWG, Appendixes presented in PANS-AIM Chapter 4 and Roy s input on resolution values into one table for further review by the Study group. It was noted that it is important that the table remains practical in its usage For the integration of the Data Catalogue, Annex 4 charts, Annex 14, Annex 15 (Appendix 1 & 8), PANS-OPS and the IFPP Tables were used and cross verified After discussion on the progress made and outstanding issues on the Chapter 4 and the Data Catalogue, concurrence was established on the following points: a) A provision is to be added that The metadata has to provide information of the achieved quality ; b) A provision is to be added that Attributes of the type Coordinates, Elevation, Bearings, Value/Length have to provide metadata at feature and attribute level of the reference system, units of measurement where appropriate ; c) The Data Catalogue will not cover GEN, ENR1 and AD1 textual information (small exceptions perhaps list of national holidays, designated authorities, ); d) ATC-sector boundaries to be included in the Data Catalogue (and AIS collection and publication provisions to be worded as Where provided ) as it is required for e.g. procedure design, flight planning; and

17 -17- AIS-AIMSG/9-SoD e) The features from RTCA DO-272C/EUROCAE ED-99C will also be added to the Data Catalogue. Action agreed 9/5 List potential GEN, ENR, AD data elements for inclusion in the Data Catalogue That Ruedi, Eddie (rapporteur) and Stephane provide a list of potential GEN, ENR, AD data elements for inclusion in the Data Catalogue (and consequent AIS collection and publication provisions) including indications of user requirements The many discussions on the exact content of the Data Catalogue demonstrated that although significant progress has been made more work was required and the meeting concluded that the subject would be further discussed in the ad-hoc group on AIM Development Meeting in Lisbon. A final proposal would be prepared in this ad-hoc meeting for final review in the plenary AIS-AIMSG/10 meeting. Action agreed 9/6 Final Data Catalogue proposal That Ruedi (rapporteur), Charity, Roy, Bill, and Peter prepare a final proposal of the exact content of the Data Catalogue. 8. AGENDA ITEM 4.3: ETOD AND AMDB 8.1 In response to Action Agreed 8/11 Aerodrome Guidance material, Stephane verbally briefed the group that during the third meeting of the Aerodrome Panel (AP3), the guidance jointly developed by AIS-AIM SG and AOSWG on determination of aerodromes eligible for collection of aerodrome mapping data features was agreed, and pending minor editorial corrections, will be included in Attachment A to Annex 14, Volume I. 9. AGENDA ITEM 4.4: NUMERICAL REQUIREMENTS (INCLUDING ACCURACY AND RESOLUTION 9.1 This item was handled under Agenda item 4.2. AGENDA ITEM 5: TEMPORALITY AND DISTRIBUTION 10. AGENDA ITEM 5.1: ANNEX 15 CHAPTER 5 DEVELOPMENT 10.1 The following was reviewed and worked into the prosed Annex 15 Chapter 5:

18 AIS-AIMSG/9-SoD -18- a) Inclusion of AI products and deletion of IAIP references as proposed by AIS- AIMSG/9/-SN/6 and discussed by the meeting; b) The current Annex 15 Chapter 10 provision requirements were integrated with the terrain and obstacle data sets provisions; c) The new AIP data set was included as a recommendation (in its entirety or in parts); d) The AMDB dataset should be provided where data is available; e) The current Annex 15 Chapter 8 - Pre-flight information service provisions were edited and included. The provision of a PIB remains as an option (in a note); f) The current Annex 15 Chapter 8 - Post-flight information provisions were incorporated as a service without changing the existing text; and g) Overall consistency editing The meeting recalled that at AIS-AIMSG/5, a discussion was started on the necessity to keep the Annex 15 provisions for the Monthly plain language text. Action item 5/12 Monthly plain language list of valid NOTAM also refers. The subject was further discussed and the group agreed that there was no need for this provision, whilst noting that the provision for the checklists would stay so the latest list of NOTAM, AIC, SUP can still be obtained. 11. AGENDA ITEM 5.2 : DEVELOPMENT OF MATERIAL FOR INCLUSION IN THE PANS-AIM 11.1 The meeting discussed the proposed PANS-AIM Chapter 5 with respect to the provisions for filing differences. In the end no major change was made as this provision was considered not to be in scope of the AIS-AIMSG Further detailed provisions from Doc 8126 concerning AIP publishing (e.g. specifications for multiple volumes, page numbering, use of ISO-Latin Alphabet, formatting for coordinates, etc) were lifted into the PANS-AIM. AGENDA ITEM 6: INFORMATION SERVICES 12. AGENDA ITEM 6.1: ANNEX 15 CHAPTER 6 DEVELOPMENT 12.1 The meeting was presented AIS-AIMSG/9-SN/4 by Eddie describing with change proposals to ICAO AIS provisions on NOTAM distribution. The study note, which identifies constraints in current ICAO SARPS related to NOTAM distribution, as compared with today s user requirements. These constraints had been identified through work done by the Eurocontrol AI Operations Sub-group and focus on NOTAM information for briefing purposes and concern:

19 -19- AIS-AIMSG/9-SoD The difficulties encountered by end users who require access to the information needed for the complete operation from one briefing location, including information for cross-border destinations regarded as domestic aerodromes or military aerodromes. Some of these difficulties are related to NOTAM that are limited to domestic distribution or internationally only provided to neighbouring States and unavailability of English translations for the content of such NOTAM; and NOTAM numbering and series management, in the context of the increase of the numbers of NOTAM published by many States and the risk of number rollover when limited number of 9999 messages per series The Study Note made proposals for changes to ICAO Annex 15 NOTAM Distribution and provided rationales for change, with the purpose to serve as input to the Study Group in the revision of Annex 15 and in the development of PANS-AIM. These changes concern: The use of English and national language; NOTAM numbering and series management, addressing allocation of series and organisation; International distribution, addressing extensions of data exchange obligations; Appendix 4 (AIRAC), proposing changes to NOTAM series to be AIRAC worthy information The meeting concurred with the issues identified and arising from the work done by the EUROCONTROL AI Operations Sub-Group. It is acknowledged that the difficulties highlighted with regard to accessing certain NOTAM necessary for international flight operations are real and concern all ICAO regions Concerning the proposal raised within the Study Note that all NOTAM, including domestic ones, should be available in English Language, some comments indicated that this might be a sensitive subject. Mandatory use of English for all domestic NOTAM might prove to be unrealistic in certain regions A concern was raised that providing domestic NOTAM to international users might further increase the number of international NOTAM. It was clarified that such domestic NOTAM should remain domestic and distributed internationally only to users that specifically ask them. Also, it was observed that focus has to be on NOTAM quality and compliance with the criteria for when a NOTAM shall be issued. Information was provided to the meeting that several national investigations had showed that there was an element of natural growth in the numbers of NOTAM, due to the increased complexity of the ATM system Concerning the risk of NOTAM rollover, the States concerned are trying to mitigate it by further splitting the NOTAM series by location and subject. However, the mitigation possibilities are limited and the only radical solution would be an increase in the number of digits used for NOTAM numbering, from 4 to 6. It is acknowledged that such a change cannot be done on short term, as it would require changes in the AIS software systems used for NOTAM storage and distribution. Although this

20 AIS-AIMSG/9-SoD -20- change is not formally proposed in the Study Note, it is an option to be kept in mind. A system change which only solves a problem of a few States should be avoided, if other options exist Concerning the list of letters that cannot be used for NOTAM series, a remark was made that there have already been proposals drafted for Doc 8126 but that its Amendment 3 publication was still urgently awaited It was agreed that the Study Group members would further comment on the changes proposed in this Study Note and if no significant comments were received or if the comments show consensus on certain aspects, then the ad-hoc group that is drafting the new Annex and PANS-AIM content may integrate these proposals. In case of major comments/concerns, a discussion in the plenary would be scheduled at one of the following meetings. Action agreed 9/7 Comment AIS-AIMSG/9-SN/4 Annex 15 NOTAM Distribution proposals That the Group provides by 30 th May 2014 further comments to Paul on the AIS-AIMSG/9- SN/4 Annex 15 NOTAM Distribution proposals Further the meeting concluded that the Annex 15 Chapter 6 was now in a mature state It was agreed that the provisions would state the updates of the AIP itself and the AIP & Instrument Flight Procedures data sets are to be synchronised. 13. AGENDA ITEM 6.2: DEVELOPMENT OF MATERIAL FOR INCLUSION IN THE PANS-AIM 13.1 In response to the action agreed 8/13 AIRAC Timing, the group agreed that this would not be further addressed as the issue was not considered a high priority and that no immediate fix could be proposed In addition some relevant Doc8126 provisions concerning NOTAM provisions were lifted from the Manual It was again confirmed that the provisions would state that NOTAM would be used to update data sets. It is also implied that Digital NOTAM provision is not in contradiction with the provisions. 14. AGENDA ITEM 6.3: NOTAM PROLIFERATION 14.1 In response to the action agreed 7/4 Reporting of NOTAM proliferation issues, the meeting was presented with AIS-AIMSG/9-SN/3 which provided the (European Air Navigation Planning

21 -21- AIS-AIMSG/9-SoD Group) EANPG paper prepared by EUROCONTROL 4 containing the analysis of the factors that contribute to the increase in NOTAM numbers and the approaches used by the States to eliminate bad practices contributing to excessive publication of unnecessary or irrelevant NOTAM The meeting reviewed the information contained in the study note derived from the European AIS Database providing an overview of the International NOTAM trends for the period in which it could be observed that the number of NOTAM keeps on increasing significantly worldwide. The meeting observed that the major reason for the increase in the number of NOTAM in Europe is natural growth, reflecting the fact that operationally significant events either happen more often or were not considered operationally significant before Apart from the natural growth, the other reasons considered to contribute to the Excessive publication of unnecessary or irrelevant NOTAM include: Excessive publication of long - term and permanent NOTAM and the lengthy transfer of such NOTAM into the AIP; Insufficient knowledge on the part of originators regarding the circumstances that require a NOTAM, and of the deadlines for publishing this information via amendments to AIP ; Long cycles for AIP amendment publication lead to increased NOTAM for the in between Time and corrections to submitted NOTAM ; The use of NOTAM to re-notify information already published in AIP, AIC or SUP; and The use of several NOTAM to address a single subject matter i.e. multiple closures of taxiways at the same airport 14.4 Good practices, possibly reusable in other regions and countries, aiming to reduce the number of NOTAM include: Awareness campaign with originators on strict application of Annex 15 para requirements; Ensuring adequate oversight of the NOTAM origination and publication process; Establishment of a NOTAM Review Group with the objective of conducting a review of national NOTAM in order to enhance the effectiveness of aeronautical information ; and Critically looking at NOTAM published for dangerous areas activity time, lanterns, balloons and fireworks and permanent information 14.5 The group discussed that the focus of the NOTAM proliferation work should move from the number of NOTAM to the actual quality of the NOTAM. 4 Found in the AIS-AIMSG/9 meeting documentation on the public website under other documents