SMETS requirement clause

5.7.4.33 — Randomised Offset Limit

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.

2

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.33 · item RandomisedOffsetLimit.value

RandomisedOffsetLimit - value

SRV touchpoint

Integer between 0 and 1799

Object
RandomisedOffsetLimit
Attribute / method
value
Interface disposition
E
Category
Configuration data
Section 20 meaning
Integer between 0 and 1799

Documented touchpoints

Evidence:source paragraph 1505, 1506Section 20 row 66

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.