UK Smart MeteringKnowledge ProjectStructured SRV and specimen referenceBrowse SRVs

Service Reference Variant

7.14 · Read Auxiliary Controller Configuration Data

Service details

Identifiers, rules, and applicability

Service reference
7.14
Service Reference Variant
7.14
DUIS section
3.8.100
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
No
On demand
Yes
Future dated
DSP
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.

ECS61d2 attributes0x011CESME
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.
SMETSAuxiliary Controller [n] Description [INFO]5.7.4.3For each Auxiliary Controller, a description of the type of controlled load connected.

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

DUIS Service Definition

Data items and DCC processing

Request data items

Table 223: .2 : ReadAuxiliaryControllerConfigurationData (sr: ReadAuxiliaryControllerConfigurationData ) data items
Data ItemDescription / 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 Valid Set 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 →