SMETS requirement clause

4.6.4.10 — Debt Recovery Rate Cap

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.

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

SMETS4.6.4.10 · item DebtRecoveryRateCap.amountCurrent

DebtRecoveryRateCap - amountCurrent

SRV touchpoint

The amount of the cap

Object
DebtRecoveryRateCap
Attribute / method
amountCurrent
Interface disposition
E
Category
Configuration data
Section 20 meaning
The amount of the cap

Documented touchpoints

Evidence:source paragraph 652, 653Section 20 row 1035

SMETS4.6.4.10 · item DebtRecoveryRateCap.amountNext

DebtRecoveryRateCap - amountNext

SRV touchpoint

The yet to be activated amount of the cap

Object
DebtRecoveryRateCap
Attribute / method
amountNext
Interface disposition
E
Category
Configuration data
Section 20 meaning
The yet to be activated amount of the cap

Documented touchpoints

Evidence:source paragraph 652, 653Section 20 row 1195

SMETS4.6.4.10 · item DebtRecoveryRateCap.activateAmountNextDateTime

DebtRecoveryRateCap - activateAmountNextDateTime

SRV touchpoint

When the 'amountNext' value is to be activated (see GBCS section 9.2.2)

Object
DebtRecoveryRateCap
Attribute / method
activateAmountNextDateTime
Interface disposition
E
Category
Configuration data
Section 20 meaning
When the 'amountNext' value is to be activated (see GBCS section 9.2.2)

Documented touchpoints

Evidence:source paragraph 652, 653Section 20 row 1213

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.