SMETS requirement clause

5.6.3.22 — Reset Average RMS Over Voltage Counter

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.

ESMESRV touchpoint
2

Atomic items

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

4

Documented touchpoints

Typed relationships supported by source mapping rows.

2

Linked SRVs

Unique retained services reached through exact control rows.

0

Linked alerts

Explicit requirement-to-alert references.

SMETS5.6.3.22 · item (Phase[1])AverageRMSOverVoltageCounter.method: reset

(Phase[1])AverageRMSOverVoltageCounter - reset

SRV touchpoint

Reset (Phase[1])AverageRMSOverVoltageCounter

Object
(Phase[1])AverageRMSOverVoltageCounter
Attribute / method
method: reset
Interface disposition
E
Category
Method
Section 20 meaning
Reset (Phase[1])AverageRMSOverVoltageCounter

Documented touchpoints

Evidence:source paragraph 1331, 1332Section 20 row 1899

SMETS5.6.3.22 · item (Phase[1])AverageRMSOverVoltageCounter.method: reset

(Phase[1])AverageRMSOverVoltageCounter - reset

SRV touchpoint

set AverageRMSOverVoltageCounter.value to zero

Object
(Phase[1])AverageRMSOverVoltageCounter
Attribute / method
method: reset
Interface disposition
E
Category
Method
Section 20 meaning
set AverageRMSOverVoltageCounter.value to zero

Documented touchpoints

Evidence:source paragraph 1331, 1332Section 20 row 494

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.