DCC Service Level Agreements for the Switching Incentive Regime (Alternative)

  • 1
    Initial Assessment
  • 2
    Solution Development
  • 3
    Consultation
  • 4
    Decision
  • 5
    Awaiting Implementation
  • 6
    Implemented
Step 6 of 6
Implemented
Summary
Requirements for the Central Switching Service (CSS) were identified during the Design, Build and Test Phase of the Ofgem-led Switching Programme as a basis for the procurement of Switching systems. These requirements were later baselined in the REC Service Definitions as Service Level Agreements (SLAs). Following the successful go-live of the CSS, these SLAs merit a review, in order to ensure that they are realistic, given the physical systems design and the actual behaviours of users, compared to the assumptions that were made in the early design phase of the Switching Programme. This Change Proposal has been raised as the vehicle to complete the review and take forward any identified changes

Latest update and next planned activity

Date of latest update
Latest Update
08/11/2024 - This Change Proposal has been implemented as part of the November 2024 REC Release.

Impacts Overview

Impacted Consumers
Non-Domestic Domestic
Impacted REC Parties and Market Participants
Electricity Distribution Network Operator (R) Data and Communications Company (DCC) Shipper (SHP) Energy Supplier (ES) Gas Transporter (GT)
Impacted REC Services
Electricity Retail Data Service (ERDS) Gas Retail Data Service (GRDS) Central Switching Service (CSS)
Priority and rationale
High

Solution development

Problem Statement
Following the introduction of Performance Charges, on 01 April 2023, charges will apply based on the CRS Provider's performance against the defined SLAs. The SLAs were developed based on assumptions made in the early phases of the Switching Programme. The DCC has proposed that these are reviewed, to ensure they are fit for purpose and any Performance Charges applied are proportionate to CSS User detriment and Consumer impact.
Proposed solution summary
  1. As a Consumer, I want the CRS Provider to provide an effective service so that my Switch is not delayed.
  2. As the REC Code Manager, I want to ensure the CRS Provider has appropriate SLAs set, which incentivises the effective functioning of the Switching Service.
  3. As the CRS Provider, I want to ensure that the appropriate SLAs are in place to incentivise the effective functioning of the Switching Service and if these SLAs are not met by the CRS Provider, the commercial impact is proportionate to the detriment experienced by CSS Users and Consumers.
Solution documents
R0092A_Legal Text at FCR (19.04.2024) 05 Jun 2026 ZIP - 837.02 KB
05 Jun 2026

There is currently no Change Plan.

Original submission

Change details

Elise Handy - REC Code Manager
26 Jan 2024

Change details

DCC Service Level Agreements for the Switching Incentive Regime
he Code Manager is raising an alternative proposal for R0092 which was raised by the Data Communications Company (DCC) to review that the current service levels under the Switching Incentive Regime are fit for purpose.
A work group was initiated to review the DCC’s proposals, and it was made clear that any changes to current service levels were a dilution and anything that was taken forward must ensure that the minimum levels of acceptable service for CSS Users are in place with appropriate protections were maintained.
Whilst the DCC have responded positively to some aspects of the feedback from the working group, and updated their proposals accordingly, there are key principles of the feedback from the work group and industry stakeholders as part of the impact assessment which the DCC have not addressed in their final solution. Therefore, the Code Manager deems that the final proposal from the DCC does not maintain appropriate protections for CSS Users and Consumer benefits. In proposing reductions to the service levels required in the REC, the DCC is not proposing a reduction in costs to REC parties, therefore any potential detriment associated with these proposals has been closely scrutinised throughout the process.
There are several reductions in service levels being proposed by the DCC, which will have varying impacts on CSS Users. A number of impacts have been identified by the working group which have not been addressed in the final solution proposed by the DCC. This includes inadequate assurances that critical messages will be processed ahead of gate closure, lack of certainty regarding response times for incidents and reduced focus on completion of the gate closure process. Without appropriate assurances from the CSS Provider, CSS Users will see an impact on operations and may impact the Consumer switching experience.
Maximum Demand Volumes (7.3 CSS Service Definition)

- The work group discussed utilising a better interpretation of maximum demand volumes within the REC so that the total volume of messages relating to Switching were reflected. The DCC proposes a peak daily volume of 1,142,000. The Code Manager proposes an average daily volume of 455,000, peak daily volume of 1,150,000 and a peak hourly volume of 103,500.

Synchronous responses (6.1 CSS Service Definition)

- The DCC proposes to combine average and peak daily response times for synchronous messages with a mean time of 2 seconds or less and 90th percentile response time of 4 seconds or less. The Code Manager agrees with this position.

Asynchronous responses (6.2 CSS Service Definition)

- The DCC proposes to combine average and peak response times for asynchronous messages with a mean time of 3 seconds or less and 90 percentile of 6 seconds or less however for this to be measured daily. The Code Manager’s proposal is for average and peak volumes to be combined at 3 seconds or less and 90th percentile at 6 seconds or less but for the measure to remain at hourly.

Gate Closure (6.3 CSS Service Definition)

- For Gate Closure, the DCC proposes for it to be measured only on when a Market Message is sent relating to a Switch to the relevant Data Service Provider. This is at an average or peak daily volume and with a mean response time of 35 minutes or less and 90th percentile at 40 minutes or less. The Code Manager proposes there is no change to Gate Closure service levels other than to combine the average and peak volumes into one service level.

Switching Incidents (5 CSS Service Definition and SO Service Definition)

- The DCC has proposed that the Switching Operator shall support the response and resolution times for its Switching Incidents, however only provided that the Switching Incident is raised by a Market Participant via the Switching Portal. The alternative proposal agrees that this is only relevant when raised by a CSS User, however, can be an incident raised through any route applicable in the Switching Service Management Schedule and not only relevant through Service Now.
- The DCC has proposed a dilution of service levels associated with P3 incidents in that only 90 percent of incidents must meet the 3 working day resolution time. The Code Manager proposes that 90 percent of Switching Incidents raised in each calendar month are resolved in 3 Working Days and all P3 Switching Incidents are resolved in 6 Working Days in any case.
- The DCC proposes that only 95 percent of P4 Switching Incidents are resolved within 10 Working Days. The Code Manager proposes that 95 percent of P4 Switching Incidents raised in each calendar month are resolved in 10 Working Days and all P4 Switching Incidents are resolved in 20 Working Days in any case.

Service Requests

- The DCC proposes that only 98% of P3 and P4 Service Requests are fulfilled within 3 and 10 days respectively. The Code Manager proposes no change to the REC for this service level due to the lack of evidence presented on the requirement for change by the DCC.
-

Impacts

Electricity, Gas, Domestic Prepayment, Domestic Credit, Microbusiness, Small and Medium Enterprise (SME), Industrial and Commercial (I&C)
Switching experience, Trust and confidence
-
No details provided
CSS Service Definition and Switching Operator Service Definition
No details provided
-
No details provided
-
No details provided
-
No details provided
-
Central Switching Service (CSS), Switching Operator, Gas Retail Data Service, Electricity Retail Data Service
-
Energy Suppliers, Distribution Network Operators, DCC
-
No details provided
-
No
No details provided

Priority & timing

No
N/A
See Change Proposal Plan for R0092
See Change Proposal Plan for R0092
No details provided
-

Activity

Proposed solution summary changed to As a Consumer, I want the CRS Provider to provide an effective service so that my Switch is not delayed.As the REC Code Manager, I want to ensure the CRS Provider has appropriate SLAs set, which incentivises the…
Show more
Implementation Date has been updated to 08 Nov 2024.
caroline.milner, amoden have been allocated as SME.