SMETS requirement clause

5.7.4.13 — Debt Recovery Rate Cap [INFO]

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

Atomic items

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

6

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.13 · 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 1459, 1460Section 20 row 1035

SMETS5.7.4.13 · item DebtRecoveryRateCap.periodCurrent

DebtRecoveryRateCap - periodCurrent

SRV touchpoint

The time period over which the DebtRecoveryRateCap will be applied. The ZSE specification fixes this at 1 week and so it is not a parameter in the command to the GSME / response from it. The DLMS COSEM value is fixed at 604800 seconds (1 week) in alignment with the ZSE constraint. Thus, 1 week shall mean a 7 day by 24 hour period prior to the point at which any calculation is undertaken using the Debt Recovery Rate Cap.

Object
DebtRecoveryRateCap
Attribute / method
periodCurrent
Interface disposition
E (DLMS COSEM) / N (ZSE)
Category
Configuration data
Section 20 meaning
The time period over which the DebtRecoveryRateCap will be applied. The ZSE specification fixes this at 1 week and so it is not a parameter in the command to the GSME / response from it. The DLMS COSEM value is fixed at 604800 seconds (1 week) in alignment with the ZSE constraint. Thus, 1 week shall mean a 7 day by 24 hour period prior to the point at which any calculation is undertaken using the Debt Recovery Rate Cap.

Documented touchpoints

Evidence:source paragraph 1459, 1460Section 20 row 1036

SMETS5.7.4.13 · item DebtRecoveryRateCap.periodNext

DebtRecoveryRateCap - periodNext

SRV touchpoint

The yet to be activated time period over which the DebtRecoveryRateCap will be applied. The ZSE specification fixes this at 1 week and so it is not a parameter in the command to the GSME / response from it. The DLMS COSEM value is fixed at 604800 seconds

Object
DebtRecoveryRateCap
Attribute / method
periodNext
Interface disposition
E (DLMS COSEM) / N (ZSE)
Category
Configuration data
Section 20 meaning
The yet to be activated time period over which the DebtRecoveryRateCap will be applied. The ZSE specification fixes this at 1 week and so it is not a parameter in the command to the GSME / response from it. The DLMS COSEM value is fixed at 604800 seconds

Documented touchpoints

Evidence:source paragraph 1459, 1460Section 20 row 1182

SMETS5.7.4.13 · 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 1459, 1460Section 20 row 1195

SMETS5.7.4.13 · 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 1459, 1460Section 20 row 1213

SMETS5.7.4.13 · item DebtRecoveryRateCap.activatePeriodNextDateTime

DebtRecoveryRateCap - activatePeriodNextDateTime

SRV touchpoint

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

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

Documented touchpoints

Evidence:source paragraph 1459, 1460Section 20 row 1214

SMETS5.7.4.13 · item DebtRecoveryRateCap.amountUnit

DebtRecoveryRateCap - amountUnit

No Section 20 bridge

Determined by CurrencyUnits.value so not in any DebtRecoveryRateCap message

Object
DebtRecoveryRateCap
Attribute / method
amountUnit
Interface disposition
N
Category
Configuration data
Section 20 meaning
Determined by CurrencyUnits.value so not in any DebtRecoveryRateCap message

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 1459, 1460Section 20 row 1286

SMETS5.7.4.13 · item DebtRecoveryRateCap(period).perIodUnit

DebtRecoveryRateCap(period) - perIodUnit

No Section 20 bridge

Always fixed so never explicitly shipped in a message

Object
DebtRecoveryRateCap(period)
Attribute / method
perIodUnit
Interface disposition
N
Category
Configuration data
Section 20 meaning
Always fixed so never explicitly shipped in a message

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 1459, 1460Section 20 row 1288

SMETS5.7.4.13 · item DebtRecoveryRateCap.scaler

DebtRecoveryRateCap - scaler

No Section 20 bridge

Fixed at -5 for GSME and 0 for ESME so not shipped (power of 10 to apply when interpreting the amount attributes)

Object
DebtRecoveryRateCap
Attribute / method
scaler
Interface disposition
N
Category
Configuration data
Section 20 meaning
Fixed at -5 for GSME and 0 for ESME so not shipped (power of 10 to apply when interpreting the amount attributes)

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 1459, 1460Section 20 row 1667

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.