SMETS requirement clause

5.7.4.28 — Meter Point Administration Numbers (MPAN) [INFO]

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.

4

Documented touchpoints

Typed relationships supported by source mapping rows.

3

Linked SRVs

Unique retained services reached through exact control rows.

0

Linked alerts

Explicit requirement-to-alert references.

SMETS5.7.4.28 · item MeterPointAdministrationNumber(combinedMPANS).value

MeterPointAdministrationNumber(combinedMPANS) - value

SRV touchpoint

Primary and secondary MPAN.

Object
MeterPointAdministrationNumber(combinedMPANS)
Attribute / method
value
Interface disposition
E
Category
Configuration data
Section 20 meaning
Primary and secondary MPAN.

Documented touchpoints

Evidence:source paragraph 1489, 1490Section 20 row 76

SMETS5.7.4.28 · item MeterPointAdministrationNumber(ExportMPAN).value

MeterPointAdministrationNumber(ExportMPAN) - value

SRV touchpoint

The MPAN associated with Export Consumption

Object
MeterPointAdministrationNumber(ExportMPAN)
Attribute / method
value
Interface disposition
E
Category
Configuration data
Section 20 meaning
The MPAN associated with Export Consumption

Documented touchpoints

Evidence:source paragraph 1489, 1490Section 20 row 77

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.