MEETING OF THE METEOROLOGY PANEL (METP) WORKING GROUP MOG (SADIS/WAFS)

Transcription

1 METPWGMOG/6/IP/7 4/04/18 MEETING OF THE METEOROLOGY PANEL (METP) WORKING GROUP MOG (SADIS/WAFS) SIXTH MEETING Frankfurt, Germany, 10 to 11 April 2018 Agenda Item 3: Matters relating to SADIS 3.2.4: SADIS Implementation 2018 Work undertaken to provide AOP and non-aop OPMET Information (Presented by Patrick Simon) SUMMARY This Information Paper summarises the work carried out by the METG and DMG with regards the creation of lists for AOP and non-aop OPMET data. 1. INTRODUCTION 1.1 The MOG/4/SADIS meeting agreed the following action: Action agreed 4/SADIS1 Review the result of IATA SADIS/WIFS monitoring That, the SADIS provider state and the WIFS provider state in coordination with the European OPMET Data Management Group, be invited to: a) Review the IATA monitoring results on SADIS/WIFS content in the appendix of SN13 and take into consideration while establishing the basic requirements from IATA for agreed exchanged non-aop aerodromes OPMET; b) continue distribution of previously agreed non-aop aerodromes METAR/TAF, and c) establish, with the support of ICAO, a process to maintain and update a list of OPMET required to, or agreed to, be exchanged. DMG has undertaken a number of tasks as explained further in the next section. (5 pages) METPWGMOG_6 SN. AOP and non AOP OPMET information V2.en.docx

2 METPWGMOG/6/IP/xx DISCUSSION 2.1 DMG report to METG and DMG proposals to METG The METG/27 meeting recalled the METG Decision 26/09, which updated the work program of the METG which included the following task to the DMG: initiate action plans to obtain data to meet defined requirements (OPMET data for AOP aerodromes maintained in eanp Volume II Table MET II-2 and OPMET data for non-aop aerodromes maintained by DMG method to be determined). This decision is based on two elements: Obtain data to meet defined requirements (AOP airports) and agreed non AOP airports data Define a catalogue for agreed non AOP airports OPMET data. The DMG/20 meeting agreed on a method that will be described further with the associated status of action by DMG. Following that agreement by DMG, DMG presented WP/06 to METG/27 that resulted in an agreement by METG/27 (September 2017) as follows: (Extract from METG/27 Final Report) The meeting noted the proposal in obtaining a list of agreed exchange OPMET data for non-aop aerodromes which included a definition of the initial list as well as maintenance and publication of the list. More details can be found in WP/06. The meeting agreed with this proposal and for the DMG to produce a list of agreed exchange OPMET data for METG/28. In addition WP/13 was presented which resulted in the following action being agreed by METG/27. ICAO Doc (WP/13) In light of the DMG s responsibility to provide measurement of implementation of OPMET data availability and timeliness for the eanp Volume III, the meeting concurred that ICAO location indicators (ICAO Doc 7910) should be made available in machine readable format as specified in Appendix H. In addition, having ICAO Doc 7910 available in machine readable format will facilitate in annual monitoring of OPMET data. Both tasks mentioned are in the DMG Terms of Reference. In order to fulfil these DMG duties, the meeting agreed to the following draft Conclusion. METG Draft Conclusion 27/05 ICAO Location Indicators (ICAO Doc 7910) format

3 - 3 - METPWGMOG/6/IP/7 That ICAO provide ICAO Location Indicators (ICAO Doc 7910) in a format that can be processed automatically (e.g. txt, csv) as specified in Appendix H to the various working groups (e.g. EUR Data Management Group) in order to fulfil their tasks as defined in their respective Terms of Reference Furthermore, the meeting noted that efforts have been made to align the eanp with ICAO Doc 7910 and that this effort should continue to avoid discrepancies when referencing the eanp for required OPMET data. 2.2 DMG set of actions Review the IATA monitoring results on SADIS/WIFS content from non-aop aerodromes As a first step, a WIFS monitoring has been performed by ROC Toulouse during February 2018 in conjunction with EUR DMG monitoring period to allow a comparison between WIFS and SADIS OPMET content. It has been proposed to verify first the alignment on AOP airports through the EUR DMG PHP Application. The resulting action has been agreed by DMG23 (13/15 of March 2018). DMG Use the workpackage AFS_SADIS-WIFS_Routine_OPMET_Data for depicting what is on WIFS and not on SADIS, and will derive the corresponding PHP tickets for each ROC M. Wagner DMG24 Having a deeper look at non AOP data should then be undertaken, once the agreed list of non AOP OPMET data (with the associated headings) has been finally agreed (see following paragraphs on this matter) Creation of the initial list of OPMET data from non-aop aerodromes and actions accepted by METG and resulting status of DMG actions Agree on the RODEX headers list of all OPMET data by comparing catalogues and routing tables from three ROCs. In its 21st session, DMG agreed on the following task: DMG P. Simon will provide the routing table in csv format to M. Pichler and M. Wagner in order to derive the ROC Vienna and London routing tables in same format and forward those to M. Mezred. Additionally, a second csv file will be generated by the three ROCs to identify the correspondence AFTN address country name France Austria UK NATS DMG23

4 METPWGMOG/6/IP/xx The three EUR ROCs exchanged their routing tables in February 2018 and a consolidated routing table is expected for June Identifying AOP and non-aop aerodromes in this RODEX list would be done by monitoring Identifying the AOP aerodromes would be done by comparing to the list of required OPMET data in the eanp Volume II, Table MET II-2. The MS Word format of the ICAO Regional Tables MET II-2 have been provided by ICAO Paris office (23/01/2018). However multiple styles causes the necessity to handle them manually to obtain a basic and uniform format suitable for integration in any other application and database. The current formats are not considered as adequate for the implementation of the Global eanp to the DMG OPMET data working table. Therefore, the draft ICAO Regional Table MET II-2 documents have been converted (best effort) to a plain text *.csv format in March The CCCC for the aerodrome must be in ICAO Doc Following EANPG decision, a Letter EUR/NAT MET (KEC/SAN), dated 30 January 2018 was sent to ICAO HQ, requesting for a machine-readable database file for measuring required OPMET data. ICAO HQ accepted the request and provided a XLS file containing the required elements with the restriction on their use by some DMG members on their duties only (granted by ICAO EUR DMG chair/vice chair). Following DMG monitoring, it appears that some OPMET data being received are not fully compliant e.g. some location are not yet listed in 7910 or more frequently the names used, such as FIR name in SIGMET, are not fully 7910 compliant. In such cases, DMG PHP application will be used for EUR data monitored as exchanged and not DOC 7910 compliant to open tickets that should be dealt in coordination between the EUR ROCs and States. For data related to other ICAO regions than the EUR region, the results will be sent through ICAO Paris office to the other ICAO regional offices. All others would be classified as agreed exchange OPMET data for non-aop aerodromes. 1. This action will be done one the AOP list has been cleared to complete it Maintenance of the list If operators request information not on this list, ICAO would consult the State accordingly and a positive response would result in the inclusion of the CCCC to the list of non-aop aerodromes updated by the DMG. This procedure is already provided and in place ( described in EUR DOC 018). Inclusion or removal of OPMET data would be provided through the METNO procedure.

5 - 5 - METPWGMOG/6/IP/7 This procedure is already provided and in place (described in EUR DOC 018) by providing each AIRAC cycle an update on the content of OPMET bulletins that will occur. The gap that should be considered is an effective exchange among the ICAO regional groups in charge of data management of modifications to occur in the data content Publication of the list The list of agreed OPMET data for non-aop aerodromes would be made available on the ICAO public website and sorted by Region, State, aerodrome name and location indicator. A list of headers would also be provided. The headings between AOP and non-aop aerodromes should be different. The list should be provided to METG/28 for adoption, with the explanation of the procedures that will be used to maintain the table and should be available to MOG/SADIS & WIFS. 3. CONCLUSION 3.1 The METP-WG/MOG is invited to note the information contained in this Information Paper. END