Atomic items
Section 20 objects, attributes or methods at this source reference.
SMETS requirement clause
9.4.1 — Clock
4 technical records havebeen identified at this reference: 3 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 onlyNo Section 20 bridgeSRV touchpoint
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.
SMETS9.4.1 · item Time.valueZigbeeEpoch
Time - valueZigbeeEpoch
The UTC date time, expressed with a Zigbee Epoch.
- Object
Time- Attribute / method
valueZigbeeEpoch- Interface disposition
- I
- Category
- Operational data
- Section 20 meaning
- The UTC date time, expressed with a Zigbee Epoch.
No GBCS or SRV bridge is recorded for this item in the current Section 20 mapping. This is an evidence status, not a statement of non-compliance.
SMETS9.4.1 · item Time.methodOutput: value
Time - value
The UTC date time
- Object
Time- Attribute / method
methodOutput: value- Interface disposition
- E
- Category
- Operational data
- Section 20 meaning
- The UTC date time
Documented touchpoints
- UpdatesECS70
0x0062SAPCSRV 6.11
SMETS9.4.1 · item Time.methodOutput: status
Time - status
May be one of three values: Invalid, Unreliable, Reliable
- Object
Time- Attribute / method
methodOutput: status- Interface disposition
- E
- Category
- Operational data
- Section 20 meaning
- May be one of three values: Invalid, Unreliable, Reliable
Documented touchpoints
- UpdatesECS70
0x0062SAPCSRV 6.11
SMETS9.4.1 · item clause.9.4.1
Clock
This source clause is explicitly referenced by the GBCS device alert table.
- Category
- Alert reference
Documented touchpoints
- Alert touchpointSAPC0x8F0CClock not adjusted (adjustment greater than 10 seconds)
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.