SMETS requirement clause

4.6.4.31 — Tariff Threshold Matrix

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.

GSMESRV touchpoint
3

Atomic items

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

3

Documented touchpoints

Typed relationships supported by source mapping rows.

2

Linked SRVs

Unique retained services reached through exact control rows.

0

Linked alerts

Explicit requirement-to-alert references.

SMETS4.6.4.31 · item TariffThresholdMatrix[1..3].thresholdCurrent

TariffThresholdMatrix[1..3] - thresholdCurrent

SRV touchpoint

The value of the thresholds to switch between tariff blocks

Object
TariffThresholdMatrix[1..3]
Attribute / method
thresholdCurrent
Interface disposition
E
Category
Operational data
Section 20 meaning
The value of the thresholds to switch between tariff blocks

Documented touchpoints

Evidence:source paragraph 704, 705Section 20 row 1363

SMETS4.6.4.31 · item TariffThresholdMatrix[1..3].thresholdNext

TariffThresholdMatrix[1..3] - thresholdNext

SRV touchpoint

The yet to be activated values

Object
TariffThresholdMatrix[1..3]
Attribute / method
thresholdNext
Interface disposition
E
Category
Configuration data
Section 20 meaning
The yet to be activated values

Documented touchpoints

Evidence:source paragraph 704, 705Section 20 row 1364

SMETS4.6.4.31 · item TariffThresholdMatrix.activateNextDateTime

TariffThresholdMatrix - activateNextDateTime

SRV touchpoint

If not high values(0xFF), the date-time at which the corresponding 'Next' parameters shall be used to overwrite the corresponding 'Current' attributes

Object
TariffThresholdMatrix
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

Evidence:source paragraph 704, 705Section 20 row 1430

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.