Skip to content
xchen edited this page Dec 10, 2024 · 2 revisions

Welcome to the wis2-operation wiki! GISC Roles

  • Short-term (by April 2025)
  • Mid-term (by September 2025)
  • Longer-term (2026+)

---------------Short-term Action List for GISC------------------------------------

  • GISCs to familiarize the Manual, Guide, Transition Guide
  • GISCs should implement a mechanism to subscribe to Monitor messages for any Global Services they operate and any WIS Centres in their Area of Responsibility; and "integrate" those messages into their service management operations
  • GISCs should implement a mechanism to subscribe to Monitor messages for any Global Services they operate and any WIS Centres in their Area of Responsibility; and "integrate" those messages into their service management operations
  • GISCs should consider how (or if) they will publish Monitor messages for any Global Services they operate and any WIS Centres in their Area of Responsibility; e.g., to advertise potential interruptions to service such as planned outages for maintenance
  • GISC to use the GM dashboard for their AoR
  • GISC to routinely review JIRA tickets
  • GISCs should familiarise themselves with the centre-id list, identifying those centre-ids relating to WIS Centres in their Area of Responsibility
  • GISCs should, in consultation with their affiliated WIS Centres, identify any "stale" (un-used/deprecated) centre-ids associated with their Area of Responsibility, and request Secretariat to review and update the Registry
  • GISCs should provide feedback to the Global Monitors to improve the layout and content of the dashboards for supporting operational service management
  • GISCs should ensure that WIS2 data exchange in their AoR is compliant before the validation is enabled: message structure / keys / values (schema validation) << "discard" implemented 1-Jan-2025
  • GISCs should ensure that WIS2 data exchange in their AoR is compliant before the validation is enabled: topic hierarchy (ensure use of official topic hierarchy) << "discard" implemented 1-Apr-2025
  • GISCs should work with RTHs to validate that all GTS data published by their affiliated WIS Centres are available from both GTS-to-WIS2 gateways (complete between 1-Jan-2025 and 31-Mar-2025)
  • GISCs need to ensure they have access to the WIS2 JIRA – nominate named individuals who will be given access
  • GISCs need to ensure they have access to the Global Monitor dashboards
  • GISCs need to work with Global Monitors to refine the Global Monitoring dashboards to enable effective GISC-Watch operation / WIS2 service monitoring
  • GISCs need to coordinate monitoring and issue management for WIS2 (i.e., GISC-Watch) (Note: depending on GISC watch guide)

---------------Mid-term Action List for GISC (by September 2025)------------------------------------

  • recommend starting by mapping GTS bulletins published by WIS Centres in their Area of Responsibility to the WIS2 Topic Hierarchy
  • GISCs need to provide guidance to WIS Centres in their Area of Responsibility for creating good-quality metadata
  • GISCs should familiarise themselves with the Global Discovery Catalogue
  • GISCs should, in consultation with their affiliated WIS Centres, review metadata records published by WIS Centres in their Area of Responsibility, identify any improvements that are needed
  • where old metadata exists that needs to be removed, GISCs should identify these records to the Secretariat and GDC operators are request their removal
  • GISCs should engage with WIS Centres in their AoR who have not yet published metadata to help them develop the skills to write/manage metadata
  • GISCs should ensure that WIS2 data exchange in their AoR is compliant before the validation is enabled: missing metadata << "discard" implemented 1-Sep-2025
  • GISCs should work with their affiliated WIS Centres to determine when they anticipate new data, published only via WIS2, to be provided operationally and to include this information in their WIS2 migration plans
  • GISCs need to manage the resolution of issues affecting the operation of WIS2 in their Area of Responsibility - a GISC is the primary point of contact in the AoR for issue resolution, document incidents and routinely report to Secretariat, must update WIS2 JIRA tickets as action is taken, and close WIS2 tickets once issues are satisfactorily resolved
  • Plan a training programme for affiliated WIS Centres on WIS2 tools, protocols, best practices
  • Plan workshops for affiliated WIS Centres to develop migration plans

---------------Longer-term Action List for GISC(2026+)------------------------------------

  • GISCs should engage with other WIS Centres in their AoR to discuss their plans for establishing WIS2 Nodes and help them define a centre-id for each WIS2 Node
  • GISCs should engage with their Regional Association to feed into the Regional WIS2 Implementation plan
  • GISCs need to coordinate between WMO Secretariat, Regional Association, affiliated WIS Centres, Regional Telecommunication Hubs (RTH) to support Transition and ongoing data exchange
  • GISCs need to provide their affiliated centres with technical guidance to understand WIS2 concepts, technical regulation, and on-going responsibilities
  • GISCs need to work with their affiliated WIS Centres to develop a transition/migration plan for their Area of Responsibilities between 2025-2030 (i.e., running a workshop for affiliated WIS Centres and through 1-to-1 engagement)
  • GISCs need to support WIS Centres establish WIS2 Nodes; including engaging with PRs (etc.) to secure endorsement for new WIS Centres (NC or DCPC) and coordination with Secretariat to update the WIS2 Registry
  • GISCs should work with their affiliated WIS Centres to ensure that all the GTS data those WIS Centres need are available, and that all the GTS data those WIS Centres publish into WIS2 correctly propagates into GTS (Note:This depends on the readiness of the WIS centres for migration)
  • GISCs should support their affiliated WIS Centres in determining when they are ready to begin decommissioning of their Message Switch (i.e., once they have successfully demonstrated operational publication of all their data onto WIS2) (Note:This depends on the readiness of the WIS centres for migration)
  • GISCs need to support WIS Centres decommission their Message Switches (Note:This depends on the readiness of the WIS centres for migration)
  • GISCs need to provide continuous technical support to ensure effective exchange of data within the Area of Responsibility
  • GISCs need to help affiliated WIS Centres publish good-quality discovery metadata; assisting in resolving issues identified by the Global Discovery Catalogue when importing metadata
  • GISCs need to provide a helpdesk for issue / problem management - for users (data consumers) and WIS Centres
  • GISCs should provide a mechanism (i.e., providing information on the Web) to communicate with / inform users about WIS2, operational status, and current/upcoming activities (including both technical and training/capacity building activities)
  • GISCs (especially those who also operate RTHs) should develop procedures for monitoring the availability of data within their Area of Responsibility - in addition to monitoring the service availability
  • GISCs need to determine how GISC Watch, Monitoring, and Incident Management Processes will be embedded within their organisation
  • GISCs should consider whether to establish local arrangements to capture metrics and provide dashboards for WIS2 Nodes (and other services) in their AoR

Clone this wiki locally