Clarity on use of on hold for switching issues, including the obligations of CSS Users

Date of latest update
Type
Change
ID
R0180
Change Category
Change Path
Priority
Urgent
No
Latest Update
06/11/26 - This Change Proposal has been implemented as part of the 6 November 2026 REC Release.
Summary
Many Switching Incidents are on hold waiting for resolution. The Switching Operator puts these tickets on hold, which is an approved business process from the Switching Programme. This is not reflected in the obligations on SDSPs or other REC Service Providers, where there is no on hold concept. Further there are no obligations on CSS Users to respond in a timely basis. This means that the REC obligations do not reflect current practice, and many tickets remain open much longer than necessary.
Proposer
anton.moden
Change Plan

Change Issue Group

Completed

Start:

03 Jun 2024

Due:

01 Aug 2024

Completion:

01 Aug 2024
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Date
Status Live
EMAR Version 4.4.0
Included changes Affected REC Items
R0180 Clarity on use of on hold for switching issues, including the obligations of CSS Users
  • Schedule 26 - Switching Service Management
R0207 Import / Export MOA Charging Clarification
  • Schedule 14 - Metering Operations
R0253 Theft - DNO/Networks not providing photos
  • Schedule 8 - Unbilled Energy Code of Practice
R0261 Addition of Export flag in D0303 flows
R0266 REC Data Specification Clarifications
  • Schedule 14 - Metering Operations
  • Schedule 30 - Resolution of Consumer Facing Switching and Billing Issues
  • Data Item Catalogue
  • Market Message Catalogue
R0317 Number of Displayed Register Digits Data Item linkage
R0328 Removal of D0383 & D0384 requirements from Sharing MTDs process
  • Schedule 14 - Metering Operations
R0336 Legal text to support REC Change R0180
  • Schedule 26 - Switching Service Management
R0343 MSC - Amending Statement Production Timescales
R0345 Housekeeping November 2026

Documents

Name Version Last updated Actions
331.85 KB
Version 1.0 - 11 Nov 2026 PDF - 331.85 KB
1.0 11 Nov 2026
1.0 11 Nov 2026
Implementation Status
Date Raised
Fuel
REC Decision Maker
Solution Development
Proposed Solution Document
Document title
Option 1
Upload document
Option 1.zip
Archive
Off
Document title
Solution Development Report
Upload document
Solution Development Report.pdf
Archive
Off
Document title
Option 2
Upload document
Option 2.zip
Archive
Off
Document title
Option 3
Upload document
Option 3.zip
Archive
Off
Problem Statement
A lack of obligations is causing issues with open tickets relating to missing messages. Tickets placed on hold also require significant additional work for the Switching Operator, which could either be released as a cost saving or it could result in time freed up for improvement activities.
SME
SME Role
Lead Technical Analyst
SME User
maxime.van-eyseren@capgemini.com
SME Role
Lead Assurance Analyst
SME User
amoden@deloitte.co.uk
Issue Form
Change Report - Proposal Plan V1.0
I0180 Extension to Plan V1.0 approved 09.07.25
I0180 Consolidated Party Impact Assessment Responses v1.0
I0180 Update to Plan V1.0 approved 10.12.25
R0180 Change Report (For Consultation) V1.0
R0180 Consolidated consultation responses V1.0
R0180 Change Report (Final Recommendation) V1.0 approved 25.03.26
Company Name
REC Code Manager
Review status
Review required

Improvements to CSS Business Process Logic

Date of latest update
Type
Change
ID
R0178
Change Category
Change Path
Priority
Urgent
No
Latest Update
17/06/2026 - The Code Manager has published an Update to Plan. This will be presented to the REC Technical Expert Panel at their meeting on 24 June 2026.
Summary
This change proposal is aimed towards rectifying a collection of issues that were identified with the CSS Business Process Logic. These have been identified as follows: 1. Deactivation of an active reg. whilst in-flight switch in progress 2. Deactivation of a prior cancelled registration 3. OFAF switch containing multiple MPxN
Proposer
Caroline Milner
Change Report - Initial Assessment and Change Plan Report
Impacted Consumers
Impacted REC Services
Implementation Date
Status Scheduled
EMAR Version 4.6.0_Scheduled

Documents

Name Version Last updated Actions
244.73 KB
Version 1.0 - 02 Nov 2026 PDF - 244.73 KB
1.0 02 Nov 2026
Implementation Status
Date Raised
Fuel
REC Decision Maker
Lead Analyst
holly.law
Solution Development
Proposed solution summary
  1. Deactivation of an active reg. whilst in-flight switch in progress As mentioned previously, the ‘Deactivation of an active reg. whilst in-flight switch in progress’ issue did have an existing REC CP raised and therefore is further along the discussion process compared to the other two issues identified. Initial discussion outlined that the most appropriate solution for this change proposal should consider the business needs and the desired outcomes. It was noted that from a business perspective, if the switch has already been accepted, then it should still go through and not be cancelled. Therefore, the following points were raised: • It was acknowledged that there are multiple solution options/approaches that could potentially be employed to resolve this issue. As such, and to avoid being overly prescriptive, it is requested that CSS provider investigate all possible options and outline their recommendation for the most suitable approach, which would be developed/progressed further through the subsequent Impact Assessments. • However, the aim is for an effective solution to be developed which would ensure that the consumer is switched with the original effective date being used and that CSS systems could cater for such registration events whilst following the normal Gate Closure processes. • Where possible, the solution should also look to proactively mitigate the impact of this scenario, as opposed to working on a retrospective basis which can lead to the issue persisting over an extended period of time. It was also noted that consideration would need to be given to state of the meters as this would also have an impact on whether switches are able to progress: Therefore, the following points were raised: • The solution would need to consider how the incumbent supplier has deactivated the meter and whether it has been moved to a ‘terminated’ state or a ‘dormant’ state. o Dormant – The meter is inactive. Note that this is a temporary state and therefore the meter could be put back into service. o Terminated – The meter has reached end of life and cannot be reinstated. Note that this is a permanent state. • If the incumbent supplier has moved the meter into a ‘terminated’ state, the in-flight switch would then need to be cancelled. • However, for the ‘dormant’ state, the following two options would be available in terms of what could happen to the status of the meter and thus the in-flight switch: o Moves from ‘inactive’ to ‘active’ (continue with the switch) o Moves from ‘inactive’ to ‘cancelled’ (cannot continue with the switch)
  2. Deactivation of a prior cancelled registration and OFAF switch contains multiple of the same MPxN It is noted that the initial approach discussed was to add new Business Data Validation Rules (BDVR) to stop these issues from occurring. However, this was only discussed at high-level and therefore we request that the CSS provider confirm this approach and provide further details as this change proposal progresses.
Problem Statement
1) Deactivation of an active reg. whilst in-flight switch in progress: There are instances where the incumbent supplier is withdrawing prior to the ‘Supply Effective from Date’, causing the accepted switch to fail at Gate Closure which occurs at 17:00hrs. This creates the scenario in which there is no longer a losing supplier for the consumer to switch from, and therefore the switch process stalls and cannot be progressed. Therefore, this has a direct impact on consumers who have a switch request which has already been accepted but CSS is not able to progress further as the switch process stops. Indeed, there have been a total of 82 missing messages observed since 1st January 2023, of which 66 messages have been related to switches where there was no registered Supplier recorded at Gate Closure. The 30th September 2023 Gate Closure was particularly impacted by this scenario and resulted in 45 registrations which did not become effective on 14th October 2023 as planned. It should also be noted that the 1st October is one of the key contracting dates for large Industrial and Commercial (I&C) consumers, consequently increasing the impact to consumers in this instance. 2) Deactivation of a prior cancelled registration: This scenario occurs when the registered supplier of a MPxN (via the active registration) is the same supplier that cancelled a previous switch for the same MPxN. In this case there is the possibility that the supplier could attempt to deactivate the active registration by accidentally providing the cancelled registration identifier. Currently, CSS still accepts the deactivation request and erroneously changes the cancelled registration state from cancelled to inactive, sending out securedInactive messages. Currently, after an MPxN is disconnected, the Supplier is required to submit a deregistration request to CSS. Therefore, there is a possibility that the suppliers could submit this request for a cancelled registration not active registration. CSS would still accept this request as the Business Data Validation Rules (BDVR) lack coverage of this case; in such cases the Supplier may incorrectly believe that they have deregistered the MPANs. 3) OFAF switch containing multiple MPxN: This is the instance where the end user sends through a One Fail All Fail (OFAF) switch with the same MPxN contained within the payload 2 or more times. Multiple registration IDs are created for the same MPxN, and the registration is left in an incorrect state given a lack of appropriate BDVRs. Indeed, there has been a further reported incident regarding an OFAF transaction of the same MPxN. The primary MPxN was associated with a secondary MPxN and therefore two registrations were created for the primary and secondary MPxN, equating to four registrations in total. There was then an objection raised but this only cancelled 1 of the 2 registrations for each MPxN. The remaining 2 registrations proceeded through gate closure.
SME
SME Role
Lead Technical Analyst
SME User
maxime.van-eyseren@capgemini.com
R0178 - Change Proposal Form
R0178 - Change Report (Proposal Plan) V2.0 (18.02.2025)
R0178 - Update to Proposal Plan V1.0 (Approved) 18.02.2025
R0178 - Consolidated Impact Assessment Responses (Non-Confidential) 18.03.2026
R0178 - Change Report (For Consultation) V1.0
R0178 - Update to Plan (17.06.2026) Pre-Approval
Company Name
REC Technical Services
Review status
Review required

Change Smart Meter Installation Consumer Survey Specification survey questions to a REC Category 2 document

Date of latest update
Type
Change
ID
R0177
Change Category
Change Path
Priority
Urgent
No
Latest Update
This change was implemented on 06 September 2024.
Summary
Adding the Smart Meter Installation Consumer Survey Specification questions to the REC list of documents will allow any amendments to follow the REC change process and allow anyone to propose such amendments.
Proposer
Lorna Mallon
Change Plan

Preliminary Change Report published

Completed

Start:

22 May 2024

Due:

05 Jul 2024

Completion:

04 Jul 2024

Consultation opened

Completed

Start:

05 Jul 2024

Due:

05 Jul 2024

Completion:

04 Jul 2024

Consultation closes

Completed

Start:

05 Jul 2024

Due:

26 Jul 2024

Completion:

26 Jul 2024

Final Change Report published

Completed

Start:

26 Jul 2024

Due:

09 Aug 2024

Completion:

08 Aug 2024

Change Panel decision

Completed

Start:

09 Aug 2024

Due:

20 Aug 2024

Completion:

20 Aug 2024
Impacted Consumers
Impacted REC Parties and Market Participants
Status
Implementation Date
Status Superseded
EMAR Version 3.13.0_Superseded

Documents

Name Version Last updated Actions
1.0 02 Nov 2026
Implementation Status
Date Raised
Fuel
REC Decision Maker
Solution Development
Proposed solution summary
  1. As a Domestic or Micro-Business Consumer, I want the Smart Meter Installation survey questions to have robust governance, so I have confidence the right KPIs are being monitored.
  2. As an Energy Supplier, I want the Smart Meter Installation survey questions to be governed by the REC Change Process, so I can suggest and provide feedback on changes to them.
Proposed Solution Document
Document title
REC Baseline Statement DRAFT
Upload document
REC Baseline Statement DRAFT.xlsx
Archive
Off
Problem Statement
The Smart Meter Installation Consumer Survey Specification questions are mandatory for Energy Suppliers to use, but there is no mechanism for Energy Suppliers to raise changes or issues against the questions as they are not held in the REC Baseline Statement.
R0177 Change Proposal Form
R0177 Change Proposal Plan v1.0 Approved
R0177 Initial Assessment Report v1.0 Approved
R0177 Preliminary Change Report v1.0
R0177 Consolidated Consultation Responses v1.0
R0177 Change Report (Final Recommendation) V1.1
Company Name
Gemserv
Review status
Review required

Improvements to the Theft Detection Incentive Scheme (TDIS)

Date of latest update
Type
Change
ID
R0173
Change Category
Urgent
No
Latest Update
22/09/25 - This Change Proposal has been implemented as part of the MHHS M8 22 September 2025 REC Release.
Summary
This Change proposes that not only Confirmed Energy Thefts are incentivised within the Theft Detection Incentive Scheme (TDIS) but also Energy Theft Desktop and Site Visit Investigations.
Proposer
Samantha Briggs
Change Plan

Party Impact Assessment Closure

Completed

Start:

20 May 2024

Due:

04 Oct 2024

Completion:

04 Oct 2024

Consultation

In Progress

Start:

04 Oct 2024

Due:

18 Oct 2024

Completion:

18 Oct 2024

Consultation Closure

Not Started

Start:

18 Oct 2024

Due:

08 Nov 2024

Completion:

Responsible Committee Decision

Not Started

Start:

08 Nov 2024

Due:

03 Dec 2024

Completion:

Send to Authority

Not Started

Start:

03 Dec 2024

Due:

04 Dec 2024

Completion:

Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Fuel
REC Decision Maker
Lead Analyst
florentina.monea
Solution Development
Proposed Solution Document
Document title
R0173 - Draft Legal Text (26.11.2024)
Upload document
R0173 - Draft Legal Text.zip
Archive
Off
Document title
I0173 - Example Calculations (13.08.2024)
Upload document
I0173 - Example Calculations.pdf
Archive
Off
Document title
R0173 - Solution Development Report v2.4 (26.11.2024)
Upload document
R0173 - Solution Development Report v2.4.pdf
Archive
Off
Problem Statement
Suppliers are not currently meeting their TDIS Theft targets within each TDIS Reporting Year because there may be financial disincentives to undertake investigations where there is no assurance that such investigations would convert into a Confirmed Energy Theft.
SME
SME Role
Lead Technical Analyst
SME User
rosalind.timperley
SME Role
Lead Assurance Analyst
SME User
awaghorn@deloitte.co.uk
I0173- Improvements to the Theft Detection Incentive Scheme
I0173 - Change Report (Proposal Plan) Approved 20.08.2024.
R0173 - Consolidated Impact Assessment Responses_NON-CONFIDENTIAL (18.10.2024)
R0173 - Change Report (For Consultation) 18.10.2024
R0173 Consolidated Consultation Responses NONCONFIDENTIAL (26.11.2024)
R0173 Final Change Report (Post-vote)
R0173 Decision Letter
Change Panel Response - Ofgem send back of R0173
Change Panel Response - Ofgem send back of R0173 - Further Clarifications
R0173 Final Decision Letter
Company Name
REC Code Manager
Review status
Review required

End-to-End New Connections Process Review

Date of latest update
Type
Issue
ID
I0172
Priority
Urgent
No
Latest Update
On 05 February 2026, the Code Manager decided that I0172 would be closed as resolved. After extensive industry engagement, no REC Code changes were identified as necessary. All address management elements raised under I0172 will be handled under I0200. The Crossed Meters process review will be raised in a separate Change Proposal (REC Issue I0314).
Summary
The REC Code Manager is conducting a end-to-end review of the new connections process, examining issues that occur across all industry codes.
Proposer
Paul Gath
Status
Implementation Status
Date Raised
Fuel
REC Decision Maker
Lead Analyst
James Hardy
Solution Development
Problem Statement
Reported inconsistencies in the application of elements of the entire new connections process result in poor Consumer outcomes. Whilst the new connections process spans multiple processes owned by different Codes, the REC Code Manager is conducting an exploratory initial analysis, owing to our place as a dual-fuel, Consumer facing Code. This analysis is expected to yield multiple modifications across multiple Codes that will result in improvements to the new connections process.
I0172 - Issue Proposal Form (pdf)
I0172 Change Report (Proposal Plan) V2.0 (17.06.2025)
I0172 - Update to Plan V1.1 (17.06.2025) Approved
Non-IGT Gas Meter Install Process Map (August 2025 Change Issues Group)
I0172 - Update to Plan V2.0 (09.12.2025) Approved
Company Name
-
Review status
Review required

Introduction of End of Gate Closure notifications

Date of latest update
Type
Change
ID
R0169
Change Category
Change Path
Priority
Urgent
No
Latest Update
15/09/2025 - following discussions at the August Change Issues Group, the Proposer has decided to withdraw R0169. The adoption window is closed.
Summary
This change seeks to introduce additional functionality within the CSS, to allow CSS users to be notified (by CSS) that the CSS has completed the processing of gate closure messages (i.e. sending of securedActive and securedInactive messages). CSS Users in receipt of this End-of-Gate-Closure (EoGC) notification are then able to commence any applicable downstream processing. It is recognised that an EoGC notification is of value to specific parties which have post-gate closure obligations, however the availability of an EoGC notification is to be made available for all CSS users.
Proposer
Stephen Baker
Status
Implementation Status
Date Raised
Fuel
REC Decision Maker
Lead Analyst
James Hardy
Solution Development
Problem Statement
The completion of a gate closure event is not reported to CSS Users (at the time), and CSS Users which require to complete downstream processing must assume when the gate closure event has completed in order to initiate any downstream processing they require to complete.
Stages Selection
SME
SME Role
Lead Technical Analyst
SME User
caroline.milner@capgemini.com
Requirements for End of GC messages
R0169 - Introduction of End of Gate Closure Notifications (Change Proposal Form)
R0169 Change Report (Proposal Plan) V1.0 (Approved) 18.02.2025
Company Name
DCC
Review status
Review required

Clarify & Strengthen CRS Providers Requirements

Date of latest update
Type
Change
ID
R0168
Change Category
Change Path
Priority
Urgent
No
Latest Update
This Change Proposal was implemented on 28 February 2025.
Summary
The RECCo MSI review focused on the analysis and assessment of; Code compliance, performance, impacts and insights from lessons learned feedback from impacted stakeholders. These assessments thematically articulated changes and improvements identified to assure industry market participants that clear and appropriate action is, and will be, taken to prevent, detect and mitigate the risks and impacts of another event, and prepare for the right response to any future incidents. This Issue has been raised to address learnings from the P1 switching incident in July 2023.
Proposer
glenn.sheern
Impacted Consumers
Status
Implementation Date
Status Superseded
EMAR Version 3.16.0_Superseded

Documents

Name Version Last updated Actions
1.0 02 Nov 2026
Implementation Status
Date Raised
Fuel
REC Decision Maker
Lead Analyst
James Hardy
Solution Development
Proposed solution summary
  1. Root Cause Communication: That the DCC, in its role as Switching Operator, delivers, clear, accurate, timely information on the incident root cause, as soon as possible, once it has obtained a reasonable understanding. Both to offset the risks of uncertainty and limited information introduce, ensuring Switching parties (like Supplier, TPIs and Networks) have the right information to enable meaningful engagement, assist their end-consumers, and all impacted Market Participants can more proactively manage the incident impacts, including making appropriate plans in response to the incident and its resolution. Switching Operator's End-Consumer Communication: Introduce a requirement for the DCC, in its role as the Switching Operator, to provide end-consumer appropriate information for REC Parties and Non-REC Parties use to determine communication and action for their Consumers.
  2. Switching Operator, Switching Incident Impact Assessment: This change should clarify the existing Switching Operator’s broader obligation to assess an incidents impact on the wider Switching Arrangements (set out in REC Schedule 26, Switching Service Management Schedule (SSMS), section 1.7, or Major Switching Incidents starting at section 2.9), to ensure the Switching Operator facilitates the most effective, efficient (time, cost, resource) overall Switching industry solution is promoted and implemented. Incident Wider Switching Impact Assessment: Clarify that if a Major Switching Incident is not going to be resolved within defined Service levels (4 hours), then the DCC in its role as Switching Operator should determine the impact on compliance with the REC end-to-end Switching Arrangements, and work with Ofgem, and the Code Administrators for BSC, UNC and DCUSA, and RECCo, to identify the cross code impacts/impacts on other Codes when managing an incident and developing an appropriate solution for industry, with least negative impact to end-consumers.
  3. Refresh and testing of Switching Operator’s (SO) incident related policies, processes, and procedures, to ensure they remain fit for purpose.
  4. Refresh and testing of Switching Operator’s (SO) incident related policies, processes, and procedures, to ensure they remain fit for purpose.
Proposed Solution Document
Document title
I0168 Switching Operator MSI Best Practice Document - for RFI and Industry Comments (02.08.2024)
Upload document
I0168 Switching Operator MSI Best Practice Document - for RFI and Industry Comments (2).docx
Archive
Off
Document title
Central Switching Service (CSS) Service Definition (R0168 - Red-lining) 05.12.2024
Upload document
Central Switching Service (CSS) Service Definition (R0168 - Red-lining) 05.12.2024.pdf
Archive
Off
Document title
Switching Operator (SO) Service Definition (R0168 - Red-lining) 05.12.2024
Upload document
Switching Operator (SO) Service Definition (R0168 - Red-lining) 05.12.2024.pdf
Archive
Off
Document title
Schedule 26 - Switching Service Management Schedule (R0168 - Red-lining) 05.12.2024
Upload document
Schedule 26 - Switching Service Management Schedule (R0168 - Red-lining) 05.12.2024.pdf
Archive
Off
Document title
R0168 Draft Switching Operator Best Practice Document (V1.0 for Industry Consultation) 05.12.2024 (Word Version)
Upload document
R0168 Draft Switching Operator Best Practice Document (V1.0 for Industry Consultation) 05.12.2024.docx
Archive
Off
Document title
R0168 Draft Switching Operator Best Practice Document (V1.0 for Industry Consultation) 05.12.2024 (PDF Version)
Upload document
R0168 Draft Switching Operator Best Practice Document (V1.0 for Industry Consultation) 05.12.2024.pdf
Archive
Off
Document title
R0168 - Change Report (for Consultation) 12.12.2024
Upload document
R0168 - Change Report (for Consultation) 12.12.2024.pdf
Archive
Off
Document title
Schedule 26 - Switching Service Management Schedule (R0168 - Red-lining) 28.01.2025
Upload document
Schedule 26 - Switching Service Management Schedule (R0168 - Red-lining) 28.01.2025.pdf
Archive
Off
Document title
Central Switching Service (CSS) Service Definition (R0168 - Red-lining) 28.01.2025
Upload document
Central Switching Service (CSS) Service Definition (R0168 - Red-lining) 28.01.2025.pdf
Archive
Off
Document title
Switching Operator (SO) Service Definition (R0168 - Red-lining) 28.01.2025
Upload document
Switching Operator (SO) Service Definition (R0168 - Red-lining) 28.01.2025.pdf
Archive
Off
Document title
Major Switching Incident: Switching Operator Best Practice Evaluation Form V1.0
Upload document
Major Switching Incident - Switching Operator Best Practice Evaluation Form V1.0.pdf
Archive
Off
Document title
Major Switching Incident: Switching Operator Best Practice Evaluation Form V1.0
Upload document
Major Switching Incident - Switching Operator Best Practice Evaluation Form V1.0.pdf
Archive
Off
Problem Statement
On 6th July 2023, a Major Switching Incident occurred with the Central Switching Service ((CSS) operated by the Switching Operator and CSS Service Provider, the Smart Data Communication Company (DCC)). It prevented the successful completion of that day’s planned electricity and gas, supply switches and new registrations. The CSS was stabilised post-incident and any new requests submitted after 9 a.m., 6th July were processed successfully. Through the collective action of the Switching Operator and industry parties, the CSS sent the missing industry messages to give effect to the intended switches and new registrations during the period of the 2nd to the 8th of August 2023. Priority 1 (P1) Major Switching Incidents of this nature are required to be resolved within 4 hours; however, DCC reported it took 1,605.6 hours in this instance. This incident had significant impacts on multiple industry parties and end consumers, demonstrating a clear need for improvement in the arrangements managing switching services and response to major incidents. The Retail Energy Code Company ((RECCo) with the assistance of its Code Manager) completed an end-to-end incident review; to identify the root cause, consider the efficiency and effectiveness of the incident management response, assess the improvements required, and identify appropriate actions for risk mitigation. With the overarching objective that by delivering the identified review recommendations, these actions should limit the possibility, or minimise the impact of, any future major switch incidents.
SME
SME Role
Lead Assurance Analyst
SME User
vaishnsharma@deloitte.co.uk
I0168 - Issue Form
I0168 Switching Operator MSI Best Practice Document - for RFI and Industry Comments (02.08.2024)
I0168 - Change Report (Change Plan) (Approved) 17.09.2024
I0168 - Update to Proposal Plan (Approved 30.10.2024)
R0168 - Consolidated Consultation Responses (Non-Confidential) 20.01.2025
R0168 - Change Report (Final Reccomendation) 04.02.2025 (Approved) V2.0
Company Name
-
Review status
Review required

Theft Detection Incentive Scheme (TDIS) Reporting Periods

Date of latest update
Type
Change
ID
R0163
Change Category
Change Path
Priority
Urgent
No
Latest Update
29/01/2028 - Adoption Window closed. Change withdrawn
Summary
This Change Proposal seeks to alter the Theft Detection Incentive Scheme (TDIS) reporting cycle from annual to a quarterly cycle. This alteration is limited the administration of the scheme and will have no impact on how Suppliers submit their reports.
Proposer
Jon Dixon
Change Plan

Responsible Committee decision

Not Started

Start:

09 Apr 2024

Due:

21 Jan 2025

Completion:

Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Fuel
REC Decision Maker
Lead Analyst
florentina.monea
Solution Development
Proposed solution summary
  1. As an Energy Supplier, I want the ability to effectively monitor my TDIS performance so that I can optimise my theft detection operations.
  2. As the Code Manager, I want the TDIS to continually evolve so that performance against the scheme can be improved.
  3. As RECCo, I want the TDIS to continually evolve to support the Theft Reduction Strategy.
Proposed Solution Document
Document title
R0163 Draft Legal Text (10.04.2024)
Upload document
R0163 Draft Legal Text.zip
Archive
Off
Problem Statement
The current annual TDIS Reporting Cycle does not support the effective cost recovery for Suppliers in year, enable Suppliers to monitor their TDIS performance or enable the Code Manager to flexibly adopt improvements to the scheme.
Stages Selection
SME
SME Role
Lead Technical Analyst
SME User
rosalind.timperley
SME Role
Lead Assurance Analyst
SME User
awaghorn@deloitte.co.uk
2023.11 Ofgem - Open letter on Energy Theft.pdf
RECCo TTM cover letter 15.01.2024.pdf
R0163 - Change Proposal Form
R0163 - Initial Assessment Report v1.1 (16.04.2024) Approved
R0163 - Change Proposal Plan V1.1 (16.04.2024) Approved
R0163 - Preliminary Change Report v1.0 (12.04.2024) Published for consultation
R0163 Consolidated Consultation Responses_Non-Confidential 09.05.2024
R0163 - Rebaseline of Change Proposal Plan (13.05.2024)
R0163 - Rebaseline of Change Proposal Plan v2.0 (06.09.2024)
R0163 Consolidated Consultation Responses (Non-confidential)
Company Name
RECCo
Review status
Review required

Enabling Robotics for SDEP

Date of latest update
Type
Change
ID
R0161
Change Category
Change Path
Priority
Urgent
No
Latest Update
24/03/26 - This Change is on hold pending the outcome of R0122 - SDEP Review Improvements
Summary
The Secure Data Exchange Portal (SDEP) is a mailbox that enables the transfer of sensitive customer related data in a way that ensures data is safe and secure. Suppliers are obliged to send and receive queries and escalations via the SDEP. Unfortunately, the SDEP has issues in bulk resolving processes which could be solved by the removal of the prohibition of the use of robotics. For example, there is no function to be able to retrieve cases specific to each team, work these and then automatically issue a response. Currently, to get the same kind of functionality, an agent or team lead would need to manually process. In another scenario, under REC schedule 30, as part of each of the processes, we are obliged to issue an escalation where there has been no response within set timeframes. Prior to SDEP implementation, we would be able to issue email escalations automatically where there was an absence of a response flow. With the SDEP this process is now manual: an agent will need to sign in to ECOES, navigate to the appropriate module, and input the data.
Proposer
David Morley
Implementation Status
Date Raised
Fuel
REC Decision Maker
Solution Development
CP Form Enabling Robotics for SDEP
Company Name
OVO Energy
Review status
Review required

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

Date of latest update
Type
Change
ID
R0092A
Change Category
Priority
Urgent
No
Latest Update
08/11/2024 - This Change Proposal has been implemented as part of the November 2024 REC Release.
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
Proposer
Elise Handy
Impacted Consumers
Status
Implementation Date
Status Superseded
EMAR Version 3.14.0_Superseded
Included changes Affected REC Items
R0108 Enabling Electricity Enquiry Service searches using a Unique Property Reference Number
R0113 Data Specification updates and clarifications
R0115 Frequency and content of CSS reports on switching via the DCC portal
R0119 Annulment Definition
  • Schedule 1 - Interpretations and Definitions
  • Schedule 23 - Registration Services
R0150 On-site Aggregation as a method to facilitate Third Party Access - BSC P455
  • Schedule 1 - Interpretations and Definitions
  • Schedule 25 - Central Switching Service
R0049 Intellectual Property Rights and Services Data Main Body changes
R0092A DCC Service Level Agreements for the Switching Incentive Regime (Alternative)
R0203 CSS Retry Strategy
  • Schedule 24 - Switching Data Management
R0206 Cross code change to align with BSC CP1598
  • Market Message Catalogue
R0211 November 2024 House Keeping Change
R0069 Amendments to Sample Access Agreement
  • Schedule 9 - Qualification and Maintenance
R0094 Clarify obligations on gas meter exchanges that occur close to CoS
  • Schedule 14 - Metering Operations
  • Market Message Catalogue
R0098 Optional fuzzy searching in EES

Documents

Name Version Last updated Actions
199.57 KB
Version 1.0 - 02 Nov 2026 PDF - 199.57 KB
1.0 02 Nov 2026
1.0 02 Nov 2026
Implementation Status
Date Raised
Fuel
REC Decision Maker
Solution Development
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.
Proposed Solution Document
Document title
R0092A_Legal Text at FCR (19.04.2024)
Upload document
R0092A_Legal Text at FCR.zip
Archive
Off
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.
SME
SME Role
Lead Technical Analyst
SME User
caroline.milner@capgemini.com
SME Role
Lead Assurance Analyst
SME User
amoden@deloitte.co.uk
R0092A - Change Proposal Form.docx
R0092A_Authority_Decision (22.07.2024)
Company Name
REC Code Manager
Review status
Review required