Atomic items
Section 20 objects, attributes or methods at this source reference.
SMETS requirement clause
5.7.5.14 — Daily Consumption Log [INFO]
5 technical records havebeen identified at this reference: 5 Section 20 items and 0 explicit clause references. The links below describe documented interfaces and observable effects; they do not assert compliance with the source requirement.
ESMESRV 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.
SMETS5.7.5.14 · item DailyConsumptionLog.methodInput: fromDateTime
DailyConsumptionLog - fromDateTime
If the Start of Time as per GBCS section 9.1.6, response contains all entries from the oldest in the log to 'toDateTime'. If not the Start of Time, response contains all entries between fromDateTime and toDateTime inclusive
- Object
DailyConsumptionLog- Attribute / method
methodInput: fromDateTime- Interface disposition
- E
- Category
- Method Input
- Section 20 meaning
- If the Start of Time as per GBCS section 9.1.6, response contains all entries from the oldest in the log to 'toDateTime'. If not the Start of Time, response contains all entries between fromDateTime and toDateTime inclusive
Documented touchpoints
- ReadsECS66
0x0060ESMESRV 4.17
SMETS5.7.5.14 · item DailyConsumptionLog.methodInput: toDateTime
DailyConsumptionLog - toDateTime
If the End of Time as per GBCS section 9.1.6, response contains all entries from 'fromDateTime' in the log to the newest. If not the End of Time, response contains all entries between fromDateTime and toDateTime inclusive
- Object
DailyConsumptionLog- Attribute / method
methodInput: toDateTime- Interface disposition
- E
- Category
- Method Input
- Section 20 meaning
- If the End of Time as per GBCS section 9.1.6, response contains all entries from 'fromDateTime' in the log to the newest. If not the End of Time, response contains all entries between fromDateTime and toDateTime inclusive
Documented touchpoints
- ReadsECS66
0x0060ESMESRV 4.17
SMETS5.7.5.14 · item DailyConsumptionLog.logEntries[1..731].logEntry.value
DailyConsumptionLog - logEntries logEntry value
Consumption for that day
- Object
DailyConsumptionLog- Attribute / method
logEntries[1..731].logEntry.value- Interface disposition
- E
- Category
- Operational data
- Section 20 meaning
- Consumption for that day
Documented touchpoints
- ReadsECS66
0x0060ESMESRV 4.17
SMETS5.7.5.14 · item DailyConsumptionLog.logEntries[1..731].logEntry.timestamp
DailyConsumptionLog - logEntries logEntry timestamp
Timestamp of the entry
- Object
DailyConsumptionLog- Attribute / method
logEntries[1..731].logEntry.timestamp- Interface disposition
- E
- Category
- Operational data
- Section 20 meaning
- Timestamp of the entry
Documented touchpoints
- ReadsECS66
0x0060ESMESRV 4.17
SMETS5.7.5.14 · item DailyConsumptionLog.Method: readLog
DailyConsumptionLog - readLog
The response contains all the log entries between fromDateTime and toDateTime inclusive
- Object
DailyConsumptionLog- Attribute / method
Method: readLog- Interface disposition
- E
- Category
- Method
- Section 20 meaning
- The response contains all the log entries between fromDateTime and toDateTime inclusive
Documented touchpoints
- ReadsECS66
0x0060ESMESRV 4.17
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.