SMETS requirement clause

4.6.4.26 — Supply Tamper State

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.

GSMESRV touchpoint
2

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.

SMETS4.6.4.26 · item SupplyTamperState.methodInput: state

SupplyTamperState - state

SRV touchpoint

Set to Locked or Unchanged

Object
SupplyTamperState
Attribute / method
methodInput: state
Interface disposition
E
Category
Method Input
Section 20 meaning
Set to Locked or Unchanged

Documented touchpoints

Evidence:source paragraph 690, 691Section 20 row 1401

SMETS4.6.4.26 · item SupplyTamperState.value

SupplyTamperState - value

SRV touchpoint

Locked(TRUE), Unchanged(FALSE)

Object
SupplyTamperState
Attribute / method
value
Interface disposition
E
Category
Configuration data
Section 20 meaning
Locked(TRUE), Unchanged(FALSE)

Documented touchpoints

Evidence:source paragraph 690, 691Section 20 row 1960

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.