Skip to content

Commit

Permalink
Some Fixes (#40)
Browse files Browse the repository at this point in the history
* Some fixes

* Back to numbering

* Typo

* Fix numbering

* Comments from @tomkralidis
  • Loading branch information
kaiwirt authored Feb 15, 2024
1 parent 994acdb commit f872e49
Show file tree
Hide file tree
Showing 5 changed files with 28 additions and 21 deletions.
4 changes: 2 additions & 2 deletions transition-guide/sections/management_of_gts_ahl.adoc
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
=== Management of GTS Abbreviated Headings

The GTS abbreviated headings are described in the Manual on the Global Telecommunication System (WMO-No. 386). In particular the data designators T1T2A1A2ii are defined in Attachement II.5 of this Manual. The GTS abbreviated heading are not required in WIS2 and their use is limited to the exchange of data in the GTS. Starting from WIS2 operational any further evolution of the GTS, including the transmission of new data, will not be permitted. Therefore the Manual on GTS will no longer be updated from 31 December 2024.
The Weather Reporting (WMO-No. 9) Volume C1 contains the list of meteorological bulletins exchanged on the GTS. There is a requirement for Members to update Volume C1 every time a change in the bulletins takes place, but only a few Members are doing it with regularly and therefore the list is incomplete and is not consistent with the bulletins effectively exchanged on GTS. With the start of WIS2 operational phase there will not be any change in the list of meteorological bulleting transmitted on GTS, therefore Volume C1 will not be updated any longer from 31 December 2024.
The GTS abbreviated headings are described in the Manual on the Global Telecommunication System (WMO-No. 386). In particular the data designators T1T2A1A2ii are defined in Attachement II.5 of this Manual. The GTS abbreviated headings are not required in WIS2 and their use is limited to the exchange of data on the GTS. Starting from WIS2 becoming operational any further evolution of the GTS, including the transmission of new data, will not be permitted. Therefore the Manual on GTS will no longer be updated from 31 December 2024.
The Weather Reporting (WMO-No. 9) Volume C1 contains the list of meteorological bulletins exchanged on the GTS. There is a requirement for Members to update Volume C1 every time a change in the bulletins takes place, but only a few Members are doing it with regularity and therefore the list is incomplete and is not consistent with the bulletins effectively exchanged on GTS. With the start of the WIS2 operational phase there will not be any change in the list of meteorological bulletins transmitted on GTS, therefore Volume C1 will not be updated any longer from 31 December 2024.

==== GTS Headings for ICAO (AFTN)

Expand Down
8 changes: 4 additions & 4 deletions transition-guide/sections/management_of_wis1_and_gts.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ During the migration to WIS2, the Main Telecommunication Network (MTN), linking

==== Regional Telecommunication Hubs

Regional Telecommunication Hubs (RTHs) shall keep their Message Switching Systems (MSS) up and continue to publish data Collecting the bulletins from their associated National Meteorological Centres (NMCs) and transmitting them in the appropriate form on the Main Telecommunication Network (MTN), either directly or through the appropriate WMC/RTH in GTS until all Members in their area of responsability migrate from GTS to WIS2.
Regional Telecommunication Hubs (RTHs) shall keep their Message Switching Systems (MSS) up and continue to publish data Collecting the bulletins from their associated National Meteorological Centres (NMCs) and transmitting them in the appropriate form on the Main Telecommunication Network (MTN), either directly or through the appropriate WMC/RTH in GTS until all Members in their area of responsibility migrate from GTS to WIS2.

When Regional Telecommunication Hubs (RTHs) have migrated to WIS2 Node and all Members in their area of responsibility (AoR) have migrated to WIS2, RTHs may decide to turn off their message switching system (MSS).

Expand All @@ -21,14 +21,14 @@ In this case, they will follow the procedure described in xxx.

National Meteorological Centres (NMCs) shall operate a WIS2 Node to share their data and discovery metadata in WIS2.

NMCs that have implemented a WIS2 Node, and published all the data transmitted in the GTS on WIS2 can, if they wish, turn off their GTS system MSS and stop transmitting data in the GTS.
When NMCs decide to decommission and turn off their GTS system MSS and stop transmitting their data in GTS, they shall include the GTS properties in the Notification Message as described in the WIS2 to GTS gateway technical requirements.
NMCs that have implemented a WIS2 Node, and published all the data transmitted on the GTS on WIS2 can, if they wish, turn off their GTS system MSS and stop transmitting data on the GTS.
When NMCs decide to decommission and turn off their GTS system MSS and stop transmitting their data on GTS, they shall include the GTS properties in the Notification Message as described in the WIS2 to GTS gateway technical requirements.

Note: this Notification Message update will concern only data that are already published in GTS. New data will be published only on WIS2.

=== Maintenance and operation of WIS1 Catalogue and Cache by GISCs

Each GISC shall maintain their Catalogue and Cache as long as WIS Users are using their services for operations. GISC are invited to help users migrating to WIS2. When having succesfully migrated its users to WIS2, GISC may stop their WIS1 Cache and Catalogue service and shall inform WMO Secretariat.
Each GISC shall maintain their Catalogue and Cache as long as WIS Users are using their services for operations. GISCs are invited to help users migrating to WIS2. When having succesfully migrated its users to WIS2, GISCs may stop their WIS1 Cache and Catalogue service and shall inform WMO Secretariat.

GISC Seoul and GISC Offenbach will continue to provide WIS1 discovery metadata and the WIS1 Catalogue until the transition from GTS and WIS1 to WIS2 is completed or deemed unnecessary when all WIS1 users have migrated to WIS2.

Expand Down
14 changes: 8 additions & 6 deletions transition-guide/sections/management_of_wis_centres.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -3,16 +3,18 @@
=== National Centres

National Centres (NCs) can start migrating to WIS2 from January 2025 when WIS2 will be operational. It is recommended to start planning and preparation in advance and in a way that the migration will be completed preferably before 2030 and not later than 2033. The migration to WIS2 of a National Centre can be considered complete when at least one WIS2 node for the NC is operational and all the datasets transmitted on GTS are also shared on WIS2 in compliance with the technical requirements described in the Manual on WIS (WMO-No. 1060) Vol. II and the Guide to WIS (WMO-No. 1061).
A National Centre fully migrated to WIS2:
1. shall communicate to the Secretariat that its migration is complete,
1. shall keep the WIS1 and GTS operational in parallel with the WIS2 systems until reception of a communication from the Secretariat allowing the switch off of the WIS1 and GTS systems.
A National Centre fully migrated to WIS2:

. shall communicate to the Secretariat that its migration is complete,
. shall keep the WIS1 and GTS operational in parallel with the WIS2 systems until reception of a communication from the Secretariat allowing the switch off of the WIS1 and GTS systems.

=== Data Collection and Production Centres

Data Collection and Production Centres (DCPCs) can start migrating to WIS2 from January 2025 when WIS2 will be operational. It is recommended to start planning and preparation in advance and in a way that the migration will be completed preferably before 2030 and not later than 2033. The migration to WIS2 of a DCPC can be considered complete when at least one WIS2 node for the DCPC is operational and all the datasets transmitted on GTS are also shared on WIS2 in compliance with the technical requirements described in the Manual on WIS (WMO-No. 1060) Vol. II and the Guide to WIS (WMO-No. 1061).
A DCPC fully migrated to WIS2:
1. shall communicate to the Secretariat that its migration is complete,
1. shall keep the WIS1 and GTS operational in parallel with the WIS2 systems until reception of a communication from the Secretariat allowing the switch off of the WIS1 and GTS systems.
A DCPC fully migrated to WIS2:

. shall communicate to the Secretariat that its migration is complete,
. shall keep the WIS1 and GTS operational in parallel with the WIS2 systems until reception of a communication from the Secretariat allowing the switch off of the WIS1 and GTS systems.

=== Global Information System Centres

Expand Down
6 changes: 3 additions & 3 deletions transition-guide/sections/migration_from_gts_to_wis2.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,9 @@ 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
==== Requirements for the 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.
During the pilot phase in 2023 the infrastructure of WIS 2.0 was developed and tests to refine the WIS 2.0 technical specifications have been carried out. The pre-operational phase is the clean-up phase to make the transition to operations.

The following actions are required for a smooth transition:

Expand All @@ -39,6 +39,6 @@ The following actions shall be completed for a smooth transition from the pre-op
** Customer services support
** Incident management
** Monitoring
* Business continuity and disaster recovery: plans must be in place to ensure that, in the event of failure, the business can continue or, in the worst case, recover within the required time scale from any significant disaster. This might include:
* Business continuity and disaster recovery plans must be in place to ensure that, in the event of failure, the business can continue or, in the worst case, recover within the required time scale from any significant disaster. This might include:
** provision for offsite backup
** Supply of an identical replacement system within a specified time
17 changes: 11 additions & 6 deletions transition-guide/sections/temporary_global_services.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -44,9 +44,13 @@ The gateway will be provided by designated Regional Telecommunication Hubs (RTH)
==== Technical requirements
===== For WIS Centres wishing to stop their MSS

A Member planning to stop GTS transmission shall, in addition to WIS2 Node operations, and when publishing a WIS2 Notification Message for data that should also be available on the GTS shall indicate the GTS Abbreviated Header Line (AHL) of the bulletin in which the data is to be published.
A Member planning to stop GTS transmission shall
* provide their data in conformance with WIS2 Node operations on WIS2
* for data that has previously been available on the GTS and that should continue to be available on the GTS
** indicate the GTS Abbreviated Header Line (AHL) of the bulletin in which the data is to be published.
** this is done by including the ``gts`` property in the WIS2 Notification Message (see example below).

This is done by including the ``gts`` property in the WIS2 Notification Message (see example below). This enables the WIS2 to GTS Gateway operator to easily identify data for republication on the GTS and the AHL of the associated data.
The ``gts`` property enables the WIS2 to GTS Gateway operator to easily identify data for republication on the GTS and the AHL of the associated data.

[source,json]
-----
Expand Down Expand Up @@ -85,8 +89,8 @@ Gradually stopping all the MSS shall be done in an orderly and coordinated manne

The "Management of WIS1 and GTS" section of this Transition Guide recalls the various roles on the GTS (NMC, RTH, WMC). It also details when a Centre can stop its MSS. When all the conditions for a Centre are met, the following decommissioning procedure can be applied.

.MSS decommissiong procedure
image::images/stopping-mss.png[MSS decommissiong procedure]
.MSS decommissioning procedure
image::images/stopping-mss.png[MSS decommissioning procedure]

The sequence diagram details the list of actions required and the role of the various entities involved in this action.
*The responsible GISC for the Centre will have a key role to play.* The GISC will have to ensure that the Centre has properly implemented the requirements and that the procedure is well understood by the Centre so that, no data is lost during the transition.
Expand All @@ -95,8 +99,9 @@ It is crucial that all parties to strictly follow the agreed procedure.

It must also be noted that the final switch (stopping the MSS by the Centre and activating the gateway function for the TTAAii/CCCC of the WIS Centre) will happen at the same moment. The exact time and date will be chosen by the various parties under the control of WMO Secretariat.

Upon request by a Centre, WMO Secretariat will inform the gateways when a new ``centre-id`` wishes to use the relay function as well as the required subscription topics. When requested by WMO Secretariat, the gateway will implement the following subscriptions:
Upon request by a Centre, WMO Secretariat will inform the gateways when a new ``centre-id`` wishes to use the relay function as well as the required subscription topics. When requested by WMO Secretariat, the gateway will implement the following subscriptions:

. Subscribe to notifications on the topic: ``+cache/a/wis2/{centre-id}/data/#+``, where ``{centre-id}`` refers to a WIS2 Node wishing to stop the native GTS function.
. Potentially subscribe to ``+origin/a/wis2/{centre-id}/data/recommended/#+`` for the WIS2 Node having also recommended data on the GTS
. Potentially subscribe to ``+origin/a/wis2/{centre-id}/data/recommended/#+`` for the WIS2 Node having also recommended data on the GTS.

*Important* Subscribing to these topics shouldn't imply pushing the data onto the ``gts`` immediately. Making the data available on the ``gts`` will require the explicit approval from WMO Secretariat. It is up to the gateway operators to implement this "kill switch" (eg. disabling the subscription, blocking the flow between the Data Consumer and the MSS for those TTAAii/CCCC only, ...)

0 comments on commit f872e49

Please sign in to comment.