SMETS requirement clause

4.5.3.21 — Set Payment Mode

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.

4

Documented touchpoints

Typed relationships supported by source mapping rows.

1

Linked SRVs

Unique retained services reached through exact control rows.

0

Linked alerts

Explicit requirement-to-alert references.

SMETS4.5.3.21 · item SuspendDebtDisabled / SuspendDebtEmergency / Payment Mode.valueNext

SuspendDebtDisabled / SuspendDebtEmergency / Payment Mode - valueNext

SRV touchpoint

See SMETS

Object
SuspendDebtDisabled / SuspendDebtEmergency / Payment Mode
Attribute / method
valueNext
Interface disposition
E
Category
Configuration data
Section 20 meaning
See SMETS

Documented touchpoints

Evidence:source paragraph 588, 589Section 20 row 1025

SMETS4.5.3.21 · item SuspendDebtDisabled / SuspendDebtEmergency / Payment Mode.activateNextDateTime

SuspendDebtDisabled / SuspendDebtEmergency / Payment Mode - 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
SuspendDebtDisabled / SuspendDebtEmergency / Payment Mode
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 588, 589Section 20 row 1030

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.