UK Smart MeteringKnowledge ProjectStructured SRV and specimen referenceBrowse SRVs

SMETS requirement clause

4.6.4.8 — Debt Recovery per Payment

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.4.8 · item DebtRecoveryperPayment.valueCurrent

DebtRecoveryperPayment - valueCurrent

SRV touchpoint

Integer representing percentage of each payment taken to recover debt. This is a number between 0 and 10,000 ( so, for example, 3000 represents 30% )

Object
DebtRecoveryperPayment
Attribute / method
valueCurrent
Interface disposition
E
Category
Configuration data
Section 20 meaning
Integer representing percentage of each payment taken to recover debt. This is a number between 0 and 10,000 ( so, for example, 3000 represents 30% )

Documented touchpoints

Evidence:source paragraph 648, 649Section 20 row 1151

SMETS4.6.4.8 · item DebtRecoveryperPayment.percentage(ZSE Reading)

DebtRecoveryperPayment - percentage(ZSE Reading)

SRV touchpoint

Use in the ZSE read use case. Integer representing percentage of each payment taken to recover debt. This is a number between 0 and 10,000 ( so, for example, 3000 represents 30% )

Object
DebtRecoveryperPayment
Attribute / method
percentage(ZSE Reading)
Interface disposition
E
Category
Operational data
Section 20 meaning
Use in the ZSE read use case. Integer representing percentage of each payment taken to recover debt. This is a number between 0 and 10,000 ( so, for example, 3000 represents 30% )

Documented touchpoints

Evidence:source paragraph 648, 649Section 20 row 1756

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.