SMETS requirement clause

5.13.2.6 — Primary Active Tariff Price [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
3

Atomic items

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

3

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.

SMETS5.13.2.6 · item (Primary)ActiveTariffPrice.unit

(Primary)ActiveTariffPrice - unit

SRV touchpoint

Currency units (as determined by CurrencyUnits.value) per unit of energy

Object
(Primary)ActiveTariffPrice
Attribute / method
unit
Interface disposition
E
Category
Operational data
Section 20 meaning
Currency units (as determined by CurrencyUnits.value) per unit of energy

Documented touchpoints

Evidence:source paragraph 1939, 1940Section 20 row 232

SMETS5.13.2.6 · item (Primary)ActiveTariffPrice.scale

(Primary)ActiveTariffPrice - scale

SRV touchpoint

power of 10 to apply when interpreting the value attribute

Object
(Primary)ActiveTariffPrice
Attribute / method
scale
Interface disposition
E
Category
Operational data
Section 20 meaning
power of 10 to apply when interpreting the value attribute

Documented touchpoints

Evidence:source paragraph 1939, 1940Section 20 row 361

SMETS5.13.2.6 · item (Primary)ActiveTariffPrice.value

(Primary)ActiveTariffPrice - value

SRV touchpoint

Number representing the price in currency units of energy consumed

Object
(Primary)ActiveTariffPrice
Attribute / method
value
Interface disposition
E
Category
Operational data
Section 20 meaning
Number representing the price in currency units of energy consumed

Documented touchpoints

Evidence:source paragraph 1939, 1940Section 20 row 99

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.