Creation of a Mechanism to Allow Third Parties to Report Objection Activity
Date of latest update
Type
Issue
ID
I0213
Change Category
Change Path
Priority
Urgent
No
Latest Update
15/07/2025 - The Code Manager has rejected Issue I0213. This Issue has been deemed out of scope of the REC and has been rejected following a legal review. This decision was ratified by the REC Change Panel at their meeting on 15 July 2025.
Summary
Presently only industry parties can raise the matter of non-compliant or unwarranted objections activity that a supplier may be participating in. This Issues has been raised to request RECCo to consider accepting notice and evidence (that can be acted upon) from qualifying 'non industry' parties, from third party consultants and brokers.
Change Plan
Proposal Plan Approved at REC Change Panel
Completed
Start:
Due:
Completion:
06 May 2025Impacted Consumers
Impacted REC Documents
Impacted REC Parties and Market Participants
Status
Status
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- I0213 has been raised with a suggestion that the Code Manager should consider accepting notice and evidence from qualifying non-industry Parties, including Third Party consultants and brokers (Third Party Intermediaries (TPIs)). A possible solution for this may include a new submission page, or form, on the REC Portal, that would allow Third Parties to submit evidence of non-compliant Objection activity.
Problem Statement
There is currently not a method for Third Parties, who may be involved in the Switching process, to report non-compliant Objection activity. Non-Compliant Objection activity can result in time consuming procedures for Consumers, creating unnecessary engagement with Energy Suppliers, and may result in a financial burden.
Stages Selection
Stages Selection
I0213 - Change Proposal Form
I0213 - Change Report (Proposal Plan) 25.04.2025 (Approved)
I0213 - Solution Development Report (for Party impact assessment) V1.0 (16.05.2025)
I0213 Consolidated Impact Assessment Responses V1.0 (Non-Confidential) 07.07.2025
Company Name
Energy Consultants Association
Review status
Review required
Review of the REC's Address Management Service
Date of latest update
Type
Issue
ID
I0200
Change Category
Change Path
Priority
Urgent
No
Latest Update
13/05/2026 - The REC Code Manager is establishing a new REC working group to support the progression of I0200 – Review of the REC’s Address Management Service. If you would like to attend the I0200 Working Group, please register your interest by contacting the Code Manager at change.management@recmanager.co.uk. The first meeting will take place in June 2026, with the exact date and time to be confirmed in due course and communicated via the REC Change Bulletin and via email to all those who register their interest.
Summary
Having the incorrect address can lead to a range of Consumer issues, including switching, billing and meter reading problems. The Meter Point Location (MPL) and Retail Energy Location (REL) have been added to the Code to resolve this issue. Whilst there had been progress resolving address data issues, there is not currently a mechanism to establish Code level targets for address improvement, resulting in around 2.8 million unmatched addresses.
Impacted Consumers
Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Status
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Problem Statement
There has been progress resolving address data issues, but there is no mechanism to clearly establish Code level targets for address improvement, or overall market performance.
Stages Selection
Stages Selection
SME
SME Role
Lead Assurance Analyst
SME User
amoden@deloitte.co.uk
I0200 - Improving Address Management Targets (Issue Form)
I0200 - Change Issues Group paper
I0200 - Change Report (Proposal Plan) V1.1 (Approved) 18.02.2025
I0200 - Update to Plan (Pre Approval) 14.04.2026
Company Name
REC 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.
Change Plan
Request for Information
Completed
Start:
03 Jun 2024Due:
05 Jul 2024Completion:
05 Jul 2024Change Issue Group
Completed
Start:
05 Jul 2024Due:
01 Aug 2024Completion:
01 Aug 2024Impacted Consumers
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Date
27 February 2026
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
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.
Stages Selection
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
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.
Impacted Consumers
Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Date
28 February 2025
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- 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.
- 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.
- Refresh and testing of Switching Operator’s (SO) incident related policies, processes, and procedures, to ensure they remain fit for purpose.
- 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)
Archive
Off
Document title
Central Switching Service (CSS) Service Definition (R0168 - Red-lining) 05.12.2024
Archive
Off
Document title
Switching Operator (SO) Service Definition (R0168 - Red-lining) 05.12.2024
Archive
Off
Document title
Schedule 26 - Switching Service Management Schedule (R0168 - Red-lining) 05.12.2024
Archive
Off
Document title
R0168 Draft Switching Operator Best Practice Document (V1.0 for Industry Consultation) 05.12.2024 (Word Version)
Archive
Off
Document title
R0168 Draft Switching Operator Best Practice Document (V1.0 for Industry Consultation) 05.12.2024 (PDF Version)
Archive
Off
Document title
R0168 - Change Report (for Consultation) 12.12.2024
Archive
Off
Document title
Schedule 26 - Switching Service Management Schedule (R0168 - Red-lining) 28.01.2025
Archive
Off
Document title
Central Switching Service (CSS) Service Definition (R0168 - Red-lining) 28.01.2025
Archive
Off
Document title
Switching Operator (SO) Service Definition (R0168 - Red-lining) 28.01.2025
Archive
Off
Document title
Major Switching Incident: Switching Operator Best Practice Document V0.2
Archive
Off
Document title
Major Switching Incident: Switching Operator Best Practice Evaluation Form V1.0
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.
Stages Selection
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
Implementation of Online Certificate Standard Protocol (OCSP) in addition to Certificate Revocation List (CRL).
Date of latest update
Type
Change
ID
R0151
Change Category
Change Path
Priority
Urgent
No
Latest Update
14/05/2024 - At the request of the proposer, this Change Proposal has now been withdrawn. The rationale for withdrawing the proposal was that the benefits afforded by this change will not be fully realised until 2026 (renew of digital certificates), and the risk profile around revoked certificates remains unchanged during this period. DCC recommend this change is revisited in 12 months, to allow sufficient time for review and resubmission ahead of any certificate renewal activities.
Summary
This Change seeks to make improvements to the Microsoft Azure Application Gateway module. A defect has been identified which requires the implementation of a manual/ customer workaround when checking the Certificate Revocation Lists (CRLs) systems within the Central Switching Service (CSS) to ensure certificates are revoked. This change seeks to remove the need to complete a manual workaround and implement a real-time certification validation capability.
Change Plan
Solution Analysis and Development
Completed
Start:
30 Oct 2023Due:
26 Jan 2024Completion:
26 Jan 2024Impacted 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
- The proposed solution is to roll out support for Online Certificate Standard Protocol (OCSP) in addition to Certificate Revocation List (CRL). The scope of the change will be: - Implementation of a central OCSP server and the update of the associated PKI processes to manage the Certificate Revocation. This will cover the TLS and JWS Certificate Revocation. - CSS implementation of Application Gateway will be reconfigured to include the OCSP functionality and server. - CSS change to implement the OCSP checking for the JWS certificates. - All new certificates that are issued will include the detail of the OCSP Server, as part of the migration approach all new certificates will have this information embedded. - All parties connecting to CSS have the relevant information for them to exploit the advanced features that OCSP introduces. The CRL checking functionality will be maintained so this change is an optional upgrade for any Systems that operate using Switching Key Infrastructure.
Problem Statement
There is currently a Microsoft Azure Application Gateway module defect against the checking of Certificate Revocation Lists (CRLs), with Microsoft stating that the CRL related defect will not be fixed. Consequently, any system within the CSS ecosystem, systems that use Switching Key Infrastructure (SWIKI), that have incorporated the Azure Application Gateway module to manage the TLS connection will have been required to implement a manual/custom workaround to ensure that certificates that are revoked are not allowed to establish a connection.
Stages Selection
SME
SME Role
Lead Technical Analyst
SME User
caroline.milner@capgemini.com
R0151 - Implementation of OCSP in addition to CRL
R0151 - Initial Assessment Report V2.0 (Approved) 06.02.2024
Company Name
Smart DCC
Review status
Review required
Annulment Definition
Date of latest update
Type
Change
ID
R0119
Change Category
Priority
Urgent
No
Latest Update
08/11/2024 - This Change Proposal has been implemented as part of the November 2024 REC Release.
Summary
Annulments are defined in the interpretations schedule as: Annulled means that a Registration has been annulled by the Losing Supplier pursuant to an Annulment Request. “Annulment” and similar expressions shall be interpreted accordingly. Annulment Request means the Registration Service Request from the Losing Supplier to terminate the progress of a Registration in accordance with Paragraph 10 of the Registration Services Schedule. The Registration Services Schedule does not define an annulment but sets out in para 10: A Losing Supplier must only submit an Annulment Request in respect of a Registration where the Losing Supplier is permitted to do so in accordance with its Energy Supply Licence. Unfortunately the Energy Supply Licence does not refer to annulments, making this term not clearly defined. REC Performance Assurance (RPA) have identified Parties using annulments when they should use other processes. The lack of a clear definition of what an annulment is could be a contributing factor to this.
Change Plan
Preliminary Change Report and Consultation Issued
Completed
Start:
17 May 2023Due:
31 May 2024Completion:
31 May 2024Final Change Report Issued
Completed
Start:
31 May 2024Due:
05 Jul 2024Completion:
05 Jul 2024Responsible Committee Decision
Not Started
Start:
05 Jul 2024Due:
16 Jul 2024Completion:
Authority Determination Requested
Not Started
Start:
16 Jul 2024Due:
17 Jul 2024Completion:
Impacted Consumers
Impacted REC Documents
Impacted REC Parties and Market Participants
Status
Implementation Date
08 November 2024
| Included changes | Affected REC Items | |
|---|---|---|
| R0105 | Review of ONAGE SLAs |
|
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed Solution Document
Document title
Extract: Schedule 23 - Registration Services (R0119 Draft Legal Text) - Published at PCR 31.05.2024
Archive
Off
Document title
Schedule 23 - Registration Services (R0119 Draft Legal Text) - Published at PCR 31.05.2024
Archive
Off
Document title
Schedule 1 - Interpretations and Definitions (R0119 Draft Legal Text) - Published at PCR 31.05.2024
Archive
Off
Document title
Schedule 1 - Interpretations and Definitions - R0119 (updated draft amendments at FCR) 05.07.2024
Archive
Off
Document title
Schedule 23 - Registration Services - R0119 (updated draft amendments at FCR) 05.07.2024
Archive
Off
Document title
Schedule 23 - Registration Services - R0119 (updated draft amendments at FCR) (Extract) 05.07.2024
Archive
Off
Document title
Schedule 1 - Interpretations and Definitions - R0119 (Recommended for Authority Approval) 16.07.2024
Archive
Off
Document title
Schedule 23 - Registration Services - R0119 (Recommended for Authority approval) 16.07.2024
Archive
Off
Document title
Schedule 23 - Registration Services - R0119 (Recommended for Authority approval) (Extract) 16.07.2024.docx
Archive
Off
Problem Statement
Parties are using annulments when they should use other processes, in particular the objection process. The lack of a clear definition of what an annulment is could be a contributing factor to this.
Stages Selection
SME
SME Role
Lead Assurance Analyst
R0119 - Change Proposal Form 17.05.2023
R0119 - Change Proposal Plan V1.0 (Approved)
R0119 - Initial Assessment Report V1.0 (Approved)
R0119 - Preliminary Change Report V1.0 (Published for Consultation) 31.05.2024
R0119 - Consolidated Consultation Responses V1.0 (25.06.2024)
R0119 - Final Change Report V2.0 (Post-Vote) 16.07.2024
R0119 - Authority Decision (10.09.2024)
Company Name
REC Code Manager
Review status
Review required
Data Specification updates and clarifications
Date of latest update
Type
Change
ID
R0113
Change Category
Change Path
Priority
Urgent
No
Latest Update
08/11/2024 - This Change Proposal has been implemented as part of the November 2024 REC Release.
Summary
It has been identified that gaps or misaligned references were transferred into the REC Data Specification at REC go-live. This Change Proposal seeks to fill these gaps and provide clarification for Parties. This will enable Parties to self-serve and reduce the risk of ambiguities in the current Data Specification resulting in incorrectly defined Market Messages. This change will update relevant legal text in the REC Data Specification to provide clarification and alignment from previous legacy documents to Parties. This will ensure existing Parties have a consistent understanding and new entrants are able to set up their systems appropriately.
Change Plan
PRELIMINARY CHANGE REPORT AND CONSULTATION ISSUED
Completed
Start:
20 Apr 2023Due:
24 May 2024Completion:
24 May 2024FINAL CHANGE REPORT ISSUED
Completed
Start:
24 May 2024Due:
24 Jul 2024Completion:
19 Jul 2024RESPONSIBLE COMMITTEE DECISION
Completed
Start:
24 Jul 2024Due:
31 Jul 2024Completion:
31 Jul 2024Impacted REC Parties and Market Participants
Status
Implementation Date
08 November 2024
| Included changes | Affected REC Items | |
|---|---|---|
| R0105 | Review of ONAGE SLAs |
|
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- As a Market Participant, I need the Data Specification to be clear and correct to ensure my systems are set-up appropriately and Market Messages are correctly defined.
- As a Market Participant, I need to understand any changes to the Data Specification that may impact my business, so I can engage in the change process and plan any required changes to my systems and processes.
Proposed Solution Document
Document title
R0113 Legal Text at FCR (19.07.2024)
Archive
Off
Document title
R0113 - Legal Text Guide (17.05.2024)
Archive
Off
Document title
R0113 Webinar Recording
Archive
Off
Problem Statement
There is a risk that the current ambiguities in the Data Specification could make it challenging for Parties to follow the Data Specification and result in Market Messages being sent that do not correctly reflect the rules of the Data Specification. This may result in Market Message rejections, which may have impacts for Consumers and other Market Participants.
Stages Selection
SME
SME Role
Lead Technical Analyst
SME Role
Lead Assurance Analyst
R0113 - Change Proposal Plan V1.0 (Approved)
R0113 - Initial Assessment Report v1.0 (Approved)
R0113 - Preliminary Change Report v1.0 (Published for Consultation) 24.05.2024
R0113 - Consolidated Consultation Responses_NON-CONFIDENTIAL (19.07.2024)
R0113 - Final Change Report (Approved) 31.07.2024
Company Name
-
Review status
Review required
Enabling Electricity Enquiry Service searches using a Unique Property Reference Number
Date of latest update
Type
Change
ID
R0108
Change Category
Change Path
Priority
Urgent
No
Latest Update
08/11/2024 - This Change Proposal has been implemented as part of the November 2024 REC Release.
Summary
Consumers that wish to utilise multi-channel switching services for gas, electricity, water, broadband, bank, home insurance etc. cannot make use of generic address-capture services for electricity switching as Unique Property Reference Number (UPRN) search functionality is not available within the Electricity Enquiry Service (EES).
Change Plan
Service Provider Impact Assessment window start
Completed
Start:
19 Apr 2023Due:
02 Oct 2023Completion:
02 Oct 2023Service Provider Impact Assessment window close
Completed
Start:
02 Oct 2023Due:
18 Dec 2023Completion:
18 Dec 2023Party Impact Assessment start
Completed
Start:
18 Dec 2023Due:
12 Jan 2024Completion:
12 Jan 2024Preliminary Change Report and Consultation issued
Completed
Start:
02 Feb 2024Due:
16 Feb 2024Completion:
16 Feb 2024Party Impact Assessment close
Completed
Start:
12 Jan 2024Due:
02 Feb 2024Completion:
02 Feb 2024Consultation close
Completed
Start:
16 Feb 2024Due:
08 Mar 2024Completion:
08 Mar 2024Final Change Report issued
Completed
Start:
08 Mar 2024Due:
15 Mar 2024Completion:
15 Mar 2024Responsible Committee decision
Completed
Start:
15 Mar 2024Due:
27 Mar 2024Completion:
27 Mar 2024Appeal window closure
Completed
Start:
27 Mar 2024Due:
12 Apr 2024Completion:
12 Apr 2024Impacted Consumers
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Date
08 November 2024
| Included changes | Affected REC Items | |
|---|---|---|
| R0105 | Review of ONAGE SLAs |
|
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- As a Consumer, I want to be able to switch my electricity easily and efficiently.
- As I Consumer, I want to be able to quote or switch my electricity as part of a packaged search.
- As a Supplier, I want Consumers to be able to search for quotes and switch efficiently.
- As an organisation providing multi-channel switching services, I want Consumers to be able to use one set of data when requesting quotes.
Proposed Solution Document
Document title
R0108 Requirements Specification v0.1
Archive
Off
Document title
Electricity Data Access Matrix_R0108 Draft
Archive
Off
Document title
EES API Interface Specification v3.1.6 - Redline
Archive
Off
Problem Statement
Consumers that wish to utilise multi-channel switching services, cannot benefit from the efficiencies of using a UPRN for the electricity Switch as the EES does not provide this functionality.
Stages Selection
SME
SME Role
Lead Technical Analyst
Change Proposal Form
R0108 - Change Proposal Plan (Approved) 17.10.2023
R0108 - Initial Assessment Report (Approved) 17.10.2023
R0108 Consolidated Party IA Responses v1.0 Non-confidential (16.02.2024)
R0108 - Preliminary Change Report v1.0 published for consultation (16.02.2024)
R0108 - Consolidated Consultation Responses_Non Confidential (15.03.2024)
R0108 - Final Change Report v2.0 Post-Vote (27.03.2024)
Company Name
GB Group plc
Review status
Review required
Central provision of DCC Technical Contacts for requesting test certificates
Date of latest update
Type
Change
ID
R0103
Change Category
Change Path
Priority
Urgent
Yes
Latest Update
19.09.2023 - approved for implementation in February 2024 Release
Summary
In order for central systems testing (including maintenance and emergency testing) to be undertaken by the Switching Operator, certificates from the SDSPs and CSS User communities are required to interact with CSS in the testing environments. The Switching Operator was able to issue certs to the simulator provider during the Switching Programme, but the replacement process via Service Now no longer allows this – instead placing onerous activity on Parties to collaborate with the Switching Operator to give them the ability to request certificates on their behalf. This change has been raised to ensure that test certificates are held at all times for enough parties to enable changes to be tested with enough simulation to replicate live operational scenarios. The solution proposed is that the Switching Operator can nominate Technical Contacts (TC) for all CSS Users, in order that certificates can be requested for simulators in the test environments. CSS Users would continue to be able to nominate / remove their own TCs as now (and be able to remove the Switching Operator-nominated Technical Contact), and would see all TCs listed on the Switching Portal.
Change Plan
Impact Assessment period - start date
Completed
Start:
23 Mar 2023Due:
19 May 2023Completion:
19 May 2023Impact Assessment period - end date
Completed
Start:
19 May 2023Due:
28 Jul 2023Completion:
28 Jul 2023Preliminary Change Report issued and consultation started
Completed
Start:
28 Jul 2023Due:
11 Aug 2023Completion:
11 Aug 2023Consultation end date
Completed
Start:
11 Aug 2023Due:
04 Sep 2023Completion:
04 Sep 2023Final Change Report issued
Completed
Start:
04 Sep 2023Due:
15 Sep 2023Completion:
08 Sep 2023Responsible Committee decision
Completed
Start:
15 Sep 2023Due:
22 Sep 2023Completion:
19 Sep 2023Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Date
23 February 2024
| Included changes | Affected REC Items | |
|---|---|---|
| R0100 | Update to Error Handling Documents |
Implementation Status
Date Raised
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- As the SO, I want sufficient simulators to be available in the test environments, so that I can test changes to CSS systems for all necessary scenarios
- As a CSS User, I want changes to the CSS systems to be robustly tested, so that implemented changes align to their design and deliver the planned benefits
- As a CSS User, I want to be able to manage my Technical Contacts, so that I am in control of my responsibilities under the REC
Proposed Solution Document
Document title
R0103 legal text changes for Party IA 22.06.2023
Archive
Off
Document title
R0103 legal text for PCR v1.0 11.08.2023
Archive
Off
Document title
R0103 - Legal text for FCR v1.0 08.09.2023
Archive
Off
Problem Statement
Due to certificate expiry, there are not currently sufficient test security certificates for connecting to CSS test environments and emulating CSS Users (simulators). The current process for CSS Users to request certificates is inefficient and is reliant on the CSS Users obtaining new certificates in a timely manner. Without sufficient test certificates, the Switching Operator may not be able to fully test changes to the CSS system.
Stages Selection
SME
SME Role
Lead Technical Analyst
SME User
beth.brown@capgemini.com
R0103 Change Proposal Form (downloadable version) 23.03.2023
R0103 legal text for IAR v1.0 26.05.2023
R0103 - Change Proposal Plan v1.0 (Approved) 06.06.2023
R0103 - Initial Assessment Report v1.0 (Approved) 06.06.2023
R0103 Consolidated Impact Assessment Responses v1.0 11.08.2023
R0103 - Preliminary change Report Consultation Responses consolidated 08.09.23
R0103 - Preliminary Change Report v1.0 11.08.2023
R0103 Final Change Report (Approved for Implementation) 19.09.2023
Company Name
-
Review status
Review required
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
| Included changes | Affected REC Items | |
|---|---|---|
| R0105 | Review of ONAGE SLAs |
|
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed Solution Document
Document title
R0099 Draft Legal Text v1.0 (20.03.2024)
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