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 Services
Impacted REC Parties and Market Participants
Status
Implementation Date
27 June 2025
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
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
Archive
Off
Document title
CSS Interface Design Specification v8.9.0 R0080 - REDLINE
Archive
Off
Document title
CSS Failed To Deliver Detailed Design (R0080) v1.3 (19.06.2024)
Archive
Off
Document title
Business Data Validation Rules v1.5.0 R0080 - REDLINE
Archive
Off
Document title
Schedule 24_Switching Data Management v1.2_R0080 Draft (19.06.2024)
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
DNOs notifying Suppliers about Crossed Meters
Date of latest update
Type
Change
ID
R0076
Priority
Urgent
No
Latest Update
28/05/2024 - R0076 has been withdrawn as the issue was addressed through R0121 - SDEP Review Improvements (1) - Process Types. The adoption window is closed.
Summary
The Change seeks to introduce a way for the DNOs to raise a crossed meter issue with the Supplier, in a way that directly feeds into the Supplier’s list of crossed meter issues. The supplier will be required to feed back progress to the DNO who has raised the issue with them, this should be defined as a process within the REC.
Impacted Consumers
Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Fuel
Date of Update to Priority
Solution Development
Stages Selection
R0076 - Change Proposal Form v1.0
Company Name
-
Review status
Review required
Introduction of a new Meter Asset Condition Code
Date of latest update
Type
Change
ID
R0072
Other Industry Codes impacted
Priority
Urgent
No
Latest Update
19/09/2024 - Change Proposal R0072 has been rejected and raised to Ofgem to consider. Despite earlier acceptance, the Code Manager believes that the proposal is not relevant to the REC and cannot progress any further.
Summary
This change seeks to introduce a new Asset Condition Code where further investigation is required by a Distribution Network Operator, where is there suspected asbestos in the metal encased cut-out
Impacted Consumers
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Fuel
Date of Update to Priority
Solution Development
Stages Selection
R0072 - Change Proposal Form
Company Name
Consumer
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
Implementation Status
Date Raised
REC Decision Maker
Date of Update to Priority
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
Archive
Off
Document title
R0070 Legal Text v2.0 - Published with Preliminary Change Report
Archive
Off
Document title
R0070 - Legal Text v3.0 - Approved for Implementation
Archive
Off
Document title
REC Category 3 - Environment Management Plan
Archive
Off
Document title
REC Category 3 Test Data Management Plan
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 | |
|---|---|---|
| R0106 | Performance Assurance Report Catalogue V5.1 |
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
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
Archive
Off
Document title
R0067 - Legal Text at FCR
Archive
Off
Document title
R0067 - Cost Benefit Analysis and Conclusions v3.0
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
Creating a Meter Operator Agent and MOCoP Installer
Date of latest update
Type
Change
ID
R0064
Change Category
Other Industry Codes impacted
Change Path
Priority
Urgent
No
Latest Update
28/06/2024 - Change implemented as part of the June 2024 REC Release
Summary
This Change Proposal seeks to clarify the obligations of each type of metering provider by reintroducing the distinction between Meter Operator Agents and MOCOPA Meter Installers which was removed by Retail Code Consolidation. At Retail Code Consolidation these organisations were merged into a new category, Metering Equipment Managers, which also included gas metering providers. Whilst both types of organisation can provide metering services, not all MEM obligations in the REC apply to both organisations.
Change Plan
Solution analysis and development
Completed
Start:
22 Aug 2022Due:
14 Jul 2023Completion:
13 Jul 2023Service Impact assessment commenced
Completed
Start:
14 Jul 2023Due:
14 Jul 2023Completion:
14 Jul 2023Impact Assessment Period Ended
Completed
Start:
09 Oct 2023Due:
03 Nov 2023Completion:
03 Nov 2023Preliminary Change Report issued
Completed
Start:
03 Nov 2023Due:
24 Nov 2023Completion:
24 Nov 2023Consultation issued
Completed
Start:
24 Nov 2023Due:
07 Dec 2023Completion:
07 Dec 2023Final Change report issued
Completed
Start:
07 Dec 2023Due:
26 Jan 2024Completion:
26 Jan 2024REC Change Panel decision
Completed
Start:
26 Jan 2024Due:
06 Feb 2024Completion:
06 Feb 2024Appeal Window closed
Completed
Start:
06 Feb 2024Due:
20 Feb 2024Completion:
20 Feb 2024Draft Legal Text Changes (Including Legal Review)
Completed
Start:
11 Aug 2023Due:
15 Sep 2023Completion:
15 Sep 2023Service Provider Impact Assessment Completed
Completed
Start:
14 Jul 2023Due:
11 Aug 2023Completion:
11 Aug 2023Impact Assessment Period Started
Completed
Start:
15 Sep 2023Due:
09 Oct 2023Completion:
06 Oct 2023Impacted Consumers
Impacted REC Documents
Status
Implementation Date
28 June 2024
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- As an electricity MEM, I want to be clear on the obligations I need to meet, based on the type of metering activity I complete. I want to meet my obligations efficiently and effectively and without the need to seek additional input/advice from the Code Manager.
- As the Code Manager, I want to be able to differentiate between electricity MEMs based on the type of activity they are responsible for and their interaction with central systems, so that I can engage appropriately. I need to be clear on the obligations that each MEM should be meeting and the performance reporting that should be provided.
Proposed Solution Document
Document title
R0064 - DRAFT legal text 24.11.2023
Archive
Off
Document title
R0064 - Roles Version F for Impact Assessment 4.10.2023
Archive
Off
Problem Statement
The REC currently groups all electricity metering providers within the MEM category. Previously, under the Master Registration Agreement (MRA) they were either classified as Meter Operator Agent or MOCOPA Meter Installers. Not all MEM obligations in the REC are intended to apply to both types of organisations. This can result in ambiguity on the obligations set out in the REC that need to be met by the different types of electricity MEM, not being able to target information to REC Parties appropriately and MEMs not being clear on their new entrant or Maintenance of Qualification obligations.
Stages Selection
SME
SME Role
Lead Technical Analyst
SME User
rosalind.timperley
R0064 - Change Proposal Form
R0064 - Change Proposal Plan v1.0 (Approved)
R0064 - Initial Assessment Report v1.0 (Approved)
R0064 - Change Proposal Plan v2.0 (Approved) 21.02.2023
R0064 - Change Proposal Plan v3.0 (Approved) 23.6.2023
R0064 - Change Proposal Plan v4.0 (Approved) 14.8.2023
R0064 - Change Proposal Plan v5.0 (Approved) 14.09.2023
R0064 - Change Proposal Plan v6.0 (Approved) 10.11.2023
Consolidated Impact Assessment Responses 29.11.2023
R0064 - Preliminary Change Report - V1.1 (Approved) 05.12.2023
R0064 - Consolidated Consultation Responses
R0064 - Final Change Report v1.0 (Approved)
Company Name
-
Review status
Review required
Resolution of invalid CSS data by Data Owners
Date of latest update
Type
Change
ID
R0061
Change Category
Other Industry Codes impacted
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 2023Impacted Consumers
Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
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
ERDS Service Definition timezone correction
Date of latest update
Type
Change
ID
R0060
Change Category
Change Path
Priority
Urgent
No
Latest Update
This Change Proposal was implemented as part of the 7 November 2025 REC Release.
Summary
This change seeks to specify timezones within the ERDS Service Definition. For example: Data received by the ERDA shall be included within the ERDS Total Daily Processing on the basis that all data received prior to 23:00hrs is made available to the SMRA, EES Provider or CSS Provider (as applicable) by 06:00hrs the following Working Day. Data received after 23:00hrs will be made available to the SMRA, EES Provider or CSS Provider (as applicable) by the second Working Day
Change Plan
Change Proposal Plan and Impact Assessment Report Published
Completed
Start:
22 Aug 2022Due:
18 Jun 2024Completion:
18 Jun 2024Change report and Consultation issued
Completed
Start:
18 Jun 2024Due:
28 Jun 2024Completion:
27 Jun 2024Consultation closed
Completed
Start:
28 Jun 2024Due:
19 Jul 2024Completion:
19 Jul 2024Responsible Committee decision
Completed
Start:
19 Jul 2024Due:
28 Aug 2024Completion:
28 Aug 2024Appeal Window Closure
Not Started
Start:
28 Aug 2024Due:
12 Sep 2024Completion:
Impacted Consumers
Impacted REC Parties and Market Participants
Status
Implementation Date
07 November 2025
| Included changes | Affected REC Items | |
|---|---|---|
| R0003 | Market-wide Half-Hourly Settlement Implementation |
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- As a Supplier, I want to have confidence that the data in the systems is aligned and accurate.
- As ERDS Provider, I want to be able to provide accurate and appropriately labelled data that can be aligned with data from other systems.
Proposed Solution Document
Document title
R0060 Proposed legal text for decision 15.08.24.zip
Archive
Off
Document title
R0060 Proposed legal text 27.06.24
Archive
Off
Document title
R0060 Legal Text ERDS Service Definition v1.0 06.06.2024
Archive
Off
Document title
R0060 Approved legal text 28.08.24
Archive
Off
Problem Statement
The ERDS Service Definition does not specify the time with a specified time zone. This has led to some instances of MPRS close of day running at 22:00GMT instead of 23:00GMT. A confirmation of time zone is required within the ERDS Service Definition to negate any confusion or delays in flow processing and systems becoming misaligned.
Stages Selection
SME
SME Role
Lead Assurance Analyst
SME User
beth.brown@capgemini.com
SME Role
Lead Assurance Analyst
R0060 - Change Proposal Form
R0060 Consolidated RFI Responses v1.0 (05.03.2024)
R0060 Change Proposal Plan (Approved) v1.0 18.06.2024
R0060 - Initial Assessment Report v1.0 (Approved) 18.06.2024
R0060 Preliminary Change Report v1.0 (For Consultation) 27.06.2024
R0060 Consolidated Consultation Responses v1.0 (15.08.24)
R0060 Change Report (Final Recommendation - Approved) v2.0
Company Name
St Clements Services
Review status
Review required
Clarification of Supplier of Last Resort Obligations under the REC
Date of latest update
Type
Change
ID
R0057
Change Category
Change Path
Priority
Urgent
No
Latest Update
04/08/2023 - Change Proposal has been withdrawn as agreed with the Proposer. The Problem Statement was addressed through C3-0047 - Updates to PAB Procedures.
Summary
Within Schedule 19 – Market Exit and Supplier of Last Resort there is currently no consideration of circumstances where the Replacement Supplier is unable to fulfil its REC obligations in respect of Consumers transferred to them, due to them having little or no control over the processes of the failed supplier or it’s administrator. This change seeks to define when the Replacement Supplier is responsible for obligations relating to the Consumers gained through a Supplier of Last Resort (SoLR) Process.
Impacted Consumers
Impacted REC Documents
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- As a Consumer when my Energy Supplier goes out of business and I am transferred to a Replacement Supplier, I want my supply transfer to be handled quickly and have confidence that my new Supplier has all the necessary data to set up my account and bill me correctly from the transfer date, and if the Replacement Supplier fails to provide the expected level of service they will be appropriately held accountable.
- As a Replacement Supplier, I want the limitations affecting my ability to meet my REC obligations to be understood by the REC Code Manager and the Performance Assurance Board, so that any breaches of obligations are considered fairly and any limitations are taken into consideration.
- As the Code Manager I want to apply appropriate and proportionate Performance Assurance Techniques, taking in to account the ability of a Replacement Supplier to meet their obligations under the REC.
Proposed Solution Document
Document title
R0057 Draft Legal Text
Archive
Off
Problem Statement
Currently, Replacement Suppliers are responsible for all obligations of the failed supplier from the date and time set out in the Last Resort Supply Direction, this includes a period of time prior to Consumer accounts transferring to the Replacement Supplier’s systems, limiting their ability to fulfil these obligations. This means that a Replacement Supplier may experience issues with the Performance Assurance obligations for which they are responsible, but do not have direct control over. Any breaches of obligations by a Replacement Supplier need to be considered fairly and any limitations the Replacement Supplier may face are taken into consideration.
Stages Selection
R0057 - Change Proposal Form
R0057 - Solution Options
R0057 - Consolidated Impact Assessment Responses
R0057 - Change Proposal Plan v1.0
R0057 - Initial Assessment Report v1.0 (Approved)
R0057 - Preliminary Change Report V1.0 (Approved)
Company Name
EDF
Review status
Review required
EES Access for Virtual Lead Parties
Date of latest update
Type
Change
ID
R0054
Change Category
Change Path
Priority
Urgent
No
Latest Update
03/04/2023 - The Data Access Matrix changes went live on 04 November 2022, the technical changes to EES were implemented alongside R0022 on 03 April 2023.
Summary
This Change Proposal seeks to allow Virtual Lead Parties (VLP) access to the Electricity Enquiry Service (EES), to allow them to efficiently register their customers for balancing services under the Balancing and Settlement Code (BSC).
Change Plan
Service Provider Impact Assessment
Completed
Start:
17 Jun 2022Due:
22 Jul 2022Completion:
22 Aug 2022Preliminary Change Report Issued
Completed
Start:
22 Jul 2022Due:
02 Sep 2022Completion:
02 Sep 2022Consultation Issued
Completed
Start:
02 Sep 2022Due:
02 Sep 2022Completion:
02 Sep 2022Consultation Complete
Completed
Start:
02 Sep 2022Due:
16 Sep 2022Completion:
16 Sep 2022Final Change Report Issued
Completed
Start:
16 Sep 2022Due:
14 Oct 2022Completion:
14 Oct 2022Responsible Committee Decision
Completed
Start:
14 Oct 2022Due:
26 Oct 2022Completion:
26 Oct 2022Impacted Consumers
Impacted REC Documents
Impacted REC Services
Status
Implementation Date
01 April 2023
| Included changes | Affected REC Items | |
|---|---|---|
| R0100 | Update to Error Handling Documents |
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- As an Energy Consumer, I want my VLP to have access to the data needed to correctly register me in a timely manner, so there aren’t delays in the delivery of my service.
- As a VLP, I want to have access to all the data I need to register my customers so I can deliver the service they have requested, without delay.
- As a VLP, I want to be able to use the EES to find the MPAN of a customer using their address information, to enable me to reliably gather this data to without delay or further engagement with my customer.
Proposed Solution Document
Document title
R0054 - Draft DAM Change
Archive
Off
Document title
R0054 - Draft Legal Text
Archive
Off
Problem Statement
VLPs are required to provide their customer’s MPAN as part of the registration process, as per the Balancing and Settlement Code (BSC). VLPs do not currently have access to the EES to enable an MPAN search and they have no reliable means to acquire the MPAN, other than asking their customer to provide it. This could potentially lead to delays in the registration process and may result in an increased risk of inaccurate data, detrimentally impacting the service VLPs are able to provide to their customers.
Stages Selection
R0054 - Initial Assessment Report v1.0 (Approved)
R0054 - Change Proposal Plan v1.0 (Approved)
R0054 - Preliminary Change Report v1.0 (Published for Consultation)
R0054 - Non-Confidential Consultation Responses
R0054 - Final Change Report v2.0
Company Name
-
Review status
Review required