Atomic items
Section 20 objects, attributes or methods at this source reference.
CHTS requirement clause
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.
Section 20 objects, attributes or methods at this source reference.
Typed relationships supported by source mapping rows.
Unique retained services reached through exact control rows.
Explicit requirement-to-alert references.
CHTS4.6.3.7 · item DailyConsumptionLog.methodInput: 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
DailyConsumptionLogmethodInput: fromDateTimeDocumented touchpoints
0x00A0GPFSRV 4.17CHTS4.6.3.7 · item DailyConsumptionLog.methodInput: 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
DailyConsumptionLogmethodInput: toDateTimeDocumented touchpoints
0x00A0GPFSRV 4.17CHTS4.6.3.7 · item DailyConsumptionLog.logEntries[1..731].logEntry.value
Consumption for that day
DailyConsumptionLoglogEntries[1..731].logEntry.valueDocumented touchpoints
0x00A0GPFSRV 4.17CHTS4.6.3.7 · item DailyConsumptionLog.logEntries[1..731].logEntry.timestamp
Timestamp of the entry
DailyConsumptionLoglogEntries[1..731].logEntry.timestampDocumented touchpoints
0x00A0GPFSRV 4.17CHTS4.6.3.7 · item DailyConsumptionLog.Method: readLog
The response contains all the log entries between fromDateTime and toDateTime inclusive
DailyConsumptionLogMethod: readLogDocumented touchpoints
0x00A0GPFSRV 4.17How to read this page
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.