SMETS requirement clause

4.5.3.20 — Set Clock

6 technical records havebeen identified at this reference: 5 Section 20 items and 1 explicit clause reference. The links below describe documented interfaces and observable effects; they do not assert compliance with the source requirement.

GSMEAlert touchpoint onlyNo Section 20 bridge
5

Atomic items

Section 20 objects, attributes or methods at this source reference.

2

Documented touchpoints

Typed relationships supported by source mapping rows.

0

Linked SRVs

Unique retained services reached through exact control rows.

2

Linked alerts

Explicit requirement-to-alert references.

SMETS4.5.3.20 · item Time.methodOutput: value

Time - value

No Section 20 bridge

The UTC date time

Object
Time
Attribute / method
methodOutput: value
Interface disposition
E
Category
Operational data
Section 20 meaning
The UTC date time

No GBCS or SRV bridge is recorded for this item in the current Section 20 mapping. This is an evidence status, not a statement of non-compliance.

Evidence:source paragraph 582, 583Section 20 row 675

SMETS4.5.3.20 · item Time.methodOutput: status

Time - status

No Section 20 bridge

May be one of three values: Invalid, Unreliable, Reliable

Object
Time
Attribute / method
methodOutput: status
Interface disposition
E
Category
Operational data
Section 20 meaning
May be one of three values: Invalid, Unreliable, Reliable

No GBCS or SRV bridge is recorded for this item in the current Section 20 mapping. This is an evidence status, not a statement of non-compliance.

Evidence:source paragraph 582, 583Section 20 row 676

SMETS4.5.3.20 · item Time.methodInput: timeRangeEnd

Time - timeRangeEnd

No Section 20 bridge

date-time of the end of the range, as an input parameter to Time.setValidTimeRange

Object
Time
Attribute / method
methodInput: timeRangeEnd
Interface disposition
E
Category
Method Input
Section 20 meaning
date-time of the end of the range, as an input parameter to Time.setValidTimeRange

No GBCS or SRV bridge is recorded for this item in the current Section 20 mapping. This is an evidence status, not a statement of non-compliance.

Evidence:source paragraph 582, 583Section 20 row 683

SMETS4.5.3.20 · item Time.methodInput: timeRangeStart

Time - timeRangeStart

No Section 20 bridge

date-time of the start of the range, as an input parameter to Time.setValidTimeRange

Object
Time
Attribute / method
methodInput: timeRangeStart
Interface disposition
E
Category
Method Input
Section 20 meaning
date-time of the start of the range, as an input parameter to Time.setValidTimeRange

No GBCS or SRV bridge is recorded for this item in the current Section 20 mapping. This is an evidence status, not a statement of non-compliance.

Evidence:source paragraph 582, 583Section 20 row 684

SMETS4.5.3.20 · item Time.method: setValidTimeRange

Time - setValidTimeRange

No Section 20 bridge

To set the date-time range in which the ESME shall adjust its time to the Comms Hub time if the Comms Hub time is within the date-time range

Object
Time
Attribute / method
method: setValidTimeRange
Interface disposition
E
Category
Method
Section 20 meaning
To set the date-time range in which the ESME shall adjust its time to the Comms Hub time if the Comms Hub time is within the date-time range

No GBCS or SRV bridge is recorded for this item in the current Section 20 mapping. This is an evidence status, not a statement of non-compliance.

Evidence:source paragraph 582, 583Section 20 row 685

SMETS4.5.3.20 · item clause.4.5.3.20

Set Clock

Alert touchpoint only

This source clause is explicitly referenced by the GBCS device alert table.

Category
Alert reference

Documented touchpoints

  • Alert touchpointGSME0x81C6Clock not adjusted (outside tolerance)
  • Alert touchpointGSME0x8145Clock adjusted (within tolerance)
Evidence:source paragraph 582, 583

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.