[WIP] ET-W2IT 2026-06 updates

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_<program>_
 
 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.

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.

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)