SMETS requirement clause

8.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.

HCALCSAlert touchpoint only
0

Atomic items

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

3

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.

SMETS8.4.4.1 · item clause.8.4.4.1

General

Alert touchpoint only

The source alert table cites SMETS 8.4.1.1; this website uses the reviewed Schedule 9 clause 8.4.4.1 and preserves the original reference as provenance.

Category
Alert reference
Section 20 meaning
The source alert table cites SMETS 8.4.1.1; this website uses the reviewed Schedule 9 clause 8.4.4.1 and preserves the original reference as provenance.

Documented touchpoints

  • Alert touchpointHCALCS0x8F1CFirmware Verification Failed
  • Alert touchpointHCALCS0x8F72Firmware Verification Successful
  • Alert touchpointHCALCS0x8F1BFirmware Verification Failed At Power On
Evidence:source paragraph 2648, 2649

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.