Resolution of invalid CSS data by Data Owners
Summary
Data is sent via the Supplier or MEM to update MPRS, which is then sent to CSS. If the data is considered invalid at CSS, an error is returned to MPRS. MPRS is the conduit of data from the Suppliers & MEMs to CSS, and ERDAs are not responsible for the data, therefore only the supplier/MEM can correct the data. The incidents must be put on hold until the owner of the data corrects the issue, this is to prevent SLA breaches. SLAs does not apply to the Supplier/MEM explicitly, so the incidents remain in the DNOs/IDNOs queue with the need to chase every few days to prevent the incident being closed. The responsibility for the incidents should be on the data owners (Suppliers/MEMs).
Latest update and next planned activity
Date of latest update
Latest Update
04 March 2024 - Change has been withdrawn following implementation of a solution outside of the REC Change Process. 10WD window to adopt change will close on 18 March 2024.
Impacts Overview
Impacted Consumers
Electricity
Impacted REC Parties and Market Participants
Energy Supplier
Distribution Network Operator
Impacted REC Documents
Schedule 26 - Switching Service Management
Impacted REC Services
Central Switching Service (CSS)
Other Industry Codes impacted
Balancing and Settlement Code (BSC)
Priority and rationale
Standard
Priority last updated on 29 May 2026
Solution development
Problem Statement
DNO/iDNOs are obligated to resolve data mismatches identified by the CSS during the switch process. However, they are unable to do so in cases where the Supplier/MEM owns data required to resolve the mismatch. Tickets assigned to the DNO (via MPRS) are therefore not going to the party best placed to resolve them, resulting in DNOs chasing the incident resolution every few days to prevent them being closed incorrectly.
Proposed solution summary
- 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.
No documents available.
Change Plan
Solution Analysis and Development
Completed
Start:
22 Aug 2022Due:
15 Aug 2023Completion:
15 Aug 2023Service Provider Impact Assessment Due
Completed
Start:
15 Aug 2023Due:
19 Oct 2023Completion:
19 Oct 2023Original submission
Change details
Daniel Tadecicco - St Clements Services
22 Aug 2022
Change details
Resolution of invalid CSS data by Data Owners
Data is sent via the supplier or MEM to update MPRS which is then sent to CSS. If the data is considered invalid at CSS, an error is returned to MPRS. An incident is then raised by the DNO/iDNO and send the detail of the invalid data to the supplier/MEM. MPRS is the conduit of data from the suppliers & MEMs to CSS and are not responsible for the data, therefore only the supplier/MEM can correct the data. The incidents must be put on hold until the DNOs/IDNOs get an answer from the owner of the data to prevent SLA breaches. As the SLA does not apply to the supplier/MEM explicitly, there is no pressure on them to provide the data, so the incidents remain in the DNOs/IDNOs queue with the need to chase every few days to prevent the incident being closed. The responsibility for the incidents should be on the suppliers (also with responsibility for MEMs) – and therefore the incidents be assigned directly to them instead of the DNOs/IDNOs
Network Operators are being asigned tickets for Supplier and MEM Data Issues. The SLA is on the Network Operator however, they are unable to resolve the issue as the data is owned by the Supplier or MEM and must be corrected by the Supplier or MEM using a data flow into MPRS or raising a BSCP604 manual ammendment request. As Network Operators cannot resolve these issues, the ticket and SLA should be assigned to the Data Owner as defined in BSCP604 4.1
CSS Service Desk Incidents relating to Supplier or MEM Data held within ERDA must be assigned to the Data Owner not the ERDA operator. SLAs must also be applied the Data Owner.
BSCP604 defines who owns what data in SMRS (ERDA/MPRS)
Impacts
Electricity
Switching experience
-
Schedule 26 - Switching Service Management
-
No details provided
-
No details provided
-
No details provided
-
No details provided
-
Central Switching Service (CSS)
-
Energy Suppliers, Distribution Network Operators
-
Balancing and Settlement Code (BSC)
-
-
No details provided
Priority & timing
No
-
-
-
No details provided
-
Activity
Proposed solution summary changed to 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 resolve…
Proposed solution summary changed to 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..
Show moreOrphaned SME: Lead Technical Analyst has been allocated as SME.