SMETS requirement clause

5.7.4.23 — Low Credit Threshold [INFO]

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.

ESMESRV 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.

SMETS5.7.4.23 · item LowCreditThreshold.thresholdCurrent

LowCreditThreshold - thresholdCurrent

SRV touchpoint

threshold in currency units

Object
LowCreditThreshold
Attribute / method
thresholdCurrent
Interface disposition
E
Category
Configuration data
Section 20 meaning
threshold in currency units

Documented touchpoints

Evidence:source paragraph 1479, 1480Section 20 row 1034

SMETS5.7.4.23 · item LowCreditThreshold.thresholdNext

LowCreditThreshold - thresholdNext

SRV touchpoint

The yet to be activated value

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

Documented touchpoints

Evidence:source paragraph 1479, 1480Section 20 row 1183

SMETS5.7.4.23 · item LowCreditThreshold.activateNextDateTime

LowCreditThreshold - 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
LowCreditThreshold
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 1479, 1480Section 20 row 1221

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.