SMETS requirement clause

9.4.2 โ€” Communications

1 technical record hasbeen identified at this reference: 0 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.

SAPCAlert touchpoint only
0

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.

5

Linked alerts

Explicit requirement-to-alert references.

SMETS9.4.2 ยท item clause.9.4.2

Communications

Alert touchpoint only

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

Category
Alert reference

Documented touchpoints

  • Alert touchpointSAPC0x8F66Future โ€“ date HAN Interface Command Successfully Actioned
  • Alert touchpointSAPC0x8F3DTrusted Source Authentication Failure
  • Alert touchpointSAPC0x8F30Source Does not have Authority for Command
  • Alert touchpointSAPC0x8F67Future โ€“ date HAN Interface Command not Successfully Actioned
  • Alert touchpointSAPC0x8F1EIntegrity check of content or format of command failed
Evidence:source paragraph 2789, 2790

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.