icao high-level iwxxm developments (wg-mie, imp) meetings seminars and worksho… · sp wx –...
TRANSCRIPT
ICAO High-Level IWXXM Developments (WG-MIE, IMP)
Workshop on Implementing IWXXM 31 May 2016
Aaron Braeckel
Overview
• MET Panel
• WG-MIE
• Information Management Panel (IMP)
MET Panel and WG-MIE
Job Cards 1,2,5 (ATMRPP6)
Job Cards 3,6,7,9,10 Job Card 8, OPSG legacy tasks
Job Cards 4, (CP8) Job Card 11
ICAO Air Navigation Commission
Meteorology Panel Peter Lechner Bill Maynard
WG-1MET Requirements and Integration (MRI)
Dennis Hart, Jun Ryuzaki
WG-4 MET Operations Group (MOG)
Colin Hord
WG-3 MET Information Exchange (MIE) Sue O’Rourke
Bill Maynard
WG-2 MET Information & Service Development
(MISD) Richard Heuwinkel
CM Shun
AG-1 MET Cost Recovery Guidance and
Governance (MCRGG) Peter Lechner
MET Panel Management Group
WS PANS MET Michael Berechree
WS xxxx
WS Sp Wx Steve Albersheim
WS RHWAC Sharon Lau
WS RRM Dirk Engelbart
WS VA Steve Albersheim
WS WAFS Pat Murphy
WS Annex 3 Tim Hailes
WS Extensions Pat Murphy
WS SWIM Aaron Braeckel
WS xxxx
WS IWXXM Guidance Chris Tyson
WS Governance & IMP Stuart Dingle
WS Support & Co-ord Bill Maynard
WS WAFS Operations
Matt Strahan
WS IAVW Operations
Emile Jansons
WS SADIS Operations
Chris Tyson
AG – Ad hoc Group IAVW – International Airways Volcano Watch PANS – Procedures for Air Navigation Services RRM – Release of Radioactive Material RHWAC – Regional Hazardous Weather Advisory Centre Sp Wx – Space Weather SWIM – System-wide Information Management VA – Volcanic Ash (and Gases) WAFS – World Area Forecast System WG – Working Group WS – Work Stream Note – The lead JC and WS responsibilities of are the shown. There are numerous areas where several WG and WS teams collaborate.
12 Jan 2016
METP and WG-MIE
WG-MIE proposes decisions and actions to the MET Panel – WG-MIE decisions may not necessarily be adopted by METP or the ANC
SARPS Timing and effective dates
An 18-month lead time would be more suitable for all changes (TAC and IWXXM) relating to Annex 3 for realistic implementation schedules
It was agreed in WG-MIE that applicability dates should therefore be at least 18 months after each Annex 3 Amendment is published
Permissible Usage
• All IWXXM messages should contain an indicator permissibleUsage that will be set to one of two possible values:
– 'OPERATIONAL' or ‘NON-OPERATIONAL’
• Optional permissibleUsageReason may be included that will be set to 'TEST' or ‘EXERCISE’.
• Optional permissibleUsageSupplementary may be included to specify details such as the exercise name.
Permissable Usage (2)
ROC Validation
• ROCs/RODBs to validate all IWXXM messages within their AOR
– Invalid IWXXM messages are not rejected
– Statistics are captured
– Suggested statistics include at least daily and monthly averages for valid messages, broken down by State and Region
Translation Centres
• Translation from TAC to IWXXM (conversion) may be performed by the originating State, or by formal agreement with another State or Region
• Thought should be given to how State-specific registered differences will be handled
Translation Centre metadata
• Translation centres should record metadata in generated IWXXM messages
Translation Errors
When translation errors are encountered the IWXXM message includes only message type (e.g., METAR) and original TAC Can happen in (at least) two scenarios: • Incomplete translation (not all elements
translated) • Errors are encountered while translating
Policy will be reviewed and refined over time by MIE
AMHS
• Extended AMHS identified for IWXXM dissemination
• Mixed AMHS implementation among States and Regions
• Compression support may be a challenge (e.g., GZIP)
• Large messages may be a challenge
MET-SWIM Plan
Work in progress by MIE, draft delivered to METP by August 2016 • Multiple data types: gridded, non-gridded,
imagery • Standardized web services/SOA infrastructure
identified for each data type • Relies upon HTTP and AMQP support (atop
general IP infrastructure) • Will utilize the SWIM Registry for data and web
service discovery metadata
MET-SWIM Roadmap
A roadmap will be developed that identifies:
• ASBUs identified for MET-SWIM implementation
• ASBUs identified for dependencies (CP and IMP components)
• A significant period for system transition where current and future capabilities are both available (likely)
Information Management Panel (IMP)
Broad group tasked with information management topics across MET, AIM, and other domains in SWIM
MIE and the IMP Governance Working Group share a few members
Recent topics have related to governance, but much broader than MET-related governance