Service Reference Variant

4.8.3 · Read Export Profile Data

Service details

Identifiers, rules, and applicability

Service reference
4.8
Service Reference Variant
4.8.3
DUIS section
3.8.31
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 FormatCountersigned SMETS1 Response
Critical
No
Sensitive response
No
Protection against replay
No
On demand
Yes
Future dated
DSP
DSP scheduled
Yes
DCC only
No
SMETS1 applicability
Yes
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.

ECS22a2 attributes0x0036ESME
SpecificationItemReferenceDescription
SMETSProfile Data Log [INFO]5.7.5.27A log capable of storing UTC date and time-stamped half hourly data (the amount of energy Imported or Exported in a half hour period) arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten. The log shall be capable of storing:
SMETSProfile Data Log [INFO]5.13.2.7Profile Data Log [INFO](5.7.5.27) 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
ECS22a0x0036
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
DSP
ResponseESMENot always GBT
SMETS1 Applicable
Yes
Eligible Roles
EESENOMDROUESME

DUIS Service Definition

Data items and DCC processing

Request data items

Table 144: ReadExportProfileData (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 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 145: DSPReadExportProfileData (sr: ReadLogPeriodOffset) data items
Data ItemDescription / Allowable valuesTypeMandatoryDefaultUnits
DSPReadExportProfileDataThe 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 →

SMETS1 Supporting Requirements

Device-model variations and equivalent steps

Review the Section 18 requirements and their applicability across the documented manufacturer, Device Type, model, and firmware profiles.

Open S1SR Requirements →