Atomic items
Section 20 objects, attributes or methods at this source reference.
SMETS requirement clause
5.16 — 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.
ESMEAlert touchpoint only
Documented touchpoints
Typed relationships supported by source mapping rows.
Linked SRVs
Unique retained services reached through exact control rows.
Linked alerts
Explicit requirement-to-alert references.
SMETS5.16 · item clause.5.16
Physical Requirements
This source clause is explicitly referenced by the GBCS device alert table.
- Category
- Alert reference
Documented touchpoints
- Alert touchpointESME0x8183Device joined SMHAN
- Alert touchpointESME0x8F3FUnauthorised Physical Access - Tamper Detect
- Alert touchpointESME0x8F69Tunnel Established
- Alert touchpointESME0x8F75Unauthorised Physical Access - Strong Magnetic field
- Alert touchpointESME0x8F76Unauthorised Physical Access - Terminal Cover Removed
- Alert touchpointESME0x81BESupply Disabled Then Locked - Supply Tamper State Cause
- Alert touchpointESME0x8F78Unauthorised Physical Access - Other
- Alert touchpointESME0x8F77Unauthorised Physical Access - Second Terminal Cover Removed
- Alert touchpointESME0x8F74Unauthorised Physical Access - Meter Cover Removed
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.