SMETS requirement clause

4.6.5.7 — Daily Read Log

7 technical records havebeen identified at this reference: 7 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.

GSMESRV touchpoint
7

Atomic items

Section 20 objects, attributes or methods at this source reference.

7

Documented touchpoints

Typed relationships supported by source mapping rows.

1

Linked SRVs

Unique retained services reached through exact control rows.

0

Linked alerts

Explicit requirement-to-alert references.

SMETS4.6.5.7 · item DailyReadLog(excExport).method: readLog

DailyReadLog(excExport) - readLog

SRV touchpoint

The response contains all the log entries between fromDateTime and toDateTime inclusive

Object
DailyReadLog(excExport)
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

Evidence:source paragraph 735, 736Section 20 row 1493

SMETS4.6.5.7 · item DailyReadLog(excExport).methodInput: fromDateTime

DailyReadLog(excExport) - fromDateTime

SRV touchpoint

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
DailyReadLog(excExport)
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

Evidence:source paragraph 735, 736Section 20 row 1522

SMETS4.6.5.7 · item DailyReadLog(excExport).methodInput: toDateTime

DailyReadLog(excExport) - toDateTime

SRV touchpoint

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.

Object
DailyReadLog(excExport)
Attribute / method
methodInput: toDateTime
Interface disposition
E
Category
Method Input
Section 20 meaning
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.

Documented touchpoints

Evidence:source paragraph 735, 736Section 20 row 1528

SMETS4.6.5.7 · item DailyReadLog(excExport).logEntries[1..31].logEntry.tariffTOURegisterMatrix[1..4].RegisterMatrixValue

DailyReadLog(excExport) - logEntries logEntry tariffTOURegisterMatrix RegisterMatrixValue

SRV touchpoint

the billing log entry recorded at that date-time

Object
DailyReadLog(excExport)
Attribute / method
logEntries[1..31].logEntry.tariffTOURegisterMatrix[1..4].RegisterMatrixValue
Interface disposition
E
Category
Operational data
Section 20 meaning
the billing log entry recorded at that date-time

Documented touchpoints

Evidence:source paragraph 735, 736Section 20 row 1781

SMETS4.6.5.7 · item DailyReadLog(excExport).logEntries[1..31].logEntry.tariffBlockCounterMatrix[1..4].CounterMatrixValue

DailyReadLog(excExport) - logEntries logEntry tariffBlockCounterMatrix CounterMatrixValue

SRV touchpoint

the billing log entry recorded at that date-time

Object
DailyReadLog(excExport)
Attribute / method
logEntries[1..31].logEntry.tariffBlockCounterMatrix[1..4].CounterMatrixValue
Interface disposition
E
Category
Operational data
Section 20 meaning
the billing log entry recorded at that date-time

Documented touchpoints

Evidence:source paragraph 735, 736Section 20 row 1782

SMETS4.6.5.7 · item DailyReadLog(excExport).logEntries[1..31].logEntry.activeImportRegisterValue/consumption

DailyReadLog(excExport) - logEntries logEntry activeImportRegisterValue/consumption

SRV touchpoint

the billing log entry recorded at that date-time

Object
DailyReadLog(excExport)
Attribute / method
logEntries[1..31].logEntry.activeImportRegisterValue/consumption
Interface disposition
E
Category
Operational data
Section 20 meaning
the billing log entry recorded at that date-time

Documented touchpoints

Evidence:source paragraph 735, 736Section 20 row 546

SMETS4.6.5.7 · item DailyReadLog(excExport).logEntries[1..31].logEntry.timestamp

DailyReadLog(excExport) - logEntries logEntry timestamp

SRV touchpoint

The UTC date-time at which the corresponding log entry was taken

Object
DailyReadLog(excExport)
Attribute / method
logEntries[1..31].logEntry.timestamp
Interface disposition
E
Category
Operational data
Section 20 meaning
The UTC date-time at which the corresponding log entry was taken

Documented touchpoints

Evidence:source paragraph 735, 736Section 20 row 611

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.