CSS End User Obligations
Date of latest update
Type
Change
ID
R0099
Change Category
Change Path
Priority
Urgent
No
Latest Update
07/02/25 - This Change Proposal has been withdrawn at the request of the proposer, as it is being developed as part of I0180
Summary
There are multiple observed instances of CSS incidents that have been raised that cannot be resolved without proactive engagement from the end user. There are currently no direct obligations on CSS Users to engage with the incident resolution process, or to provide up to date contact details, which can result in the CSS System Operator struggling to resolve incidents in a timely manner. This results in CSS incidents remaining unresolved and results in a degradation of the effectiveness of the switching process. This Change Proposal has been raised to address this issue.
Impacted Consumers
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Date
08 November 2024
Documents
| Name | Version | Last updated | Actions |
|---|---|---|---|
| 1.0 | 02 Nov 2026 | ||
| 1.0 | 02 Nov 2026 |
Implementation Status
Date Raised
Fuel
REC Decision Maker
Solution Development
Proposed Solution Document
Document title
R0099 Draft Legal Text v1.0 (20.03.2024)
Upload document
Main Body_R0099 Draft v1.0.docx
Archive
Off
Stages Selection
SME
SME Role
Lead Technical Analyst
SME Role
Lead Assurance Analyst
R0099 - Change Proposal Form 10.03.2023
Company Name
-
Review status
Review required
Consequential Change for CSS Smart Meter Data Retriever Appointments
Date of latest update
Type
Change
ID
R0097
Change Category
Change Path
Urgent
Yes
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 looks to make amendments to the Data Specification for the Supplier Arranged Appointments messages exchanged between the Electricity Retail Data Service and Central Switching Service.
Change Plan
Service Provider Impact Assessment started
Completed
Start:
20 Feb 2023Due:
22 Mar 2023Completion:
22 Mar 2023Service Provider Impact Assessment completed
Completed
Start:
22 Mar 2023Due:
03 May 2023Completion:
03 May 2023Preliminary Change Report and Consultation issued
Completed
Start:
03 May 2023Due:
19 May 2023Completion:
19 May 2023Consultation closed
Completed
Start:
19 May 2023Due:
05 Jun 2023Completion:
05 Jun 2023Final Change Report issued
Completed
Start:
05 Jun 2023Due:
21 Jun 2023Completion:
15 Jun 2023Responsible Committee decision
Completed
Start:
21 Jun 2023Due:
28 Jun 2023Completion:
04 Jul 2023Appeal Window opens
Completed
Start:
28 Jun 2023Due:
04 Jul 2023Completion:
04 Jul 2023Appeal Window closes
Completed
Start:
04 Jul 2023Due:
18 Jul 2023Completion:
18 Jul 2023Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Date
MHHS Programme Milestone M8 (Code changes delivered)
| Included changes | Affected REC Items | |
|---|---|---|
| R0044 | MHHS Programme Changes required to Central Switching Service |
|
| R0173 | Improvements to the Theft Detection Incentive Scheme (TDIS) |
|
| R0209 | Implementation of Market-wide Half Hourly Settlement (MHHS) Arrangements |
|
| R0222 | ESME ID Update Rejections | |
| R0223 | Reconciliation of Unallocatable Transactions Review |
|
| R0241 | MHHS Incremental Changes for go live |
|
| R0259 | Update to R0173 Implementation Date | |
| R0264 | Data Specification Housekeeping | |
| R0083 | Changes to Supply Number Format for MHHS | |
| R0097 | Consequential Change for CSS Smart Meter Data Retriever Appointments |
|
Implementation Status
Date Raised
Fuel
REC Decision Maker
Solution Development
Proposed solution summary
- As the CSS Provider, I want to be able to identify which appointment messages received from ERDS require a response, so that I can confirm whether the appointment was successfully made in SMDSP
- As the ERDS Provider, I want to be able to indicate which appointment messages I need to receive a response for, so that I can understand which appointments have been successful in the SMDSP
- As an Electricity Supplier, I want Supplier appointments in the ERDS to match those held in SMDSP
Proposed Solution Document
Document title
R0097 Proposed Solution (Initial Assessment) 14.03.23
Upload document
R0097 Proposed Solution (Initial Assessment) 14.03.23.zip
Archive
Off
Document title
R0097 Proposed Solution (Impact Assessment) 22.03.23
Upload document
R0097 Proposed Solution (Impact Assessment) 22.03.23.zip
Archive
Off
Document title
R0097 Proposed Solution (Consultation) 17.05.23
Upload document
R0097 Proposed Solution (Consultation) 17.05.23.zip
Archive
Off
Document title
R0097 Draft Legal Text (Consultation) 17.05.2023
Upload document
Attachment B_R0097 Proposed Data Specification Changes_v1.6.pdf
Archive
Off
Problem Statement
The implementation of Change Proposal R0044, will result in the Central Switching Service (CSS) providing an asynchronous response to the Electricity Retail Data Service (ERDS) upon a successful, or unsuccessful Smart Meter Data Retriever (SMDR) appointment within the SMDSP. This will significantly increase the volume of CSS messages, as there is currently no mechanism for the CSS to recognise when a response is required. The increased volume could have a significant impact on central system performance.
Stages Selection
SME
SME Role
Lead Technical Analyst
Workgroup
Workgroup(s)
R0097 - Change Proposal Form downloadable version 20.02.2023
R0097 - Change Proposal Plan v2.0 (Approved) 21.03.2023
R0097 - Initial Assessment Report v2.0 (Approved) 21.03.23
R0097 - Preliminary Change Report v1.0 (For Consultation) 19.05.2023
R0097 Consolidated Consultation Responses v1.0 PUBLIC 15.06.2023
R0097 - Final Change Report v2.0 (Post-Vote) 04.07.2023
Company Name
REC Technical Services
Review status
Review required
CSS Message Regeneration Functionality
Date of latest update
Type
Change
ID
R0096
Change Category
Change Path
Priority
Urgent
No
Latest Update
25/02/2026 On 25 February 2026, the Technical Expert Panel voted in line with the Code Manager recommendation to approve R0096 for implementation in November 2027. The appeal window is now open until 23:59, 11 March 2026.
Summary
An inability by the Central Switching Service (CSS) to re-generate Market Messages that were not sent as intended can result in issues with the Switching process, both for REC Parties, and Consumers. This Change seeks to create a message regeneration functionality that would mitigate this Consumer detriment.
Change Plan
Update to Plan approved at Change Panel
Completed
Start:
Due:
Completion:
21 Oct 2025Final Recommendation approved at TEP
Completed
Start:
Due:
Completion:
25 Feb 2026Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Date
05 November 2027
| Included changes | Affected REC Items | |
|---|---|---|
| R0096 | CSS Message Regeneration Functionality |
|
Documents
| Name | Version | Last updated | Actions |
|---|---|---|---|
| 1.0 | 02 Nov 2026 |
Implementation Status
Date Raised
Fuel
REC Decision Maker
Solution Development
Proposed Solution Document
Document title
R0096 Solution Development Document V1.0
Upload document
R0096 Solution Development Document V1.0.pdf
Archive
Off
Document title
R0096 Detailed Design Document v1.0
Upload document
CSS Message Regeneration Detailed Design (R0096)_Final_Ver.1.01.pdf
Archive
Off
Problem Statement
Failures by the CSS to generate Market Messages can result in a breakdown of the Switching process. As the CSS cannot re-generate Market Messages that should have been sent but were not, this results in message asynchronisation, and breakdown of CSS functions and processes, resulting in substantial impacts for those involved – Difficulties for the REC Parties using the CSS, and difficulties for Consumers, where the Switch process is impacted.
Stages Selection
SME
SME Role
Lead Technical Analyst
SME User
maxime.van-eyseren@capgemini.com
R0096 - Change Proposal Form downloadable version 17.02.2023
R0096 Change Report (Plan) (Approved) V1.0 21.01.25
R0096 Change Report Re-Plan (Pre-Approval) v1.0
R0096 Change Report (Re-Plan) v1.0 approved 21/10/2025
R0096 Change Report (Impact Assessment) v1.0
R0096 Consolidated Party Impact Assessment Responses v1.0
R0096 Change Report (Consultation) approved 17.12.2025 v1.2
R0096 Consolidated Consultation Responses v2.0
R0096 White Paper - Business Case Assessment v1.5
R0096 Change Report (Final Recommendation) approved 25.02.2026 v1.0
Company Name
REC Technical Services
Review status
Review required
Changes to allow DNOs to reinstate disconnected MPANs
Date of latest update
Type
Change
ID
R0095
Change Category
Other Industry Codes impacted
Change Path
Priority
Urgent
No
Latest Update
The Code Manager have taken R0095 off of hold and published an Information Request for R0095 on 22 October 2026, this is open to responses until 13 November 2026.
Summary
When Meter Point Administration Numbers (MPANs) are erroneously disconnected, they cannot be reinstated. As a result, Consumers suffer billing issues and Registered Suppliers cannot settle against the disconnected MPAN. This change seeks to introduce a mechanism to restore erroneously disconnected MPANs.
Change Plan
Solution Development
Completed
Start:
17 Feb 2023Due:
26 Jan 2024Completion:
26 Jan 2024Impacted Consumers
Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Fuel
REC Decision Maker
Solution Development
Proposed solution summary
- As a Consumer, I do not want the erroneous disconnection of my MPAN to affect the continuity of my supply contract and billing arrangements.
- As a DNO, I want to be able to reverse erroneous disconnections with no lasting effect so that I don’t need to create a new MPAN to resolve the issue, thereby avoiding DUoS payment collection issues. 2 - As a Supplier, I want to be able to reverse erroneous disconnections with no lasting effect so that I can correctly bill my consumers. 3 - As the CSS, I want users to be able to effectively resolve discrepancies, so that industry data for their portfolio is accurate. 4 - As MPRS, I want users to be able to effectively resolve discrepancies, so that industry data for their portfolio is accurate.
Problem Statement
When MPANs are incorrectly identified and targeted for disconnection, the RMP will be erroneously terminated following receipt of Termination Market Messages by the CSS. This process is irreversible once triggered, meaning that there is no mechanism to restore the MPAN as it was previously. This results in a poor Consumer experience, and settlement misbalancing for Registered Suppliers. Currently, there is no mechanism to mitigate the negative impact on Registered Suppliers/DNO and Consumers.
Stages Selection
SME
SME Role
Lead Technical Analyst
R0095 - Change Proposal form downloadable version 17.02.2023
R0095 Change Proposal Plan v1.0 (Approved) - 20.09.23
R0095 Initial Assessment Report v1.0 (Approved) - 20.09.2023
R0095 - Change Proposal Re-Plan (Approved) v1.0-13.12.23
Company Name
-
Review status
Review required
ERDS Upload File in the Data Specification and clarification of cancellation code
Date of latest update
Type
Change
ID
R0086
Priority
Urgent
No
Latest Update
06/11/2023 - Withdrawal adoption window closed.
Summary
The MPAS/ERDS Upload file has historically been a part of the Data Specification however during transition from the MRA, the process has been omitted. This change seeks to restore the file to the specification. Secondly, the file previously provided a cancellation reason code for Switches. Under the current REC arrangements (i.e. since CSS go live) Reason codes are not provided and have been defaulting to W which indicated a reason of “withdrawn” which may now be misleading. This Change Proposal has been raised to address these issues
Status
Implementation Status
Date Raised
Solution Development
Stages Selection
R0086 - Change Proposal Form (downloadable version)
Company Name
-
Review status
Review required
CSS Market Message Retry Strategy
Date of latest update
Type
Change
ID
R0081
Priority
Urgent
No
Latest Update
15/11/2023 - Change Proposal has been withdrawn. Market message success data for September 2023 was reviewed to ensure that a stable period was analysed which represented ‘normal’ conditions. Upon completion of the review, it has been concluded that the success of the current retry strategy has significantly improved since this change proposal was raised. The Code Manager will introduce cyclical reviews of performance to ensure this continues at the expected levels.
Summary
The prescriptive nature of the Market Message retry drafting is currently impeding on the CSS Service Provider’s ability to ensure all Market Messages are sent and received successfully between the CSS and the CSS User. This CP proposes a move to a principles-based obligation that allows for flexibility to ensure the CSS and CSS User are able to attempt retries but not have to follow specific timings or have a maximum number of retries.
Status
Implementation Status
Date Raised
Fuel
Solution Development
Stages Selection
R0081 - Change Proposal Form
Proposed legal text submitted with the CP
Company Name
-
Review status
Review required
Improvements to ‘Failed to Deliver’ CSS Messages
Date of latest update
Type
Change
ID
R0080
Change Category
Change Path
Priority
Urgent
No
Latest Update
This Change Proposal has been implemented as part of the REC Release on 27 June 2025.
Summary
Since CSS Go-Live a large number of messages have not been successfully delivered due to failures of CSS User's gateways, resulting in CSS exhausting the 12-hour retry period. This Change Proposal has been raised to explore and address this issue
Change Plan
Service Provider Impact Assessment close
Completed
Start:
09 Nov 2022Due:
25 Jan 2024Completion:
25 Jan 2024Party Impact Assessment trigger
Completed
Start:
25 Jan 2024Due:
02 Feb 2024Completion:
02 Feb 2024Party Impact Assessment close
Completed
Start:
02 Feb 2024Due:
23 Feb 2024Completion:
23 Feb 2024Preliminary Change Report and Consultation issued
Completed
Start:
23 Feb 2024Due:
10 May 2024Completion:
10 May 2024Consultation close
Completed
Start:
10 May 2024Due:
03 Jun 2024Completion:
03 Jun 2024Responsible Committee Decision
Completed
Start:
24 Jul 2024Due:
31 Jul 2024Completion:
31 Jul 2024Final Change Report Issued
Completed
Start:
03 Jun 2024Due:
24 Jul 2024Completion:
19 Jul 2024Impacted Consumers
Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Date
28 June 2025
| Included changes | Affected REC Items | |
|---|---|---|
| R0155 | Change of Occupier: Evidentiary Standards and Timescales |
|
| R0193 | Add Enumeration Values to the DI51035 - Communications Provider Data Item |
|
| R0202 | Performance Assurance Report Catalogue Updates (MHHS) | |
| R0225 | Clarification on TDIS portfolio transfers on sale |
|
| R0233 | Introduction of an Energy Theft Unit (ETU) under the REC | |
| R0234 | Introduction of an energy theft Referral Assessment Service under the REC | |
| R0236 | REC Party Auto de-accession proposal |
|
| R0238 | Performance Assurance Reporting Catalogue - Annual Review | |
| R0249 | Correction to Change Management Schedule regarding sub-committee voting |
|
| R0258 | Housekeeping June 2025 | |
| R0080 | Improvements to ‘Failed to Deliver’ CSS Messages |
|
Implementation Status
Date Raised
Fuel
REC Decision Maker
Solution Development
Proposed solution summary
- As a Consumer, I want the Switching process to work successfully, so that I can switch Energy Supplier without delays or issues.
- As the CSS Provider I want the messages I send to CSS Users to be received and processed successfully, so that there is no interruption to the Switching process or the Consumers’ Switching experience.
- As the CSS User I want to receive CSS messages in a timely manner following any outage of my own gateway or systems, so that there is no interruption to the Switching process or the Consumers’ Switching experience.
Proposed Solution Document
Document title
R0080 - Solution Development Report 11.01.2024
Upload document
R0080 - Solution Development Report 11.01.2024.pdf
Archive
Off
Document title
CSS Interface Design Specification v8.9.0 R0080 - REDLINE
Upload document
CSS Interface Design Specification v8.9.0 R0080 - TRACKED.docx
Archive
Off
Document title
CSS Failed To Deliver Detailed Design (R0080) v1.3 (19.06.2024)
Upload document
CSS Failed To Deliver Detailed Design (R0080) v1.3.docx
Archive
Off
Document title
Business Data Validation Rules v1.5.0 R0080 - REDLINE
Upload document
Copy of Business Data Validation Rules v1.5.0 R0080 - REDLINE.xlsx
Archive
Off
Document title
Schedule 24_Switching Data Management v1.2_R0080 Draft (19.06.2024)
Upload document
Schedule 24_Switching Data Management v1.2_R0080 Draft.doc
Archive
Off
Problem Statement
Following an unexpected or extended period of gateway outage for a CSS User, there is currently no automated process to resend any CSS messages from the CSS Provider that were triggered during the period of outage. This results in the CSS Provider needing to manually correct any issues, which is time consuming and may affect Consumer Switches due to delays in messages being processed.
Stages Selection
SME
SME Role
Lead Technical Analyst
SME User
caroline.milner@capgemini.com
SME Role
Lead Assurance Analyst
R0080 - Change Proposal form
R0080 Onboarding document
R0080 - Change Proposal Plan (Approved) 16.01.2024
R0080 - Rebaselined Change Plan (26.04.2024)
R0080 - Initial Assessment Report (Approved) 16.01.2024
R0080 Consolidated Party IA Responses v1.0 (10.05.2024)
R0080 - Preliminary Change Report v1.0 (Published for Consultation) 10.05.2024
R0080 Consolidated Consultation Responses (19.06.2024)
R0080 - Final Change Report v2.0 (Approved) 31.07.2024
Company Name
-
Review status
Review required
Provision of Enduring Test Environments
Date of latest update
Type
Change
ID
R0070
Change Category
Change Path
Priority
Urgent
No
Latest Update
28/06/2024 - Change implemented as part of the June 2024 REC Release
Summary
Currently the REC does not require the Central Switching Service (CSS) and Switching Operator (SO) to provide the enduring test environments and test data for use by REC Parties when making necessary system changes for REC Change Proposals or internal system updates. This Change Proposal has been raised to introduce these obligations in to the REC.
Change Plan
Solution Analysis and Development
Completed
Start:
09 Sep 2022Due:
06 Jun 2023Completion:
06 Jun 2023Service Provider Impact Assessment Period
Completed
Start:
06 Jun 2023Due:
06 Oct 2023Completion:
06 Oct 2023Service Provider Impact Assessment
Completed
Start:
24 Nov 2023Due:
03 Jan 2024Completion:
03 Jan 2024Party Impact Assessment Issued
Completed
Start:
06 Oct 2023Due:
24 Nov 2023Completion:
24 Nov 2023Preliminary Change Report Issued
Completed
Start:
03 Jan 2024Due:
16 Jan 2024Completion:
16 Jan 2024Responsible Committee Review
Completed
Start:
16 Jan 2024Due:
23 Jan 2024Completion:
23 Jan 2024Consultation Issued
Completed
Start:
23 Jan 2024Due:
26 Jan 2024Completion:
26 Jan 2024Final Change Report Issued
Completed
Start:
26 Jan 2024Due:
23 Feb 2024Completion:
23 Feb 2024Responsible Committee Decision
Completed
Start:
23 Feb 2024Due:
05 Mar 2024Completion:
05 Mar 2024Impacted Consumers
Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Date
28 June 2024
| Included changes | Affected REC Items | |
|---|---|---|
| R0043 | Commissioning of Works by the Crowded Meter Room Coordinator (CMRC) to Resolve Issues In Crowded Meter Rooms |
|
| R0158 | Amendment to the ‘Supplier Registration Report (MAP)’ report methodology | |
| R0160 | Electricity Supply to Hydrogen Electrolysers |
|
| R0064 | Creating a Meter Operator Agent and MOCoP Installer |
|
| R0070 | Provision of Enduring Test Environments |
|
Documents
| Name | Version | Last updated | Actions |
|---|---|---|---|
| 1.0 | 16 Nov 2026 | ||
| 1.0 | 02 Nov 2026 |
Implementation Status
Date Raised
REC Decision Maker
Solution Development
Proposed solution summary
- As a CSS User I want access to a CSS Test Environment, to enable me to test my systems and processes ahead of the implementation of complex or significant changes, so that I can identify any issues prior to go-live.
- As the SO, I want clarity on the obligations placed on me regarding the provision and maintenance of CSS Test Environments and data, so that I can meet my obligations and provide CSS Users and Service Providers with access to appropriate Test Environments.
- As a Switching Data Service Provider (SDSP), I want clarity on the obligations placed on me regarding the provision and maintenance of Test Environments and data, so that I can meet my obligations to test CSS changes. As a Switching Data Service Provider (SDSP), I want access to a CSS Test Environment, to enable me to test my systems and processes ahead of the implementation of complex or significant changes, so that I can identify any issues and address prior to go-live.
Proposed Solution Document
Document title
R0070 legal text v1.0 - Published with Impact Assessment
Upload document
R0070 legal text v1.0 - Published with Impact Assessment.docx
Archive
Off
Document title
R0070 Legal Text v2.0 - Published with Preliminary Change Report
Upload document
R0070 legal text v2.0.pdf
Archive
Off
Document title
R0070 - Legal Text v3.0 - Approved for Implementation
Upload document
R0070 legal text v3.0.pdf
Archive
Off
Document title
REC Category 3 - Environment Management Plan
Upload document
REC Cat 3 Environment Management Plan v0.6 - Published with Impact Assessment.docx
Archive
Off
Document title
REC Category 3 Test Data Management Plan
Upload document
REC Cat 3 Test Data Management Plan v0.6 - Published with Impact Assessment.docx
Archive
Off
Problem Statement
For specific types of changes, industry system testing will be required to ensure the end-to-end Switching processes will work as expected following implementation. If Test Environments and Test Data are not available, CSS Users will not be able to complete testing to confirm their systems will operate correctly in the live environment. The REC currently doesn’t define specific obligations on Service Providers regarding enduring test systems and Test Data for Switching processes. The lack of specific obligations may impact the availability of appropriate Test Environments. This could impact the progression of improvements to Switching processes that require a technical change.
Stages Selection
SME
SME Role
Lead Technical Analyst
SME User
beth.brown@capgemini.com
R0070 Initial Assessment Report v1.0 (Approved)
R0070 - Preliminary Change Report (Approved 23.01.2024)
R0070 - Change Proposal Plan v2.0 (Approved)
R0070 - Change Proposal Form
R0070 - Consolidated Impact Assessment Responses
R0070 - Consolidated Consultation Responses
R0070 - Final Change Report V2.0 (Post-Vote) 05.03.2024
Company Name
-
Review status
Review required
Introduction of CSS refresh functionality
Date of latest update
Type
Change
ID
R0067
Change Category
Change Path
Priority
Urgent
No
Latest Update
06/12/2023- This Change was implemented as part of the 6 December 2023 Extraordinary Release
Summary
CSS Market Messages sent by the Central Switching Service (CSS) to Switching Data Service Providers (SDSP) are either not being received, being received after Gate Closure, or are being received out of the order that they were originally sent in. This Change Proposal seeks to introduce a refresh functionality to mitigate these issues.
Change Plan
Solution Analysis and Development
Completed
Start:
29 Aug 2022Due:
19 Oct 2022Completion:
19 Oct 2022Service Provider Impact Assessment
Completed
Start:
19 Oct 2022Due:
29 Mar 2023Completion:
29 Mar 2023Consultation
Completed
Start:
11 Apr 2023Due:
09 May 2023Completion:
28 Apr 2023Preliminary Change Report Issued
Completed
Start:
29 Mar 2023Due:
11 Apr 2023Completion:
05 Apr 2023Final Change Report Issued
Completed
Start:
Due:
Completion:
21 Jun 2023Responsible Committee Decision
Completed
Start:
09 May 2023Due:
28 Jun 2023Completion:
28 Jul 2023Impacted Consumers
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Date
06 December 2023
| Included changes | Affected REC Items | |
|---|---|---|
| R0118 | Review of Schedule 12 and processes to manage access to data |
|
| R0128 | Removal of CSS Business Rule 1177 to reflect OFAF optionality | |
| R0136 | Change to REC Schedule 22 Market Stabilisation Charge (MSC) | |
| R0149 | Updates to the EES API Interface Specification | |
| R0067 | Introduction of CSS refresh functionality |
Documents
| Name | Version | Last updated | Actions |
|---|---|---|---|
| 1.0 | 02 Nov 2026 | ||
| 1.0 | 02 Nov 2026 |
Implementation Status
Date Raised
Fuel
REC Decision Maker
Solution Development
Proposed solution summary
- As a Consumer, I want the Switching process to work successfully, so that I can switch Energy Supplier without delays or issues.
- As the CSS Provider I want the messages I send to SDSPs to be received and processed successfully, so that there is no interruption to the Switching process or the Consumers’ Switching experience. As the CSS Provider, I want the functionality to be available for SDSPs to automatically resolve issues when messages are not received in the correct order or are received after Gate Closure, so that this work does not have to be done manually.
- As an SDSP, I want to be able to detect when I have not received the expected CSS messages, so that I am able to request that the missing messages are sent to me to process. As an SDSP I want to be able to request a refresh of CSS messages when they are not received in the correct order or they are received after Gate Closure, so that I am able to maintain an accurate reflection of the current Switch status and minimise impacts on CSS Users and Consumers.
Proposed Solution Document
Document title
R0067 - Legal Text at PCR
Upload document
R0067 - Legal Text at PCR.zip
Archive
Off
Document title
R0067 - Legal Text at FCR
Upload document
R0067 - Legal Text at FCR.zip
Archive
Off
Document title
R0067 - Cost Benefit Analysis and Conclusions v3.0
Upload document
R0067 - Cost Benefit Analysis and Conclusions v3.0.pdf
Archive
Off
Problem Statement
CSS messages not received by the SDSPs in the order they were sent or received, or after Gate Closure, can be difficult to detect and often require significant manual effort to resolve. This issue can directly impact Consumer switching experiences causing disruption and possible delays.
Stages Selection
SME
SME Role
Lead Technical Analyst
R0067 - Change Proposal Form
R0067 - Consolidated Consultation Responses
R0067 - Change Proposal Plan v1.0
R0067 - Initial Assessment Report v1.0
R0067 - Change Proposal Plan v2.0 (Approved) 07.03.2023
R0067 - Change Proposal Plan v3.0 04.04.2023
R0067 - Preliminary Change Report v2.0 (Issued for Consultation) 14.04.2023
R0067 - Final Change Report (Post-Vote) 28.06.2023
Company Name
-
Review status
Review required
Resolution of invalid CSS data by Data Owners
Date of latest update
Type
Change
ID
R0061
Change Category
Change Path
Priority
Urgent
No
Latest Update
04 March 2024 - Change has been withdrawn following implementation of a solution outside of the REC Change Process. 10WD window to adopt change will close on 18 March 2024.
Summary
Data is sent via the Supplier or MEM to update MPRS, which is then sent to CSS. If the data is considered invalid at CSS, an error is returned to MPRS. MPRS is the conduit of data from the Suppliers & MEMs to CSS, and ERDAs are not responsible for the data, therefore only the supplier/MEM can correct the data. The incidents must be put on hold until the owner of the data corrects the issue, this is to prevent SLA breaches. SLAs does not apply to the Supplier/MEM explicitly, so the incidents remain in the DNOs/IDNOs queue with the need to chase every few days to prevent the incident being closed. The responsibility for the incidents should be on the data owners (Suppliers/MEMs).
Change Plan
Solution Analysis and Development
Completed
Start:
22 Aug 2022Due:
15 Aug 2023Completion:
15 Aug 2023Service Provider Impact Assessment Due
Completed
Start:
15 Aug 2023Due:
19 Oct 2023Completion:
19 Oct 2023Status
Implementation Status
Date Raised
Fuel
REC Decision Maker
Solution Development
Proposed solution summary
- As a Consumer, I want data relating to my energy supply to be accurate, so that I can have a consistent and faultless switching experience. As a Consumer, I want any data issues related to my switch to be resolved quickly and by the party responsible, to ensure a fast and efficient switching experience.
- As a DNO, I want my service level requirements to be reflective of my data ownership responsibilities, so that data queries can be resolved more efficiently. As the CSS Service Desk provider, I want my tickets to be allocated to the most appropriate party able to resolve them.
Proposed Solution Document
Document title
R0061 Solution - Service Desk Guidance Article
Archive
Off
Problem Statement
DNO/iDNOs are obligated to resolve data mismatches identified by the CSS during the switch process. However, they are unable to do so in cases where the Supplier/MEM owns data required to resolve the mismatch. Tickets assigned to the DNO (via MPRS) are therefore not going to the party best placed to resolve them, resulting in DNOs chasing the incident resolution every few days to prevent them being closed incorrectly.
Stages Selection
SME
SME Role
Lead Technical Analyst
R0061 - Change Proposal Form
R0061 - Initial Assessment Report v1.0 (Approved) - 18.07.2023
R0061 - Change Proposal Plan v1.0 (Approved) - 18.07.2023
R0061 Change Proposal Re-Plan (Approved) v1.0 - 19.10.23
Company Name
St Clements Services
Review status
Review required