SAM COM-MET 2019 - Informe Final PDF
SAM COM-MET 2019 - Informe Final PDF
Reunión de Implantación
SAM COM-MET 2019
INFORME FINAL
INDICE
RESEÑA DE LA REUNION
La Reunión de Implantación SAM COM/MET 2019, se llevó a cabo en Lima, Perú, del
23 al 25 de abril de 2019.
El Sr. Aníbal Castro, Especialista MET de la Dirección General de Aeronáutica Civil del Estado
Plurinacional de Bolivia, fue elegido como Presidente de la Reunión. El señor Jorge Armoa, Oficial
Regional de Gestión de Información Aeronáutica y Meteorología de la Oficina Sudamericana de la OACI,
actuó como Secretario contando con el apoyo del Sr. Francisco Almeida, Oficial Regional de
Comunicaciones, Navegación y Vigilancia de la Oficina Sudamericana de la OACI.
ii-5 AGENDA
Cuestión 1 del
Orden del Día: Intercambio OPMET
a) revisión de los requisitos para el intercambio OPMET
b) revisión de los resultados de los controles de intercambio OPMET de los años 2017,
2018 y 2019;
c) operación, funcionamiento y utilización del Banco Internacional de datos OPMET
de Brasilia;
d) revisión del Catálogo de datos del Banco Internacional de datos OPMET Brasilia;
SAM COM/MET 2019 ii – Reseña de la Reunión ii-3
Cuestión 2 del
Orden del Día: Seguimiento a la implantación regional del proyecto de implantación de la arquitectura
de la ATN y de las Aplicaciones tierra-tierra de la ATN en la Región SAM (sistemas
AMHS y la interconexión de los mismos).
Cuestión 3 del
Orden del Día: Revisión de los mensajes SIGMET. Análisis del formato e intercambio.
Cuestión 4 del
Orden del Día: Ejercicios de mensajes SIGMET por cenizas volcánicas. Evolución y futuros
proyectos.
Cuestión 5 del
Orden del Día: Enmienda 78 al Anexo 3. Implantación del intercambio de datos OPMET en formato
XML/GML, modelo IWXXM, preparación para el intercambio de mensajes OPMET
en un ambiente SWIM y mensajes de condición espacial (Meteorología espacial).
Cuestión 6 del
Orden del Día: Otros asuntos
ii-6 ASISTENCIA
LISTA DE PARTICIPANTES
ARGENTINA URUGUAY
BOLIVIA
VENEZUELA
2. Aníbal Castro Cárdenas
3. Iver Mijael Vargas Ponce de León 20. Alfredo Manrique
21. Aura Romero
22. Reidy Zambrano
COLOMBIA 23. Antonio Espinoza
PARAGUAY
PERÚ
Cuestión 1 del
Orden del Día: Intercambio OPMET
a) revisión de los requisitos para el intercambio OPMET
b) revisión de los resultados de los controles de intercambio OPMET de los años
2017, 2018 y 2019;
c) operación, funcionamiento y utilización del Banco Internacional de datos
OPMET de Brasilia;
d) revisión del Catálogo de datos del Banco Internacional de datos OPMET
Brasilia;
e) revisión de e-ANP CAR/SAM, Parte V-MET del Vol. I, Vol. II y de la Guía
OPMET para las Regiones CAR/SAM;
f) preparación de la parte MET del Vol. III del e-ANP CAR/SAM;
g) análisis de las oportunidades de mejoras observadas en los mensajes OPMET
transmitidos (METAR, SPECI, TAF, SIGMET).
1.1 La Reunión, bajo este punto del orden del día, analizó las siguientes notas de estudios y
notas informativas:
1.3 Con relación a la misma, la reunión creyó conveniente realizar un análisis de la necesidad
de llenar dicha tabla en base a los vuelos regulares y no-regulares que se realizan entre cada par de Estado
involucrado, además de considerar los aeropuertos alternos para las rutas que desarrollan los operadores
aéreos para cubrir la conexión entre cada par de Estados. Por este motivo, la Reunión recomendó revisarlo
en sus Estados y enviar las actualizaciones y comentarios a la Secretaría, a más tardar el 17 de mayo del
2019. De igual, manera, solicitó a la Secretaría dar seguimiento a esta acción con los Estados que no han
asistido a la Reunión.
1.4 Adicionalmente, se han revisado los resultados de los Controles OPMET realizados
trimestralmente por el Banco Internacional de Datos OPMET de Brasilia. Con relación a los mismos, se
han observado las bajas eficiencias respecto a los Estados de Colombia, Venezuela, Surinam, Guyana y
Panamá. Los Estados mencionaron dificultades experimentadas en las conexiones vía Atlanta en algunas
oportunidades que pudieron haber ocasionado estas bajas eficiencias.
1.5 La Reunión al analizar esta situación, consideró que pudieron presentarse dos problemas,
los cuales son:
Por ello, la Reunión recomendó revisar las tablas utilizadas para los Controles de Intercambio
OPMET, tanto de las Oficinas Meteorológicas Aeronáuticas y Oficinas de Vigilancias
Meteorológicas, y actualizarlas en caso necesario. Además, se definió hacer pruebas sobre la
recepción de los datos OPMET en el Banco OPMET de Brasilia requiriéndole tres minutos
luego de su remisión, durante 10 días de lo siguiente:
1-2 Informe sobre la Cuestión 1 del Orden del Día SAM COM/MET 2019
NE/03- Revisión del Catálogo de datos del Banco Internacional de datos OPMET de Brasilia
(Presentada por Secretaría)
1.6 La Reunión analizó el Catálogo de datos del Banco Internacional de Datos OPMET de
Brasilia. La Reunión observó que este ha sido actualizado con las Enmiendas 76, 77 y 78 del Anexo 3-
Servicios Meteorológicos para la Navegación Aérea Internacional. Sin embargo, consideró que las Tablas
de Oficinas Meteorológicas Aeronáuticas y Oficinas de Vigilancia Meteorológica, que deben tributar al
Banco OPMET (incluye aeropuertos AOP y no-AOP), debieran ser revisadas y actualizadas en caso
necesario, para que reflejen verazmente lo que cada Estado está enviando al Banco OPMET de Brasilia.
La Reunión recomendó a los Estados realizar estas revisiones y actualizaciones en caso necesario, y
remitirlas a la Secretaría a más tardar para el 17 de mayo del 2019. Así mismo, la Reunión pidió a la
Secretaría remitir estás nuevas tablas, una vez revisadas y actualizadas, al Banco de Datos OPMET de
Brasilia para ser utilizadas como base para los Controles de Intercambio OPMET.
NE/04 – Revisión de los Volúmenes I y II del e-ANP CAR/SAM (Presentada por Secretaría)
• el Volumen I que debe contener los elementos estables del plan, cuya enmienda requiere
la aprobación del Consejo;
• el Volumen II que debe contener los elementos dinámicos del plan, cuya enmienda no
requiere la aprobación del Consejo (la aprobación es por acuerdo regional de los PIRGs
pertinentes); y
• el Volumen III que debe contener los elementos dinámicos/flexibles del plan, brindando
orientación para la planificación de la implantación de los sistemas de navegación aérea y su
modernización, tomando en cuenta los programas emergentes, como el ASBU, y las hojas de ruta
de las tecnologías asociadas descritas en el GANP.
1.8 La Secretaría informó que los Volúmenes I y II han sido aprobados en el 2016 y que el
Volumen III fue postergado por Conclusión CRPP/4-3 hasta la aprobación del GANP-Sexta Edición.
Adicionalmente, la Secretaría informó que, una vez aprobado, el mismo debió ser sujeto de constantes
revisiones y actualizaciones, en caso fuera necesario. Los Volúmenes I y II se encuentran como
Apéndices B y C a esta parte del informe.
1.9 La Reunión, al analizar las Tablas MET de ambos volúmenes, consideró importante
revisar las contenidas en el Vol. II. La Reunión definió enviar los comentarios y actualizaciones el 3 de
junio del presente año.
Estados informaron que tienen previsto implementarlo para el 2020. La Reunión recomendó consultar con
las partes interesadas y realizar un estudio de costo-beneficio para plantear el volver a implantar el
servicio de VOMET o D-VOLMET. Los resultados de estos análisis serán enviados a la Secretaría a más
tardar el 30 de agosto del 2019.
1.11 Así mismo, la Reunión revisó la Guía de Preparación y Difusión de Mensajes OPMET
para las Regiones CAR/SAM, actualizadas las enmiendas 76, 77 y 78 del Anexo 3 de la OACI. La
Reunión recomendó revisarla con las autoridades y otras áreas de su Estado y remitir los comentarios el
30 de agosto del presente año.
NE/05- Desarrollo de la Parte MET del Vol. III del e-ANP CAR/SAM (Presentada por Secretaría)
1.12 La Reunión fue informada que el Plan Global de Navegación Aérea está actualmente en
revisión, y será puesto a disposición de la Asamblea 40 de la OACI para su revisión.
1.13 Considerando que es necesario el desarrollo de la parte MET del Vol. III del e-ANP
CAR/SAM en base a los elementos de los módulos del ASBU, la Secretaría hizo una presentación sobre
el Portal del GANP, y el enfoque que daría la Sexta Edición en relación a los elementos del módulo B0-
AMET. Adicionalmente, presentó lo relacionado a los Elementos Constitutivos Básicos (BBBs) para el
área MET.
1.14 Los Estados han tomado el compromiso de rellenar las Tablas de cada elemento del
módulo B0-AMET a más tardar el 3 de junio del presente año, tiempo prudencial para revisarlas y
preparar los Planes de Acción para los elementos que aún no han sido implantados.
NI/04 - Resultados de los controles de intercambio OPMET del año 2018 en los aeropuertos del Ecuador
(Presentada por Ecuador)
1.15 Ecuador informó sobre los resultados de sus Controles de Intercambio OPMET realizados por su
Banco de Datos OPMET. Los controles son realizados en forma mensual. Los resultados pueden
observarse en los Apéndices D, E, F y G a esta parte del informe. Como conclusión, se puede observar
que el aeropuerto internacional de Quito (SEQM) muestra los mejores porcentajes de eficiencia dentro de
los AOP, mientras que el aeropuerto de Riobamba (SERB), lo es para los NO-AOP.
SAM COM/MET 2019 Apéndice A al Informe sobre la Cuestión 1 del Orden del Día 1A-1
EXPLICACIÓN DE LA TABLA
Note.- Aerodromes not included in Table AOP are in italics/los aeródromos que no están listados
en la Tabla AOP aparecen en letra cursiva.
SAM COM/MET 2019 Apéndice B al Informe sobre la Cuestión 1 del Orden del Día 1B-1
1. INTRODUCTION
1.1 This part of the CAR/SAM ANP constitutes the agreed regional requirements considered
to be the minimum necessary for effective planning and implementation of aeronautical meteorology
(MET) facilities and services in the Caribbean and South American Regions and complements the
provisions of the ICAO SARPs and PANS related to MET. It contains stable plan elements related to the
assignment of responsibilities to States for the provision of MET facilities and services within the ICAO
Caribbean and South American regions in accordance with Article 28 of the Convention on
International Civil Aviation (Doc 7300) and mandatory requirements related to the MET facilities and
services to be implemented by States in accordance with regional air navigation agreements.
1.2 The dynamic plan element related to the assignment of responsibilities to States for the
provision of MET facilities and services and the mandatory requirements based on regional air navigation
agreements related to MET are contained in the CAR/SAM ANP Volume II, Part V - MET.
1.3 The CAR/SAM ANP Volume III contains dynamic/flexible plan elements related to the
implementation of air navigation systems and their modernization in line with the ICAO Aviation System
Block Upgrades (ASBUs) methodology and associated technology roadmaps described in the Global Air
Navigation Plan. The ASBU modules are aimed at increasing capacity and improving efficiency of the
aviation system whilst maintaining or enhancing safety level, and achieving the necessary harmonization
and interoperability at regional and global level. This includes the regionally agreed ASBU modules
applicable to the specified ICAO region/sub-region and associated elements/enablers necessary for the
monitoring of the status of implementation of these ASBU modules.
Standards and Recommended Practices and Procedures for Air Navigation Services
1.4 The SARPs and PANS and related guidance material applicable to the provision of MET
are contained in:
d) Manual on Volcanic Ash, Radioactive Material and Toxic Chemical Clouds (Doc
9691);
2.2 In the Caribbean and South American Regions, WAFS products in digital form should
be disseminated by WAFC Washington using the SADIS 2G satellite broadcast and the Secure SADIS
FTP service and/or WIFS.
Volcanic Ash
2.3 Volcanic ash advisory centres (VAACs) Buenos Aires, Washington and Wellington
have been designated to prepare volcanic ash advisory information for the Caribbean and South
American Regions, as indicated below. The status of implementation of volcanic ash advisory
information is detailed in Volume III.
2.4 Selected State volcano observatories have been designated for notification of significant
pre-eruption volcanic activity, a volcanic eruption and/or volcanic ash in the atmosphere for the
Caribbean and South American Regions to their corresponding ACC/FIC, MWO and VAAC, as
indicated at Table MET I-1. The status of implementation of volcano observatory notice for aviation
(VONA) is detailed in Volume III.
Tropical Cyclone
2.5 Tropical cyclone advisory centre (TCAC) Miami has been designated to prepare tropical
cyclone advisory information for the Caribbean and South American Regions, as indicated below. The
status of implementation of tropical cyclone advisory information is detailed in Volume III.
______________________
TABLE MET I-1 - STATE VOLCANO OBSERVATORIES
Explanation of the Table
Column
1 Name of the State responsible for the provision of a volcano observatory
2 Name of the volcano observatory
1 2
Argentina Servicio Geológico Minero Argentino, SEGEMAR, Buenos Aires
Chile Southern Andes Volcano Observatory (SAVO), Departamento de Ciencias Físicas,
Temuco
Servicio Nacional de Geología y Minería (SERNAGEOMIN), Santiago
Colombia Servicio Geológico Colombiano, Observatorios Vulcanológicos y Sismológicos de
Manizales, Popayán y Pasto
Costa Rica Observatorio de Volcanes y Sismológico de Costa Rica, (OVSICORI-UNA), Heredia
Ecuador Instituto Geofísico y Sismológico, Quito
El Salvador Servicio Nacional de Estudios Territoriales (SNET), Ministerio de Medio Ambiente y
Recursos Naturales, (MARN), El Salvador
French Antilles Observatoire volcanologique de la Soufriere, Guadeloupe
(France) Observatoire volcanologique de la Pelée, Martinique
Guatemala INSIVUMEH Sección Vulcanología, Ciudad de Guatemala
Guyana Guyana Geology and Mines Commission
Mexico Centro Nacional de Prevención de Desastres (CENAPRED)
Centro Universitario de Investigaciones en Ciencias del Ambiente, Universidad de Colima
Instituto de Geofísica, UNAM Observatorio de volcanes, Universidad de Colima
Montserrat
Montserrat Volcano Observatory
(U.K.)
Nicaragua Dirección General del Inst. Nicaragüense de Estudios Territoriales (INETER), Dirección de
Vulcanologia, Managua
Panama Instituto de Geociencias
Peru Instituto Geofísico del Perú (IGP), Arequipa
Trinidad and
Tobago Seismic Research Unit, University of Indies, St. Augustine
SAM COM/MET 2019 Apéndice C al Informe sobre la Cuestión 1 del Orden del Día 1C-1
1. INTRODUCTION
1.1 This part of the Caribbean and South American ANP, Volume II, complements the provisions in
the ICAO SARPs and PANS related to aeronautical meteorology (MET). It contains dynamic plan elements
related to the assignment of responsibilities to States for the provision of MET facilities and services within a
specified area in accordance with Article 28 of the Convention on International Civil Aviation (Doc 7300); and
mandatory requirements related to the MET facilities and services to be implemented by States in accordance
with regional air navigation agreements. Such agreement indicates a commitment on the part of the States
concerned to implement the requirements specified.
Meteorological offices
2.1 In the Caribbean and South American Regions, meteorological watch offices (MWO) have been
designated to maintain continuous watch on meteorological conditions affecting flight operations within their
area(s) of responsibility, as indicated at Table MET II-1.
2.2 In the Caribbean and South American Regions, routine observations, issued as a METAR,
should be made throughout the 24 hours of each day at intervals of one hour or, for RS and AS designated
aerodromes[1] , at intervals of one half-hour at aerodromes as indicated in Table MET II-2. For aerodromes
included on the VHF VOLMET broadcast as indicated in Table MET II-3, routine observations, issued as
METAR, should be made throughout the 24 hours of each day. (at intervals of one half-hour) [if applicable]
2.3 At aerodromes that are not operational throughout 24 hours, METAR should be issued at least 3
hours prior to the aerodrome resuming operations in the Caribbean and South American Regions.
Forecasts
2.4 In the Caribbean and South American Regions, an aerodrome forecast, issued as a TAF, should
be for the aerodromes indicated in Table MET II-2.
2.5 In the Caribbean and South American Regions, the period of validity of a routine TAF should be
of 9-, 24-, or 30-hours to meet the requirements indicated in Table MET II-2.
2.6 In the Caribbean and South American Regions, the forecast maximum and minimum
temperatures expected to occur during the period of validity, together with their corresponding day and time of
occurrence, should be included in TAF at aerodromes indicated in Table MET II-2.
2.7 In the Caribbean and South American Regions, landing forecasts (prepared in the form of a trend
forecast) should be provided at aerodromes indicated in Table MET II-2.
2.8 Operational meteorological information prepared as METAR, SPECI and TAF for aerodromes
indicated in Table MET II-2, and SIGMET and AIRMET messages prepared for flight information regions or
control areas indicated in Table MET II-1, should be disseminated to the international OPMET databanks
designated for the Caribbean and South American Regions (namely IODB BRAZILIA of OPMET databank) and
to the centre designated for the operation of the aeronautical fixed service satellite distribution system (SADIS)
and the Internet-based service (Secure SADIS FTP) and/or WIFS in the CAR/SAM Region(s).
2.9 SIGMET messages should be disseminated to other meteorological offices in the Caribbean and
South American Regions. (In accordance with the regional OPMET bulletin exchange scheme).
2.10 Special air-reports that do not warrant the issuance of a SIGMET should be disseminated to
other meteorological offices in the Caribbean and South American Regions. (In accordance with the regional
OPMET bulletin exchange scheme).
2.11 In the Caribbean and South American Regions, meteorological information for use by aircraft in
flight should be supplied through VOLMET broadcasts.
2.12 In the Caribbean and South American Regions, the aerodromes for which METAR and SPECI
are to be included in VOLMET broadcasts, the sequence in which they are to be transmitted and the broadcast
time, is indicated in Table MET II-3.
None
Column
1 Name of the State where meteorological service is required
2 Name of the flight information region (FIR) or control area (CTA) where meteorological service is
required
Note: The name is extracted from the ICAO Location Indicators (Doc 7910) updated quarterly. If a
State wishes to change the name appearing in Doc 7910 and this table, ICAO should be notified
officially.
3 ICAO location indicator of the FIR or CTA
4 Name of the meteorological watch office (MWO) responsible for the provision of meteorological
service for the FIR or CTA
Note: The name is extracted from the ICAO Location Indicators (Doc 7910) updated quarterly. If a
State wishes to change the name appearing in Doc 7910 and this table, ICAO should be notified
officially.
5 ICAO location indicator of the responsible MWO
6 Requirement for SIGMET information (excluding for volcanic ash and for tropical cyclones) to be
provided by the MWO for the FIR or CTA concerned, where:
Y – Yes, required
N – No, not required
7 Requirement for SIGMET information for volcanic ash to be provided by the MWO for the FIR or
CTA concerned, where:
Y – Yes, required
N – No, not required
8 Requirement for SIGMET information for tropical cyclone to be provided by the MWO for the FIR
or CTA concerned, where:
Y – Yes, required
N – No, not required
9 Requirement for AIRMET information to be provided by the MWO for the FIR or CTA concerned,
where
Y – Yes, required
N – No, not required
SIGMET (WC)
SIGMET (WS)
SIGMET (WV)
State
Indicator
Indicator
Location
Location
SIGMET
ICAO
ICAO
(WA)
Name Name
1 2 3 4 5 6 7 8 9
SABE Y Y N
Ezeiza SAEF BUENOS AIRES/ Aeroparque,
N
Jorge Newbery
SAVC
SAVF
Comodoro Rivadavia COMODORO
Y Y N N
RIVADAVIA/General Mosconi
Argentina
Córdoba SACF CORDOBA/Ing. Aer. A.L. SACO
Y Y N N
Taravela
Recife SBRE
RECIFE/CINDACTA III SBRE Y Y Y N
Atlántico SBAO
SANTIAGO/Arturo Merino
Santiago SCEZ SCEL Y Y N N
Benitez
Bogotá SKED
Bogotá/El Dorado SKBO Y Y Y N
Colombia
Barranquilla below FL200 (cf.
SKEC N N N N
Bogotá)
GUAYAQUIL/José Joaquín de
Ecuador Guyaquil SEFG SEGU Y Y N N
Olmedo
SIGMET (WC)
SIGMET (WS)
SIGMET (WV)
State
Indicator
Indicator
Location
Location
SIGMET
ICAO
ICAO
(WA)
Name Name
1 2 3 4 5 6 7 8 9
PORT-AU-PRINCE/ Port-au-
Haiti Port-au-Prince MTEG MTPP Y Y Y N
Prince Intl
KINGSTON/Norman al Manley
Jamaica Kingston MKJK MKJP Y Y Y N
Intl
LIMA-CALLAO/Jorge Chávez
Peru Lima SPIM SPJC Y Y N N
Intl
United States Miami FIR /Oceanic FIR KZMA KANSAS CITY KMCI Y Y Y N
INTERNATIONAL, MO. Aviation
Weather Center
MONTEVIDEO/Carrasco Intl
Uruguay Montevideo SUEO Gral. Cesareo L. SUMU Y Y N N
Berisso
Column
1 Name of the State where meteorological service is required
2 Name of the AOP aerodrome where meteorological service is required
Note: The name is extracted from the ICAO Location Indicators (Doc 7910) updated quarterly. If a
State wishes to change the name appearing in Doc 7910 and this table, ICAO should be notified
officially.
3 ICAO location indicator of the AOP aerodrome
4 Designation of AOP aerodrome:
RG - international general aviation, regular use
RS - international scheduled air transport, regular use
RNS - international non-scheduled air transport, regular use
AS - international scheduled air transport, alternate use
ANS - international non-scheduled air transport, alternate use
5 Name of the aerodrome meteorological office responsible for the provision of meteorological service
Note: The name is extracted from the ICAO Location Indicators (Doc 7910) updated quarterly. If a
State wishes to change the name appearing in Doc 7910 and this table, ICAO should be notified
officially.
6 ICAO location indicator of the responsible aerodrome meteorological office
7 Requirement for METAR/SPECI from the aerodrome concerned, where:
Y – Yes, required
N – No, not required
8 Requirement for information on the state of the runway provided by the appropriate airport authority
to be included as supplementary information in METAR/SPECI from the aerodrome concerned,
where:
Y – Yes, required
N – No, not required
9 Requirement for trend forecast to be appended to METAR/SPECI from the aerodrome concerned,
where
Y – Yes, required
N – No, not required
10 Requirement for TAF from the aerodrome concerned, where
C - Requirement for 9-hour validity aerodrome forecasts in TAF code (9H)
T - Requirement for 18/24-hour validity aerodrome forecasts in TAF code (18/24H)
X - Requirement for 30-hour validity aerodrome forecasts in TAF code (30H)
N – No, not required
11 Requirement for maximum and minimum temperature (expected to occur during the period of
validity of the TAF) to be included in TAF from the aerodrome concerned, where:
Y – Yes, required
N – No, not required
12 Availability of METAR/SPECI and TAF from the aerodrome concerned, where:
F – Full availability : OPMET information as listed issued for the aerodrome all through the 24-hour
period
P – Partial availability: OPMET information as listed not issued for the aerodrome for the entire 24-
hour period
METAR/SPECI and
TAF availability
provided meteorological office to be provided
ICAO Location
ICAO Location
METAR/SPECI
Temperature
State of the
Indicator
Indicator
State
forecast
runway
Trend
Name
Name
Tx/Tn
TAF
Use
1 2 3 4 5 6 7 8 9 10 11 12
Argentina
NEUQUÉN/ Presidente Perón SAZN RNS& Buenos Aires/ SABE Y N N T Y F
AS Aeroparque J. Newbery
METAR/SPECI and
TAF availability
provided meteorological office to be provided
ICAO Location
ICAO Location
METAR/SPECI
Temperature
State of the
Indicator
Indicator
State
forecast
runway
Trend
Name
Name
Tx/Tn
TAF
Use
1 2 3 4 5 6 7 8 9 10 11 12
WEST END/ West End MYGW RNS&AS West End Intl. MYGW N N N N
International Airport.
Belize BELIZE/ Philip S.W. Goldson MZBZ RS Belize/ Philip S.W. MZBZ Y N N T Y F
Intl Goldson Intl.
METAR/SPECI and
TAF availability
provided meteorological office to be provided
ICAO Location
ICAO Location
METAR/SPECI
Temperature
State of the
Indicator
Indicator
State
forecast
runway
Trend
Name
Name
Tx/Tn
TAF
Use
1 2 3 4 5 6 7 8 9 10 11 12
METAR/SPECI and
TAF availability
provided meteorological office to be provided
ICAO Location
ICAO Location
METAR/SPECI
Temperature
State of the
Indicator
Indicator
State
forecast
runway
Trend
Name
Name
Tx/Tn
TAF
Use
1 2 3 4 5 6 7 8 9 10 11 12
BUCARAMANGA/Palonegro SKBG RS
PEREIRA/Matecaña SKPE RS
METAR/SPECI and
TAF availability
provided meteorological office to be provided
ICAO Location
ICAO Location
METAR/SPECI
Temperature
State of the
Indicator
Indicator
State
forecast
runway
Trend
Name
Name
Tx/Tn
TAF
Use
1 2 3 4 5 6 7 8 9 10 11 12
CAYO LARGO DEL SUR/Vilo MUCL RS Habana/ Jose Marti Intl MUHA Y N N T N F
Acuna Intl
CIENFUEGOS/Jaime MUCF RS
González
Ecuador
MANTA/Eloy Alfaro SEMT RS Quito/Mariscal Sucre SEQM Y N N T Y F
METAR/SPECI and
TAF availability
provided meteorological office to be provided
ICAO Location
ICAO Location
METAR/SPECI
Temperature
State of the
Indicator
Indicator
State
forecast
runway
Trend
Name
Name
Tx/Tn
TAF
Use
1 2 3 4 5 6 7 8 9 10 11 12
METAR/SPECI and
TAF availability
provided meteorological office to be provided
ICAO Location
ICAO Location
METAR/SPECI
Temperature
State of the
Indicator
Indicator
State
forecast
runway
Trend
Name
Name
Tx/Tn
TAF
Use
1 2 3 4 5 6 7 8 9 10 11 12
METAR/SPECI and
TAF availability
provided meteorological office to be provided
ICAO Location
ICAO Location
METAR/SPECI
Temperature
State of the
Indicator
Indicator
State
forecast
runway
Trend
Name
Name
Tx/Tn
TAF
Use
1 2 3 4 5 6 7 8 9 10 11 12
METAR/SPECI and
TAF availability
provided meteorological office to be provided
ICAO Location
ICAO Location
METAR/SPECI
Temperature
State of the
Indicator
Indicator
State
forecast
runway
Trend
Name
Name
Tx/Tn
TAF
Use
1 2 3 4 5 6 7 8 9 10 11 12
CUERNAVACA/General MMCB RS
Mariano Matamoros
MMNG RG
NOGALES/Nogales Intl.
MMPQ RS
PALENQUE/Palenque
PUERTO MMPE RS
PEÑASCO/Aeropuerto del
Mar de Cortes
MMSF RG
SAN FELIPE/San Felipe Intl.
MMEP RS
TEPIC/Tepic Intl
BOCAS DEL TORO/ Bocas MPBO RG&AS Panama/ Tocumen Intl MPTO Y N N T Y P
Del Toro
METAR/SPECI and
TAF availability
provided meteorological office to be provided
ICAO Location
ICAO Location
METAR/SPECI
Temperature
State of the
Indicator
Indicator
State
forecast
runway
Trend
Name
Name
Tx/Tn
TAF
Use
1 2 3 4 5 6 7 8 9 10 11 12
METAR/SPECI and
TAF availability
provided meteorological office to be provided
ICAO Location
ICAO Location
METAR/SPECI
Temperature
State of the
Indicator
Indicator
State
forecast
runway
Trend
Name
Name
Tx/Tn
TAF
Use
1 2 3 4 5 6 7 8 9 10 11 12
METAR/SPECI and
TAF availability
provided meteorological office to be provided
ICAO Location
ICAO Location
METAR/SPECI
Temperature
State of the
Indicator
Indicator
State
forecast
runway
Trend
Name
Name
Tx/Tn
TAF
Use
1 2 3 4 5 6 7 8 9 10 11 12
Names in lower case letters indicate aerodromes for which reports (routine or selected special) are
required.
Names in upper-case letters indicate aerodromes for which forecasts are required.
Note: To be completed
AEROP. INTERNACIONALES
PROMEDIO
MES BASE SEQM SELT SEMT SEGU
ENERO 98,4 81,7 76,1 96,6 88,2
FEBRERO 98,6 95,7 72,7 91,5 89,6
MARZO 97,7 95,6 93,8 98,9 96,5
ABRIL 97,1 91,7 77,2 93,5 89,9
MAYO 98,0 94,2 84,1 93,5 92,5
JUNIO 97,7 95,6 71,4 94,0 89,7
75%
JULIO 93,8 89,5 77,7 91,8 88,2
AGOSTO 98,3 93,0 79,6 97,4 92,1
SEPTIEMBRE 96,7 94,2 81,6 98,7 92,8
OCTUBRE 98,4 90,3 88,6 98,0 93,8
NOVIEMBRE 99,3 94,9 88,8 98,8 95,5
DICIEMBRE 99,2 94,2 85,8 97,4 94,2
AER. INTERNACIONALES
PROMEDIO
MES BASE SEQM SELT SEMT SEGU
ENERO 99,3 97,5 95,2 97,9 97,5
FEBRERO 98,8 99,1 94,9 98,4 97,8
MARZO 98,9 98,4 93,8 98,9 97,5
ABRIL 98,8 97,5 94,9 97,8 97,3
MAYO 99,3 97,8 96,1 99,3 98,1
JUNIO 98,9 98,4 93,8 98,9 97,5
75%
JULIO 99,5 98,5 96,8 99,2 98,5
AGOSTO 99,7 97,8 96,1 99,3 98,2
SEPTIEMBRE 98,6 98,5 96,0 99,9 98,3
OCTUBRE 99,5 97,2 96,2 99,3 98,1
NOVIEMBRE 99,7 97,6 96,4 99,4 98,3
DICIEMBRE 99,7 99,1 96,9 97,2 98,2
AEROPUERTOS NO AOP
PROM.
MES SER SEC SEC SET SES SER SEG SES SEC SEJ SEM SEN SES
SETU
B U A N A O S T O D C L M
ENERO 83,8 82,8 84,8 82,8 72,7 77,9 70,2 88,6 66,3 56,8 69,2 66,7 72,7 81,6 75,5
FEBRERO 95,7 93,2 87,1 87,9 90,1 69,5 70,1 75,0 65,6 78,3 92,6 93,2 70,3 91,7 82,9
MARZO 87,8 97,9 94,0 95,5 89,8 97,0 96,8 98,3 97,5 77,7 89,4 90,6 73,4 94,8 91,5
ABRIL 85,0 94,7 89,2 92,8 83,6 73,6 84,0 78,5 83,6 65,4 91,7 96,9 74,9 94,6 84,9
MAYO 82,5 98,4 90,5 95,0 89,6 75,7 81,7 92,8 95,3 51,4 76,7 74,7 77,4 90,1 83,7
JUNIO 87,8 97,9 94,0 95,5 89,8 77,2 73,6 82,4 96,5 77,7 89,4 90,6 73,4 94,8 87,2
JULIO 77,2 94,7 88,9 90,6 81,4 64,8 78,8 91,8 90,3 79,2 76,2 90,8 73,0 91,1 83,5
100,
AGOSTO 88,4 96,2 94,8 84,4 76,9 87,9 93,5 95,0 85,6 93,8 97,5 81,9 99,0 91,1
0
SEPT. 94,1 99,3 93,1 93,3 79,7 89,2 89,7 90,0 94,7 94,5 86,2 91,8 81,5 97,2 91,0
OCTUBRE 93,9 98,5 94,0 93,5 86,8 82,9 92,1 90,1 95,8 90,3 80,6 97,3 91,6 96,8 91,7
NOV. 87,8 98,3 93,6 91,0 86,2 86,8 94,0 87,7 97,9 85,9 88,7 89,7 95,4 97,7 91,5
DIC. 87,7 96,3 92,0 94,8 90,1 87,8 94,0 93,1 95,3 78,9 88,6 98,8 91,3 96,8 91,8
PROMEDIO 87,6 96,0 91,5 92,3 85,4 79,9 84,4 88,5 89,5 76,8 85,3 89,9 79,7 93,9 87,2
SAM COM/MET 2019 Apéndice G al Informe sobre la Cuestión 1 del Orden del Día 1G-1
AEROPUERTOS NO AOP
PROM.
MES SER SEC SEC SET SES SER SEG SES SEC SEJ SEM SEN SES
SETU
B U A N A O S T O D C L M
ENERO 97,5 97,5 98,6 97,1 94,3 97,3 95,9 98,5 97,1 93,8 90,4 99,1 94,8 93,1 96,4
FEBRERO 99,4 97,5 96,2 95,8 96,9 97,3 95,7 96,7 95,3 96,9 97,5 98,1 98,6 96,4 97,2
MARZO 97,4 95,2 98,0 97,5 99,0 97,0 96,8 98,3 97,5 98,0 96,3 97,8 94,8 95,3 97,2
ABRIL 93,3 99,4 98,1 96,7 95,1 97,9 98,3 98,2 97,4 97,2 98,9 98,7 92,1 96,7 97,1
MAYO 99,0 99,5 99,4 98,5 98,5 98,5 98,2 99,0 97,3 95,5 97,4 98,3 97,3 97,3 98,1
JUNIO 97,4 99,5 98,0 97,5 99,0 97,0 96,8 98,3 97,5 98,0 96,3 97,8 94,8 95,3 97,4
JULIO 100,0 100,0 98,6 99,3 98,3 98,0 98,4 99,5 99,0 99,3 95,5 99,5 97,8 99,0 98,7
AGOSTO 97,5 100,0 98,6 98,8 99,3 98,0 99,2 96,5 98,5 98,8 97,5 99,3 97,0 98,5 98,4
SEPT. 94,4 95,0 98,1 98,5 98,7 98,5 99,2 95,9 99,2 94,1 91,8 96,9 98,7 98,5 97,3
OCTUBRE 99,5 100,0 98,0 96,0 94,8 98,3 97,6 97,0 99,3 97,0 87,3 99,3 97,8 98,8 97,4
NOV. 96,1 100,0 97,7 96,9 97,7 97,7 99,6 98,2 99,0 97,9 98,7 99,0 99,2 98,2 98,3
DIC. 99,4 100,0 97,0 97,0 97,5 96,2 99,6 99,3 99,3 95,3 93,8 98,5 97,3 97,5 97,8
PROMEDI
97,6 98,6 98,0 97,5 97,4 97,6 97,9 98,0 98,0 96,8 95,1 98,5 96,7 97,1 97,5
O
SAM COM/MET 2019 Informe sobre la Cuestión 2 del Orden del Día 2-1
Cuestión 2 del
Orden del Día: Seguimiento a la implantación regional del proyecto de implantación de la
arquitectura de la ATN y de las Aplicaciones tierra-tierra de la ATN en la Región
SAM (sistemas AMHS y la interconexión de los mismos).
2.1 Sobre esta cuestión del orden del día, la Reunión analizó la siguiente nota de estudio:
2.2 La Reunión tomó nota del estatus de la implantación AMHS por los Estados de la Región
Sudamericana de OACI (SAM). Sobre el asunto, fue resaltado que todos los Estados ya han implantado
sus sistemas AMHS en los Centros COM. El Apéndice A a este Informe presenta todas las
interconexiones AMHS planeadas para la región, siendo que las que están en color verde ya están
operativas.
2.5 El nuevo sistema AMHS a ser implantado por Perú, deberá permitir el intercambio de
datos tierra-tierra, utilizando el modelo de Intercambio de Información de Vuelos (FIXM), el modelo de
Intercambio de Información Aeronáutica (AIXM) y el modelo para Intercambio de Información
Meteorológica (IWXXM), con formatos normalizados del Lenguaje de Marcado Extensible (XML), y
proveerá una interfaz para la integración con el SWIM, que permita la interoperabilidad con sus
aplicaciones e infraestructura.
Humano-Máquina (HMI) que construya el adjunto con la información OPMET en el formato IWXXM y
transmita en un mensaje AMHS.
2.8 Otra posibilidad es tener una aplicación (software) que codifique la información OPMET
en el formato IWXXM, generando un archivo XML, que podrá ser encaminado como adjunto a un
mensaje AMHS.
2.9 La Reunión tomó nota que el Banco Regional OPMET de Brasilia ha sido adecuado para
recibir y almacenar informaciones meteorológicas en el formato IWXXM, como también, enviar vía
AMHS las informaciones disponibles, como adjunto a un mensaje AMHS. Existe una dirección AMHS
específica del Banco OPMET de Brasilia para recepción/transmisión en el formato IWXXM, que es:
2.10 Sin embargo, el Banco Regional OPMET de Brasilia sigue, también, recibiendo y
transmitiendo, las informaciones OPMET en el formato TAC por medio de la dirección AMHS usual
(C=XX; A=ICAO; P=SB; O=SBBR; OU1=SBBR; CN=SBBRYZYX).
2.11 La Secretaría de la Reunión informó que en la última reunión del Grupo de Implantación
de la Región SAM (SAM/IG/22, Lima-Perú, 19 al 23 de noviembre de 2018), fue creado el Grupo de
Tarea de Interoperabilidad (GT Interop) que podrá conformar un Subgrupo para tratar la interoperabilidad
de los sistemas existentes para confeccionar, transmitir y recibir mensajes en el formato IWXXM, en la
Región. La Secretaría presentará una nota en la SAM/IG/23 con la sugerencia para que se conforme el
Subgrupo MET IWXXM en el GT Interop.
-----
SAM COM/MET 2019 Apéndice A al Informe sobre la Cuestión 2 del Orden del Día 2A-1
Interconexiones AMHS – Región SAM / AMHS Interconnection – SAM Region
Conexión P1 / Operativa en /
Situación / Situation Observaciones / Notes
P1 Connection Operational in
1 SAEZ – SBBR Operativa / Operational 04/04/2018
2 SAEZ – SCSC Pre operativa / Pre-operational
3 SAEZ – SGAS Operativa / Operational 30/11/2018
4 SAEZ – SLLP
5 SAEZ – SPIM Pre operativa / Pre-operational
6 SAEZ – SUMU
7 SBBR – SGAS Operativa / Operational 30/11/2018
8 SBBR – SLLP En coordinación / In coordination
9 SBBR – SKBO Operativa / Operational 22/05/2017
10 SBBR – SMJP Operativa / Operational 11/10/2018
11 SBBR – SOCA En coordinación / In coordination
12 SBBR – SPIM Operativa / Operational 14/12/2015
13 SBBR – SUMU
14 SBBR – SVCA Operativa / Operational 28/02/2018
15 SBBR – SYCJ Operativa / Operational 16/07/2017
16 SCSC – SPIM Operativa / Operational 14/12/2015
17 SEQU – SKBO Pre operativa / Pre-operational
18 SEQU – SPIM Operativa / Operational 14/12/2015
19 SEQU – SVCA Operativa / Operational 11/10/2018
20 SKBO – SPIM Operativa / Operational
21 SKBO – SVCA Operativa / Operational 01/12/2017
22 SLLP – SPIM En coordinación / In coordination
23 SMJP – SVCA En coordinación / In coordination
24 SMJP – SYCJ Operativa / Operational 11/10/2018
25 SOCA – SVCA En coordinación / In coordination
26 SPIM – SVCA Operativa / Operational 01/12/2017
27 SVCA – SYCJ En coordinación / In coordination
SAM COM/MET 2019 Apéndice A al Informe sobre la Cuestión 2 del Orden del Día 2A-2
Interconexiones AMHS – Región SAM / AMHS Interconnection – SAM Region
Conexión P1 / Operativa en /
Situación / Situation Observaciones / Notes
P1 Connection Operational in
28 SAEZ – FAOR
29 SAEZ – SITA
30 SAEZ – SVCA
31 SBBR – GOOO En coordinación / In coordination
32 SBBR – KATL En coordinación / In coordination
33 SBBR – LEEE Operativa / Operational 11/10/2018
34 SBBR – SITA Operativa / Operational 16/08/2018
35 SKBO – MPPC En coordinación / In coordination
36 SPIM – KATL En coordinación / In coordination
37 SVCA – KATL En coordinación / In coordination
38 SVCA – LEEE
39 SVCA – TNCC En coordinación / In coordination
40 SVCA – TTPP
SAM COM/MET 2019 Apéndice B al Informe sobre la Cuestión 2 del Orden del Día 2B-1
<saf:locationIndicatorICAO>LFPG</saf:locationIndicatorICAO>
<saf:ARP>
<gml:Point gml:id="ref-point-LFPG" uomLabels="deg
deg m" axisLabels="Lat Lon Altitude" srsDimension="3"
srsName="http://www.opengis.net/def/crs/EPSG/0/4979">
<gml:pos>49.016666666666666 2.5166666666666666
109</gml:pos>
</gml:Point>
</saf:ARP>
</saf:Aerodrome>
</sam:sampledFeature>
<sams:shape>
<gml:Point gml:id="obs-point-LFPG" uomLabels="deg deg m"
axisLabels="Lat Lon Altitude" srsDimension="3"
srsName="http://www.opengis.net/def/crs/EPSG/0/4979">
<gml:pos>49.016666666666666 2.5166666666666666
109</gml:pos>
</gml:Point>
</sams:shape>
</sams:SF_SpatialSamplingFeature>
</om:featureOfInterest>
<om:result>
<iwxxm:MeteorologicalAerodromeObservationRecord
gml:id="observation-record-LFPG-20160511T123000Z"
cloudAndVisibilityOK="false">
<iwxxm:airTemperature uom="Cel">18</iwxxm:airTemperature>
<iwxxm:dewpointTemperature
uom="Cel">15</iwxxm:dewpointTemperature>
<iwxxm:qnh uom="hPa">1002</iwxxm:qnh>
<iwxxm:surfaceWind>
<iwxxm:AerodromeSurfaceWind variableDirection="true">
<iwxxm:meanWindSpeed uom="kn">3</iwxxm:meanWindSpeed>
</iwxxm:AerodromeSurfaceWind>
</iwxxm:surfaceWind>
Page 2
<iwxxm:visibility>
<iwxxm:AerodromeHorizontalVisibility>
<iwxxm:prevailingVisibility
uom="km">10</iwxxm:prevailingVisibility>
<iwxxm:prevailingVisibilityOperator>ABOVE</iwxxm:prevailingVisibilit
yOperator>
</iwxxm:AerodromeHorizontalVisibility>
</iwxxm:visibility>
<iwxxm:presentWeather
xlink:href="http://codes.wmo.int/306/4678/-RA" xlink:title="Light
precipitation of rain"/>
<iwxxm:cloud>
<iwxxm:AerodromeObservedClouds>
<iwxxm:layer>
<iwxxm:CloudLayer>
<iwxxm:amount
xlink:href="http://codes.wmo.int/bufr4/codeflag/0-20-008/2"
xlink:title="Scattered"/>
<iwxxm:base uom="ft">1200</iwxxm:base>
</iwxxm:CloudLayer>
</iwxxm:layer>
<iwxxm:layer>
<iwxxm:CloudLayer>
<iwxxm:amount
xlink:href="http://codes.wmo.int/bufr4/codeflag/0-20-008/3"
xlink:title="Broken"/>
<iwxxm:base uom="ft">8400</iwxxm:base>
</iwxxm:CloudLayer>
</iwxxm:layer>
</iwxxm:AerodromeObservedClouds>
</iwxxm:cloud>
</iwxxm:MeteorologicalAerodromeObservationRecord>
</om:result>
</om:OM_Observation>
</iwxxm:observation>
</iwxxm:METAR></metgate:data><metgate:mwoname>LFPG</metgate:mwoname>
<metgate:mwolocation><gml:Point srsName="urn:ogc:def:crs:EPSG::4326"
srsDimension="2"><gml:pos>49.016667
2.533333</gml:pos></gml:Point></metgate:mwolocation><metgate:mwocrea
tiondate>2016-05-25T12:00:00Z</metgate:mwocreationdate><metgate:inse
rtiondate>2016-05-25T12:18:48.261Z</metgate:insertiondate></metgate:
metariwxxm></wfs:member></wfs:FeatureCollection>
Page 3
SAM COM/MET 2019 Apéndice C al Informe sobre la Cuestión 2 del Orden del Día 2C-1
International Civil Aviation Organization
Concept of Operations for the Transition of
OPMET Data Exchange using
IWXXM
(EUR Doc 033)
First Edition ‐ 2016
PREPARED BY THE EUROPEAN AND NORTH ATLANTIC OFFICE OF ICAO
EDITION DATE 15/06/2016
International Civil Aviation Organization
PREPARED BY THE EUROPEAN AND NORTH ATLANTIC OFFICE OF ICAO EDITION DATE 15/06/2016
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 1 of 22
TABLE of CONTENT
TABLE of CONTENT 2
1 Introduction 3
3 Assumptions 4
3.1 Managing the transition 4
3.2 Variances to the IWXXM Model 4
3.3 Translation 4
3.4 Data collection 5
3.5 Transmission & Routing 5
3.6 Compliance Testing 5
3.7 Databank 5
3.8 Aeronautical Information Metadata 6
4 Framework 7
4.1 Functionalities definitions 8
4.1.1 Data Producer/Originating Unit 8
4.1.2 International Data Aggregator 8
4.1.3 International functions for Data Translation Centre 10
4.1.4 Data Switch 11
4.1.5 Databank 12
4.2 Regional Centres Definitions 15
4.2.1 National OPMET Centre (NOC) 15
4.2.2 Regional OPMET Centre (ROC) 15
4.2.3 Interregional OPMET Gateway (IROG) 15
4.2.4 Regional OPMET Databank (RODB) 15
5 Transition 17
5.1 Phase 1 Pre–Requisites to Transition – until Nov 2016 17
5.2 Phase 2 From Nov 2016 until Amendment 78 applicability date – 2018 19
5.3 Phase 3 After Amendment 78 applicability date – 2018 21
6 Glossary 22
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 2 of 22
1 Introduction
The bilateral exchange of IWXXM (ICAO Meteorological Information Exchange Model) based information is
introduced in amendment 76 to ICAO Annex 3 (Meteorological Service for International Air Navigation ) from
November 2013, enabling States to exchange their OPMET data not only in TAC (Traditional Alphanumeric Code
form) but also in XML (Extensible Mark-up Language). This represents the start of a huge change from the
provision and exchange of textual OPMET data towards a digital environment supporting SWIM (System Wide
Information Management). Since their inception, OPMET data have been promulgated to end systems and they
were initially designed to be human readable, with a requirement to be highly compact because of limitations in
bandwidth.
The current use of OPMET in a TAC format presents an obstacle to the digital use of the data as it is not geo-
referenced. This makes the handling of global data difficult to use correctly and expensive to maintain, this has
been exemplified in significant difficulties during code changes. The current coding practices also present an
obstacle to efficient automation as State coding exceptions are quite commonly used.
IWXXM represents the first step to move to an environment where the systems handling this data can make
more use of standard applications and techniques. The development of new systems which provide and support
digital OPMET will require initial investment but the use of enabling data exchange standards for other domains
such as AIXM (Aeronautical Information Exchange Model) and FIXM (Flight Information eXchange Model) along
with IWXXM will lead to cost reduction due to the implementation of widely used data modelling techniques
including OGC (Open Geospatial Consortium) segments. Consequently, users will be presented with opportunities
to create new products at lower cost by fusing this data.
It is essential that the transition towards the use of IWXXM is adequately planned and equipped to make
reliable data sets available to users for exploitation as soon as possible at a Regional - and Global - scale. This
Concept of Operation provides elements and steps for consideration in achieving that aim by defining common
definitions, concepts as well as structured phases to be implemented in relation to the International exchange of
OPMET data.
Amendment 76 enabled the bilateral exchange of XML data for those States in a position to do so.
The planned Amendment 77 recommends the international exchange of XML-formatted METAR/SPECI,
TAF, AIRMET and SIGMET from November 2016.
The planned Amendment 78 will require the international exchange of XML-formatted METAR/SPECI,
TAF, AIRMET and SIGMET as a standard (planned 2018).
Note: VAA and TCA are also part of amendments 77 and 78, but they will not be explicitly dealt within this
document.
The intention of this Concept of Operation is not to define Net Centric services but to provide guidance for a
swift transition to IWXXM implementation as a first step towards SWIM.
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 3 of 22
3 Assumptions
Assumptions on applicable general principles for the international exchange of OPMET data have been made.
Their intention is to support the different identified phases that will lead to a managed pan-European IWXXM
based international exchange of METAR/SPECI, TAF, AIRMET and SIGMET by the Amendment 78 to Annex 3
applicability date. This could also support a global implementation of IWXXM exchange by the same date.
These Assumptions are listed below.
It is assumed that different regions will progress at different rates. It is necessary to create a plan that
facilitates this different implementation pace. (Assumption 2)
Note: Groups such as Data Management Group for EUR & Bulletin Management Group for MID could be the
right groups to manage this transition (or equivalent groups in other regions).
Note: “IWXXM model” should here be understood as the XML schema including all necessary GML
components (including metadata) necessary for the exchange of IWXXM data
3.3 Translation
In order to minimize as much as possible the translation between formats from the Amendment 77
applicability date until the Amendment 78 applicability date for IWXXM, it is assumed that more and more
Originating Units e.g. aerodrome meteorological offices, Met Watch Offices etc. will have IWXXM capability and
will produce both TAC and IWXXM formats. Following Annex 3 Amendments 76 and 77 requirements, when a
State produces IWXXM data, it will also produce TAC data that will be exchanged internationally in addition to
IWXXM data. (Assumption 4)
As a consequence of previous Assumption 4, there will be no translation/conversion from IWXXM to TAC for
international distribution before the Amendment 78 applicability date. (Assumption 5)
Where a translation from TAC to IWXXM is necessary and conducted, the translation centre and date/time of
when the translation occurred will be identified within the XML message. The translation centre metadata will be
defined as part of a globally accepted GML/XML model. (Assumption 6)
To avoid transmission of TAC messages translated from IWXXM after the implementation of Amendment 78
to Annex 3, all inter-regional exchange will be carried out using only IWXXM. (Assumption 7)
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 4 of 22
Note: If it happens that TAC exchange is still present and no longer required beyond the Amendment 78
applicability date - at least partly in some regions - this should be organized (by regional agreement) within the
region. Such an arrangement might also include XML to TAC translation.
It is assumed that non regular reports (e.g. SIGMET) will NOT be aggregated in the same file. (Assumption 8)
When creating a feature collection of the same type of IWXXM data (e.g. METAR) , further named as
“bulletin”, the aggregating centre identifier and date/time group of when the collection was created will be
indicated within the XML message. The aggregating centre metadata will be defined as part of a globally accepted
GML/XML model.
(Assumption 9)
A single bulletin will only contain TAC or XML, never both. (Assumption 10)
Given the size and character set of IWXXM messages, it will not be possible for these messages to be
transmitted via AFTN. The file containing the bulletin will be compressed and FTBP (File Transfer Body Part)
under Extended AMHS (ATS Message Handling System) will be used to exchange IWXXM data internationally
through the AFS. (Assumption 12)
The principles of exchanging IWXXM data on AMHS are further described in section 4.1.4 but, in general, rules
close to the ones governing the TAC transmission are applied.
The WMO abbreviated header structure (TTAAiiCCCC) will be part of the filename of the File Transfer Body Part
and used as data identifier. The routing of IWXXM messages will associate this data identifier with AMHS
address(es) that the message should be sent to. (Assumption 13)
As a file name extension, the appropriate suffix developed by WMO will be used to identify compressed data
using globally agreed compression techniques. (Assumption 14)
Note: The number of FTBPs and the maximum message size are subject to the AMHS specifications.
3.7 Databank
In order to allow IWXXM data retrieval from International Databanks, a standard set of queries for IWXXM
data will also need to be developed, agreed and documented. An Interface Control Document will be provided to
describe the query structure, structure of the answer(s) and bulletin header(s) to be used by the International
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 5 of 22
Databank, as well as all other information necessary for the automatic use of the query answers. The proposed
query language for IWXXM data will follow similar rules as the TAC-requests (c.f. section 4.1.5).
(Assumption 16)
The metadata is additional information relevant to the type of the aeronautical information object i.e. an
airport, an FIR. A challenge resides in getting the correct state of this aeronautical information, especially for
centres that will perform translation from TAC to XML that will require this. Therefore, obtaining this from an
authorized source is implied, in order to provide the right piece of information that characterizes the data (e.g. for
a METAR, which airport location indicator and official name, its altitude, longitude, latitude etc …).
Note: A further step that could be foreseen is a possible indirect link to the AIXM model where the IWXXM
data will just reference where to get this aeronautical information metadata from, therefore avoiding possible
inconsistencies between the transported metadata inside the IWXXM data and the current status of this
aeronautical information as part of the AIXM model.
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 6 of 22
4 Framework
This section is intended to describe the generalized elements which can be used to establish a framework for
the exchange of IWXXM data, both intra-regionally and inter-regionally, with the neighbour regions. One key
aspect is, that the framework needs to be flexible to permit development of an intra-regional structure suitable to
the requirements, but at the same time allowing establishment of controlled and coordinated exchange between
regions.
The framework is organized into a basic set of functions/type of operations as described in section 4.1. A list
of requirements that should be met to carry out each respective function as well as illustrations on how these
functions may be performed/combined are provided in the same section.
In section 4.2, more complex regional entities which comprise some of the above functions are described.
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 7 of 22
4.1 Functionalities definitions
The Data Producer-function may be performed by an aeronautical meteorological station (e.g. producing a
METAR), a MWO (Meteorological Watch Office) producing AIRMET or SIGMETS or as well by an AMO (Aerodrome
Meteorological Office) providing TAFs.
IWXXM TAC
Producer Producer
For an IWXXM Producer, the following functions could be the subject to compliance testing:
When aggregating reports, the Aggregator shall collect and combine them as a bulletin – defined as a Feature
collection - in conformance with the globally agreed GML/XML model. In particular, all required metadata
information, as defined by the globally accepted GML model, should be indicated.
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 8 of 22
IWXXM Report 1
IWXXM Report 2
IWXXM Report 3
IWXXM
Aggregator
IWXXM Report 1
IWXXM Report 3
IWXXM Report 2
For an IWXXM Aggregator, the following functions could be the subject of compliance testing.
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 9 of 22
4.1.3 International functions for Data Translation Centre
A data translator converts TAC data into IWXXM on behalf of another State. To do so, it shall be able to parse
incoming TACs and apply the data to IWXXM schema.
It is expected that this will be carried out on a bulletin basis so that the translator will always be associated
with an aggregator function.
The translator should provide an indication of where and when the translation has been carried out in order
to provide traceability. This shall be achieved by introducing agreed metadata elements (centre identifier and
time stamp) that shall be defined as part of a globally accepted GML/XML model.
It is highly likely that not all incoming TACs will be translatable because of non-conformance with TAC
standards. There will be a need to have procedures in place to deal with these rejected data.
IWXXM
IWXXM IWXXM
Translator Aggregator
TAC
IWXXM
Bulletins
For an IWXXM Translator, the following functions could be the subject of compliance testing.
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 10 of 22
4.1.4 Data Switch
A Data Switch will route IWXXM data according to the TTAAiiCCCC part of the filename of the File Transfer
Body Part. The filename including the current WMO bulletin header will be structured as follows (WMO naming
convention A):
A_TTAAiiCCCCYYGGggBBB_C_CCCC_YYYYMMddhhmmss.xml.[compression_suffix],
Where the elements in black and bold are fixed elements and:
TTAAiiCCCCYYGGgg is the current WMO header with the date time group
BBB is optional (as usual),
CCCC is the repeated CCCC part from TTAAiiCCCC,
YYYYMMddhhmmss is the date/time group
Note: [compression_suffix] will be subject to further acceptance, depending on which compression technique is
agreed. Compression software such as zip should be avoided as it may allow transportation of more than one file
and directories as well.
The routing table will associate this TTAAiiCCCC data identifier with the AMHS addresses where the data should
be sent to. The compressed file will be named with the suffix appropriate to the compression and sent onto
AMHS.
(Assumption 12)
WMO defined T1T2 (from TTAAii) for the following data types:
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 11 of 22
IWXXM
Switch
IWXXM Bulletin
TAC Report 1
IWXXM Report 1
IWXXM IWXXM Report 2
IWXXM Report 1
Translator IWXXM Report 3
IWXXM Report 4
IWXXM Report 5
METAR
IWXXM Report 2
IWXXM
Aggregator
IWXXM Report 3
METAR
IWXXM Report 4
IWXXM Report 5
METAR
METAR
4.1.5 Databank
An International Databank will provide the capability for users to interrogate IWXXM data through the AFS in
much the same way as the RODBs currently provide for TAC data.
There will be no TAC to IWXXM translation taking place by the Databank in case the requested OPMET is only
available in TAC, as this translation should be done upstream by a Translation Centre.
Although the implementation of Net Centric Services is beyond the scope of this CONOPS, the Databank
element could as well provide Net Centric services in addition to the AFS based IWXXM interrogation capabilities.
As soon as agreed descriptions of the interface to request data via web-services are available, this additional
feature may be added for the databank.
For an IWXXM Databank, the following functions could be the subject of compliance testing.
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 12 of 22
Example: the implementation of a combined TAC & IWXXM Databank
The picture below illustrates a possible implementation of a RODB with combined TAC and IWXXM functionalities.
Technical principles:
- Interfaces:
o the Databank has an AMHS P3 connection to the AMHS Message Transfer Agent (MTA) of a COM
centre
o in case the COM Centre still serves AFTN users, the Databank may have a separate AFTN
connection to the COM Centres AFTN switch or alternatively, the COM Centre will take care of the
AFTN-AMHS conversion
- Databank tables: data in IWXXM and data in TAC are stored in separate sets of tables.
Operational principles:
- DB Requests
o Requests for TAC data can be sent via AFTN or via AMHS (Textual Body Part). These requests will
continue to work as described in the current RODB Interface Control Documents
o Requests for IWXXM data shall be sent via AMHS as Textual Body Part.
o Requesting data in IWXXM will work in a similar way as requesting TAC data. The above example
uses a syntax similar to the TAC requests, but:
“RQX/” is used as the start of the query
only the new IWXXM T1T2 message types defined by WMO are allowed
For example: RQX/LALOWW/LTEBBR/LSLFFF=
o Requests for TAC data and requests for IWXXM data shall not be mixed
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 13 of 22
o Any violation of the above principles (e.g. the request “RQX/LSLOWW=” received via AFTN), will
result in an automatic reply sent by the databank, informing the user that this is not allowed.
- DB Replies
o Replies to TAC requests will continue to work as described in the current RODB Interface Control
Documents.
o Reply reports of a IWXXM request will be aggregated into one or more files, according to the same
rules used by the Data Aggregators, e.g. no mixing of message types in one file.
o These files will be compressed and a correct file name with appropriate suffix supplied.
o These files will be sent as FTBP through AMHS.
o The RODB Interface Control Documents will specify an extended set of standardized information
& error replies.
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 14 of 22
4.2 Regional Centres Definitions
Note: It is assumed that the data provided by NOCs is in accordance with the similar specifications as
applicable for an International Data Aggregator
Within the EUR-region, there are three IROGs: London, Toulouse and Vienna.
An IROG is responsible for the collection of all required OPMET data from its Interregional Area(s) of
Responsibility (IAoR) and its dissemination to the ROCs in its region.
Furthermore, the IROGs are responsible for collection and dissemination of their region’s required OPMET
data to their partner IROGs.
The IROG is responsible for the validation of the bulletins sent to the IROGs of its IAoR and received from their
IAoR.
For IWXXM exchange, an IROG should perform the following functions:
Data Aggregator
Data Translation Centre
Data Switch
The Regional OPMET Databank(s) (RODB) are supplied with required OPMET data by the ROCs. These
databases can be queried via the AFS by using a specified query language.
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 15 of 22
Details on the query language as well as the supported data types can be found in EUR Doc 018, Appendix A
(EUR Regional Interface Control Document for OPMET Database Access Procedures). Those documents will be
updated to integrate the new functions.
An RODB shall be able to fulfil the requirements to handle IWXXM-code as described in paragraph 4.1.5.
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 16 of 22
5 Transition
The first necessary step is to define the prerequisites in order to be able to exchange IWXXM OPMET data.
This will impact not only the network itself, but also the Message Switching Systems and most of the end-user
systems.
Governance
Furthermore a full liaison should be established and maintained between the ICAO groups in charge of
meteorology & data exchange and groups in charge of the AFS network.
For data translation purposes, if there is a systematic need for the translation of data on behalf of a State, this
may be performed by the dedicated ROC for the part of the region under its Area of Responsibility and the IROGs
for the interregional distribution.
Documentation
The region will define and have a plan in place to provide IWXXM data. This plan shall be published and
maintained by the designated responsible groups (FAQ’s etc. should be available).
ICAO and WMO documentation and provisions should be published/available describing the IWXXM code
itself as well as documentation referencing the appropriate schemas and rules made available in order to handle
this new format.
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 17 of 22
Facilities
An agreed process should be defined to ensure that data generated by Data Producers are compliant – in
particular, no extension will be published internationally. In order to promote the use of IWXXM, the process
should be widely known and shared and some tools to check the compliance state of the data easily accessible
and usable.
An identical process should be agreed to initiate and enable the IWXXM exchange between regions.
An AMHS network will be available to support exchange IWXXM data by the use of FTBP for between those
States wishing to do so. Corresponding AMHS connections will be available between those regions exchanging
IWXXM data.
Cyber Security
- appropriate AFS security elements should be defined by the ICAO groups in charge of information
management / networks in order to introduce the operational exchange of IWXXM data via AMHS.
Source of Metadata
- Update process or notification on modifications about Aeronautical information metadata by the States
should be in place at the end of the period or metadata sources should be defined and agreed.
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 18 of 22
5.2 Phase 2 From Nov 2016 until Amendment 78 applicability date – 2018
Note: if it happens that some delays occur in having the IWXXM model including metadata structure and
agreement in FTBP use available, it is assumed that the operations in exchanging IWXXM data will be delayed and
probably not be ready at the start of the period.
Regional Coordination/planning
- The regional group(s) designated to deal with the transition should define and monitor:
- Intra-regional plan about AMHS infrastructure/links planning and IWXXM data exchange
between the three ROCs, and between ROC and RODB.
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 19 of 22
- Intra-regional plan about the IWXXM data exchange planning by the States to their ROC.
- The Contingency plans for the ROCs should integrate the IWXXM data and be ready before the end of the
period.
- Testing platform and software are made available and accessible for every State.
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 20 of 22
Figure 1 below provides an example of the EUR Region interfacing with 2 other Regions.
Region 2
Region 2
IWXXM EUR Region 1
Region 2
Switch IWXXM
(IROG 2)
Region 2
TAC
Switch
Region 1
(IROG 1)
IWXXM
(converted)
TAC to IWXXM
(IROG 1) Region 1
TAC
Figure 1: Phase 2, I/R exchange with Region1 (not IWXXM capable) and Region 2 (IWXXM capable)
TBD
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 21 of 22
6 Glossary
Concept of Operations for the Transition of OPMET Data Exchange using IWXXM
Version 1.1 15/06/2016 Page 22 of 22
SAM COM/MET 2019 Informe sobre la Cuestión 3 del Orden del Día 3-1
Cuestión 3 del
Orden del Día: Revisión de los mensajes SIGMET. Análisis del formato e intercambio.
3.1 Bajo esta cuestión del orden del día, la Reunión analizó las siguientes notas de estudios e
informativas:
3.2 El Estado de Ecuador recordó a la Reunión que la Reunión de MP/2 consideró los casos
en que existen problemas relacionados a la vigilancia de los fenómenos severos en ruta. En este sentido,
se han observado mensajes SIGMET emitidos para un mismo fenómeno, pero que afectan varias FIR. Los
problemas observados se refieren a inconsistencias en la información de áreas afectadas, diferencias en
los niveles de topes e incoherencia en la información relacionada con fenómenos severos entre los límites
de la región de información de vuelo (FIR). La Reunión reconoció la dificultad para las coordinaciones
entre los Estados, pero entiende necesario establecer procedimientos de coordinación utilizando los
medios tecnológicos actualmente disponibles (chat, teleconferencia, entre otros), a fin de emitir informes
coherentes entre las Oficinas de Vigilancia Meteorológica involucradas que reflejen fielmente la
ocurrencia de los fenómenos, emitiendo informes homogéneos y que permita una continuidad en la
descripción de los fenómenos.
3.4 Los Estados coordinarán para hacer los ejercicios y comunicar a la Secretaría sobre sus
resultados y factibilidad de implementación de los procedimientos de coordinación de vigilancia de los
fenómenos.
ZOOM: https://play.google.com/store/apps/details?id=us.zoom.videomeetings
TELEGRAM: https://play.google.com/store/apps/details?id=org.telegram.messenger
3.6 La Reunión tomo nota que, en particular durante el año 2018, la Región se ha visto
afectada por varios incidentes aéreos en los que las tormentas, la formación de hielo y la turbulencia
severa han sido factores contribuyentes o han ocasionado los mismos.
3.7 La Reunión consideró que, teniendo en cuenta las situaciones ocurridas en los últimos
años, y atendiendo el nuevo escenario que se genera con el cambio climático que está experimentando
nuestro planeta, podría estar contribuyendo significativamente en la intensidad, recurrencia y presencia de
condiciones meteorológicas cada día más severas que constituyen un peligro mayor para las operaciones
de vuelo. Entendió que, conocer con la mayor precisión los lugares, la severidad, la presencia y la
recurrencia de ellas, ayudará a prevenir o evitar los riesgos que podrían enfrentar las tripulaciones de
vuelo.
3.8 La Reunión al observar estas situaciones, entendió que es necesario tomar acciones para
ayudar a mitigar los riesgos que conlleva la ocurrencia de fenómenos severos atmosféricos para la
aviación. En ese contexto, entendió que las acciones a ser implementadas deben ser enfocadas en
diferentes ámbitos como:
a) Coordinación ATS/MET
b) Personal MET
c) DOV y tripulación de vuelos (Pilotos)
3.10 Así mismo, pidió a la Secretaría estudie la factibilidad de organizar un Taller Regional
sobre SIGMET, en coordinación con otras instituciones, orientado a toda la comunidad aeronáutica
(Pilotos, ATCO, AIM, MET, DOV) para el año 2020.
-------
SAM COM/MET 2019 Informe sobre la Cuestión 4 del Orden del Día 4-1
Cuestión 4 del
Orden del Día: Ejercicios de mensajes SIGMET por cenizas volcánicas. Evolución y futuros
proyectos.
4.1 Bajo esta cuestión del orden del día, la Reunión consideró la NE/10 - Análisis de los
resultados de Ejercicios de Cenizas Volcánicas, presentada por la Secretaría.
4.2 La Reunión recordó que los ejercicios de mensajes SIGMET por cenizas volcánicas han
sido realizados periódicamente desde el GREPECAS/14, en virtud de la Conclusión 14/2 del
GREPECAS.
4.3 La Reunión recordó, además, que, en el año 2015, el VAAC de Washington propuso
disminuir el período de ejercicios, de 36 horas a 12 horas por una cuestión de sobrecarga de trabajo. La
Reunión de Proyectos MET dispuso que pudieran realizarse dos ejercicios, uno liderado por el VAAC de
Buenos Aíres, con una validez de 36 horas, y otro por el VAAC de Washington, con una duración de 12
horas.
4.4 Adicionalmente, en el 2017, luego de una teleconferencia entre representantes del VAAC
de Washington, representante de la Oficina NACC de la OACI y delegados de los Estados de la Región
SAM que se encuentran asociados al VAAC de Washington, se propuso la utilización de un canal de chat
para la obtención de información de asesoramiento sobre cenizas volcánicas, así como probables
ejercicios. Algunas pruebas realizadas por el Estado de Ecuador no han sido satisfactorias.
4.5 La Reunión al considerar esta situación y considerando que la Conclusión 14/2 continúa
vigente, recomendó retomar los ejercicios con una frecuencia de una vez por año para.
4.6 Con relación a la liberación de material radiactivo, y atendiendo que ningún Estado ha
manifestado contar con un Plan de Contingencia sobre la misma, la Reunión recomendó incluir este punto
en la revisión de los Acuerdos ATS/MET mencionado en la Cuestión 3, además de planificar talleres y
charlas con personal ATS acerca de las implicancias de la liberación de material radiactivo en la
atmósfera. Así mismo, instó a los Estados a actualizar al personal en la preparación de los mensajes
SIGMET relativos a liberación de material radiactivo en el contexto de la Enmienda 78 al Anexo 3 de la
OACI.
SAM COM/MET 2019 Informe sobre la Cuestión 5 del Orden del Día 5-1
Cuestión 5 del
Orden del Día:
Enmienda 78 al Anexo 3. Implantación del intercambio de datos OPMET en
formato XML/GML, modelo IWXXM, preparación para el intercambio de
mensajes OPMET en un ambiente SWIM y mensajes de condición espacial
(Meteorología espacial).
5.1 Bajo esta cuestión del orden del día se presentaron las siguientes notas de estudios e
informativas:
5.2 La Reunión fue informada que, con relación al IWXXM, la Enmienda 78 al Anexo 3 de la
OACI ha indicado lo siguiente:
Hasta el 4 de noviembre del 2020, es una recomendación transmitir en formato
IWXXM GML todos los mensajes de asesoramiento (Cenizas Volcánicas,
Ciclones Tropicales, Condiciones Espaciales) y los mensajes OPMET
(METAR, SPECI, TAF, SIGMET, AIRMET).
A partir del 5 de noviembre del 2020, la transmisión en formato IWXXM GML
es una estándar.
Con relación a los mensajes de asesoramiento sobre condiciones espaciales, la
recomendación es a partir del 7 de noviembre del 2019.
5.5 Con relación al mismo, Venezuela presentó el desarrollo del convertidor de mensajes
OPMET, del formato alfanumérico al formato XML. Los desarrollos realizados por el proveedor de
servicios meteorológicos aeronáuticos de Venezuela, actualmente puede convertir al formato XML los
mensajes OPMET de METAR y TAF, tanto individualmente como en forma colectiva, y presentarlos en el
formato como para adjuntarlos a los mensajes en el AMHS.
5.6 Considerando que el Estado de Cuba también ha desarrollado su propio banco de datos y
los procesos para la transmisión de la información a través de la red AMHS, la Reunión sugirió realizar
trabajos en conjunto entre los Estados de Cuba y Venezuela, en cuanto al desarrollo de una versión del
IWXXM que esté en capacidad de codificar los mensajes OPMET y ser transmitidos por los sistemas
AMHS, ya que en la actualidad Venezuela cuenta con un software de codificación llamado METAX que
está en capacidad de convertir los METAR y TAF de formato TAC a formato XML ya funcionando y
operativo.
5.8 En ese sentido, las tareas que están actualmente en proceso son:
a) Designación de los centros de meteorología espacial;
b) Definición de los encabezamientos para los mensajes de Asesoramiento y los
mensajes administrativos;
c) Definición de Lista de distribución (AFS, AFTN, AMHS)
d) Formato y plantillas para los mensajes
5.9 La Secretaría informó a la Reunión que algunas tareas ya han culminado y otras están
actualmente en proceso. La Reunión tomó nota que durante la Reunión de Proyectos MET serán brindadas
otras informaciones.
SAM COM/MET 2019 Informe sobre la Cuestión 6 del Orden del Día 6-1
Cuestión 6 del
Orden del Día: Otros asuntos
6.1 Bajo esta cuestión del orden del día, la Reunión no analizó ninguna nota de estudio.
An Inter-Regional OPMET Gateway (IROG) is responsible for collecting and disseminating OPMET data from its Interregional Area of Responsibility (IAoR) to Regional OPMET Centres (ROCs) and other partner IROGs. In terms of IWXXM data exchange, IROGs act as data aggregators, translators, and switches. To ensure efficient intra- and inter-regional data exchange, a flexible framework is essential for accommodating specific regional needs while allowing for coordinated data exchange across regions. This includes agreements on data formats, compliance testing, and query languages to integrate the IWXXM model into the regional data infrastructure .
Maintaining updated guidelines and documentation is critical for ensuring consistent IWXXM compliance testing and data exchange procedures. It ensures that data producers and regional centers adhere to established standards, facilitating seamless integration across various regions while reducing the risk of data incompatibility. Clear documentation also aids in training and supports the transition by providing definitive references for implementing new technologies, managing queries, and understanding framework guidelines, which are essential for operational readiness and efficiency in data exchange .
In transitioning from TAC to IWXXM formats, a significant challenge is ensuring the correct state and consistency of aeronautical metadata, which becomes essential for accurate data characterization. The transition requires authorized data sources for airports, FIRs, and other elements, coupled with a consistent update and notification process to prevent data inconsistencies. Furthermore, the integration into current systems, including AMHS networks, involves overcoming compatibility issues, ensuring security, and maintaining reliable information exchange protocols, which makes it a complex endeavor .
Implementing XML/GML formats for OPMET messages, particularly with the IWXXM model, modernizes aeronautical communication by enhancing data coherence and accessibility. This transition permits robust data exchange frameworks that integrate seamlessly with international systems, enabling more accurate risk management, especially concerning adverse meteorological conditions. Such improvements facilitate the shift towards a System-Wide Information Management (SWIM) environment, ultimately contributing to increased safety and efficiency within the aviation sector .
Regional groups are crucial in facilitating the transition to IWXXM formats by managing the planning and execution of intra- and inter-regional data exchange infrastructure. These groups define implementation guidelines, oversee testing platforms and software, and ensure compliance with ICAO's mandates. Governance tasks also involve outlining cyber security protocols, coordinating with adjacent regional bodies, and addressing operational challenges, such as TAC to IWXXM conversion issues, thus ensuring a structured and efficient transition process .
Transitioning to the IWXXM model offers several benefits, including enhanced data interoperability, improved data accuracy and consistency, and the capability to integrate into a System-Wide Information Management (SWIM) environment. This aligns with future initiatives in meteorological services by facilitating automated, globally standardized meteorological data distribution, crucial for advanced weather monitoring and predictive analytics applications. These improvements are pivotal in improving aviation safety and operational efficiency while meeting evolving data requirements .
A robust framework for IWXXM data exchange is crucial to maintain a controlled and coordinated exchange of aeronautical information across regions. This framework must incorporate strategies that accommodate regional diversities, such as tailored compliance testing protocols, specific data interoperability agreements, and adaptable network infrastructure, including AMHS upgrades. Effective management strategies should focus on managing regional implementation plans, ensuring inter-regional cooperation, and establishing governance structures to oversee the transition .
To improve handling of SIGMET messages, adjustments have been proposed for conducting exercises that issue volcanic ash advisories. Initially, the duration of these exercises was reduced from 36 to 12 hours due to workload concerns raised by the Washington VAAC. However, a compromise was reached to conduct two types of exercises: a 36-hour exercise led by the Buenos Aires VAAC and a 12-hour one led by the Washington VAAC. Additionally, suggestions were made to utilize chat channels for information advisory, though initial tests were not successful and recommended annual exercises to continue addressing these challenges were suggested .
Regional OPMET Databanks (RODBs) serve as vital hubs for the collection, storage, and dissemination of IWXXM data within and between regions. They facilitate data queries via the AFS networks using specified query languages that align with IWXXM formats. Effective regional cooperation is reinforced through standardized protocols for data exchange, such as consistent query language specifications and coordinated infrastructure among RODBs, ensuring seamless interoperable data access across different regions .
Fabio Rabbani, from the South American Office of ICAO, highlighted the importance of transitioning OPMET messages to digital formats to enhance efficiency. There is a focus on improving coordination between COM and MET areas to better manage and mitigate risks associated with adverse meteorological conditions in aviation. This is crucial as coordinated projects between GREPECAS and RASG-PA are underway to address these risks, which arise from incidents linked to adverse weather phenomena affecting air navigation .