Atomic items
Section 20 objects, attributes or methods at this source reference.
CHTS requirement clause
5 technical records havebeen identified at this reference: 4 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.
Section 20 objects, attributes or methods at this source reference.
Typed relationships supported by source mapping rows.
Unique retained services reached through exact control rows.
Explicit requirement-to-alert references.
CHTS4.5.2 · item BillingDataLog(BillingCalendarTriggeredExcExport).logEntries[1..12].logEntry.Block[1..4].RegisterMatrixValue
the register value recorded
BillingDataLog(BillingCalendarTriggeredExcExport)logEntries[1..12].logEntry.Block[1..4].RegisterMatrixValueDocumented touchpoints
0x0076GPFSRV 4.4.30x008BGPFCHTS4.5.2 · item BillingDataLog(BillingCalendarTriggeredExcExport).logEntries[1..12].logEntry.tariffTOU[1..4].RegisterMatrixValue
the register value recorded
BillingDataLog(BillingCalendarTriggeredExcExport)logEntries[1..12].logEntry.tariffTOU[1..4].RegisterMatrixValueDocumented touchpoints
0x0076GPFSRV 4.4.30x008BGPFCHTS4.5.2 · item BillingDataLog(BillingCalendarTriggeredExcExport).logEntries[1..12].logEntry.activeImportRegisterValue/consumption
the register value recorded
BillingDataLog(BillingCalendarTriggeredExcExport)logEntries[1..12].logEntry.activeImportRegisterValue/consumptionDocumented touchpoints
0x008BGPF0x0076GPFSRV 4.4.3CHTS4.5.2 · item BillingDataLog(BillingCalendarTriggeredExcExport).logEntries[1..12].logEntry.timestamp
The UTC date-time at which the corresponding snapshot was taken
BillingDataLog(BillingCalendarTriggeredExcExport)logEntries[1..12].logEntry.timestampDocumented touchpoints
0x008BGPF0x0076GPFSRV 4.4.3CHTS4.5.2 · item clause.4.5.2
This source clause is explicitly referenced by the GBCS device alert table.
Documented touchpoints
How to read this page
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.