Atomic items
Section 20 objects, attributes or methods at this source reference.
SMETS requirement clause
5.7.5.25 — Power Event Log
6 technical records havebeen identified at this reference: 6 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.25 · item PowerEventLog.method: readLog
PowerEventLog - readLog
The response contains all the log entries between fromDateTime and toDateTime inclusive
- Object
PowerEventLog- 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
- ReadsECS35e
0x00B9ESMESRV 6.13
SMETS5.7.5.25 · item PowerEventLog.logEntries[1..100].logEntry.logCode
PowerEventLog - logEntries logEntry logCode
The Alert / Log Code corresponding to this event (as defined in GBCS)
- Object
PowerEventLog- Attribute / method
logEntries[1..100].logEntry.logCode- Interface disposition
- E
- Category
- Operational data
- Section 20 meaning
- The Alert / Log Code corresponding to this event (as defined in GBCS)
Documented touchpoints
- ReadsECS35e
0x00B9ESMESRV 6.13
SMETS5.7.5.25 · item PowerEventLog.logEntries[1..100].logEntry.otherInformation
PowerEventLog - logEntries logEntry otherInformation
Where required by the alert code: other information relating to this alert. See Alert/Log Codes section of the GBCS which details when this is required
- Object
PowerEventLog- Attribute / method
logEntries[1..100].logEntry.otherInformation- Interface disposition
- E
- Category
- Operational data
- Section 20 meaning
- Where required by the alert code: other information relating to this alert. See Alert/Log Codes section of the GBCS which details when this is required
Documented touchpoints
- ReadsECS35e
0x00B9ESMESRV 6.13
SMETS5.7.5.25 · item PowerEventLog.logEntries[1..100].logEntry.timestamp
PowerEventLog - logEntries logEntry timestamp
The UTC date- time stamp of this entry
- Object
PowerEventLog- Attribute / method
logEntries[1..100].logEntry.timestamp- Interface disposition
- E
- Category
- Operational data
- Section 20 meaning
- The UTC date- time stamp of this entry
Documented touchpoints
- ReadsECS35e
0x00B9ESMESRV 6.13
SMETS5.7.5.25 · item PowerEventLog.methodInput: fromDateTime
PowerEventLog - 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
PowerEventLog- 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
- ReadsECS35e
0x00B9ESMESRV 6.13
SMETS5.7.5.25 · item PowerEventLog.methodInput: toDateTime
PowerEventLog - 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
PowerEventLog- 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
- ReadsECS35e
0x00B9ESMESRV 6.13
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.