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
Frequency and content of CSS reports on switching via the DCC portal
Date of latest update
Type
Change
ID
R0115
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
This change has been raised by Ofgem to make updates to CSS reports provided by the Switching Operator; for these be provided on a weekly basis and be designed in such a way that only genuine Switches between Suppliers are reported. At present the latter is not possible as all switches at MPID level are reported with no indication of switching flows.
Change Plan
Preliminary Change Report published
Completed
Start:
27 Apr 2023Due:
15 Dec 2023Completion:
15 Dec 2023Consultation issued
Completed
Start:
15 Dec 2023Due:
15 Dec 2023Completion:
15 Dec 2023Consultation close
Completed
Start:
15 Dec 2023Due:
19 Jan 2024Completion:
19 Jan 2024Final Change Report published
Completed
Start:
19 Jan 2024Due:
26 Jan 2024Completion:
26 Jan 2024Responsible Committee Decision
Completed
Start:
26 Jan 2024Due:
06 Feb 2024Completion:
06 Feb 2024Send to Authority for determination
In Progress
Start:
06 Feb 2024Due:
07 Feb 2024Completion:
Impacted REC Documents
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 Ofgem to effectively monitor the market to ensure the right policy decisions are made.
- As Ofgem, I need accurate and timely data to ensure that I can make informed decisions on any interventions in relation to market stability.
Proposed Solution Document
Document title
Attachment A_R0115 Solution Requirements Matrix v2.0
Archive
Off
Document title
Attachment B_R0115 Report Templates v1.0
Archive
Off
Document title
Switching Operator (SO) Service Definition_redline 15.12.2023
Archive
Off
Problem Statement
Without appropriate reporting, Ofgem cannot effectively monitor the level of Switching in the market in a timely and accurate manner. This hinders its ability to act and inform any policy interventions in relation to market stability.
Stages Selection
SME
SME Role
Lead Technical Analyst
SME User
caroline.milner@capgemini.com
R0115 - Change Proposal Form
R0115 - Change Proposal Plan v2.0 (Approved) 05.12.2023
R0115 Initial Assessment Report v2.0 (Approved) 05.12.2023
R0115 - Preliminary Change Report v1.0 (Published for Consultation) 15.12.2023
R0115 - Consolidated Consultation Responses_Non Confidential (26.01.2024)
R0115 - Final Change Report v1.0 (Post-Vote) 06.02.2024
R0115 Authority Decision (23.04.2024)
Company Name
Ofgem
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
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
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 2025Impacted Consumers
Impacted REC Services
Status
Implementation Date
05 November 2027
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed Solution Document
Document title
R0096 Solution Development Document V1.0
Archive
Off
Document title
R0096 Detailed Design Document v1.0
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
10/04/2026 - Change has been taken of hold. This change will be triggered for a reassessment for Code Manager Impact on 14/04/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.
Impacted 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 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
Impacted 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
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.
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
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 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