6.8 · Update Device Configuration (Billing Calendar)

18.42a · Where the target SMETS1 ESME or SMETS1 GSME does not support a time other than midnight UTC in its Billing Calendar (with its SMETS1 meaning), the S1SP shall ignore the time elements of the BillingTime or BillingPeriodStart (with their DUIS meanings) and shall set the time in the Billing Calendar (with its SMETS1 meaning) to midnight UTC.

18.42b · Where the target SMETS1 ESME or SMETS1 GSME does not support a time resolution greater than minutes in its Billing Calendar (with its SMETS1 meaning), the S1SP shall ignore the seconds part of the time in the BillingTime or BillingPeriodStart (with their DUIS meanings) and shall set the seconds part of the time in the Billing Calendar (with its SMETS1 meaning) to zero.

18.42c · Where the target SMETS1 GSME does not support the Billing Calendar (with its SMETS1 meaning), the S1SP shall create a SMETS1 Response indicating failure.

18.42d · Where the target SMETS1 GSME only supports a Billing Calendar timetable of either (1) midnight daily, (2) weekly at midnight on Monday or (3) monthly at midnight on the first of the month (with its SMETS1 meaning) and the Service Request specifies a GasBillingCalendar (with its DUIS meaning) with a timetable that is other than one of those options, the S1SP shall create a SMETS1 Response indicating failure.

18.42e · Where the target SMETS1 ESME requires a Billing Calendar (with its SMETS1 meaning) with a start date in the past, and where a Periodicity of Yearly, SixMonthly or Quarterly (with their DUIS meanings) is specified in the Service Request, the S1SP shall derive, using the S1SP Time, a DayOf Month and BillingPeriodStartMonth (with their DUIS meanings) from the corresponding fields in the Service Request to ensure they refer to a dateTime (with its DUIS meaning) which is earlier than today, according to the S1SP Time.

18.42f · Where the SMETS1 GSME does not support BillingPeriodStart (with its DUIS meaning) in the future and the S1SP receives a Service Request where, according to the S1SPs current time, the BillingPeriodStart is in the future, then the S1SP shall return a SMETS1 Response indicating failure and undertake no further processing.

18.42g · Where the SMETS1 GSME does not support BillingPeriodStart (with its DUIS meaning) in the future and the S1SP receives a Service Request where, according to the S1SPs current time, the BillingPeriodStart is in the future, then the S1SP shall: (i) derive, using the S1SP Time, a BillingPeriodStart by taking the specified BillingPeriodStart and decreasing it by the minimum number of periods specified in the Periodicity (with its DUIS meaning) in order to derive a date-time in the past; and (ii) configure the Device with the resulting BillingPeriodStart, recognising that the time element will be ignored by the Device, in terms of when resulting Billing Data Log (with its SMETS1 meaning) entries are created. Rather the Device shall create such entries at 23:59:59 on the dates prior to the dates specified by the derived BillingPeriodStart and Periodicity. Additionally, the Device will immediately create a BillingDataLog entry which would be returned in a subsequent Retrieve Change Of Mode / Tariff Triggered Billing Data Log (SRV 4.4.2) Service Request which covers this period.

18.42h · Where the target SMETS1 ESME receives Service Request with BillingPeriodStart (with its DUIS meaning) in the future then SMETS1 ESME updates the billing period correctly but the associated SMETS1 PPMID will not reflect the EMSE update and associated data.