SMETS requirement clause

5.7.4.15 — Disablement Threshold [INFO]

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

ESMENo Section 20 bridgeSRV touchpoint
5

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.

SMETS5.7.4.15 · item DisablementThreshold(MeterBalance).thresholdNext

DisablementThreshold(MeterBalance) - thresholdNext

SRV touchpoint

The yet to be activated threshold

Object
DisablementThreshold(MeterBalance)
Attribute / method
thresholdNext
Interface disposition
E
Category
Configuration data
Section 20 meaning
The yet to be activated threshold

Documented touchpoints

Evidence:source paragraph 1463, 1464Section 20 row 1190

SMETS5.7.4.15 · item DisablementThreshold(MeterBalance).activateNextDateTime

DisablementThreshold(MeterBalance) - 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
DisablementThreshold(MeterBalance)
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 1463, 1464Section 20 row 1203

SMETS5.7.4.15 · item DisablementThreshold(MeterBalance).scalerCurrent

DisablementThreshold(MeterBalance) - scalerCurrent

No Section 20 bridge

power of 10 to apply when interpreting the value attribute

Object
DisablementThreshold(MeterBalance)
Attribute / method
scalerCurrent
Interface disposition
E
Category
Configuration data
Section 20 meaning
power of 10 to apply when interpreting the value attribute

No GBCS or SRV bridge is recorded for this item in the current Section 20 mapping. This is an evidence status, not a statement of non-compliance.

Evidence:source paragraph 1463, 1464Section 20 row 1306

SMETS5.7.4.15 · item DisablementThreshold(MeterBalance).ScalerNext

DisablementThreshold(MeterBalance) - ScalerNext

No Section 20 bridge

The yet to be activated scale. Fixed so never shipped

Object
DisablementThreshold(MeterBalance)
Attribute / method
ScalerNext
Interface disposition
N
Category
Configuration data
Section 20 meaning
The yet to be activated scale. Fixed so never shipped

No GBCS or SRV bridge is recorded for this item in the current Section 20 mapping. This is an evidence status, not a statement of non-compliance.

Evidence:source paragraph 1463, 1464Section 20 row 1689

SMETS5.7.4.15 · item DisablementThreshold(MeterBalance).thresholdCurrent

DisablementThreshold(MeterBalance) - thresholdCurrent

SRV touchpoint

Threshold value

Object
DisablementThreshold(MeterBalance)
Attribute / method
thresholdCurrent
Interface disposition
E
Category
Configuration data
Section 20 meaning
Threshold value

Documented touchpoints

Evidence:source paragraph 1463, 1464Section 20 row 864

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.