SMETS requirement clause

5.7.5.28 — Randomised Offset

1 technical record hasbeen identified at this reference: 1 Section 20 item 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
1

Atomic items

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

1

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.28 · item RandomisedOffset.value

RandomisedOffset - value

SRV touchpoint

RandomisedOffsetNumber.value * RandomisedOffsetLimit * (10 to the power -4) rounded to the nearest integer number of seconds

Object
RandomisedOffset
Attribute / method
value
Interface disposition
E
Category
Operational data
Section 20 meaning
RandomisedOffsetNumber.value * RandomisedOffsetLimit * (10 to the power -4) rounded to the nearest integer number of seconds

Documented touchpoints

Evidence:source paragraph 1616, 1617Section 20 row 65

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.