SMETS requirement clause

5.7.4.6 — Average RMS Voltage Measurement Period

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.

6

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.7.4.6 · item (Phase[1])AverageRMSVoltageMeasurementPeriod.value

(Phase[1])AverageRMSVoltageMeasurementPeriod - value

SRV touchpoint

The length of time over which the RMS voltage is averaged.

Object
(Phase[1])AverageRMSVoltageMeasurementPeriod
Attribute / method
value
Interface disposition
E
Category
Configuration data
Section 20 meaning
The length of time over which the RMS voltage is averaged.

Documented touchpoints

Evidence:source paragraph 1444, 1445Section 20 row 1882

SMETS5.7.4.6 · item (Phase[1])AverageRMSVoltageProfileDataLog.measurementPeriod

(Phase[1])AverageRMSVoltageProfileDataLog - measurementPeriod

SRV touchpoint

The time in seconds between each capture in this object. This shall be the same as the period over which the average RMS is averaged

Object
(Phase[1])AverageRMSVoltageProfileDataLog
Attribute / method
measurementPeriod
Interface disposition
E
Category
Configuration data
Section 20 meaning
The time in seconds between each capture in this object. This shall be the same as the period over which the average RMS is averaged

Documented touchpoints

Evidence:source paragraph 1444, 1445Section 20 row 663

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.