SMETS requirement clause

4.6.5.8 — Emergency Credit Balance

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.

GSMESRV touchpoint
2

Atomic items

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

2

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.

SMETS4.6.5.8 · item EmergencyCreditBalance.value

EmergencyCreditBalance - value

SRV touchpoint

amount of emergency credit remaining

Object
EmergencyCreditBalance
Attribute / method
value
Interface disposition
E
Category
Operational data
Section 20 meaning
amount of emergency credit remaining

Documented touchpoints

Evidence:source paragraph 737, 738Section 20 row 1040

SMETS4.6.5.8 · item EmergencyCredit.method: select

EmergencyCredit - select

SRV touchpoint

Activate emergency credit if emergency credit can be activated.

Object
EmergencyCredit
Attribute / method
method: select
Interface disposition
E
Category
Method
Section 20 meaning
Activate emergency credit if emergency credit can be activated.

Documented touchpoints

Evidence:source paragraph 737, 738Section 20 row 1050

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.