Service Reference Variant

4.6.2 · Retrieve Export Daily Read Log

Service details

Identifiers, rules, and applicability

Service reference
4.6
Service Reference Variant
4.6.2
DUIS section
3.8.28
Command variants
1, 2, 3
DUIS possible responses
AcknowledgementService Response from Device - GBCSPayloadService Response from Device - DSPScheduledMessage FormatResponse to a Command for Local Delivery Request - LocalCommand Format
Critical
No
Sensitive response
No
Protection against replay
No
On demand
Yes
Future dated
DSP
DSP scheduled
Yes
DCC only
No
SMETS1 applicability
No
SAPC requirement
Optional
DUIS applicability
3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3

Cross-specification evidence

SMETS/CHTS to GBCS Mapping

This section shows the SMETS and CHTS attributes that can be read or written by the identified GBCS Use Case. Command requirements are shown separately from the mapped attributes.

ECS21c2 attributes0x0035ESME
SpecificationItemReferenceDescription
SMETSDaily Read Log5.7.5.13A log capable of storing thirty one UTC date and time stamped entries of the Tariff TOU Register Matrix [INFO](5.7.5.34), the Tariff TOU Block Register Matrix(5.7.5.35), the Active Import Register [INFO](5.7.5.3) and the Active Export Register [INFO](5.7.5.2) arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten.
SMETSDaily Read Log5.13.2.4Daily Read Log(5.7.5.13) in Part A shall not apply to ESME.

Specific Errors

Response codes and descriptions

No specific error data is available for this SRV.

GBCS Use Case

Use cases, device coverage, and applicability

Use Case / Message Code
ECS21c0x0035
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
DSP
GBT
No
SMETS1 Applicable
No
Eligible Roles
EESMDRESME

DUIS Service Definition

Data items and DCC processing

Request data items

Table 138: RetrieveExportDailyReadLog (sr:ReadLogFutureDatable) data items
Data ItemDescription / Allowable valuesTypeMandatoryDefaultUnits
ExecutionDateTimeA User shall only add this Data Item to the Service Request where they require the Service Request to be executed at a future date and time. The UTC date and time the User requires the command to be executed on the Device ID Date-time in the future that is either <= current date + 30 days or the date = ‘3000-12-31T00:00:00Z’xs:dateTimeNoNoneUTC Date-Time
ReadLogPeriodThe Start and End Date-Times for which the data is requiredsr:ReadLogPeriod (see clause 3.10.1.14)YesNoneN/A
Table 139: DSPRetrieveExportDailyReadLog (sr:ReadLogPeriodOfffset) data items
Data ItemDescription / Allowable valuesTypeMandatoryDefaultUnits
DSPRetrieveExportDailyReadLogThe Start and End Date Offsets from the current date and the Start and End Times which together define the date-time period for which the data is requiredsr:ReadLogPeriodOffset (See clause 3.10.1.15)YesNoneN/A

DUGIDS service matrix

DUGIDS DS.0226 Table 36 footnote extract

FootnoteExtractColumnCell ValueSource
5Service Request also available to the ‘Old’ Registered Supplier (EES)Eligible User RoleEESDS.0226 Table 36 Service Request Matrix
11Service Request also available to the ‘Old’ Registered Meter Data RetrieverEligible User RoleMDRDS.0226 Table 36 Service Request Matrix

Message Patterns & Examples

Pattern explorer

Open Message Patterns →