Service Reference Variant

6.18.1 · Set Maximum Demand Configurable Time Period

Service details

Identifiers, rules, and applicability

Service reference
6.18
Service Reference Variant
6.18.1
DUIS section
3.8.70
Command variants
1, 2, 3
DUIS possible responses
AcknowledgementService Response from Device - GBCSPayloadResponse to a Command for Local Delivery Request - LocalCommand Format
Critical
No
Sensitive response
No
Protection against replay
Yes
On demand
Yes
Future dated
DSP
DSP scheduled
No
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.

ECS371 attribute0x004AESME
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.

Specific Errors

Response codes and descriptions

Response CodeResponse Code Description
E061801
Invalid Start Time - The Start Time is not valid. Start Time minutes must be either 00 or 30.
E061802
Invalid End Time - The End Time is not valid. End Time minutes must be either 00 or 30.

Source: DUIS 3.8.70.3

GBCS Use Case

Use cases, device coverage, and applicability

Use Case / Message Code
ECS370x004A
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
ENOESME

DUIS Service Definition

Data items and DCC processing

Request data items

Table 190: SetMaximumDemandConfigurableTimePeriod (sr:SetMaximumDemandConfigurableTimePeriod) data items
Data ItemDescription / Valid SetTypeMandatoryDefaultUnits
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
MaximumDemandTimePeriodScheduleThe date-time period (maximum of 24 hours) when the Maximum Demand is to be recorded on a daily basis.sr: MaximumDemandTimePeriodScheduleYesNoneN/A
Table 191: MaximumDemandTimePeriodSchedule (sr:MaximumDemandTimePeriodSchedule) data items
Data ItemDescription / Valid SetTypeMandatoryDefaultUnits
StartTimeThe Start time from which the Maximum Demand period begins.xs:timeYesNoneN/A
EndTimeThe End Time at which the Maximum Demand period ends.xs:timeYesNoneN/A

Message Patterns & Examples

Pattern explorer

Open Message Patterns →