Post-MHHS Full Transition Complete (M15) REC updates
Date of latest update
Type
Issue
ID
I0325
Change Category
Other Industry Codes impacted
Change Path
Priority
Urgent
No
Latest Update
21/07/2026 - On 21 July 2026, the REC Change Panel voted to approve the Change Report (Proposal Plan) for I0325.
Summary
The REC was updated, primarily through R0209 and R0241, to add requirements that support the transition to, and enduring operation of the MHHS arrangements. As part of the transition, each impacted Metering Point will be migrated using processes defined in Codes, including the REC. Once this migration activity is complete, the legacy and transitional arrangements will become redundant and should be removed from the REC to support its efficient operation
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
Retention of redundant obligations within the REC would make it more complex to navigate for Market Participants and could cause confusion on the obligations that are in effect to support the efficient operation of the Great British Energy retail market. It is also worth noting that until Ofgem formally closes the MHHS Significant Code Review (SCR), this REC Issue could potentially impact that SCR.
Stages Selection
Stages Selection
SME
SME Role
Lead Technical Analyst
SME Role
Lead Assurance Analyst
I0325 submission form
I0325 Scope list
Company Name
-
Review status
Review required
Enabling transparency of the CRS Provider’s REC service level performance
Date of latest update
Type
Change
ID
R0272
Change Category
Change Path
Priority
Urgent
No
Latest Update
This Change Proposal has been implemented as part of the February 2026 REC Release.
Summary
RECCo regularly reports on the performance of REC Service Providers in relation to their activities under the REC. However, there is currently no formal agreement to permit the publication of CRS performance measures between the CRS Provider and RECCo. Due to the multi-Party agreement, the REC does not specifically address the publication of this performance data. Instead, RECCo are operating under an informal understanding with the CRS Provider, which means there is a possibility that publication may be delayed or not agreed to in a given month. RECCo is dependent on the CRS Provider’s approval for each publication, which can cause delays. This approval could also be withheld at any point.
Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Status
Implementation Date
27 February 2026
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- An update to the REC Schedule 6 – Performance Assurance.
Proposed Solution Document
Document title
R0272 Approved legal text (26.01.2026)
Archive
Off
Problem Statement
Unlike REC Service Providers, there is currently no formal agreement in place between the CRS Provider and RECCo to publish details about the CRS Provider’s performance. RECCo is therefore dependent on the CRS Provider’s approval for each publication. Not only could there be delays in RECCo’s reporting, but the approval could also be withheld at any point, preventing RECCo’s reporting.
Stages Selection
SME
SME Role
Lead Technical Analyst
SME Role
Lead Assurance Analyst
SME User
vaishnsharma@deloitte.co.uk
I0272 Change Proposal Form
R0272 Consolidated Consultation responses V1.0
Company Name
-
Review status
Review required
Schedule 25 - Central Switching Service 1.3
– Implemented on
Loading...
Schedule 25 - Central Switching Service 1.2
– Implemented on
Loading...
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
CSS Message Time Stamping
Date of latest update
Type
Change
ID
R0107
Urgent
No
Latest Update
11/08/2023 - This Change Proposal has been withdrawn. During the progression of the Preliminary Impact Assessment work, it was found that an existing data item ‘EventDate’ could be leveraged to address the issue stated in the Change Proposal. R107 will be open for adoption until 25/08/2023.
Summary
Empty
Change Plan
Test
In Progress
Start:
14 Apr 2023Due:
19 Mar 2026Completion:
19 Mar 2026Impacted Consumers
Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Date of Update to Priority
Solution Development
Stages Selection
SME
SME Role
Lead Technical Analyst
SME User
caroline.milner@capgemini.com
R0107 - Change Proposal Form
Company Name
DCC
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
Schedule 25 - Central Switching Service 1.1
– Implemented on
Loading...
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