Service Reference Variant

1.1.2 · Update Import Tariff (Secondary Element)

Service details

Identifiers, rules, and applicability

Service reference
1.1
Service Reference Variant
1.1.2
DUIS section
3.8.2
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
Not stated
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.

ECS01c1 command3 attributes0x00B7ESME

Command mapped to ECS01c

SpecificationItemReferenceDescription
SMETSTariff Switching Table [INFO]5.7.4.48A set of rules for allocating half-hourly Consumption to a Tariff Register for Time-of-use Pricing and Time-of-use with Block Pricing. The rules stored within the table shall specify which of 16 Day Profiles should be used to allocate Consumption to Tariff Registers according to:
SMETSSecondary Tariff TOU Price Matrix [INFO]5.13.1.1A 1 x 4 matrix containing Prices for Time-of-use Pricing Tariffs relating to Supply via the secondary measuring element of the Electricity Meter.
SMETSTariff Switching Table [INFO]5.13.1.2Tariff Switching Table(5.7.4.48) in Part A shall not apply to ESME.

Specific Errors

Response codes and descriptions

Response CodeResponse Code Description
E010101
Too many switching rules defined (exceeds 200)

Source: DUIS 3.8.2.3

GBCS Use Case

Use cases, device coverage, and applicability

Use Case / Message Code
ECS01c0x00B7
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Critical
Sensitive Response
No
Future Dated
Device
CommandESMENot always GBT
SMETS1 Applicable
No
Eligible Roles
EISESME

DUIS Service Definition

Data items and DCC processing

Request data items

Table 69: UpdateImportTariffSecondaryElement (sr:TariffSecondaryElement) 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
SwitchingTableA calendar defining UTC times, days and dates for switching the Secondary Element tariffsr:ElecSwitchingTableSecondaryYesNoneN/A
SpecialDaysA calendar defining special dates for switching the Secondary Element tariffsr:ElecSpecialDaysSecondaryYes If there are no Special Days, this XML element will be present, but empty, i.e. it will contain 0 SpecialDay elementsNoneN/A
PriceElementsAll the Data Items required to update the price on the Device are defined in Service Request 1.2.2 Update Price (Secondary Element)sr:PriceSecondaryYesNoneN/A
Table 70: ElectricityTariffSwitchingTable (sr:TariffSwitchingTableSecondaryElement) data items
Data ItemDescription / Allowable valuesTypeMandatoryDefaultUnits
DayProfilesContaining up to 16 DayProfile elementssr:ElecDayProfilesSecondaryYesNoneN/A
WeekProfilesContaining up to 4 WeekProfile elementssr:ElecWeekProfilesYesNoneN/A
SeasonsContaining up to 4 Season elementssr:ElecSeasonsSecondaryYesNoneN/A
Table 71: DayProfiles (sr:ElecDayProfilesSecondary) data items
Data ItemDescription / Allowable valuesTypeMandatoryDefaultUnits
DayProfileA DayProfile definition containing a DayName and ProfileSchedule elements. Can include up to 16 Day Profilessr:ElecDayProfileSecondary (minOccurs = 1 maxOccurs = 16)YesNoneN/A
Table 72: DayProfile (sr:ElecDayProfileSecondary) data items
Data ItemDescription / Allowable valuesTypeMandatoryDefaultUnits
DayNameAn identifier for that day that has a number of ProfileSchedule elements associated with it. Note that this is referenced from the WeekProfile element. The DayName value must begin at 1 and increment by 1 for each subsequent DayName.sr:ElecDayName (Restriction of xs:positiveInteger (minInclusive = 1, maxInclusive = 16))YesNoneN/A
ProfileScheduleArray of up to 48 Actions and Start Times when an action to trigger a tariff switch is to be runsr:ElecProfileScheduleSecondary (minOccurs = 1 maxOccurs = 48)YesNoneN/A
Table 73: ProfileSchedule (sr:ElecProfileScheduleSecondary) data items
Data ItemDescription / Allowable valuesTypeMandatoryDefaultUnits
StartTimeThe time at which the action is to executexs:timeYesNoneN/A
TOUTariffActionIdentifier (n) of the Secondary TOU tariff to be applied (see Table 91)(n between 1 and 4) Valid set: Value between 1 and 4Restriction of xs:nonNegativeInteger (minInclusive = 1, maxInclusive = 4)YesNoneN/A
Table 74: WeekProfiles (sr:ElecWeekProfiles) data items
Data ItemDescription / Allowable valuesTypeMandatoryDefaultUnits
WeekProfileA collection of WeekName and ReferencedDayName elements. Can include up to 4 Week Profilessr:ElecWeekProfile (minOccurs = 1 maxOccurs = 4)YesNoneN/A
Table 75: WeekProfile (sr:ElecWeekProfile) data items
Data ItemDescription / Allowable valuesTypeMandatoryDefaultUnits
WeekNameAn identifier for the week. The WeekName value must begin at 1 and increment by 1 for each subsequent WeekName.sr:ElecWeekName (Restriction of xs:positiveInteger (minInclusive = 1, maxInclusive = 4))YesNoneN/A
ReferencedDayNameDay as defined Note that the attribute index provides an ordering for these elements.sr:ElecReferencedDayName (minOccurs = 7, maxOccurs = 7)YesNoneN/A
Index (Attribute of ReferencedDayName)Provides an ordering for the ReferencedDayName elements. Monday = 1, incrementing by day through to Sunday = 7 Unique and consecutive numbers starting at 1sr:range_1_7 (positiveinteger minInclusive = 1 maxInclusive = 7)YesNoneN/A
Table 76: Seasons (sr: sr:ElecSeasonsSecondary) data items
Data ItemDescription / Allowable valuesTypeMandatoryDefaultUnits
SeasonA single season definition Can include up to 4 Seasonssr:ElecSeasonSecondary (minOccurs = 1 maxOccurs = 4)YesNoneN/A
Table 77: Season (sr:ElecSeasonSecondary) data items
Data ItemDescription / Allowable valuesTypeMandatoryDefaultUnits
SeasonNameAn identifier for the season.Restriction of xs:string (maxLength = 8)YesNoneN/A
SeasonStartDateThe date from which this season is defined to startsr:Date (with wildcards)YesNoneN/A
ReferencedWeekNameWeek name as definedsr:ElecWeekName (Restriction of xs:positiveInteger (minInclusive = 1, maxInclusive = 4))YesNoneN/A
Table 78: SpecialDays (sr:ElecSpecialDaysSecondary) data items
Data ItemDescription / Allowable valuesTypeMandatoryDefaultUnits
SpecialDayA collection of between 0 and 50 Special Days.sr:ElecSpecialDaySecondary (minOccurs = 0 maxOccurs = 50)NoNoneN/A
Table 79: SpecialDay (sr:ElecSpecialDaySecondary) data items
Data ItemDescription / Allowable valuesTypeMandatoryDefaultUnits
DateThe date on which the special day appliessr:Date (with wildcards)YesNoneN/A
ReferencedDayNameDayName as definedsr:ElecDayName (Restriction of xs:positiveInteger (minInclusive = 1, maxInclusive = 16))YesNoneN/A

Message Patterns & Examples

Pattern explorer

Open Message Patterns →