SMETS requirement clause

4.6.4.23 — Standing Charge

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

Atomic items

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

6

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.23 · item StandingCharge.activateNextDateTime

StandingCharge - 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
StandingCharge
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 684, 685Section 20 row 1143

SMETS4.6.4.23 · item StandingCharge.amountCurrent

StandingCharge - amountCurrent

SRV touchpoint

Charge in currency units per unit time

Object
StandingCharge
Attribute / method
amountCurrent
Interface disposition
E
Category
Operational data
Section 20 meaning
Charge in currency units per unit time

Documented touchpoints

Evidence:source paragraph 684, 685Section 20 row 1439

SMETS4.6.4.23 · item StandingCharge.amountNext

StandingCharge - amountNext

SRV touchpoint

The yet to be activated value

Object
StandingCharge
Attribute / method
amountNext
Interface disposition
E
Category
Configuration data
Section 20 meaning
The yet to be activated value

Documented touchpoints

Evidence:source paragraph 684, 685Section 20 row 1442

SMETS4.6.4.23 · item StandingCharge.numberOfBlockThresholdsInUse

StandingCharge - numberOfBlockThresholdsInUse

SRV touchpoint

Number of block thresholds in use. ZSE requires this as part of the command to set Standing Charge, and so the User needs to provide it. If TOU is in use, the value is 0.

Object
StandingCharge
Attribute / method
numberOfBlockThresholdsInUse
Interface disposition
E
Category
Configuration data
Section 20 meaning
Number of block thresholds in use. ZSE requires this as part of the command to set Standing Charge, and so the User needs to provide it. If TOU is in use, the value is 0.

Documented touchpoints

Evidence:source paragraph 684, 685Section 20 row 1551

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.