DPI Extract from CSS

Date of latest update
Type
Change
ID
R0183
Change Category
Change Path
Priority
Urgent
No
Latest Update
11/03/2025 - The proposer has withdrawn the request due to the expected delivery of enquiry data in the same anticipated timescales & the continued pursuance of I0224. The adoption window has closed.
Summary
It has emerged that there are data quality issues relating to the Domestic Premises Indicator (DPI) Data Item, where MPxNs have been recorded as having the wrong DPI. This Change has been raised to identify a mechanism by which this issue can be resolved.
Proposer
Andrew Waghorn
Change Plan

Solution Analysis and Development

In Progress

Start:

11 Jun 2024

Due:

20 Sep 2024

Completion:

Status
Implementation Status
Date Raised
Fuel
REC Decision Maker
Lead Analyst
holly.law
Solution Development
Proposed solution summary
  1. C1 - As a Consumer, I want industry data relating to my energy supply to be accurate, so that I do not experience any issues when switching or engaging with other consumer facing industry practices.
  2. M1 - As a CSS User, I want available DPI data to be accurate, so that when I engage with industry processes that require DPI data, I am confident that I am engaging with the right information. M2 - As the CSS, I want to provide accurate data to CSS Users, so that I am able to facilitate successful industry operations for my Users.
Problem Statement
Inaccurate DPI data available within industry data sources can result in less accuracy within REC processes that utilise this data, and poorer consumer outcomes. DPI data accuracy needs to be improved to ensure that industry processes and Consumers are not impacted.
Stages Selection
SME
SME Role
Lead Technical Analyst
SME User
maxime.van-eyseren@capgemini.com
SME Role
Lead Assurance Analyst
SME User
vaishnsharma@deloitte.co.uk
Change Proposal Form
R0183 Change Report V3.0 02.12.2024
Company Name
-
Review status
Review required

Schedule 14 - Metering Operations Footnote Review

Date of latest update
Type
Change
ID
R0181
Change Category
Change Path
Priority
Urgent
No
Latest Update
23/08/2024 - This change was successfully implemented as part of the August 2024 Extraordinary REC Release on 23 August 2024.
Summary
The footnotes within Schedule 14 - Metering Operations are not in the correct place, are missing or no longer relevant. This Change Proposal looks to correct issues within the footnotes and move them into the legal text to prevent this from happening when future Change Proposals impacting this schedule are implemented.
Proposer
Holly Law
Change Plan

Change Proposal Plan and Impact Assessment Report issued

Completed

Start:

06 Jun 2024

Due:

18 Jun 2024

Completion:

18 Jun 2024

Preliminary Change Report issued

Completed

Start:

18 Jun 2024

Due:

19 Jun 2024

Completion:

19 Jun 2024

Consultation issued

Completed

Start:

19 Jun 2024

Due:

19 Jun 2024

Completion:

19 Jun 2024

Consultation Close

Completed

Start:

19 Jun 2024

Due:

10 Jul 2024

Completion:

10 Jul 2024

Final Change Report Issued

Completed

Start:

10 Jul 2024

Due:

11 Jul 2024

Completion:

11 Jul 2024

Responsible Committee Decision

Completed

Start:

11 Jul 2024

Due:

19 Jul 2024

Completion:

19 Jul 2024

Appeal Window Closure

Not Started

Start:

19 Jul 2024

Due:

02 Aug 2024

Completion:

Status
Implementation Date
Status Superseded
EMAR Version 3.12.0_Superseded

Documents

Name Version Last updated Actions
159.49 KB
Version 1.0 - 02 Nov 2026 PDF - 159.49 KB
1.0 02 Nov 2026
1.0 02 Nov 2026
Implementation Status
Date Raised
Fuel
REC Decision Maker
Lead Analyst
holly.law
Solution Development
Proposed Solution Document
Document title
Metering Operations v4.1 footnote review legal drafting for PCR
Upload document
Metering Operations v4.1 footnote review - PCR.docx
Archive
Off
Document title
Metering Operations v4.1 footnote review legal drafting for FCR
Upload document
Metering Operations v4.1 footnote review - FCR (2).docx
Archive
Off
Problem Statement
REC parties are unable to ensure their processes and procedures correctly reflect their obligations as the footnotes within Schedule 14 - Metering Operations are not in the correct place, are missing or no longer relevant.
R0181 Change Proposal Plan (Approved) 18.06.2024
R0181 Initial Assessment Report (Approved) 18.06.2024
R0181 Preliminary Change Report
Consolidated Consultation Responses
R0181 Final Change Report - approved 22.07.24
Company Name
Code Manager
Review status
Review required

Proposal for Limiting Queries in EES API Calls (Single Query per API Call)

Date of latest update
Type
Change
ID
R0179
Change Category
Change Path
Priority
Urgent
No
Latest Update
This Change Proposal has been implemented as part of the February 2026 REC Release.
Summary
This issue has been raised proposing to establish a limit on the number of queries permitted within a single Application Programming Interface (API) call. As there is potential for performance degradation and system instability that can occur when a large number of queries are made in a single API call to the Electricity Enquiry Services (EES) API. The aim would be to prevent overwhelming the system and ensure consistent response times and reliability. Therefore, this proposes implementing a limit of 1000 queries per single API call.
Proposer
Andres Alvarez
Change report - Final Change Report

Comments deadline
Change Plan

Request for Information

Completed

Start:

03 Jun 2024

Due:

05 Jul 2024

Completion:

05 Jul 2024

Change Issue Group

Completed

Start:

05 Jul 2024

Due:

01 Aug 2024

Completion:

01 Aug 2024
Impacted REC Parties and Market Participants
Status
Implementation Date
Status Superseded
EMAR Version 4.2.0_Superseded
Included changes Affected REC Items
R0179 Proposal for Limiting Queries in EES API Calls (Single Query per API Call)
R0190 Related Meter Point RMP status rules
  • Schedule 28 - Related Metering Points
R0198 Metering Asset Manager (MAM) Communication Method Register
R0242 Missing Scenario Variant from R0043
  • Market Message Catalogue
R0244 C21 to be introduced into STIRG Document
  • Data Item Catalogue
R0235A Missing Scenario Variants in D0179 Alternate Solution
R0256 MM00023 /D0135 - Asset Condition Report clarification of intent on R0021/R0101
  • Market Message Catalogue
R0270 Clarification of SIP Qualification Requirements
  • Schedule 1 - Interpretations and Definitions
  • Schedule 14 - Metering Operations
  • Schedule 15 - Metering Accreditation
R0271 Clarification of ASP, AMI, and EMO Accession Requirements
  • Schedule 15 - Metering Accreditation
  • Schedule 1 - Interpretations and Definitions
R0272 Enabling transparency of the CRS Provider’s REC service level performance
  • Schedule 1 - Interpretations and Definitions
  • Schedule 6 - Performance Assurance
  • Schedule 26 - Switching Service Management
  • Schedule 24 - Switching Data Management
R0277 Data Latency SLA Alignment for Gas Enquiry Service
  • Schedule 1 - Interpretations and Definitions
R0280 CSS Certificate Authority audit clarification
  • Schedule 1 - Interpretations and Definitions
R0283 Annual Address Management Plan Updates
  • Schedule 1 - Interpretations and Definitions
  • Schedule 6 - Performance Assurance
  • Schedule 29 - Address Management
R0287 Clarification and Amendments to Annulment Definition in Schedule 23 – Alignment with SLC Obligations
  • Schedule 1 - Interpretations and Definitions
  • Schedule 23 - Registration Services
R0293 Housekeeping February 2026
Implementation Status
Date Raised
REC Decision Maker
Lead Analyst
holly.law
Solution Development
Proposed Solution Document
Document title
Request For Information (RFI)
Archive
Off
Problem Statement
The absence of a limit on the number of queries (batch processing) within a single API call could cause performance issues and system instability. As a result, system responsiveness may degrade when a large number of queries are made in a single call, impacting user experience and hindering the ability of the EES API to consistently meet user demands.
SME
SME Role
Lead Technical Analyst
SME User
maxime.van-eyseren@capgemini.com
Issue Form
EES API Interface Specification REDLINE DRAFT for R0179
R0179 - Change Report - Final Recommendation Approved
R0179 Change Report (Consultation)
R0179 Consolidated consultation responses (non- confidential)
Re-baseline Change Plan 15.07.25
Consolidated IA responses (non-confidential)
I0179 Change Report (Impact Assessment)
Service Provider - Impacts Data
I0179 - Consolidated RFI Responses
Change Report (Proposal Plan)
Consultation on implementation date response
Change Report - Final Recommendation (new implementation date)
Company Name
RECCo
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

Comments deadline
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

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

June 2024 Housekeeping

Date of latest update
Type
Change
ID
R0171
Change Category
Change Path
Priority
Urgent
No
Latest Update
12/06/24 - this Change Proposal has been withdrawn at the request of the Proposer.
Summary
The Code Manager has identified a number of typographical and formatting errors, as well as opportunities to provide clarity, improve consistency and accuracy across the REC Services and products. These changes have been assessed as meeting the criteria to be progressed via a Housekeeping Change Proposal.
Proposer
Holly Law
Status
Implementation Status
Date Raised
REC Decision Maker
Lead Analyst
holly.law
Solution Development
Problem Statement
This is a Housekeeping Change Proposal subject to the Housekeeping Change Proposal process, rather than the standard change process. The nature of the change is that it makes non-material changes to the REC Products to correct typographical and consistency errors. It also provides an opportunity to introduce necessary clarifications.
Stages Selection
SME
SME Role
Lead Technical Analyst
SME User
caroline.milner@capgemini.com
CP Form R0171 - June 2024 Housekeeping
Company Name
Code Manager
Review status
Review required

Withdrawal of Service Termination Issue Reporting Guidance (STIRG) from REC Governance.

Date of latest update
Type
Change
ID
R0170
Change Category
Priority
Urgent
No
Latest Update
15/11/2024 - The Authority have published their decision, to reject this change proposal in line with the Code Manager and REC Change Panel recommendations. This decision can be found here: https://www.ofgem.gov.uk/decision/retail-energy-code-modification-r0170-rejected
Summary
REC MEP have decided that the current governance for the STIRG is unsuitable for this type of document, and that it should be removed from the REC into ENA governance.
Proposer
Paul Abreu
Change Plan

Party Impact Assessment opens

Completed

Start:

09 May 2024

Due:

21 Jun 2024

Completion:

20 Jun 2024

Party Impact Assessment closes

Completed

Start:

21 Jun 2024

Due:

12 Jul 2024

Completion:

12 Jul 2024

Preliminary Change Report published

Completed

Start:

12 Jul 2024

Due:

26 Jul 2024

Completion:

25 Jul 2024

Change Panel review

Completed

Start:

26 Jul 2024

Due:

06 Aug 2024

Completion:

06 Aug 2024

Consultation opens

Completed

Start:

06 Aug 2024

Due:

09 Aug 2024

Completion:

08 Aug 2024

Consultation closes

Completed

Start:

09 Aug 2024

Due:

02 Sep 2024

Completion:

02 Sep 2024

Final Change Report published

Completed

Start:

02 Sep 2024

Due:

20 Sep 2024

Completion:

05 Sep 2024

Change Panel review

Completed

Start:

20 Sep 2024

Due:

01 Oct 2024

Completion:

17 Sep 2024
Status
Implementation Status
Date Raised
REC Decision Maker
Solution Development
Proposed solution summary
  1. As a Consumer, I want to be confident that any person working on the metering at my property has the adequate guidance under the appropriate governance to allow works to be conducted safely.
  2. As an electricity MEM or DNO, I need the STIR Guidance Document to sit under appropriate governance so I can be confident it is kept up to date for industry needs.
Proposed Solution Document
Document title
R0170 Draft Legal Text 06.06.24
Upload document
R0170 Draft Legal Text 06.06.24.zip
Archive
Off
Problem Statement
The issues surrounding the status of the STIR Guidance document is impacting on the ability of involved parties to review and update the guidance.
Stages Selection
ENALET~1.pdf
Change Proposal Form
R0170 Change Proposal Plan v1.0 (Approved) 18.06.2024
R0170 Initial Assessment Report v1.0 (approved) 18.06.24
R0170 Consolidated Impact Assessment Responses PUBLIC v1.0
R0170 Change Report (For Consultation) V1.1
R0170 Consolidated Consultation Responses PUBLIC v1.0
R0170 Change Report (Final Recommendation) Post Vote v1.0
Company Name
Energy Networks Association
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

Prepayment Method Levelisation Reconciliation Housekeeping Change

Date of latest update
Type
Change
ID
R0165
Change Category
Change Path
Priority
Urgent
No
Latest Update
Implemented on 10/05/2024
Summary
The Code Manager has identified typographical and formatting errors, as well as opportunities to provide clarity, improve consistency and accuracy across the REC Services and products. These changes have been assessed as meeting the criteria to be progressed via a Housekeeping Change Proposal. Schedule 31 - Prepayment Method Levelisation Reconciliation: The Electricity and Gas Meter Point Portfolio Example's have typographical and formatting errors.
Proposer
Holly Law
Change Plan

House Keeping Change report published

Completed

Start:

16 Apr 2024

Due:

25 Apr 2024

Completion:

25 Apr 2024

Responsible Committee Decision

Not Started

Start:

25 Apr 2024

Due:

07 May 2024

Completion:

Status
Implementation Date
Status Superseded
EMAR Version 3.10.1_Superseded
Included changes Affected REC Items
R0165 Prepayment Method Levelisation Reconciliation Housekeeping Change
Implementation Status
Date Raised
REC Decision Maker
Lead Analyst
holly.law
Solution Development
Proposed Solution Document
Document title
Payment Method Levelisation Reconciliation V1.1
Upload document
Payment Method Levelisation Reconciliation v1.1.doc
Archive
Off
Problem Statement
This is a Housekeeping Change Proposal subject to the Housekeeping Change Proposal process, rather than the standard change process. The nature of the change is that it makes non-material changes to the REC Products to correct typographical and consistency errors. It also provides an opportunity to introduce necessary clarifications.
Gas Template AAA_01.csv
Electricity Template FFFF_01.csv
R0165 Housekeeping Change Report Post Vote
Company Name
Code Manager RPS
Review status
Review required