SMETS requirement clause

5.7.5.6 — Auxiliary Controller Event Log

7 technical records havebeen identified at this reference: 7 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
7

Atomic items

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

7

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.

SMETS5.7.5.6 · item AuxiliaryControllerEventLog.logEntries[1..100].logEntry.outcome

AuxiliaryControllerEventLog - logEntries logEntry outcome

SRV touchpoint

0x00 (Outcome not known), 0x01 (Success), 0x02 (Failure). 'Outcome not known' shall only be used where this entry relates to a Command being sent to an HCALCS (and so the sending Device cannot know the outcome)

Object
AuxiliaryControllerEventLog
Attribute / method
logEntries[1..100].logEntry.outcome
Interface disposition
E
Category
Operational data
Section 20 meaning
0x00 (Outcome not known), 0x01 (Success), 0x02 (Failure). 'Outcome not known' shall only be used where this entry relates to a Command being sent to an HCALCS (and so the sending Device cannot know the outcome)

Documented touchpoints

Evidence:source paragraph 1559, 1560Section 20 row 1827

SMETS5.7.5.6 · item AuxiliaryControllerEventLog.logEntries[1..100].logEntry.HANCommandID

AuxiliaryControllerEventLog - logEntries logEntry HANCommandID

SRV touchpoint

0x00000000, if this entry relates to an ALCS or APC. For entries related to an HCALCS, an identifier, allocated by the sending Device, for the Command / Response between the sending Device and HC ALCS

Object
AuxiliaryControllerEventLog
Attribute / method
logEntries[1..100].logEntry.HANCommandID
Interface disposition
E
Category
Operational data
Section 20 meaning
0x00000000, if this entry relates to an ALCS or APC. For entries related to an HCALCS, an identifier, allocated by the sending Device, for the Command / Response between the sending Device and HC ALCS

Documented touchpoints

Evidence:source paragraph 1559, 1560Section 20 row 1828

SMETS5.7.5.6 · item AuxiliaryControllerEventLog.logEntries[1..100].logEntry.switchNumberAndAction

AuxiliaryControllerEventLog - logEntries logEntry switchNumberAndAction

SRV touchpoint

See GBCS Section 7.3.6.1 and Section 18.1.1.1

Object
AuxiliaryControllerEventLog
Attribute / method
logEntries[1..100].logEntry.switchNumberAndAction
Interface disposition
E
Category
Operational data
Section 20 meaning
See GBCS Section 7.3.6.1 and Section 18.1.1.1

Documented touchpoints

Evidence:source paragraph 1559, 1560Section 20 row 565

SMETS5.7.5.6 · item AuxiliaryControllerEventLog.method: readLog

AuxiliaryControllerEventLog - readLog

SRV touchpoint

The response contains all the log entries between fromDateTime and toDateTime inclusive

Object
AuxiliaryControllerEventLog
Attribute / method
method: readLog
Interface disposition
E
Category
Method
Section 20 meaning
The response contains all the log entries between fromDateTime and toDateTime inclusive

Documented touchpoints

Evidence:source paragraph 1559, 1560Section 20 row 580

SMETS5.7.5.6 · item AuxiliaryControllerEventLog.logEntries[1..100].logEntry.timestamp

AuxiliaryControllerEventLog - logEntries logEntry timestamp

SRV touchpoint

The UTC date- time stamp of this entry

Object
AuxiliaryControllerEventLog
Attribute / method
logEntries[1..100].logEntry.timestamp
Interface disposition
E
Category
Operational data
Section 20 meaning
The UTC date- time stamp of this entry

Documented touchpoints

Evidence:source paragraph 1559, 1560Section 20 row 603

SMETS5.7.5.6 · item AuxiliaryControllerEventLog.methodInput: fromDateTime

AuxiliaryControllerEventLog - fromDateTime

SRV touchpoint

If the Start of Time as per GBCS section 9.1.6, response contains all entries from the oldest in the log to 'toDateTime'. If not the Start of Time, response contains all entries between fromDateTime and toDateTime inclusive

Object
AuxiliaryControllerEventLog
Attribute / method
methodInput: fromDateTime
Interface disposition
E
Category
Method Input
Section 20 meaning
If the Start of Time as per GBCS section 9.1.6, response contains all entries from the oldest in the log to 'toDateTime'. If not the Start of Time, response contains all entries between fromDateTime and toDateTime inclusive

Documented touchpoints

Evidence:source paragraph 1559, 1560Section 20 row 634

SMETS5.7.5.6 · item AuxiliaryControllerEventLog.methodInput: toDateTime

AuxiliaryControllerEventLog - toDateTime

SRV touchpoint

If the End of Time as per GBCS section 9.1.6, response contains all entries from 'fromDateTime' in the log to the newest. If not the End of Time, response contains all entries between fromDateTime and toDateTime inclusive

Object
AuxiliaryControllerEventLog
Attribute / method
methodInput: toDateTime
Interface disposition
E
Category
Method Input
Section 20 meaning
If the End of Time as per GBCS section 9.1.6, response contains all entries from 'fromDateTime' in the log to the newest. If not the End of Time, response contains all entries between fromDateTime and toDateTime inclusive

Documented touchpoints

Evidence:source paragraph 1559, 1560Section 20 row 655

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.