UK Smart MeteringKnowledge ProjectStructured SRV and specimen referenceBrowse SRVs

Service Reference Variant

6.14.3 · Update Device Configuration (Auxiliary Controller Scheduler)

Service details

Identifiers, rules, and applicability

Service reference
6.14
Service Reference Variant
6.14.3
DUIS section
3.8.66
Command variants
4, 5, 6, 7
DUIS possible responses
AcknowledgementResponse to Transform Request - PreCommand FormatService Response from Device - GBCSPayloadFutureDatedDeviceAlertMessageResponse to a Command for Local Delivery Request - LocalCommand Format
Critical
Yes
Sensitive response
No
Protection against replay
Yes
On demand
Yes
Future dated
Device
DSP scheduled
No
DCC only
No
SMETS1 applicability
No
SAPC requirement
Mandatory
DUIS applicability
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.

ECS46d1 attribute0x011AESME
SpecificationItemReferenceDescription
SMETSAuxiliary Controller Calendar [INFO]5.7.4.2A Switching Table containing a set of rules for setting the commanded state of up to five Auxiliary Controllers.

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
ECS46d0x011A
DUIS Applicability
v4.0 – v5.3
GBCS Applicability
v4.0 – v4.3
GBCS Criticality
Critical
Sensitive Response
No
Future Dated
Device
GBT
No
SMETS1 Applicable
No
Eligible Roles
EISESME

DUIS Service Definition

Data items and DCC processing

Request data items

Table 183: .1 : UpdateDeviceConfigurationAuxiliaryControllerScheduler (sr: UpdateDeviceConfigurationAuxiliaryControllerScheduler) 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
AuxiliaryControllerSchedulesee table 183.2sr:AuxiliaryControllerSchedule (minOccurs = 0 maxOccurs = 120)YesNoneN/A
AuxiliaryControllerSpecialDayDefinitionssee table 183.4sr: AuxiliaryControllerSpecialDayDefinitionsYes If Users do not wish to include any special days, this XML element should be present, but empty.NoneN/A
Table 183: .2 : AuxiliaryControllerSchedule (sr: AuxiliaryControllerSchedule) data items
Data ItemDescription / Valid SetTypeMandatoryDefaultUnits
AuxiliaryControllerActionsee table 183.3sr: AuxiliaryControllerActionYesNoneN/A
SpecialDaysApplicabilityeach occurence identifies, via the value of the identifier, a special day definition to which the schedule appliesN/A minOccurs = 0 maxOccurs = 20NoNoneN/A
identifier (attribute of SpecialDaysApplicability)identifies the AuxiliaryControllerSpecialDayDefinitionsr:range_1_20 (xs:positiveInteger minInclusive 1 maxInclusive 20)Yes (attribute)NoneN/A
DaysOfWeekApplicabilitySee Table 105sr:DaysOfWeekApplicabilityNoNoneN/A
AuxiliaryControllerSchedulePeriodAndTimeThe schedule execution time and date range (with wildcards).sr:ScheduleDatesAndTime See 3.10.1.19YesNoneN/A
Table 183: .3 : AuxiliaryControllerAction (sr: AuxiliaryControllerAction) data items
Data ItemDescription / Valid SetTypeMandatoryDefaultUnits
auxiliaryControllerN (attribute of AuxiliaryControllerAction)The value [n] for the Auxiliary Controller[n] with its SMETS meaning. The identifier associated with the Auxiliary Controller.sr:range_1_5 (xs:positiveInteger minInclusive 1 maxInclusive 5)Yes (attribute)NoneN/A
CommandedStateLevelAn integer indicating the required state of the Auxiliary Controller. Where the Auxiliary Controller is an APC, the number reflects the percentage to which its commanded state level is to be set. Where the Auxiliary Controller is an ALCS or HCALCS, 100 shall be interpreted by the Device as meaning closure of the switch (allowing energy to flow) and any other number shall be interpreted as meaning opening of the switch (not allowing energy to flow).sr:AuxiliaryControllerLevel ( xs:unsignedShort minInclusive = 0, maxInclusive = 100)YesNoneN/A
InputFromControlledLoadThis element is only relevant to an APC, and will be ignored by the Device where the Auxiliary Controller is not an APC. If present, this element specifies that the direction of energy flow in the CommandedStateLevel of the APC shall relate to the input of energy from the controlled load. If not present, then the CommandedStateLevel shall relate to the output of energy to the controlled load.sr:NoTypeNoNoneN/A
Table 183: .4 : AuxiliaryControllerSpecialDayDefinitions (sr: AuxiliaryControllerSpecialDayDefinitions) data items
Data ItemDescription / Valid SetTypeMandatoryDefaultUnits
AuxiliaryControllerSpecialDayDefinitionspecial day date with wildcards allowedsr:Date (minOccurs = 0 maxOccurs = 20)NoNoneN/A
identifier (attribute of AuxiliaryControllerSpecialDayDefinition)identifies each AuxiliaryControllerSpecialDayDefinition Unique and consecutive starting at 1sr:range_1_20 (xs:positiveInteger minInclusive 1 maxInclusive 20)No (attribute)NoneN/A

Additional System Processing - DUIS

When the DCC receives a Response indicating Success from an UpdateDeviceConfiguration (AuxiliaryControllerScheduler) command, the DCC shall send a DCC Alert N58 to the Registered Network Operator for that Device.

Message Patterns & Examples

Pattern explorer

Open Message Patterns →