Skip to content

Add outage notification guideline for Global Services#248

Merged
6a6d74 merged 1 commit into
wmo-im:INFCOM-4from
jmaxmarno:INFCOM-4
May 12, 2026
Merged

Add outage notification guideline for Global Services#248
6a6d74 merged 1 commit into
wmo-im:INFCOM-4from
jmaxmarno:INFCOM-4

Conversation

@jmaxmarno
Copy link
Copy Markdown

Added a guideline for notifying WIS2 centres about outages exceeding 4 hours.

Added a guideline for notifying WIS2 centres about outages exceeding 4 hours.
Copy link
Copy Markdown
Collaborator

@6a6d74 6a6d74 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Max. I think we also need to indicate that this notification follows the WIS2 Monitoring Event Specification. @amilan17 should be able to give you a reference to where this new spec will appear in the WIS2 Manual. I think it's likely to be APPENDIX G: WIS2 MONITORING EVENTS.

@6a6d74
Copy link
Copy Markdown
Collaborator

6a6d74 commented May 7, 2026

Note discussion scheduled for ET-W2IT on 11-MAY-2026: which types of events should Global Services be publishing and when. PR wmo-im/wis2-monitoring-events#28 WMEM: add more types and remove data.subtype proposes to add code-list for event type controlled vocab.

@6a6d74
Copy link
Copy Markdown
Collaborator

6a6d74 commented May 12, 2026

From ET-W2IT meeting 11-MAY-2026

ET-WISOP have a separate discussion (see Issue wmo-im/wis2-operation#49) about whether or not a Global Service anticipating an outage should directly create a WIS2 Monitoring Event message, or create a JIRA ticket that will prompt a Global Monitor to automatically generate the message.

ET-W2IT agree that the JIRA-based procedure seems more streamlined as there's no mechanism for a Global Service to directly raise a WME message.

Consequently, the Technical Regulation needs to be updated to state the requirement to raise a JIRA ticket according to a "maintenance" template (details of the template are as yet undefined - but are also not necessary to include in the Techical Regulation).

@6a6d74
Copy link
Copy Markdown
Collaborator

6a6d74 commented May 12, 2026

@jmaxmarno - the text you've added is almost what's needed. I'm going to merge your change and then create a new PR with text mentioning JIRA.

Copy link
Copy Markdown
Collaborator

@6a6d74 6a6d74 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given change in approach, the proposed text is good.

@6a6d74 6a6d74 merged commit 3fea7c9 into wmo-im:INFCOM-4 May 12, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants