UK Smart MeteringKnowledge ProjectStructured SRV and specimen referenceBrowse SRVs

SMETS requirement clause

5.7.4.42 — Standing Charge [INFO]

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

Atomic items

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

9

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.

SMETS5.7.4.42 · item StandingCharge.valueCurrent.price_scale

StandingCharge - valueCurrent price scale

SRV touchpoint

power of 10 to apply when interpreting the charge_per_unit value

Object
StandingCharge
Attribute / method
valueCurrent.price_scale
Interface disposition
E
Category
Configuration data
Section 20 meaning
power of 10 to apply when interpreting the charge_per_unit value

Documented touchpoints

Evidence:source paragraph 1523, 1524Section 20 row 1067

SMETS5.7.4.42 · item StandingCharge.valueCurrent.charge_per_unit

StandingCharge - valueCurrent charge per unit

SRV touchpoint

charge per unit

Object
StandingCharge
Attribute / method
valueCurrent.charge_per_unit
Interface disposition
E
Category
Configuration data
Section 20 meaning
charge per unit

Documented touchpoints

Evidence:source paragraph 1523, 1524Section 20 row 1073

SMETS5.7.4.42 · item StandingCharge.valueCurrent.classID

StandingCharge - valueCurrent classID

SRV touchpoint

class ID of the Commodity Reference Object

Object
StandingCharge
Attribute / method
valueCurrent.classID
Interface disposition
E
Category
Configuration data
Section 20 meaning
class ID of the Commodity Reference Object

Documented touchpoints

Evidence:source paragraph 1523, 1524Section 20 row 1079

SMETS5.7.4.42 · item StandingCharge.valueNext.price_scale

StandingCharge - valueNext price scale

SRV touchpoint

power of 10 to apply when interpreting the charge_per_unit value

Object
StandingCharge
Attribute / method
valueNext.price_scale
Interface disposition
E
Category
Configuration data
Section 20 meaning
power of 10 to apply when interpreting the charge_per_unit value

Documented touchpoints

Evidence:source paragraph 1523, 1524Section 20 row 1113

SMETS5.7.4.42 · item StandingCharge.valueNext.charge_per_unit

StandingCharge - valueNext charge per unit

SRV touchpoint

charge per unit

Object
StandingCharge
Attribute / method
valueNext.charge_per_unit
Interface disposition
E
Category
Configuration data
Section 20 meaning
charge per unit

Documented touchpoints

Evidence:source paragraph 1523, 1524Section 20 row 1119

SMETS5.7.4.42 · 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 1523, 1524Section 20 row 1143

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.