Atomic items
Section 20 objects, attributes or methods at this source reference.
SMETS requirement clause
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.
Section 20 objects, attributes or methods at this source reference.
Typed relationships supported by source mapping rows.
Unique retained services reached through exact control rows.
Explicit requirement-to-alert references.
SMETS5.7.4.27 · item PrepaymentCredit(MaxMeterBalance).valueCurrent
The largest value that a credit could take MeterBalance.value to and still be accepted
PrepaymentCredit(MaxMeterBalance)valueCurrentDocumented touchpoints
0x003BESMESRV 4.13SMETS5.7.4.27 · item PrepaymentCredit(MaxMeterBalance).valueNext
The largest value that a credit could take MeterBalance.value to and still be accepted
PrepaymentCredit(MaxMeterBalance)valueNextDocumented touchpoints
0x00DEESMESRV 2.1SMETS5.7.4.27 · item PrepaymentCredit(MaxMeterBalance).activateNextDateTime
If not high values(0xFF), the date-time at which the corresponding 'Next' parameters shall be used to overwrite the corresponding 'Current' attributes
PrepaymentCredit(MaxMeterBalance)activateNextDateTimeDocumented touchpoints
0x00DEESMESRV 2.1How to read this page
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.