SMETS requirement clause

4.6.4.6 — Currency Units

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

Atomic items

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

3

Documented touchpoints

Typed relationships supported by source mapping rows.

3

Linked SRVs

Unique retained services reached through exact control rows.

0

Linked alerts

Explicit requirement-to-alert references.

SMETS4.6.4.6 · item CurrencyUnit.valueNext

CurrencyUnit - valueNext

SRV touchpoint

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

Evidence:source paragraph 644, 645Section 20 row 18

SMETS4.6.4.6 · item CurrencyUnit.valueCurrent

CurrencyUnit - valueCurrent

SRV touchpoint

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

Evidence:source paragraph 644, 645Section 20 row 19

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.