Service Reference Variant

6.8 · Update Device Configuration (Billing Calendar)

Service details

Identifiers, rules, and applicability

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

ECS30a1 attribute0x00D7ESME
SpecificationItemReferenceDescription
SMETSBilling Calendar5.7.4.7A calendar defining billing dates for the storage of billing related information in the Billing Data Log(5.7.5.10).
GCS251 attribute0x007EGSME
SpecificationItemReferenceDescription
SMETSBilling Calendar4.6.4.2A calendar defining billing dates for the storage of billing related information in the Billing Data Log(4.6.5.3).
GCS25a1 attribute0x00D8GSME
SpecificationItemReferenceDescription
SMETSBilling Calendar4.6.4.2A calendar defining billing dates for the storage of billing related information in the Billing Data Log(4.6.5.3).

Specific Errors

Response codes and descriptions

Response CodeResponse Code Description
E060801
The Service Request is not valid for the Device Type where the Billing Calendar is to be configured. • Electricity Smart Meter. The Service Request includes the ElectricityBillingCalendar data item • Gas Smart Meter. The Service Request includes the GasBillingCalendar data item
E060802
The Service Request Gas Billing Period Start Date day of the month is 29, 30 or 31 which is not valid
E060803
The GBCS version that pertains to the Device Model recorded in the SMI for this Device doesn’t support the requested Billing Calendar periodicity

Source: DUIS 3.8.60.3

GBCS Use Case

Use cases, device coverage, and applicability

Use Case / Message Code
ECS300x0046
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v1.1
GBCS Criticality
Critical
Sensitive Response
No
Future Dated
No
GBT
No
SMETS1 Applicable
No
Eligible Roles
EISESME
Use Case / Message Code
ECS30a0x00D7
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v2.0 – v4.3
GBCS Criticality
Critical
Sensitive Response
No
Future Dated
No
GBT
No
SMETS1 Applicable
Yes
Eligible Roles
EISESME
Use Case / Message Code
GCS250x007E
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v1.1
GBCS Criticality
Critical
Sensitive Response
No
Future Dated
No
GBT
No
SMETS1 Applicable
No
Eligible Roles
GISGSME
Use Case / Message Code
GCS25a0x00D8
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v2.0 – v4.3
GBCS Criticality
Critical
Sensitive Response
No
Future Dated
No
GBT
No
SMETS1 Applicable
Yes
Eligible Roles
GISGSME

DUIS Service Definition

Data items and DCC processing

Request data items

Table 171: UpdateDeviceConfigurationBillingCalendar (sr:BillingCalendar) data items
Data ItemDescription / Valid SetTypeMandatoryDefaultUnits
ElectricityBillingCalendarIndicates that the Billing Calendar to be configured is that of an Electricity Smart Metersr:ElectricityBillingCalendarTarget Device Type = ESME: Yes Otherwise: N/ANoneN/A
GasBillingCalendarIndicates that the Billing Calendar to be configured is that of an Gas Smart Metersr:GasBillingCalendarTarget Device Type = GSME Yes Otherwise: N/ANoneN/A
Table 172: ElectricityBillingCalendar (sr:ElectricityBillingCalendar) data items
Data ItemDescription / Valid SetTypeMandatoryDefaultUnits
BillingTimeThe time from which the billing period startsxs:timeYesNoneN/A
DailyIndicates that the billing data is to be captured on a daily basis and it is a fixed valuesr:NoTypeDaily: Yes Otherwise: N/ADailyN/A
WeeklyIndicates that the billing data is to be captured on a weekly basis, the numeric value defines the day of the week Valid set: •1 (Monday) to 7 (Sunday)sr:BillingCalendarDayOfWeek (xs:postiveInteger (between 1 and 7))Weekly: Yes Otherwise: N/ANoneN/A
MonthlyIndicates that the billing data is to be captured on a monthly basis, the numeric value defines the day of the month Valid set: •1 to 28sr:BillingCalendarDayOfMonth (xs:postiveInteger (between 1 and 28))Monthly: Yes Otherwise: N/ANoneN/A
QuarterlyIndicates that the billing data is to be captured on a quarterly basis, i.e. every 3 months, and defines the day of the month and the start month of the billing period. Valid set for Start Month is 1 (January) to 12 (December). See Table 174. For example, if the start month is 1, the billing calendar schedule will be 1 (January), 4 (April), 7 (July) and 10 (October). If the start month is 7, the billing calendar schedule will be 7 (July), 10 (October), 1 (January) and 4 (April), Quarterly is only supported on Devices with a Device Model recorded in the Smart Metering Inventory that pertains to GBCS version 2.0 according to the entry for that Device Model in the Central Products Listsr:BillingCalendarQSMYQuarterly: Yes Otherwise: N/ANoneN/A
SixMonthlyIndicates that the billing data is to be captured on a six monthly basis and defines the day of the month and the start month of the billing period. Valid set for Start Month is 1 (January) to 12 (December). See Table 174. For example, if the start month is 1, the billing calendar schedule will be 1 (January) and 7 (July). If the start month is 7, the billing calendar schedule will be 7 (July) and 1 (January), SixMonthly is only supported on Devices with a Device Model recorded in the Smart Metering Inventory that pertains to GBCS version 2.0 according to the entry for that Device Model in the Central Products Listsr:BillingCalendarQSMYSixMonthly: Yes Otherwise: N/ANoneN/A
YearlyIndicates that the billing data is to be captured on a yearly basis and defines the day of the month and the start month of the billing period. For example, if the start month is 7, the billing calendar schedule will be 7 (July) of every year, Valid set for Start Month is 1 (January) to 12 (December). See Table 174. Yearly is only supported on Devices with a Device Model recorded in the Smart Metering Inventory that pertains to GBCS version 2.0 according to the entry for that Device Model in the Central Products Listsr:BillingCalendarQSMYYearly: Yes Otherwise: N/ANoneN/A
Table 173: GasBillingCalendar (sr: GasBillingCalendar) data items
Data ItemDescription / Valid SetTypeMandatoryDefaultUnits
BillingPeriodStartThe date and time from which the billing period starts Valid set: •Valid date-time except if day of the month is 29, 30 or 31 which are not valid (can only use values 1-28).xs:dateTimeYesNoneUTC Date-Time
PeriodicityIndicates that the billing data is to be captured on a reoccurring basis, from the BillingPeriodStart date time. Valid set: •Daily •Weekly •Monthly •Quarterly (only supported on Devices with a Device Model recorded in the Smart Metering Inventory that pertains to GBCS version 2.0 according to the entry for that Device Model in the Central Products List) •SixMonthly (only supported on Devices with a Device Model recorded in the Smart Metering Inventory that pertains to GBCS version 2.0 according to the entry for that Device Model in the Central Products List) •Yearly (only supported on Devices with a Device Model recorded in the Smart Metering Inventory that pertains to GBCS version 2.0 according to the entry for that Device Model in the Central Products List)Restriction of xs:string (Enumeration)YesDailyN/A
Table 174: ElectricityBillingCalendar (sr: BillingCalendarQSMY) data items
Data ItemDescription / Valid SetTypeMandatoryDefaultUnits
DayOfMonthIt defines the day of the month Valid set: •1 to 28sr:BillingCalendarDayOfMonth (xs:postiveInteger (between 1 and 28))YesNoneN/A
BillingPeriodStartMonthIndicates that the billing period starting month for billing calendar periodicities of quarterly, six monthly or yearly Valid set: •1 to 12sr:BillingPeriodStartMonth (xs:positiveInteger between 1 and 12)YesNoneN/A

Message Patterns & Examples

Pattern explorer

Open Message Patterns →

SMETS1 Supporting Requirements

Device-model variations and equivalent steps

Review the Section 18 requirements and their applicability across the documented manufacturer, Device Type, model, and firmware profiles.

Open S1SR Requirements →