Atomic items
Section 20 objects, attributes or methods at this source reference.
SMETS requirement clause
5.7.5.27 — Profile Data Log [INFO]
16 technical records havebeen identified at this reference: 16 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.27 · item ProfileDataLog(ActiveEnergyImportedInPeriod).logEntries[1..19056].logEntry.primaryValue
ProfileDataLog(ActiveEnergyImportedInPeriod) - logEntries logEntry primaryValue
The total active energy imported in this 30 minute period (if a twin element meter, this is for the primary element; if on a polyphase meter, it is cumulative across the phases)
- Object
ProfileDataLog(ActiveEnergyImportedInPeriod)- Attribute / method
logEntries[1..19056].logEntry.primaryValue- Interface disposition
- E
- Category
- Operational data
- Section 20 meaning
- The total active energy imported in this 30 minute period (if a twin element meter, this is for the primary element; if on a polyphase meter, it is cumulative across the phases)
Documented touchpoints
- ReadsECS22b
0x0037ESMESRV 4.8.1
SMETS5.7.5.27 · item ProfileDataLog(Export).logEntries[1..4464].logEntry.activeEnergyExportedValue
ProfileDataLog(Export) - logEntries logEntry activeEnergyExportedValue
The total active energy exported in this 30 minute period (if a twin element meter, this is for the primary element; if on a polyphase meter, it is cumulative across the phases)
- Object
ProfileDataLog(Export)- Attribute / method
logEntries[1..4464].logEntry.activeEnergyExportedValue- Interface disposition
- E
- Category
- Operational data
- Section 20 meaning
- The total active energy exported in this 30 minute period (if a twin element meter, this is for the primary element; if on a polyphase meter, it is cumulative across the phases)
Documented touchpoints
- ReadsECS22a
0x0036ESMESRV 4.8.3
SMETS5.7.5.27 · item ProfileDataLog(Export).logEntries[1..4464].logEntry.reactiveEnergyExportedValue
ProfileDataLog(Export) - logEntries logEntry reactiveEnergyExportedValue
The total reactive energy exported in this 30 minute period (if a twin element meter, this is for the primary element; if on a polyphase meter, it is cumulative across the phases)
- Object
ProfileDataLog(Export)- Attribute / method
logEntries[1..4464].logEntry.reactiveEnergyExportedValue- Interface disposition
- E
- Category
- Operational data
- Section 20 meaning
- The total reactive energy exported in this 30 minute period (if a twin element meter, this is for the primary element; if on a polyphase meter, it is cumulative across the phases)
Documented touchpoints
- ReadsECS22a
0x0036ESMESRV 4.8.3
SMETS5.7.5.27 · item ProfileDataLog(ReactiveImport).logEntries[1..4464].logEntry.reactiveEnergyImportedValue
ProfileDataLog(ReactiveImport) - logEntries logEntry reactiveEnergyImportedValue
The total reactive energy imported in this 30 minute period (if a twin element meter, this is across the primary and secondary element; if on a polyphase meter, it is cumulative across the phases)
- Object
ProfileDataLog(ReactiveImport)- Attribute / method
logEntries[1..4464].logEntry.reactiveEnergyImportedValue- Interface disposition
- E
- Category
- Operational data
- Section 20 meaning
- The total reactive energy imported in this 30 minute period (if a twin element meter, this is across the primary and secondary element; if on a polyphase meter, it is cumulative across the phases)
Documented touchpoints
- ReadsECS22c
0x0038ESMESRV 4.8.2
SMETS5.7.5.27 · item ProfileDataLog(ActiveEnergyImportedInPeriod).method: readLog
ProfileDataLog(ActiveEnergyImportedInPeriod) - readLog
The response contains all the log entries between fromDateTime and toDateTime inclusive
- Object
ProfileDataLog(ActiveEnergyImportedInPeriod)- 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
- ReadsECS22b
0x0037ESMESRV 4.8.1
SMETS5.7.5.27 · item ProfileDataLog(Export).method: readLog
ProfileDataLog(Export) - readLog
The response contains all the log entries between fromDateTime and toDateTime inclusive
- Object
ProfileDataLog(Export)- 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
- ReadsECS22a
0x0036ESMESRV 4.8.3
SMETS5.7.5.27 · item ProfileDataLog(ReactiveImport).method: readLog
ProfileDataLog(ReactiveImport) - readLog
The response contains all the log entries between fromDateTime and toDateTime inclusive
- Object
ProfileDataLog(ReactiveImport)- 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
- ReadsECS22c
0x0038ESMESRV 4.8.2
SMETS5.7.5.27 · item ProfileDataLog(ActiveEnergyImportedInPeriod).logEntries[1..19056].logEntry.timestamp
ProfileDataLog(ActiveEnergyImportedInPeriod) - logEntries logEntry timestamp
The date-time stamp at the end of the period to which the value relates
- Object
ProfileDataLog(ActiveEnergyImportedInPeriod)- Attribute / method
logEntries[1..19056].logEntry.timestamp- Interface disposition
- E
- Category
- Operational data
- Section 20 meaning
- The date-time stamp at the end of the period to which the value relates
Documented touchpoints
- ReadsECS22b
0x0037ESMESRV 4.8.1
SMETS5.7.5.27 · item ProfileDataLog(Export).logEntries[1..4464].logEntry.timestamp
ProfileDataLog(Export) - logEntries logEntry timestamp
The date-time stamp at the end of the period to which the value relates
- Object
ProfileDataLog(Export)- Attribute / method
logEntries[1..4464].logEntry.timestamp- Interface disposition
- E
- Category
- Operational data
- Section 20 meaning
- The date-time stamp at the end of the period to which the value relates
Documented touchpoints
- ReadsECS22a
0x0036ESMESRV 4.8.3
SMETS5.7.5.27 · item ProfileDataLog(ReactiveImport).logEntries[1..4464].logEntry.timestamp
ProfileDataLog(ReactiveImport) - logEntries logEntry timestamp
The date-time stamp at the end of the period to which the value relates
- Object
ProfileDataLog(ReactiveImport)- Attribute / method
logEntries[1..4464].logEntry.timestamp- Interface disposition
- E
- Category
- Operational data
- Section 20 meaning
- The date-time stamp at the end of the period to which the value relates
Documented touchpoints
- ReadsECS22c
0x0038ESMESRV 4.8.2
SMETS5.7.5.27 · item ProfileDataLog(ActiveEnergyImportedInPeriod).methodInput: fromDateTime
ProfileDataLog(ActiveEnergyImportedInPeriod) - 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
ProfileDataLog(ActiveEnergyImportedInPeriod)- 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
- ReadsECS22b
0x0037ESMESRV 4.8.1
SMETS5.7.5.27 · item ProfileDataLog(Export).methodInput: fromDateTime
ProfileDataLog(Export) - 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
ProfileDataLog(Export)- 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
- ReadsECS22a
0x0036ESMESRV 4.8.3
SMETS5.7.5.27 · item ProfileDataLog(ReactiveImport).methodInput: fromDateTime
ProfileDataLog(ReactiveImport) - 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
ProfileDataLog(ReactiveImport)- 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
- ReadsECS22c
0x0038ESMESRV 4.8.2
SMETS5.7.5.27 · item ProfileDataLog(ActiveEnergyImportedInPeriod).methodInput: toDateTime
ProfileDataLog(ActiveEnergyImportedInPeriod) - 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.
- Object
ProfileDataLog(ActiveEnergyImportedInPeriod)- 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
- ReadsECS22b
0x0037ESMESRV 4.8.1
SMETS5.7.5.27 · item ProfileDataLog(Export).methodInput: toDateTime
ProfileDataLog(Export) - 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
ProfileDataLog(Export)- 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
- ReadsECS22a
0x0036ESMESRV 4.8.3
SMETS5.7.5.27 · item ProfileDataLog(ReactiveImport).methodInput: toDateTime
ProfileDataLog(ReactiveImport) - 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
ProfileDataLog(ReactiveImport)- 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
- ReadsECS22c
0x0038ESMESRV 4.8.2
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.