TT AvData Adhoc Discussion 2025 Jun 18 - wmo-im/iwxxm GitHub Wiki

2025-Jun-18, 11:00-12:00 UTC, Webex

This is a discussion on the anticipated contribution of TT-AvData to the development of AMOIS, AMFIS and HWIS and associated schedule.

1. METP/6 discussions, decisions and actions:

   AMOIS

   (Click to expand)

   4.2.8 The Panel noted that the following core principles had been followed in the development process for AMOIS:

   a) The minimum requirements for meteorological observational information to be provided via an AMOIS include all the elements available in the current local routine report, local special report, METAR and SPECI. Thus, all existing aerodrome meteorological observational information, which may be derived from current observations, can be made available via an AMOIS.

   b) As with current local routine report, local special report, METAR and SPECI, conditional elements can also be made available via an AMOIS. A requirement may be considered ‘conditional’ in accordance with the presence of a certain meteorological phenomenon at the aerodrome, or the ability to observe a specific meteorological phenomenon with an automated system.

   c) Any elements beyond the minimum (mandatory) requirements as described above are considered ‘optional’. States may choose to include the optional elements in aerodrome meteorological observational information provided via an AMOIS, based on available meteorological observing system capabilities and identified user needs. The optional elements are to be defined to ensure that when provided, aeronautical users are presented with global consistency, while also encouraging States in a position to do so to provide information beyond the minimum requirements. For example, optional elements include greater update frequency of observations, additional observation points at operationally sensitive locations etc.

   4.2.9 ... It was recognized that information services would allow users to select specific data for their operational decision-making and third-party information service providers. The onus being placed on users to determine which information they select would bring a ‘paradigm shift’ from the current product-centric environment, where meteorological information is provided in human-readable code form or abbreviated plain language with little or no additional visualization required. It was noted that such a paradigm shift was considered throughout the requirement development process. It was also noted that AMOIS, by using the ICAO Meteorological Information Exchange Model (IWXXM) format, would enable the provision of observational data from multiple sensor locations at, in the vicinity of, and potentially beyond an aerodrome, which would bring about an improvement from the current observational reports containing observational data from a single or a relatively limited number of sensors.

   4.2.11 The meeting discussed the eventual documentation of the optional elements... The Panel concluded that the list of optional elements should be included in an Attachment to the PANS-MET (Doc 10157), as this would provide broader awareness among States and users, and also prompt the World Meteorological Organization (WMO) to initialize the development of a new IWXXM schema to support this new AMOIS. Nevertheless, following further considerations by the Panel, the Panel ultimately decided to postpone this publishing arrangement until matured draft for Standards and Recommended Practices... for both mandatory and optional parameters could be presented to the next seventh meeting of the METP (METP/7), likely to be held in late 2027...

   Decision 4/1 - Endorsement of AMOIS Requirements

   That, the Meteorology Panel endorse the initial set of requirements for the new Aerodrome Meteorological Observational Information Service (AMOIS), including both mandatory and optional elements, as detailed in the Appendix 4-1E to this report.

   AMFIS

   (Click to expand)

   4.2.15 The Panel also noted that further optional elements for AMFIS had been identified, and that this set of optional requirements was refined based on the following principles:

   a) Any additional aerodrome forecast information beyond the minimum (mandatory) requirements are considered ‘optional’. This ensures flexibility and promotes innovation by allowing States in a position to do so to provide additional aerodrome forecast information while maintaining a certain level of consistency in aerodrome forecast information across the States. Optional elements include increased temporal resolution within the forecast period, providing forecasts for additional location(s) of operational significance etc.

   b) A number of States already provide additional aerodrome forecast information beyond requirements currently prescribed in Annex 3, to satisfy local user requirements, such as enhanced meteorological support to local air traffic control (ATC) units and airport collaborative decision-making (A-CDM) functions. Current examples from six European States (Belgium, Finland, Germany, Netherlands, Switzerland, and the United Kingdom) were used as an initial (baseline) set of optional requirements.

   c) The inclusion of more comprehensive probabilistic information into aerodrome meteorological forecast information provided via an AMFIS would be encouraged.

   4.2.18 Similar to that of AMOIS (paragraph 4.2.11 refers), the meeting discussed the eventual documentation of AMFIS and the Panel ultimately decided to postpone the initial publishing arrangement into Annex 3 and the PANS-MET until matured draft for SARPs for both mandatory and optional parameters could be presented to METP/7 in late 2027...

   Decision 4/2 - Endorsement of AMFIS Requirements

   That, the Meteorology Panel endorse the initial set of requirements for the new Aerodrome Meteorological Forecast Information Service (AMFIS), including both mandatory and optional elements, as detailed in Appendices 4-1F and 4-1G to this report.

   HWIS

   (Click to expand)

   4.3.4 ... the Panel addressed the draft HWIS Implementation Plan... the document was intended to serve as a guidance for the next steps of HWIS development, namely, the deployment of trials and initial operating test implementations to verify the feasibility of the outlined concepts, as follows:

   a) The provision of globally consistent en-route hazardous weather information requires sophisticated and adaptive approaches. Rather than selecting centres which take over the responsibility for certain regions, phenomena, or roster-times, the experts in the HWIS work stream have proposed a de-centralised solution whereby each designated meteorological service provider may retain its role for the responsible sovereign air spaces and/or flight information regions (FIR), and may, additionally, extend its geographical coverage further via local or regional agreements.

   b) This introduces a concept of local contributions which make use of the existing experience, data and other information sources which are being compiled into consistent data sets and being made accessible to aviation users. By applying this de-centralised approach, each Contracting States’ sovereignty is considered while the goal of providing consistent hazardous weather information remains unchallenged.

   c) Accordingly, each Contracting State may act as contributor in the HWIS workflow and forward data (initially polygons) concerning the occurrence or expected occurrence of cumulonimbus (CB) cloud, icing and turbulence towards the responsible integrator. It is desired that contributors coordinate with their neighbouring partners to harmonize their input before contribution, e.g. by using the same data model, data composites or merged information, to minimize discrepancies in the down-stream procedure.

   d) If a Contracting State is not in a position to contribute and no other local solution can be found, it is intended that hazard data contained in WAFS forecasts is used instead, as common baseline. By applying this solution, in theory no gaps of data provision would exist globally.

   e) An integrator will gather all contributions from their agreed area of responsibility, in a regular manner and compile them into a consistent data set which is subsequently made available to users in a SWIM-compliant manner. Currently, various ideas for the integrating role are being considered, e.g. regional integrators and back-ups or virtual integration, meaning that integration is being done as an automated process and not by designated entities.

   f) In the current concept, contributors and the WAFCs are responsible for the content and availability of their input into HWIS. The integrator needs to ensure that the final data set has no gaps and is being made available in a stable manner.

   g) HWIS will initially contain IWXXM polygons for forecasts of CB cloud, icing and turbulence and optionally CB analysis. An initial set of requirements for each has been developed, to support HWIS trials.

   h) Substantial parts of the intended architecture, roles and procedures are recognised to be theoretical concepts and require validation by real-world test and trials. Therefore, the WS-HWIS proposed a comprehensive trial period to verify and validate the concepts provided. This trial phase is being supported by a dedicated ad-hoc group of the WG-MRAD’s WS-HWIS.

   i) It is planned that the outcomes of these trials will be used to inform the development of HWIS related SARPs for consideration at METP/7, for inclusion in Annex 3 and the PANS-MET (Doc 10157), including a final set of common requirements. It is also envisioned that further atmospheric hazards could be later added to HWIS as determined by user needs.

2. To understand the driving force for early availability of IWXXM schemas for AMOIS, AMFIS and HWIS.

3. To confirm participation of TT-AvData prior to the approval of relevant requirements in Annex 3 and PANS-MET (TT-AvData Terms of Reference).

4. To be aware of the key components affecting evolution of IWXXM:

   1. Requirements: MET parameters (representation comprehensive or aviation specific), collection of parameters to form a message (producer push or user pull), degree of conformance to existing TAC (how to re-create 'the story' given by existing TAC), other administrative/management parameters (how producers and users should deal with the information like distribution/usage policy, and how to guarantee they conform)
   2. Information services: Capability of the information services (filtering, consolidation, formatting (vector vs raster), trans-coding (XML vs JSON), etc.)
   3. Use cases: Anticipation of user (rendering in text/graphics, latency), capability of devices (choices of processing and outputs (types like vector vs raster, formats like XML vs JSON) from server-side)

5. To discuss activities, associated teams and convenors involved.

6. To confirm schema development and (release candidate) publication schedules.

7. AOB

• An initial consensus is that initial development of IWXXM schemas for AMOIS and AMFIS will commence in the latter part of Q3 2025 targeting a first publication of the schemas by Q1 2026.

Choy to start inviting experts to participate in the development activities.

Not expected but will be held again as necessary.