UK Smart MeteringKnowledge ProjectStructured SRV and specimen referenceBrowse SRVs

SMETS requirement clause

4.6.4.4 — Contact Details

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.

1

Linked SRVs

Unique retained services reached through exact control rows.

0

Linked alerts

Explicit requirement-to-alert references.

SMETS4.6.4.4 · item ContactDetails.supplierTelephoneNumber

ContactDetails - supplierTelephoneNumber

SRV touchpoint

Octet string of the telephone number

Object
ContactDetails
Attribute / method
supplierTelephoneNumber
Interface disposition
E
Category
Configuration data
Section 20 meaning
Octet string of the telephone number

Documented touchpoints

Evidence:source paragraph 640, 641Section 20 row 1197

SMETS4.6.4.4 · item ContactDetails.supplierName

ContactDetails - supplierName

SRV touchpoint

The Supplier name. This is the same value that is updated by UpdateSecurityCredentials on change of Supplier

Object
ContactDetails
Attribute / method
supplierName
Interface disposition
E
Category
Configuration data
Section 20 meaning
The Supplier name. This is the same value that is updated by UpdateSecurityCredentials on change of Supplier

Documented touchpoints

Evidence:source paragraph 640, 641Section 20 row 1251

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.