SMETS requirement clause

9.4.4.1 — General

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.

6

Documented touchpoints

Typed relationships supported by source mapping rows.

0

Linked SRVs

Unique retained services reached through exact control rows.

6

Linked alerts

Explicit requirement-to-alert references.

SMETS9.4.4.1 · item clause.9.4.4.1

General

Alert touchpoint only

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

Category
Alert reference

Documented touchpoints

  • Alert touchpointSAPC0x8F1CFirmware Verification Failed
  • Alert touchpointSAPC0x8F72Firmware Verification Successful
  • Alert touchpointSAPC0x8F53Failed Authentication or Authorisation not covered by other codes
  • Alert touchpointSAPC0x8F60Unusual numbers of malformed, out-of-order or unexpected Commands received
  • Alert touchpointSAPC0x8F1BFirmware Verification Failed At Power On
  • Alert touchpointSAPC0x8F43Change in the executing Firmware version
Evidence:source paragraph 2805, 2806

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.