Atomic items
Section 20 objects, attributes or methods at this source reference.
SMETS requirement clause
5.7.5.29 — Reactive Export Register
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.
ESMESRV 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.
SMETS5.7.5.29 · item ReactiveExportRegister.value
ReactiveExportRegister - value
- Object
ReactiveExportRegister- Attribute / method
value- Interface disposition
- E
- Category
- Operational data
Documented touchpoints
- ReadsECS17a
0x0026ESMESRV 4.2
SMETS5.7.5.29 · item ReactiveExportRegister.unit
ReactiveExportRegister - unit
VARh
- Object
ReactiveExportRegister- Attribute / method
unit- Interface disposition
- E
- Category
- Constant data
- Section 20 meaning
- VARh
Documented touchpoints
- ReadsECS17a
0x0026ESMESRV 4.2
SMETS5.7.5.29 · item ReactiveExportRegister.scale
ReactiveExportRegister - scale
0 (power of 10 to apply when interpreting the value attribute)
- Object
ReactiveExportRegister- Attribute / method
scale- Interface disposition
- E
- Category
- Constant data
- Section 20 meaning
- 0 (power of 10 to apply when interpreting the value attribute)
Documented touchpoints
- ReadsECS17a
0x0026ESMESRV 4.2
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.