UK Smart MeteringKnowledge ProjectStructured SRV and specimen referenceBrowse SRVs

SMETS requirement clause

5.7.4.26 — Maximum Demand Configurable Time Period

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.

ESMESRV touchpoint
2

Atomic items

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

4

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.

SMETS5.7.4.26 · item MaximumDemandConfigurableTimePeriod.currentEntries[1..2].scriptSelector

MaximumDemandConfigurableTimePeriod - currentEntries scriptSelector

SRV touchpoint

Determines whether the associated switchTime is the start or the end time of the MaximumDemandConfigurableTimePeriod. scriptSelector has the value of 1 where it relates to the start time and 2 where it relates to the end time.

Object
MaximumDemandConfigurableTimePeriod
Attribute / method
currentEntries[1..2].scriptSelector
Interface disposition
E
Category
Configuration data
Section 20 meaning
Determines whether the associated switchTime is the start or the end time of the MaximumDemandConfigurableTimePeriod. scriptSelector has the value of 1 where it relates to the start time and 2 where it relates to the end time.

Documented touchpoints

Evidence:source paragraph 1485, 1486Section 20 row 748

SMETS5.7.4.26 · item MaximumDemandConfigurableTimePeriod.currentEntries[1..2].switchTime

MaximumDemandConfigurableTimePeriod - currentEntries switchTime

SRV touchpoint

The time during the day at which the action is triggered

Object
MaximumDemandConfigurableTimePeriod
Attribute / method
currentEntries[1..2].switchTime
Interface disposition
E
Category
Configuration data
Section 20 meaning
The time during the day at which the action is triggered

Documented touchpoints

Evidence:source paragraph 1485, 1486Section 20 row 761

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.