Agile Reporting within CSS
Summary
As part of the impact assessment process for R0115, it was identified that it is very costly and time consuming to make reporting changes within the CSS architecture. As such, we would like to explore enabling agile reporting within the CSS ecosystem, by creating a functionality that consolidates all necessary data into a single, centralised database.
Latest update and next planned activity
Date of latest update
Latest Update
18/03/2026 - An update to plan has been published for consideration at the Technical Expert Panel on 25 March 26.
Impacts Overview
Impacted REC Parties and Market Participants
DCC
Impacted REC Documents
Schedule 5 - Change Management
Schedule 12 - Data Access
Schedule 24 - Switching Data Management
Impacted REC Services
Central Switching Service (CSS)
Priority and rationale
Standard
Priority last updated on 29 May 2026
Change Reports, Impact Assessments, Consultations and Documents
Change Reports
Solution development
Problem Statement
Current CSS arrangements mean that REC Changes designed to facilitate access to CSS data are more onerous that they need to be. Current arrangements are costly and have relatively long lead-times. This Issue seeks to explore changing the way that the CSS data can be accessed.
No documents available.
There is currently no Change Plan.
Original submission
Change details
- - -
21 Nov 2024
Change details
Agile Reporting within CSS
As part of the impact assessment process for R0115, it was identified that it is very costly and time consuming to make reporting changes within the CSS architecture. As such, we would like to explore enabling agile reporting within the CSS ecosystem, by creating a functionality that consolidates all necessary data into a single, centralised database.
Within the current CSS architecture, it is both costly and time-consuming to make reporting changes. R0115, for example, took over 1 year and 6 months from the change request being raised, to implementation, at a total cost of £126,307.64 for design, build, test and deployment. As such, end-users of the reports can potentially experience major delays on operations that rely on timely data. This can lead to frustration and decreased satisfaction. As the number of change request increases, the current CSS architecture may struggle to keep up with the increasing volume and complexity of reporting changes. This could exacerbate the existing problems and lead to even longer delays and higher costs. The significant resources required for each change request prevent other changes from being implemented and the resources could be better utilised elsewhere. The current system’s demands on time and money may divert resources from other strategic initiatives or innovations.
RTS propose exploring the implementation of agile reporting within the CSS ecosystem. Agile reporting would allow for more flexible and responsive updates to reports, reducing the time and cost associated with making changes. The desired solution involves creating a functionality that consolidates all necessary data into a single, centralised database. This database would be accessible to analysts, enabling them to generate the required reports efficiently and accurately. By having all the data in one place, analysts can easily access and manipulate the information they need, streamlining the reporting process and improving overall efficiency.
Initial discussions have taken place at two TCWs (technical change workshops) , held on the 01/10/24 and 05/11/24. The CSS provider has come forward with two potential solutions: • Option 1: Data publication to a centralised database for comprehensive reporting. • Option 2: Central reporting and intelligence platform for the CSS.
Impacts
No details provided
Trust and confidence, Other (please provide details in Additional information box below)
Deliver accurate data to consumers promptly.
Schedule 5 - Change Management, Schedule 12 - Data Access, Schedule 24 - Switching Data Management
-
No details provided
-
No details provided
-
No details provided
-
No details provided
-
Central Switching Service (CSS)
-
DCC
-
No details provided
-
-
No details provided
Priority & timing
No
-
-
-
No details provided
Trust and confidence, Other (please provide details in the Additional information box below)
Activity
Change report - Final Change Report has been updated to R0224 Change Report (Consultation) V1.1.pdf.
Status has been changed to Decision.
holly.law has been allocated as Lead Analyst.
Status has been changed to Solution Development.
holly.law has been allocated as Lead Analyst.
maxime.van-eyseren, vaishnsharma have been allocated as SME.