From f87928769f4b4dc069451a0e3d141b609bd17c44 Mon Sep 17 00:00:00 2001 From: Tom Kralidis Date: Fri, 26 Jan 2024 22:57:36 +0800 Subject: [PATCH] update document structure (#14), add new section (#9) (#19) * update document structure (#14), add new section (#9) * Create Implementation_Plan.adoc Text draft for the introduction * Update wis2_implementation_plan.adoc * Delete transition-guide/sections/Implementation_Plan.adoc --------- Co-authored-by: Haddouch Hassan <103424042+hhaddouch@users.noreply.github.com> --- transition-guide/index.adoc | 10 ++--- .../sections/gts_to_wis2_gateway.adoc | 26 ----------- transition-guide/sections/introduction.adoc | 8 ---- .../sections/management_of_wis_centres.adoc | 40 +++++++++++++++++ ...s.adoc => migration_from_gts_to_wis2.adoc} | 10 +++-- ...ay.adoc => temporary_global_services.adoc} | 43 ++++++++++++++++--- .../sections/wis2_implementation_plan.adoc | 6 +++ 7 files changed, 94 insertions(+), 49 deletions(-) delete mode 100644 transition-guide/sections/gts_to_wis2_gateway.adoc delete mode 100644 transition-guide/sections/introduction.adoc create mode 100644 transition-guide/sections/management_of_wis_centres.adoc rename transition-guide/sections/{pre_operational_and_operational_phases.adoc => migration_from_gts_to_wis2.adoc} (90%) rename transition-guide/sections/{wis2_to_gts_gateway.adoc => temporary_global_services.adoc} (63%) create mode 100644 transition-guide/sections/wis2_implementation_plan.adoc diff --git a/transition-guide/index.adoc b/transition-guide/index.adoc index b9aed23..780d80d 100644 --- a/transition-guide/index.adoc +++ b/transition-guide/index.adoc @@ -35,20 +35,20 @@ toc::[] include::sections/preamble.adoc[] -include::sections/introduction.adoc[] +include::sections/wis2_implementation_plan.adoc[] include::sections/principles.adoc[] -include::sections/pre_operational_and_operational_phases.adoc[] +include::sections/migration_from_gts_to_wis2.adoc[] -include::sections/gts_to_wis2_gateway.adoc[] - -include::sections/wis2_to_gts_gateway.adoc[] +include::sections/temporary_global_services.adoc[] include::sections/management_of_wis1_and_gts.adoc[] include::sections/management_of_gts_ahl.adoc[] +include::sections/management_of_wis_centres.adoc[] + include::sections/wis1cat.adoc[] include::sections/references.adoc[] diff --git a/transition-guide/sections/gts_to_wis2_gateway.adoc b/transition-guide/sections/gts_to_wis2_gateway.adoc deleted file mode 100644 index fd2922c..0000000 --- a/transition-guide/sections/gts_to_wis2_gateway.adoc +++ /dev/null @@ -1,26 +0,0 @@ -== GTS to WIS2 Gateway - -The Executive Council, with resolution 34 (EC-76), endorsed the WMO Information System 2 (WIS2) implementation plan and recognized the importance of establishing a pilot phase to develop the WIS2 infrastructure and begin testing it in order to be ready for a preoperational phase in 2024, and then for the transition starting on 2025. According to the WIS2 implementation plan, the Global Telecommunication System (GTS) will be decommissioned by 2030, and National Meteorological and Hydrological Services NMHSs will use the WIS2 platform for data exchange. - -During the transition period, in order to avoid some WIS centres being forced to run both data-sharing frameworks WIS2 and GTS simultaneously, with the challenges associated with maintaining two operational systems for the same purpose, a gateway from GTS to WIS2 is designed, taking into account the time required for Members to migrate to the new systems and minimizing the time a member has to operate both systems in parallel. - -=== Purpose - -The purpose of the GTS to WIS2 gateway is to enable members who have migrated to WIS2 and have stopped their GTS systems to continue receiving GTS data from WIS2. This gateway also enables users who are not connected to GTS to access GTS data, during the transition phase, from WIS2. The GTS to WIS2 gateway will forward all the GTS traffic it receives to WIS2, that is each bulletin received on one of its GTS channels will be stored to the HTTP(s) endpoint of the Gateway and a WIS2 Notification Message is generated which points to that bulletin file. The Notification Message is published at the GTS to WIS2 gateway topic. - -=== GTS to WIS2 Gateway provider - -The gateway will be provided by Germany's Deutscher Wetterdienst (DWD) and the Japan Meteorological Agency (JMA). - -=== Technical requirements - -* GTS headers SHALL be used in the WIS2 Topic Hierarchy (WTH) -* The TH for GTS data on WIS2 SHALL be as follows: -** ``origin/a/wis2/[GC-name]/data/[core|recommended]/T1/T2/A1/A2/ii/CCCC`` -** e.g for DWD: ``origin/a/wis2/de-dwd-gts-to-wis2/data/[core|recommended]/T1/T2/A1/A2/ii/CCCC`` and for JMA: ``origin/a/wis2/jp-jma-gts-to-wis2/data/[core|recommended]/T1/T2/A1/A2/ii/CCCC`` -* The GTS to WIS2 data is copied on the WIS2 Global Caches if the data is WMO Core Data. -* Each GTS to WIS2 Gateway SHALL maintain a list of TTAAii headers for Core and for Recommended data in order to be able to send the notification to the correct topic. The list is coordinated and shared between the Gateways. -* The data_id for each GTS to WIS2 Gateway SHALL be unique. That is each gateway will choose different data ids for example by adding their centre name reflecting the fact, that GTS bulletins with the same header might be different at the different locations. Therefore there will be two or more different GTS to WIS2 datasets (one for each gateway). -* Example for a valid GTS to WIS2 data id is ``wis2/de-dwd-gts-to-wis2/data/core/W/W/X/X/60/EDZW/WWXX60EDZW200900`` -* Data Consumers receiving the GTS data through WIS2 will need to be able to handle duplicates. This is in line with the current practices of handling duplicate messages on the GTS. -* Access to recommended GTS data should be restricted to WMO members. diff --git a/transition-guide/sections/introduction.adoc b/transition-guide/sections/introduction.adoc deleted file mode 100644 index 7754b36..0000000 --- a/transition-guide/sections/introduction.adoc +++ /dev/null @@ -1,8 +0,0 @@ -=== Introduction - -The WMO Information System 2.0 (WIS2) will be implemented according to the schedule provided in Figure 1. As planned and after a succesful pilot phase in 2023, WIS2 has entered its pre-operational phase from 1st January 2024. The operational phase of WIS2 will begin on 1st January 2025. - -.WIS2 implementation timeline -image::images/wis2-timeline.png[WIS2 implementation timeline] - -According to the WIS2 implementation plan (see figure 1), the Global Telecommunication System (GTS) will be decommissioned by 2033, and National Meteorological and Hydrological Services NMHSs will use the WIS2 platform for data exchange. During the transition period, centres will operate WIS2 and/or WIS/GTS. Some of them will need to run both data-sharing frameworks simultaneously for some time, for various reasons (eg. being an RTHs,...), with the difficulties associated with maintaining two operational systems for the same purpose. Therefore, and to make the transition as smooth as possible and to avoid unnecessary burden on all Members, a mechanisms including gateways have been defined. Gateways will operate in both directions between WIS2 and GTS. Consequently, there will be both GTS to WIS2 gateways and WIS2 to GTS gateways. This guide details the various aspects of the transition as well as the way Centres will gradually evolve from a pure WIS/GTS setup to a full WIS2 environment. diff --git a/transition-guide/sections/management_of_wis_centres.adoc b/transition-guide/sections/management_of_wis_centres.adoc new file mode 100644 index 0000000..f0817b7 --- /dev/null +++ b/transition-guide/sections/management_of_wis_centres.adoc @@ -0,0 +1,40 @@ +== Management of WIS centres + +=== National Centres + +During the transition (2025-2030): + +* National Centres (NCs) will decide when to stop the GTS and WIS1, preferably before 2030, but not later than 2033. +* NCs shall deploy a WIS2 node, on-premises or in the cloud, to publish their data and discovery metadata, they may use one of the three options: +** use Free and Open Source Software System (FOSS), for example wis2box +** use a commercial solution +** develop their own solution in accordance with the Technical Regulations of WIS 2.0 +* NCs shall check that all data and metadata transmitted in WIS1 and GTS are published in WIS2 in accordance with the WCMP2 +* NCs shall support their users to access data from WIS1 and WIS2 +* NCs shall notify WMO when they decide to stop GTS and WIS1 +* NCs shall run GTS/WIS1 and WIS2 in parallel for a period to ensure a smooth transition. + +=== Data Collection and Production Centres + +During the transition (2025-2030): + +* Data Collection and Production Centres (DCPCs) will decide when to stop WIS1 system, preferably before 2030, but not later than 2033. +* DCPCs shall deploy a WIS2 node, on-premises or in the cloud, to publish their data and discovery metadata, they may use one of the three options: +** use Free and Open Source Software System (FOSS), for example wis2box +** use a commercial solution +** develop their own solution in accordance with the Technical Regulations of WIS 2.0 +* DCPCs shall check that all data published in WIS1 are published in WIS2 +* DCPCs shall check that all discovery metadata published in WIS1 are published in WIS2 in accordance with the WCMP2 +* DCPCs shall support their customers to access data from WIS1 and WIS2 when the migration is completed +* DCPCs shall notify WMO when they decide to turn off WIS1 +* DCPCs shall run WIS1 and WIS2 in parallel for a period to ensure a smooth transition and that all their customers are served by WIS2. + +=== Global Information System Centres + +During the transition (2025-2030): + +* Global Information System Centres (GISCs) will decide when to stop WIS1 system, preferably before 2030, but not later than 2033. +* To be able to decommission their WIS1 systems, GISCs shall liaise with their users and with centers in their AoR and point them to the WIS Portals of the WIS Authorities, namely GISC Seoul and GISC Offenbach. +* GISC Seoul and GISC Offenbach will continue to provide WIS1 services and maintain their WIS1 Catalogues until the transition from GTS and WIS1 to WIS2 is advanced. +* GISCs shall support the centres in their AoR within the implementation of WIS 2.0 and ensuring the effective operation of WIS. +* GISCs shall notify WMO when they decide to turn off WIS1 diff --git a/transition-guide/sections/pre_operational_and_operational_phases.adoc b/transition-guide/sections/migration_from_gts_to_wis2.adoc similarity index 90% rename from transition-guide/sections/pre_operational_and_operational_phases.adoc rename to transition-guide/sections/migration_from_gts_to_wis2.adoc index 8e2be7b..9ed14fe 100644 --- a/transition-guide/sections/pre_operational_and_operational_phases.adoc +++ b/transition-guide/sections/migration_from_gts_to_wis2.adoc @@ -1,6 +1,8 @@ -== Pre-operational and operational phases +== Migration from GTS to WIS2 -=== Definition of pre-operational phase +=== Pre-operational and operational phases + +==== Definition of pre-operational phase The objective of the pre-operational phase is to make the transition from the Pilot Phase to the operational phase. @@ -8,7 +10,7 @@ The purpose of this phase is to verify that the WIS 2.0 implementation has been This phase covers all activities related to the installation and integration of the WIS 2.0 components developed during the pilot phase, including the testing activities necessary to verify the integration and proper functioning of data exchange via WIS 2.0. -=== How to transition from the pilot to pre-operational phase +==== How to transition from the pilot to pre-operational phase The pilot phase aims to develop the infrastructure of WIS 2.0 and make the tests to refine the WIS 2.0 technical specifications. The pre-operational phase is the clean-up phase to make the transition to operations. @@ -21,7 +23,7 @@ The following actions are required for a smooth transition: * Discovery Metadata shall be prepared and published in accordance with the WMO Core Metadata Profile (WCMP2) * SYNOP core data shall be published hourly (minutely data not required) -=== How to make the transition from the pre-operational to operational phase +==== How to make the transition from the pre-operational to operational phase The pre-operational phase aims to ensure that all the improvements made during the pilot phase are deployed and tested. During this phase performance tests of all the WIS 2.0 components will be made and relevant adjustments will be completed to be ready for the operation. diff --git a/transition-guide/sections/wis2_to_gts_gateway.adoc b/transition-guide/sections/temporary_global_services.adoc similarity index 63% rename from transition-guide/sections/wis2_to_gts_gateway.adoc rename to transition-guide/sections/temporary_global_services.adoc index b15b3cb..fda5b6a 100644 --- a/transition-guide/sections/wis2_to_gts_gateway.adoc +++ b/transition-guide/sections/temporary_global_services.adoc @@ -1,4 +1,35 @@ -== WIS2 to GTS Gateway +== Temporary global services + +=== GTS to WIS2 Gateway + +The Executive Council, with resolution 34 (EC-76), endorsed the WMO Information System 2 (WIS2) implementation plan and recognized the importance of establishing a pilot phase to develop the WIS2 infrastructure and begin testing it in order to be ready for a preoperational phase in 2024, and then for the transition starting on 2025. According to the WIS2 implementation plan, the Global Telecommunication System (GTS) will be decommissioned by 2030, and National Meteorological and Hydrological Services NMHSs will use the WIS2 platform for data exchange. + +During the transition period, in order to avoid some WIS centres being forced to run both data-sharing frameworks WIS2 and GTS simultaneously, with the challenges associated with maintaining two operational systems for the same purpose, a gateway from GTS to WIS2 is designed, taking into account the time required for Members to migrate to the new systems and minimizing the time a member has to operate both systems in parallel. + +==== Purpose + +The purpose of the GTS to WIS2 gateway is to enable members who have migrated to WIS2 and have stopped their GTS systems to continue receiving GTS data from WIS2. This gateway also enables users who are not connected to GTS to access GTS data, during the transition phase, from WIS2. The GTS to WIS2 gateway will forward all the GTS traffic it receives to WIS2, that is each bulletin received on one of its GTS channels will be stored to the HTTP(s) endpoint of the Gateway and a WIS2 Notification Message is generated which points to that bulletin file. The Notification Message is published at the GTS to WIS2 gateway topic. + +==== GTS to WIS2 Gateway provider + +The gateway will be provided by Germany's Deutscher Wetterdienst (DWD) and the Japan Meteorological Agency (JMA). + +==== Technical requirements + +* GTS headers SHALL be used in the WIS2 Topic Hierarchy (WTH) +* The TH for GTS data on WIS2 SHALL be as follows: +** ``origin/a/wis2/[GC-name]/data/[core|recommended]/T1/T2/A1/A2/ii/CCCC`` +** e.g for DWD: ``origin/a/wis2/de-dwd-gts-to-wis2/data/[core|recommended]/T1/T2/A1/A2/ii/CCCC`` and for JMA: ``origin/a/wis2/jp-jma-gts-to-wis2/data/[core|recommended]/T1/T2/A1/A2/ii/CCCC`` +* The GTS to WIS2 data is copied on the WIS2 Global Caches if the data is WMO Core Data. +* Each GTS to WIS2 Gateway SHALL maintain a list of TTAAii headers for Core and for Recommended data in order to be able to send the notification to the correct topic. The list is coordinated and shared between the Gateways. +* The data_id for each GTS to WIS2 Gateway SHALL be unique. That is each gateway will choose different data ids for example by adding their centre name reflecting the fact, that GTS bulletins with the same header might be different at the different locations. Therefore there will be two or more different GTS to WIS2 datasets (one for each gateway). +* Example for a valid GTS to WIS2 data id is ``wis2/de-dwd-gts-to-wis2/data/core/W/W/X/X/60/EDZW/WWXX60EDZW200900`` +* Data Consumers receiving the GTS data through WIS2 will need to be able to handle duplicates. This is in line with the current practices of handling duplicate messages on the GTS. +* Access to recommended GTS data should be restricted to WMO members. + + +=== WIS2 to GTS Gateway + The WIS2 Implementation plan outlines a gradual transition of data exchange from the Global Telecommunications System (GTS) to WIS2. The transition is expected to occur between 2025 and 2030. The GTS will be decommissioned once the transition is complete. Once a WIS centre has migrated from GTS to WIS2, subject to validation of readiness, the centre will cease to share data on the GTS. Consequently, during the transition period some data will be published on the GTS and some via WIS2. @@ -9,16 +40,16 @@ To remove the need for WIS centres to operate both GTS and WIS2 systems in paral To ensure resilient operation there will be more than one WIS2 to GTS Gateway. -=== Purpose +==== Purpose The purpose of the WIS2 to GTS Gateway is to enable Members relying on the GTS, who are yet to migrate to WIS2, to receive operational data published via WIS2 that would otherwise be unavailable on the GTS. **Note**: Only data that have been already published in GTS are concerned by this Gateway, New data will be available **only** on WIS2. -=== WIS2 to GTS Gateway operators +==== WIS2 to GTS Gateway operators The gateway will be provided by designated Regional Telecommunication Hubs (RTH). These RTHs are: [TODO: Add the RTHs that will each operate a WIS2-to-GTS Gateway. Provisional list is: China, UK, Brazil.] -=== Technical requirements -==== For Data Providers +==== Technical requirements +===== For Data Providers A Member seeking to stop GTS transmission shall contact the WMO Secretariat, providing the following information: . The proposed date that GTS transmission will stop. @@ -43,7 +74,7 @@ This is done by including the ``gts`` property in the WIS2 Notification Message } ----- -==== For WIS2 to GTS Gateway operators +===== For WIS2 to GTS Gateway operators A WIS2 to GTS Gateway operator shall operate the following components throughout the transition period: . A WIS2 client application to retrieve data published on WIS2. diff --git a/transition-guide/sections/wis2_implementation_plan.adoc b/transition-guide/sections/wis2_implementation_plan.adoc new file mode 100644 index 0000000..47c881c --- /dev/null +++ b/transition-guide/sections/wis2_implementation_plan.adoc @@ -0,0 +1,6 @@ +== Introduction + +The Executive Council, with Resolution 34 (EC-76), endorsed the WMO Information System 2.0 (WIS2) implementation plan and recognized the importance of establishing a pilot phase to develop the WIS2 infrastructure and begin testing it to be ready for a pre-operational phase in 2024, and then for the transition starting on 2025. This plan will be implemented according to the schedule provided in Figure 1. The pilot phase has been completed at the end of 2023, with several countries collaborating in building the WIS2 infrastructure. Each country had a different role in the WIS2 framework and implemented a specific component. Starting in January 2024, the implementation of WIS2 will enter the pre-operational phase, and the WIS2 services shall be ready to transition to an operational configuration, which is critical to ensure that WIS2 can serve the WMO community operationally from the beginning of 2025. It is planned to migrate to WIS2 between 2025 and 2030, with an expected progress rate of up to 90%. The GTS is planned to be decommissioned by 2033. + +.WIS2 implementation timeline +image::images/wis2-timeline.png[WIS2 implementation timeline]