Service Reference Variant

4.12.1 · Read Maximum Demand Import Registers

Service details

Identifiers, rules, and applicability

Service reference
4.12
Service Reference Variant
4.12.1
DUIS section
3.8.35
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.

ECS18b4 attributes0x002CESME
SpecificationItemReferenceDescription
SMETSMaximum Demand Configurable Time Period5.7.4.26A single time period of up to 24 hours comprising a number of half-hour periods (commencing at the start of minutes 00 and 30 in each hour) during which recording to the Maximum Demand (Configurable Time) Active Power Import Value(5.7.5.20) is active.
SMETSMaximum Demand Active Power Import Value5.7.5.19A store capable of holding the largest average value of Active Power Import [INFO](5.7.5.4) recorded in any 30 minute period (commencing at the start of minutes 00 and 30 in each hour and including the UTC date and time at the end of the 30 minute period to which the data relates) since the value was last reset (as set out in Section 5.6.3.26), together with the UTC date and time when the value was last reset, arranged such that the recording of a larger value shall cause the previous entry to be overwritten.
SMETSMaximum Demand (Configurable Time) Active Power Import Value5.7.5.20A store capable of holding the largest average value of Active Power Import [INFO](5.7.5.4) recorded in any 30 minute period (commencing at the start of minutes 00 and 30 in each hour) within the time period specified in Maximum Demand Configurable Time Period(5.7.4.26) (including the UTC date and time at the end of the 30 minute period to which the data relates) since the value was last reset (as set out in Section 5.6.3.28), together with the UTC date and time when the value was last reset, arranged such that the recording of a larger value shall cause the previous entry to be overwritten.
SMETSMaximum Demand Active Power Export Value5.7.5.21A store capable of holding the largest average value of the Active Power Export recorded in any 30 minute period (commencing at the start of minutes 00 and 30 in each hour and including the UTC date and time at the end of the 30 minute period to which the data relates) since the value was last reset (as set out in Section 5.6.3.27), together with the UTC date and time when the value was last reset, arranged such that the recording of a larger value shall cause the previous entry to be overwritten.

Specific Errors

Response codes and descriptions

No specific validation is defined for this SRV.

GBCS Use Case

Use cases, device coverage, and applicability

Use Case / Message Code
ECS18b0x002C
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
EISENOESME

DUIS Service Definition

Data items and DCC processing

Request data items

Table 148: ReadMaximumDemandImportRegisters (sr:ReadDataFutureDated) 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

Message Patterns & Examples

Pattern explorer

Open Message Patterns →