UK Smart MeteringKnowledge ProjectStructured SRV and specimen referenceBrowse SRVs

SMETS requirement clause

5.7.5.2 — Active Export Register [INFO]

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
3

Atomic items

Section 20 objects, attributes or methods at this source reference.

3

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.

SMETS5.7.5.2 · item ActiveExportRegister.value

ActiveExportRegister - value

SRV touchpoint

The active energy exported, as measured by the measuring element

Object
ActiveExportRegister
Attribute / method
value
Interface disposition
E
Category
Operational data
Section 20 meaning
The active energy exported, as measured by the measuring element

Documented touchpoints

Evidence:source paragraph 1551, 1552Section 20 row 100

SMETS5.7.5.2 · item ActiveExportRegister.unit

ActiveExportRegister - unit

SRV touchpoint

Wh

Object
ActiveExportRegister
Attribute / method
unit
Interface disposition
E
Category
Constant data
Section 20 meaning
Wh

Documented touchpoints

Evidence:source paragraph 1551, 1552Section 20 row 233

SMETS5.7.5.2 · item ActiveExportRegister.scale

ActiveExportRegister - scale

SRV touchpoint

0 (power of 10 to apply when interpreting the value attribute)

Object
ActiveExportRegister
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

Evidence:source paragraph 1551, 1552Section 20 row 362

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.