Atomic items
Section 20 objects, attributes or methods at this source reference.
SMETS requirement clause
4.6.5.11 — Meter Balance
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
Documented touchpoints
Typed relationships supported by source mapping rows.
Linked SRVs
Unique retained services reached through exact control rows.
Linked alerts
Explicit requirement-to-alert references.
SMETS4.6.5.11 · item MeterBalance.value
MeterBalance - value
For ESME: if positive, credit available; if negative, money due For GSME: if positive, money due; cannot be negative
- Object
MeterBalance- Attribute / method
value- Interface disposition
- E
- Category
- Operational data
- Section 20 meaning
- For ESME: if positive, credit available; if negative, money due For GSME: if positive, money due; cannot be negative
Documented touchpoints
- ReadsGCS60a
0x012AGSMESRV 4.18
SMETS4.6.5.11 · item MeterBalance.valuePrepaymentMode
MeterBalance - valuePrepaymentMode
For GSME: if positive, credit available; if negative, money due
- Object
MeterBalance- Attribute / method
valuePrepaymentMode- Interface disposition
- E
- Category
- Operational data
- Section 20 meaning
- For GSME: if positive, credit available; if negative, money due
Documented touchpoints
- ReadsGCS60a
0x012AGSMESRV 4.18
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.