Atomic items
Section 20 objects, attributes or methods at this source reference.
SMETS requirement clause
10 technical records havebeen identified at this reference: 10 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.
SMETS5.7.5.26 · item PrepaymentDailyReadLog.method: readLog
The response contains all the log entries between fromDateTime and toDateTime inclusive
PrepaymentDailyReadLogmethod: readLogDocumented touchpoints
0x0034ESMESRV 4.14SMETS5.7.5.26 · item PrepaymentDailyReadLog.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
PrepaymentDailyReadLogmethodInput: fromDateTimeDocumented touchpoints
0x0034ESMESRV 4.14SMETS5.7.5.26 · item PrepaymentDailyReadLog.methodInput: toDateTime
Except for GSME, if the End of Time as per GBCS section 9.1.6, the response contains all entries from 'fromDateTime' in the log to the newest. If not the End of Time, the response contains all entries between fromDateTime and toDateTime inclusive. For GSME, the response contains entries between fromDateTime and toDateTime, including those matching the fromDateTime but excluding those matching toDateTime. Note that this means GSME log entries with an 'invalid time' cannot be retrieved.
PrepaymentDailyReadLogmethodInput: toDateTimeDocumented touchpoints
0x0034ESMESRV 4.14SMETS5.7.5.26 · item PrepaymentDailyReadLog.logEntries[1..31].logEntry.accumulatedDebtRegisterValue
the billing log entry recorded at that date-time
PrepaymentDailyReadLoglogEntries[1..31].logEntry.accumulatedDebtRegisterValueDocumented touchpoints
0x0034ESMESRV 4.14SMETS5.7.5.26 · item PrepaymentDailyReadLog.logEntries[1..31].logEntry.emergencyCreditBalanceValue
the billing log entry recorded at that date-time
PrepaymentDailyReadLoglogEntries[1..31].logEntry.emergencyCreditBalanceValueDocumented touchpoints
0x0034ESMESRV 4.14SMETS5.7.5.26 · item PrepaymentDailyReadLog.logEntries[1..31].logEntry.meterBalanceValue
the billing log entry recorded at that date-time
PrepaymentDailyReadLoglogEntries[1..31].logEntry.meterBalanceValueDocumented touchpoints
0x0034ESMESRV 4.14SMETS5.7.5.26 · item PrepaymentDailyReadLog.logEntries[1..31].logEntry.paymentDebtRegisterValue
the billing log entry recorded at that date-time
PrepaymentDailyReadLoglogEntries[1..31].logEntry.paymentDebtRegisterValueDocumented touchpoints
0x0034ESMESRV 4.14SMETS5.7.5.26 · item PrepaymentDailyReadLog.logEntries[1..31].logEntry.timeDebtRegisters1Value
the billing log entry recorded at that date-time
PrepaymentDailyReadLoglogEntries[1..31].logEntry.timeDebtRegisters1ValueDocumented touchpoints
0x0034ESMESRV 4.14SMETS5.7.5.26 · item PrepaymentDailyReadLog.logEntries[1..31].logEntry.timeDebtRegisters2Value
the billing log entry recorded at that date-time
PrepaymentDailyReadLoglogEntries[1..31].logEntry.timeDebtRegisters2ValueDocumented touchpoints
0x0034ESMESRV 4.14SMETS5.7.5.26 · item PrepaymentDailyReadLog.logEntries[1..31].logEntry.timestamp
The UTC date-time at which the corresponding log entry was taken
PrepaymentDailyReadLoglogEntries[1..31].logEntry.timestampDocumented touchpoints
0x0034ESMESRV 4.14How 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.