SMETS requirement clause

4.3 — Physical requirements

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.

GSMEAlert touchpoint only
0

Atomic items

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

9

Documented touchpoints

Typed relationships supported by source mapping rows.

0

Linked SRVs

Unique retained services reached through exact control rows.

9

Linked alerts

Explicit requirement-to-alert references.

SMETS4.3 · item clause.4.3

Physical requirements

Alert touchpoint only

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

Category
Alert reference

Documented touchpoints

  • Alert touchpointGSME0x8F3FUnauthorised Physical Access - Tamper Detect
  • Alert touchpointGSME0x8F69Tunnel Established
  • Alert touchpointGSME0x8F75Unauthorised Physical Access - Strong Magnetic field
  • Alert touchpointGSME0x8F74Unauthorised Physical Access - Meter Cover Removed
  • Alert touchpointGSME0x81BESupply Disabled Then Locked - Supply Tamper State Cause
  • Alert touchpointGSME0x8F73Unauthorised Physical Access - Battery Cover Removed
  • Alert touchpointGSME0x8F76Unauthorised Physical Access - Terminal Cover Removed
  • Alert touchpointGSME0x8F78Unauthorised Physical Access - Other
  • Alert touchpointGSME0x8183Device joined SMHAN
Evidence:source paragraph 155, 156

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.