UK Smart MeteringKnowledge ProjectStructured SRV and specimen referenceBrowse SRVs

SMETS requirement clause

4.6.4.34 — Events Configuration Settings

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.34 · item Events and Alerts Configuration Settings.method: getSettings

Events and Alerts Configuration Settings - getSettings

SRV touchpoint

The response to this method contains the Events and Alerts Configuration Settings.

Object
Events and Alerts Configuration Settings
Attribute / method
method: getSettings
Interface disposition
E
Category
Method
Section 20 meaning
The response to this method contains the Events and Alerts Configuration Settings.

Documented touchpoints

Evidence:source paragraph 710, 711Section 20 row 1940

SMETS4.6.4.34 · item Events and Alerts Configuration Settings.settings

Events and Alerts Configuration Settings - settings

SRV touchpoint

A list of Event / Alert Codes and, for each, a BIT STRING defining the current configuration settings

Object
Events and Alerts Configuration Settings
Attribute / method
settings
Interface disposition
E
Category
Configuration data
Section 20 meaning
A list of Event / Alert Codes and, for each, a BIT STRING defining the current configuration settings

Documented touchpoints

Evidence:source paragraph 710, 711Section 20 row 1941

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.