Alert Details
WAN: YUse Case Specific Alert StructureMandatedCriticalPre-config: No
GBCS 16.2 / 0x8F37
Supply Outage Restored on Phase 1
Cross-specification evidence
Technical requirement relationships
The source clauses below explicitly relate this alert to equipment behaviour. Confidence and evidence labels show how each relationship was established.
Alert touchpoint
1 clause · 1 linked record- SMETS 5.17.2.6Exact evidence
1 direct clause reference
- Supply outage reporting phase [n]
ESMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 47 · reference 5.17.2.6
Device Specific Details
- ESME
- Network Operator
DUIS Annex 15 / 15.4.3
Device Alert payload structure
This alert carries additional structured payload defined by DUIS Annex 15 section 15.4.3, delivered inside ra:DeviceAlertContent asSupplyOutageRestoreAlert.
- Payload root
SupplyOutageRestoreAlert- Payload type
SupplyOutageRestoreAlertType- Annex section
- 15.4.3 — Supply Outage Restored Device Alerts
Message codes and device contexts
| Message code | Device context | Message name | GBCS use case |
|---|---|---|---|
0067 | — | Supply Outage Restore Alert from ESME | ECS80 |
Payload fields
| Field | Type | Mandatory | Units | Description | Sensitivity |
|---|---|---|---|---|---|
interruptionValue | xs:dateTime | Yes | UTC Date-Time | Date-time at which power was interrupted. | Non-Sensitive |
restorationValue | xs:dateTime | Yes | UTC Date-Time | Date-time at which power was restored. | Non-Sensitive |
Message Patterns and Examples
View the step-by-step alert delivery pattern — from device event through WAN transmission to Known Remote Party notification — with available XML examples.
View Message Patterns →