SMETS requirement clause

5.5.12.6 — Supply outage reporting

3 technical records havebeen identified at this reference: 2 Section 20 items and 1 explicit clause reference. The links below describe documented interfaces and observable effects; they do not assert compliance with the source requirement.

ESMEAlert touchpoint onlyGBCS use case only
2

Atomic items

Section 20 objects, attributes or methods at this source reference.

5

Documented touchpoints

Typed relationships supported by source mapping rows.

0

Linked SRVs

Unique retained services reached through exact control rows.

3

Linked alerts

Explicit requirement-to-alert references.

SMETS5.5.12.6 · item SupplyOutageRestore.interruptionValue

SupplyOutageRestore - interruptionValue

GBCS use case only

The date-time at which power was interrupted

Object
SupplyOutageRestore
Attribute / method
interruptionValue
Interface disposition
E
Category
Alert
Section 20 meaning
The date-time at which power was interrupted

Documented touchpoints

  • ReadsECS800x0067ESME
Evidence:source paragraph 1170, 1171Section 20 row 1771

SMETS5.5.12.6 · item SupplyOutageRestore.restorationValue

SupplyOutageRestore - restorationValue

GBCS use case only

The date-time at which power was restored

Object
SupplyOutageRestore
Attribute / method
restorationValue
Interface disposition
E
Category
Alert
Section 20 meaning
The date-time at which power was restored

Documented touchpoints

  • ReadsECS800x0067ESME
Evidence:source paragraph 1170, 1171Section 20 row 1772

SMETS5.5.12.6 · item clause.5.5.12.6

Supply outage reporting

Alert touchpoint only

This source clause is explicitly referenced by the GBCS device alert table.

Category
Alert reference

Documented touchpoints

  • Alert touchpointESME0x8F57Supply interrupted
  • Alert touchpointESME0x8F36Supply Outage Restored - Outage >= 3 minutes
  • Alert touchpointESME0x8F35Supply Outage Restored
Evidence:source paragraph 1170, 1171

How to read this page

Evidence is kept at record level

A source clause can contain several separately mapped Section 20 items and an explicit alert reference. One item may be read by an SRV, another updated by a different service, and another have only an Alert or local-HAN path. Accordingly, the clause summary does not collapse those distinctions into a single covered or uncovered result.