Atomic items
Section 20 objects, attributes or methods at this source reference.
SMETS requirement clause
5.7.4.9 — Currency Units [INFO]
3 technical records havebeen identified at this reference: 3 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.4.9 · item CurrencyUnit.activateNextDateTime
CurrencyUnit - activateNextDateTime
If not high values(0xFF), the date-time at which the corresponding 'Next' parameters shall be used to overwrite the corresponding 'Current' attributes
- Object
CurrencyUnit- Attribute / method
activateNextDateTime- Interface disposition
- E
- Category
- Configuration data
- Section 20 meaning
- If not high values(0xFF), the date-time at which the corresponding 'Next' parameters shall be used to overwrite the corresponding 'Current' attributes
Documented touchpoints
- ConfiguresECS01a
0x0019ESMESRV 1.1.1
SMETS5.7.4.9 · item CurrencyUnit.valueNext
CurrencyUnit - valueNext
GB Pounds(TRUE), ECB Euro (FALSE)
- Object
CurrencyUnit- Attribute / method
valueNext- Interface disposition
- E
- Category
- Configuration data
- Section 20 meaning
- GB Pounds(TRUE), ECB Euro (FALSE)
Documented touchpoints
- ConfiguresECS01a
0x0019ESMESRV 1.1.1
SMETS5.7.4.9 · item CurrencyUnit.valueCurrent
CurrencyUnit - valueCurrent
GB Pounds(TRUE), ECB Euro (FALSE)
- Object
CurrencyUnit- Attribute / method
valueCurrent- Interface disposition
- E
- Category
- Configuration data
- Section 20 meaning
- GB Pounds(TRUE), ECB Euro (FALSE)
Documented touchpoints
- ReadsECS24
0x003AESMESRV 4.11.1
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.