SMETS requirement clause

5.7.5.7 — Average RMS Over Voltage Counter

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.

6

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.7 · item (Phase[1])AverageRMSOverVoltageCounter.unit

(Phase[1])AverageRMSOverVoltageCounter - unit

SRV touchpoint

No units

Object
(Phase[1])AverageRMSOverVoltageCounter
Attribute / method
unit
Interface disposition
I
Category
Operational data
Section 20 meaning
No units

Documented touchpoints

Evidence:source paragraph 1561, 1562Section 20 row 226

SMETS5.7.5.7 · item (Phase[1])AverageRMSOverVoltageCounter.scale

(Phase[1])AverageRMSOverVoltageCounter - scale

SRV touchpoint

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

Object
(Phase[1])AverageRMSOverVoltageCounter
Attribute / method
scale
Interface disposition
E
Category
Operational data
Section 20 meaning
0 (power of 10 to apply when interpreting the value attribute)

Documented touchpoints

Evidence:source paragraph 1561, 1562Section 20 row 355

SMETS5.7.5.7 · item (Phase[1])AverageRMSOverVoltageCounter.value

(Phase[1])AverageRMSOverVoltageCounter - value

SRV touchpoint

The count since last reset

Object
(Phase[1])AverageRMSOverVoltageCounter
Attribute / method
value
Interface disposition
E
Category
Operational data
Section 20 meaning
The count since last reset

Documented touchpoints

Evidence:source paragraph 1561, 1562Section 20 row 93

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.