World Meteorological Organization

Date: 2025-10-06

Version: 0.1

Document status: DRAFT

1. PART 0. Introduction

The overall service performance of the WMO Information System 2.0 (WIS2) relies on the operational quality of all Global Services. The WIS2 monitoring procedure was launched in April 2025, succeeding the WIS1 Watch, which had been active from 2017 through 2024. This Guide was first developed in 2020 to standardize the procedures for GISC Watch operation in accordance with the Resolution 57 (Cg-18) and the feedbacks from GISC based on their experience of the WISC Watch practice. This 2025 edition aims at adapting the procedures to WIS2. It is intended to assist GISCs in fulfilling their GISC Watch responsibilities.

This guide presents the procedures to be used:

  1. Procedures for Take over

  2. Procedures for Monitoring

  3. Procedures for Issue Management

  4. Procedures for Hand over

  5. Procedure for Escalation

2. PART I. Procedures for Take over

Procedure to use when a GISC starts its GISC watch period:

(a). Take over the GISC Watch duty according to the agreed roster.

The GISC Watch roster is available here: https://community.wmo.int/en/activity-areas/wis/gisc_watch

(b). Handover acknowledgement

  • Accept the hand-over-report from previous GISC

  • Send an acknowledgement to confirm receipt.

Note: To ensure the continuity of GISC Watch, the incoming GISC must begin monitoring duties at the start of its roster period even if the handover email/report has not yet been received.

Sample takeover email:

From: GISC Beijing
To: GISC Toulouse
Cc: gisc-ops@groups.wmo.int,wis@wmo.int
Subject: GISC WATCH Takeover (16-30 April) confirmed: GISC Watch Report 01-15 April 2025
Dear GISC Toulouse,
Thank you for your efforts and the handover report.
GISC Beijing will take over the duty from April 16th to 30th 2025.
Best regards,
GISC Beijing

(c). Review open tickets

At the beginning of its monitoring period, review any open tickets from the previous period.

3. PART II.Procedures for Monitor

Procedure to use by the GISC on duty during the monitoring period.

Basic Principles:

  1. The GISC Watch’s goal is focusing on the Global Services level (Global Broker, Global Cache, Global Discovery Catalogue, Global Monitoring).

  2. Issues regarding data coming from WIS2Nodes are manages by GISCs according to their AoR (Area of Responsibility). The GISC Watch can pinpoint issues to the GISCs, but this is not mandatory.

  3. A large part of the monitoring activity is already performed on the Global Monitoring level, with JIRA tickets to be automatically initiated.

The following table shall be filled in, by checking Global Monitoring metrics (see detailed information how to get the figures after the table):

For GM-China Dashboard:

GM CHINA 01
GM CHINA 02
GM CHINA 03
GM CHINA 04
GM CHINA 05
GM CHINA 06
GM CHINA 07
GM CHINA 08
GM CHINA 09

For GM-Morocco Dashboard:

GM Marocco 01
GM Marocco 02
GM Marocco 03
GM Marocco 04
GM Marocco 05
GM Marocco 06
GM Marocco 07
GM Marocco 08
Global Services Test Source Details Roster Start Optional additional dates Roster end

Global Monitorings

YYYY/MM/DD

…​

YYYY/MM/DD

GM CMA GISC

https://gm.wis.cma.cn

User: gisc_user

connect OK

…​

connect OK

GM CMA GS

https://gm.wis.cma.cn

User: gs_user

connect OK

…​

connect OK

GM MAROCMETEO GISC

https://wis2gmc.marocmeteo.ma/

User: gisc-user

connect OK

…​

connect NOK

Global Brokers

Based on dashboard WIS2-GISC/wis2-gisc-GB (gisc_user) / Indicator: "WIS2Nodes Total Messages over past 24h"

YYYY/MM/DD

…​

YYYY/MM/DD

GB Brazil

From GM China

63

…​

64

GB Brazil

From GM MAROCMETEA

63

…​

Not Available

GB China

From GM China

68

…​

68

GB China

From GM MAROCMETEA

68

…​

Not Available

GB France

From GM China

62

…​

63

GB France

From GM MAROCMETEA

62

…​

Not Available

GB USA

From GM China

46

…​

52

GB USA

From GM MAROCMETEA

46

…​

Not Available

Global Caches

Based on dashboard WIS2-GISC/wis2-gisc-GC (gisc_user) / Indicator: "WIS2Nodes Total downloaded over past 24h"

YYYY/MM/DD

…​

YYYY/MM/DD

GC CN CMA

From GM China

No data

…​

No data

GB CN CMA

From GM MAROCMETEA

No data

…​

No data

GC MO NOAA US/UK

From GM China

58

…​

58

GB MO NOAA US/UK

From GM MAROCMETEA

58

…​

58

GC DE DWD

From GM China

56

…​

58

GB DE DWD

From GM MAROCMETEA

56

…​

58

GC JP JMA

From GM China

57

…​

58

GB JP JMA

From GM MAROCMETEA

57

…​

58

GC SA NCM

From GM China

No data

…​

59

GB SA NCM

From GM MAROCMETEA

No data

…​

59

JIRA Ticketing System

YYYY/MM/DD

…​

YYYY/MM/DD

Total "In Progress"

No data

…​

2

Total "To Do"

No data

…​

2

Total "Done"

No data

…​

2

Total "In Review"

No data

…​

2

Total "Triage"

(should be zero)

No data

…​

2

How to fetch data from the dashboards:

3.1. Global brokers data

3.2. Global caches data

01 LOGIN

Log in as gisc_user

02 GC Dashboard

Click on Dashboards, then wis2-gisc-GC

03 GC Data

Select GC and read value

Check has to be performed at roster start and roster end. Additional dates can also be added.

4. PART III. Procedures for Issues Management

The WIS2 ticketing system is provided and operated by WMO : https://jira.wmo.int.

5. Tickets review guideline

The GISC in charge needs to review the tickets with the following guidelines:

(1) Review frequency

  • At least once or twice a week.

(2) Key focus

  • Focus on “stalled” ticket”: send reminder for tickets inactive for more than 2 weeks

(3) Automatic ticket creation

  • Most tickets are expected to be created automatically by the GISC Monitoring system

6. Procedure to review Jira Tickets for the GISC Watch:

(1) Access the JIRA system:

If there are any changes or updates to the JIRA accounts for your GISC, please inform the WMO Secretariat so that the necessary updates can be made to ensure continued access.

(2) Select the correct project

  • Choose Project "WIS2 IMS"

JIRA summary 01

(3) Filter tickets

  • "Issues" → " View all issues and tickets" (upper right) → Filter "Status" by unchoosing "Done"

Workflow of the tickets can be found here: https://wmoomm.sharepoint.com/:w:/s/wmocpdb/EXmYNLQKs59AlHToO9rH6YAB3xoVjdqeoD2fkC-4h4aPjA?e=XqmxpR

(4) Ticket Handling

  • Review ticket list and send reminders (inside tickets) for tickets inactive for more than 2 weeks.

  • Assign tickets to relevant Assignees for the tickets with status “TRIAGE” (new tickets)

JIRA summary 02

Table-1: Priority Levels

6.1. Incident Impact Levels and GISC Response Times

Level Impact Examples Assigned GISC: Time to Respond Assigned GISC: Time to Resolve

Very High

- Severe impact on one or more GISC operations
- Immediate action required

- Total failure of Global Services

ASAP / within 1 day

ASAP / within 1 week

High

- One or more essential services are unavailable
- Action required within one week

- Global Services are offline

Within 1 week

Within 1 month

Medium

- Essential services not affected
- Response required, monitoring ongoing

- Partial outage of a Global Service
- Missing data from multiple WIS2Nodes simultaneously

Within 1 week

Monthly progress updates

Low

Not to be used

—

—

—

None

Not to be used

—

—

—

7. PART IV. Procedures for Handover

7.1. (a) Handover Process

  1. The GISC currently on duty is responsible for sending the handover report to the next GISC in the roster.

  2. If no confirmation is received:

    • The current GISC must follow up with a reminder.

    • GISC Watch duties must be maintained until the next GISC acknowledges receipt of the handover.

  3. If there is still no response:

    • The GISC following the next one in the roster should be contacted to agree on a revised handover date.

    • The purpose is to ensure continuity by splitting the remaining period between the two GISCs if needed.

7.2. (b) Summary Handover Report

  1. The handover report formally transfers GISC Watch responsibilities to the next GISC.

  2. The report must be sent as follows:

  3. The GISC Watch report to be completed is available here

    • Note1: The GISC Watch report is a consolidated report. Outgoing GISCs are responsible for adding the columns corresponding to the GISC Watch period.

    • Note2: Only the email addresses of the GISCs included in the mailing list gisc-ops@groups.wmo.int, which serves as the official channel for GISC Watch handover and takeover communications, have the access to edit this document as per the decisions at the ET-WISOP 10th meeting.

    • Note3: For any changes of the email addresses, please contact the WMO Secretariat at wis@wmo.int.

  4. A sample Handover email

8. GISC WATCH REPORT EXAMPLE

From: GISC Toulouse
To: GISC Beijing
Cc: gisc-ops@groups.wmo.int, wis@wmo.int
Subject: GISC WATCH REPORT — 01–15 April 2025
GISC Toulouse has completed the GISC Watch duty for the period *1–15 April 2025*.
Please find below the summary report for this period:
1. General Information
▪	 WIS2 to GTS gateway test conducted on *9 April 2025*
2. Global Services Status
▪	[Provide a summary of the operational status, issues encountered, or actions taken during the watch period]
3.JIRA tickets activity:
▪	Several ticket assignations from “TRIAGE” performed
▪	Duplicate tickets closed
▪	Several stalled tickets reminders send
GISC Beijing: Would you please confirm the GISC Watch handover?
Best regards,
GISC Toulouse

9. PART V. Procedure for Escalation

For any issue related to GISC Watch that requires escalation, the Chair of ET-WISOP is the first escalation point for all GISCs

Appendix 1: IMS-GISC Operator Manual

10. 1. How to Login as External User

10.1. Step 1:

Access the login URL: https://jira.wmo.int/secure/Dashboard.jspa

Step1.1

10.2. Step 2:

Click on the External Users button.

Step1.2

10.3. Step 3:

You will be redirected to the login page. Enter your email and password as registered in our database.

Step1.3

11. 2. How to Resolve an Issue

  • Note1 The GISC Watch on-duty may close tickets if the comments clearly indicate that the issue has been resolved. If the comments are unclear, lack evidence, or show no progress, the GISC Watch on-duty is responsible for following up with the assignee to verify the ticket’s status.

  • Note2 The ticket reporter may close tickets once the issue has been resolved.

  • Note3 The assignee may close tickets once the issue has been resolved.

  • Note4 The WMO Secretariat may close the tickets if the comments clearly indicate the issue has been resolved.

11.1. Step 1:

After logging in, you may find the issues assigned to you.

Step2.1.1

You can also find your issues by navigating to: User Profile → Boards → Only My Issues

Step2.1.2

Alternatively, click on Issues in the top menu and select My Open Issues from the left panel.

Step2.1.3

11.2. Step 2:

The GISC Operator should: - Check the issue. - Assign it to the responsible person (e.g., HAN Xinqiang). - Set the issue status from Triage to TO DO.

Step2.2.1
Step2.2.2

You can view the workflow by clicking on View Workflow.

Step2.2.3

11.3. Step 3:

The assignee (e.g., HAN Xinqiang) begins work on the issue and sets the status from TO DO to IN PROGRESS.

Step2.3.1
Step2.3.2

11.4. Step 4:

After addressing the issue, the assignee submits it for review: - Set the status from IN PROGRESS to IN REVIEW. - Assign the issue to the reviewer (e.g., XUE Lei).

The process history is visible in the comments below, along with Reporter, Assignee, Watchers, etc., on the right.

Step2.4.1

11.5. Step 5:

The reviewer (XUE Lei) reviews the issue, assigns it back to the original handler (e.g., HAN Xinqiang), and sets the status from IN REVIEW to IN PROGRESS.

Step2.5.1
Step2.5.2

11.6. Step 6:

The assignee receives the feedback, completes any follow-up, and sets the status from IN PROGRESS to DONE.

The issue is now successfully resolved.

Step2.6.1
Step2.6.2

12. 3. How to Create an Issue

12.1. Step 1:

In the user interface, click Create, describe the problem in detail using graphics and/or text, set the Priority, and assign the issue to the relevant GISC.

Step3.1.1

12.2. Step 2:

Add a comment to further explain the issue.

Step3.2.1

12.3. Step 3:

Add a Due Date as needed

  • Note1 Reporter may add a Due Date when creating a ticket.

  • Note2 The GISC Watch on-duty may add a due date and update the ticket priority if none is set or if the issues have been outstanding for some time.

Step3.3.1