CSS Message Regeneration Functionality
Update to Plan approved at Change Panel
Start:
Due:
Completion:
21 Oct 202505 November 2027
Uplift to CSS Maximum Demand Volumes during MHHS Migration Period
Solution Analysis and Development completed
Start:
08 Feb 2023Due:
06 Apr 2023Completion:
04 Apr 2023Service Provider Preliminary Impact Assessment period started
Start:
06 Apr 2023Due:
06 Apr 2023Completion:
04 Apr 2023Service Provider impact assessment period completed
Start:
06 Apr 2023Due:
23 Oct 2023Completion:
23 Oct 2023Preliminary Change Report issued
Start:
23 Oct 2023Due:
17 Nov 2023Completion:
17 Nov 2023Responsible Committee review
Start:
17 Nov 2023Due:
29 Nov 2023Completion:
29 Nov 2023Consultation issued
Start:
29 Nov 2023Due:
01 Dec 2023Completion:
01 Dec 2023Consultation closed
Start:
01 Dec 2023Due:
15 Dec 2023Completion:
15 Dec 2023Final Change Report issued
Start:
15 Dec 2023Due:
12 Jan 2024Completion:
12 Jan 2024Responsible Committee decision
Start:
12 Jan 2024Due:
24 Jan 2024Completion:
24 Jan 2024Appeal Window closure
Start:
24 Jan 2024Due:
08 Feb 2024Completion:
08 Feb 202428 March 2024
- As an Electricity Consumer, I want the migration of my MPAN to the new HH Settlement arrangements to be as smooth as possible, so that the service I receive from my Electricity Supplier or it’s appointed agents is not interrupted As an Electricity Consumer, I want my ability to switch to be impacted as little as possible by MHHS migration activities
- As the Switching Operator, I want to be prepared for the increased volumes expected during the MHHS Migration Period. As the ERDS Provider, I want the CSS to be able to manage the volume of messages being sent so that I can provide the service I am required to during the MHHS Migration Period
- As an Electricity Supplier, I want the MPANs I select to the new HH Settlement arrangements to complete their migration without undue delay, so that the service I provide to Consumers is impacted as little as possible and so that I can meet my migration obligations As a MEM, as part of migration I want my new appointment and my legacy de-appointment to occur within the planned timescales so that the services I provide are impacted as little as possible As a Data Service, as part of migration, I want my new appointment to occur within the planned timescales so that the services I provide can commence in a timely manner As a Data Collector, I want my legacy de-appointment to occur within the planned timescales so that I have a clear understanding and smooth ending to the service I provide
Alignment of Data Specification with Pre-REC Rules and Consequential Impacts on R0011 Legal Text
Solution Development
Start:
23 Jan 2023Due:
23 Feb 2023Completion:
23 Feb 2023Party Impact Assessment Issued
Start:
23 Feb 2023Due:
24 Feb 2023Completion:
24 Feb 2023Preliminary Change Report Issued
Start:
24 Feb 2023Due:
27 Mar 2023Completion:
24 Mar 2023Consultation Issued
Start:
27 Mar 2023Due:
27 Mar 2023Completion:
24 Mar 2023Final Change Report Issued
Start:
27 Mar 2023Due:
19 Apr 2023Completion:
19 Apr 2023Responsible Committee Decision
Start:
19 Apr 2023Due:
26 Apr 2023Completion:
30 June 2023
- As a Market Participant I want to have clarity on the format of Data Items within the Data Specification, so that my internal systems can be correctly configured to send and receive Data Items within Market Messages.
Make Shipper NExA values available on the GES portal
Initial Assessment and Change Proposal Plan issued
Start:
16 Jan 2023Due:
24 Mar 2023Completion:
24 Mar 2023Initial Assessment Report and Change Plan approved
Start:
24 Mar 2023Due:
04 Apr 2023Completion:
04 Apr 2023Service Provider Impact Assessment
Start:
04 Apr 2023Due:
25 Apr 2023Completion:
24 Apr 2023Party Impact Assessment
Start:
25 Apr 2023Due:
31 May 2023Completion:
31 May 2023Preliminary Change Report published
Start:
31 May 2023Due:
16 Jun 2023Completion:
16 Jun 2023Consultation
Start:
16 Jun 2023Due:
21 Jul 2023Completion:
21 Jul 2023Final Change Report published
Start:
21 Jul 2023Due:
18 Aug 2023Completion:
18 Aug 2023Responsible Committee decision
Start:
18 Aug 2023Due:
30 Aug 2023Completion:
30 Aug 202303 November 2023
| Included changes | Affected REC Items | |
|---|---|---|
| R0104 | Clarifying requirement for continuous billing following an Erroneous Switch |
Documents
| Name | Version | Last updated | Actions |
|---|---|---|---|
| 1.0 | 08 Jun 2026 | ||
| 1.0 | 08 Jun 2026 |
- As a Consumer, where I have entered a bi-lateral NExA with the relevant Transporter, I want my Shipper and Transporter to have access to all the data they need when capacity referrals to the Gas Transporters are required.
- As a Gas Transporter, I want the details of the NExA to be held in GES, to increase visibility of the existence of the NExA and to provide details of the offtake parameters.
- As a Gas Shipper, I need to understand both that a NExA exists, and that I have visibility of the offtake parameters relative to the site, so that I can ensure that I take the necessary actions to ensure the Consumer has the appropriate booked Supply Point Capacity.
Improvements to ‘Failed to Deliver’ CSS Messages
Service Provider Impact Assessment close
Start:
09 Nov 2022Due:
25 Jan 2024Completion:
25 Jan 2024Party Impact Assessment trigger
Start:
25 Jan 2024Due:
02 Feb 2024Completion:
02 Feb 2024Party Impact Assessment close
Start:
02 Feb 2024Due:
23 Feb 2024Completion:
23 Feb 2024Preliminary Change Report and Consultation issued
Start:
23 Feb 2024Due:
10 May 2024Completion:
10 May 2024Consultation close
Start:
10 May 2024Due:
03 Jun 2024Completion:
03 Jun 2024Responsible Committee Decision
Start:
24 Jul 2024Due:
31 Jul 2024Completion:
31 Jul 2024Final Change Report Issued
Start:
03 Jun 2024Due:
24 Jul 2024Completion:
19 Jul 202427 June 2025
- 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.
EMR Settlement Limited - additional access to EES
SERVICE PROVIDER IMPACT ASSESSMENT ISSUED
Start:
26 Oct 2022Due:
07 Jul 2023Completion:
11 Aug 2023PRELIMINARY CHANGE REPORT AND CONSULTATION ISSUED
Start:
07 Jul 2023Due:
18 Aug 2023Completion:
18 Aug 2023FINAL CHANGE REPORT ISSUED
Start:
18 Aug 2023Due:
08 Sep 2023Completion:
08 Sep 2023RESPONSIBLE COMMITTEE DECISION
Start:
08 Sep 2023Due:
15 Sep 2023Completion:
15 Sep 202329 September 2023
- As EMRS I want to have an appropriate understanding of the portfolio so that I am able to complete metering assessments and checks on Switches so that I can fulfil my role.
- As the EES Provider I want to be able to provide access to EMR Settlement Limited as set out in the Data Access Matrix.
Release of Community View Data Items to MEMs in GES
Service Provider Impact Assessment
Start:
05 Oct 2022Due:
21 Nov 2022Completion:
16 Dec 2022Party Impact Assessment
Start:
21 Nov 2022Due:
21 Nov 2022Completion:
18 Dec 2022Preliminary Change Report Issued
Start:
21 Nov 2022Due:
13 Jan 2023Completion:
13 Jan 2023Consultation closure
Start:
13 Jan 2023Due:
27 Jan 2023Completion:
27 Jan 2023Responsible Committee Decision
Start:
27 Jan 2023Due:
22 Feb 2023Completion:
22 Feb 202324 February 2023
| Included changes | Affected REC Items | |
|---|---|---|
| R0130 | Updates to the Data Access Matrix |
|
- As a Consumer, I want a Metering Equipment Manager to be able to access and validate my site details, ahead of their arrival on site for planned or emergency metering work, so that I do not experience any delays in work being completed and can have continuity of supply.
- As a MEM, I want access to sufficient data for sites where I am not the Appointed MEM, to enable me to complete pre-metering works validations of the site details, so I can undertake these works correctly and safely.
- As a MEM, I want access to data for sites where I am not the Appointed MEM, so I can confirm de-appointments and answer invoice validation queries.
Introduction of CSS refresh functionality
Solution Analysis and Development
Start:
29 Aug 2022Due:
19 Oct 2022Completion:
19 Oct 2022Service Provider Impact Assessment
Start:
19 Oct 2022Due:
29 Mar 2023Completion:
29 Mar 2023Consultation
Start:
11 Apr 2023Due:
09 May 2023Completion:
28 Apr 2023Preliminary Change Report Issued
Start:
29 Mar 2023Due:
11 Apr 2023Completion:
05 Apr 2023Final Change Report Issued
Start:
Due:
Completion:
21 Jun 2023Responsible Committee Decision
Start:
09 May 2023Due:
28 Jun 2023Completion:
28 Jul 202306 December 2023
| Included changes | Affected REC Items | |
|---|---|---|
| R0106 | Performance Assurance Report Catalogue V5.1 |
- 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.
Addition of key information to all Service Now tickets
Solution Analysis and Development
Start:
22 Aug 2022Due:
07 Feb 2023Completion:
07 Feb 2023Service Provider Impact Assessment - Preliminary
Start:
07 Feb 2023Due:
20 Mar 2023Completion:
20 Mar 2023Service Provider Detailed Impact Assessments
Start:
20 Mar 2023Due:
10 Jul 2023Completion:
27 Jun 2023Preliminary Change Report issued
Start:
10 Jul 2023Due:
14 Jul 2023Completion:
14 Jul 2023Responsible Committee review
Start:
14 Jul 2023Due:
26 Jul 2023Completion:
26 Jul 2023Consultation trigger
Start:
26 Jul 2023Due:
28 Jul 2023Completion:
28 Jul 2023Consultation close
Start:
28 Jul 2023Due:
18 Aug 2023Completion:
18 Aug 2023Final Change Report issued
Start:
18 Aug 2023Due:
15 Sep 2023Completion:
14 Sep 2023Responsible Committee decision
Start:
15 Sep 2023Due:
27 Sep 2023Completion:
27 Sep 202312 April 2024
| Included changes | Affected REC Items | |
|---|---|---|
| R0105 | Review of ONAGE SLAs |
|
- As a Consumer I want the Switch process to work efficiently and effectively, so that I can switch Energy Supplier without unnecessary delay or issues.
- As an ERDS and GRDS, I want to receive SNOW tickets that contain all of the relevant data to enable me to triage and resolve issues efficiently, so that Consumers do not experience unnecessary switching delays and I am able to meet my service level obligations.
- As the CSS Provider, I want the ERDS related SNOW tickets to contain all of the relevant data to enable the efficient resolution of issues without the need for a manual workaround to be utilised, so that Consumers do not experience unnecessary switching delays.
Resolution of invalid CSS data by Data Owners
Solution Analysis and Development
Start:
22 Aug 2022Due:
15 Aug 2023Completion:
15 Aug 2023Service Provider Impact Assessment Due
Start:
15 Aug 2023Due:
19 Oct 2023Completion:
19 Oct 2023- 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.