From d40449fcb3e633cfa983b8d28664243a19c1d9dd Mon Sep 17 00:00:00 2001 From: Tom Kralidis Date: Mon, 8 Jun 2026 13:41:52 -0400 Subject: [PATCH 1/4] part 2: move general section --- guide/sections/part2/global-services.adoc | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/guide/sections/part2/global-services.adoc b/guide/sections/part2/global-services.adoc index 94057b4..a7c69ef 100644 --- a/guide/sections/part2/global-services.adoc +++ b/guide/sections/part2/global-services.adoc @@ -26,7 +26,11 @@ The WMO Secretariat and other Global Services will make the required changes to ==== 2.7.2 Performance management and monitoring of a Global Service -===== 2.7.2.1 Monitoring and metrics for WIS2 operations +===== 2.7.2.1 General + +The performance management of designated Global Services is governed by §§2.7–2.9 of the Manual on WIS, Volume II. This section of the Guide provides operational guidance on the service level, the methodology used to assess it, the reporting cadence, and the remediation and restoration practice. Section 2.7.2.9 sets out the per-component operational criteria specific to each category of Global Service. The framework set out in this section and in sections 2.7.2.8 and 2.7.2.9 applies for the purposes of the suspension procedure set out in §2.8 of the Manual and the revocation procedure set out in §2.9 of the Manual; routine incident management for Global Services continues to be coordinated by GISCs under §4.7.4 of the Manual. + +===== 2.7.2.2 Monitoring and metrics for WIS2 operations The availability of data and the performance of system components within WIS2 are actively monitored by GISCs and the Global Monitor service to ensure proactive responses to incidents and effective capacity planning for future operations. @@ -43,7 +47,7 @@ Metrics for WIS2 monitoring should follow the naming convention ``wmo__ The full set of the WIS2 monitoring metrics is given in WMO: WIS2 Metric Hierarchy footnote:[See https://github.com/wmo-im/wis2-metric-hierarchy.] -===== 2.7.2.2 Service levels, performance indicators, and fair usage policies +===== 2.7.2.3 Service levels, performance indicators, and fair usage policies * Each WIS centre operating a WIS2 Node is responsible for achieving the highest possible level of service based on its resources and capabilities. * All Global Services, in particular Global Brokers and Global Caches, are collectively responsible for making WIS a reliable and efficient means of exchanging the data required for the operation of all WIS centres. The architecture provides a redundant solution where the failure of one component will not impact the overall level of service of WIS. * Each Global Service should aim to achieve at least 99.5% availability of the service it provides. This is not a contractual target. It should be considered by the entity providing the Global Service as a guideline when designing and operating that service. @@ -65,14 +69,10 @@ The full set of the WIS2 monitoring metrics is given in WMO: WIS2 Metric Hierarc ** Should support a minimum of 20 000 metadata records; ** Should support a minimum of 50 requests per second to the API endpoint. -===== 2.7.2.3 Metrics for Global Services +===== 2.7.2.4 Metrics for Global Services In the following sections, and for each Global Service, a set of metrics is defined. Each Global Service will provide those metrics. They will then be ingested by the Global Monitor. -===== 2.7.2.4 General - -The performance management of designated Global Services is governed by §§2.7–2.9 of the Manual on WIS, Volume II. This section of the Guide provides operational guidance on the service level, the methodology used to assess it, the reporting cadence, and the remediation and restoration practice. Section 2.7.2.9 sets out the per-component operational criteria specific to each category of Global Service. The framework set out in this section and in sections 2.7.2.8 and 2.7.2.9 applies for the purposes of the suspension procedure set out in §2.8 of the Manual and the revocation procedure set out in §2.9 of the Manual; routine incident management for Global Services continues to be coordinated by GISCs under §4.7.4 of the Manual. - ===== 2.7.2.5 Service level The service level is met in a calendar month where the designated Global Service is operational for not less than the proportion of that month set out, for the relevant category of Global Service, in the per-component operational criteria in section 2.7.2.9. The conditions under which a Global Service is considered operational are set out in those criteria, and the proportion of operational time over the month is determined in accordance with section 2.7.2.6. From 180426845606a96cb6044a7d2b075c88ed28e23a Mon Sep 17 00:00:00 2001 From: Jeremy Tandy Date: Mon, 8 Jun 2026 21:51:40 -0300 Subject: [PATCH 2/4] Require service offer for designation of Other Services. Added a note about the service offer submission process. --- guide/sections/part3/other-services.adoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/guide/sections/part3/other-services.adoc b/guide/sections/part3/other-services.adoc index 17cd7a3..9d61f98 100644 --- a/guide/sections/part3/other-services.adoc +++ b/guide/sections/part3/other-services.adoc @@ -1,5 +1,8 @@ === 3.2 Other services +// TODO - define link to designation process +A Member wishing to operate a Service defined in this Guide must submit a service offer as per the DESIGNATION PROCESS. + ==== 3.2.1 Global Replay A Global Replay provides access and subscription to past WIS Notification Messages. From 580a2602a78d642885d3646200beda3193a8cf76 Mon Sep 17 00:00:00 2001 From: Jeremy Tandy Date: Mon, 8 Jun 2026 21:55:42 -0300 Subject: [PATCH 3/4] Update Sensor Centre guidelines and governance details Following discussions at ET-W2IT (Brasilia, 8-JUN) sensor centre overview is revised and simplified. --- guide/sections/part3/sensor-centres.adoc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/guide/sections/part3/sensor-centres.adoc b/guide/sections/part3/sensor-centres.adoc index 94651fa..fc69945 100644 --- a/guide/sections/part3/sensor-centres.adoc +++ b/guide/sections/part3/sensor-centres.adoc @@ -24,15 +24,15 @@ A Sensor Centre may also provide logs, in addition to the defined metrics, throu Sensor Centres monitoring the Global Services that are critical to the function of WIS 2.0 are described below: Sensor Centre Global Broker, Sensor Centre Global Cache, and Sensor Centre Global Discovery Catalogue. -Given that Sensors Centres may be used to monitor any function in WIS 2.0, further Sensor Centres may be proposed to meet additional requirements, such as validation of GBON or RBON compliance. Every Sensor Centre must follow the standard mechanism for publishing metrics for presentation in dashboards that can be used to monitor the performance of the WIS 2.0 function being assessed. +Given that Sensors Centres may be used to monitor any function in WIS 2.0, additional Sensor Centre types may be used to meet other requirements, such as validation of GBON or RBON compliance. -// TODO: add link to sensor centre designation process +Any Member may choose to design and operate a Sensor Centre to meet the needs they identify. They may also choose to propose a new recipe for the WIS2 Cookbook that describes what their Sensor Centre monitors and how it functions. Where a Sensor Centre has an official role unrelated to WIS2 (e.g., in support of RBON compliance) the responsible body for that function may assert their own governance requirements regarding their designation and operation. Sensor Centres supporting the formal monitoring of WIS2 - including contributing to the objective evaluation of Global Service performance - are governed by INFCOM. SC-IMT welcomes proposals for new Sensor Centre types that contribute to the formal monitoring of WIS2. Members are invited to contact the Secretariat with details of their Sensor Centre and implementation evidence. -Any Member may request to operate a Sensor Centre via the [.underline]#designation process# - either for a new or existing type of Sensor Centre. Requests must specify what type of Sensor Centre will be operated and refer to the specification they will implement. +// TODO: add link to designation process +A Member wishing to operate a Sensor Centre defined in this Guide must submit a service offer as per the DESIGNATION PROCESS and undergo assessment to assure their correct operation. -The specification of a Sensor Centre must be published in a publicly accessible location, such as a public GitHub repository. Where a Sensor Centre has a role in the objective assessment of Global Service performance, the Sensor Centre specification is subject to approval by INFCOM and will be published in the Guide to WIS, Vol 2, Part III. Where a Sensor Centre has some other official role (e.g., in support of RBON compliance) the responsible body for that function may assert their own governance requirements. - -Where a Sensor Centre provides insight about the performance of WIS 2.0 as a whole, Global Monitors may agree to collect metrics from the Sensor Centre and provide monitoring dashboards. As part of the designation process, a Member may include a request for Global Monitors to harvest metrics, including suggested thresholds for metrics that would trigger a Global Monitor to publish an alert or warning. +// TO BE CONFIRMED: Do we want to require Members to publish a WCMP2 service record for a Sensor Centre? Issue: additional burden to operate a MQTT broker and provide WNM messages to publish the WCMP2 record. Is this appropriate? +A Member operating a Sensor Centre must publish a WCMP2 record (`properties.type=service`) that describes it. These WCMP2 records collectively form a register of Sensor Centres in the Global Discovery Catalogue. ==== 3.3.2 Sensor Centres for Global Brokers (SCGB) From f3ecfe5b80a7fee63a16ff3dabb050f641c2c083 Mon Sep 17 00:00:00 2001 From: Jeremy Tandy Date: Mon, 8 Jun 2026 22:16:51 -0300 Subject: [PATCH 4/4] Add designation process for Additional Components Expanded the overview section to include value-added capabilities of Additional Global Services and Sensor Centres, along with a detailed designation procedure for Additional Components in WIS2. See https://github.com/wmo-im/et-w2it/issues/28#issuecomment-4654652221 for details of discussion. --- guide/sections/part3/introduction.adoc | 42 +++++++++++++++++++++++++- 1 file changed, 41 insertions(+), 1 deletion(-) diff --git a/guide/sections/part3/introduction.adoc b/guide/sections/part3/introduction.adoc index 7a66b95..7741ecd 100644 --- a/guide/sections/part3/introduction.adoc +++ b/guide/sections/part3/introduction.adoc @@ -1,9 +1,49 @@ === 3.1 Overview -In addition to the core set of Global Services defined, additional Global Services may exists in WIS2. +==== 3.1.1 Value-added capabilities + +Alongside the core set of Global Services defined, Additional Global Services and Sensor Centres provide value-added capabilities within WIS2. Additional Global Services: * provide value added capabilities and insights into WIS2 * are not required components of WIS2 * may be provided with various access control policies depending on their scope + +Sensor Centres: + +* provide continuous measurement and assessment on WIS2 functions + +==== 3.1.2 Designation procedure for Additional Components + +Any WMO Member or partner organisation may request to operate an Additional Component that is defined in this Guide. + +Additional Components provide value to the entire WIS2 ecosystem. As such, all instances of Additional Components must be assessed to assure their correct operation before being designated as a WIS2 component. + +The designation of an Additional Component involves the following steps: + +* Request to host an Additional Component: the “service offer”. +** A service offer shall be made by the Permanent Representative of the Member country or territory from where the Additional Component will operate, or by the organisation responsible for WMO Programme or Activity that will operate the Additional Component. +** A service offer shall include: (i) the type of Additional Component - this shall be a type that is defined in this Guide, (ii) an outline the Centre’s capacity to deliver the proposed component, and (iii) contact details for the focal point responsible for the Additional Component. +* Complete the WIS2 Register. +** Once the Additional Component is ready for assessment, the focal point shall update the WIS2 Register providing the information requested by the Secretariat, including but not limited to: the proposed centre identifier (“centre-id”), and technical details for the Additional Component required to connect with other WIS2 components. +* Provide details of WIS2 components. +** The Secretariat provides connection details (such as IP addresses or hostnames) for the WIS2 services or components to which Additional Component needs to connect. +* Additional Component assessment. +** In coordination with the WMO Secretariat and SC-IMT, the principal GISC of the Member country or territory from where the Additional Component will operate will assess technical compliance with specifications of WIS2 (e.g., provision of metrics, provision of WIS2 Monitor Event messages) and the specification of the Additional Component defined in this Guide. +** Following successful technical compliance validation, the principal GISC undertakes a pre-operational assessment of the Additional Component for a period not less than one month. The GISC, in coordination with WMO Secretariat and SC-IMT, will facilitate connection with the Global Services if required. This assessment includes verifying interoperability with Global Services and validating performance against any KPIs defined for the Additional Component. During the pre-operational testing the Additional Component and any outputs it provides will be marked as experimental. +* Approve the designation of the Additional Component. +** Based on the findings of the technical validation and operational assessment, SC-IMT will consider the service offer and provide a recommendation to President of INFCOM for approval. In cases where the proposal is rejected, SC-IMT will provide constructive feedback to the requestor. +* Add new Additional Component to WIS2 (if approved). +** The Additional Component is added to the list of designated Additional Components maintained and published by the WMO Secretariat. +** Experimental marking is removed. + + + +==== 3.1.3 Suspension and revocation procedure for Additional Components + +// TODO + +==== 3.1.4 Decommissioning procedure for Additional Components + +// TODO