Removal of ERDA meteringPointEnergyFlow change restriction

  • 1
    Initial Assessment
  • 2
    Solution Development
  • 3
    Consultation
  • 4
    Decision
  • 5
    Awaiting Implementation
  • 6
    Implemented
Step 6 of 6
Implemented
Summary
As part of the Faster Switching Programme Enactment Phase change CR-E37, a restriction was applied to Electricity Retail Data Agents (ERDAs) to prevent multiple changes being made to the RMP. Any errors can be rectified once in the lifetime of an RMP, back to the creation of the RMP. This change has been raised to allow ERDAs to make more than one change to Energy Flow to improve data accuracy without requiring a new RMP

Latest update and next planned activity

Date of latest update
Latest Update
This change was implemented on 12 April 2024. *This change is expected to have a direct impact on the Market-wide Half Hourly Settlement Design for it to be maintained in the enduring arrangements. The change has been approved as it has value for the interim period.*

Impacts Overview

Impacted Consumers
Non-Domestic Domestic
Impacted REC Parties and Market Participants
Electricity Distribution Network Operator (R) Energy Supplier (ES)
Impacted REC Documents
Schedule 27 - RMP Lifecycle
Impacted REC Services
Electricity Retail Data Service (ERDS)
Priority and rationale
Standard

Solution development

Problem Statement
To maintain accurate values for Settlement, DNOs must make regular changes to the LLFC Indicator in ERDS. Until June 2023, the meteringPointEnergyFlow has been tied to this Data Item, which has sometimes resulted in changes to the energy direction. For example, going from Import to Export. Where errors have been identified, the DNO needs to be able to correct meteringPointEnergyFlow back to the correct value to ensure data accuracy. The current restriction, to only one change of Energy Direction against an RMP, can be overcome through by terminating the existing RMP and creating a new RMP with the correct Metering Point Energy Flow value. This has a detrimental impact on the Consumer and Settlement. It is inconvenient for the Consumer to be assigned a new MPAN and Settlement relies on an accurate history that will be lost when a new MPAN is assigned.
Proposed solution summary
  1. As a Consumer, I want any metering data issues to be resolved without the need for a new MPAN to be created, so that I am able to reference my current MPAN in any discussions with my Energy Supplier or other Market Participants.
  2. As an ERDA, I want to be able to correct the Metering Point Energy Flow Data Item more than once, to remove the need for the termination of RMPs and the creation of new RMPs and to facilitate data accuracy. As an impacted Market Participant, I want to ensure good quality underlying data is available to support the transition to MHHS to avoid additional time and effort being spent fixing data quality issues during the migration period.
  3. As an Energy Supplier, I want data issues associated with the Metering Point Energy Flow to be resolved without the need to create a new RMP, so that my Settlement accuracy and performance is not impacted As an Energy Supplier, I want data issues associated with the Metering Point Energy Flow to be resolved without the need to create a new RMP, so that discussions I have with my customers are not unnecessarily confused by a change in RMP reference.
Solution documents
05 Jun 2026
05 Jun 2026
R0062 Draft Legal text 07.12.2023 05 Jun 2026 ZIP - 440.24 KB
05 Jun 2026
R0062 - Approved Legal Text 20.02.2024 05 Jun 2026 ZIP - 440.25 KB
05 Jun 2026
Change Plan

Solution analysis and development completed

Completed

Start:

22 Aug 2022

Due:

16 Aug 2023

Completion:

16 Aug 2023

Service Provider impact assessment started

Completed

Start:

16 Aug 2023

Due:

18 Aug 2023

Completion:

18 Aug 2023

Service Provider impact assessment completed

Completed

Start:

18 Aug 2023

Due:

25 Sep 2023

Completion:

25 Sep 2023

Party impact assessment issued

Completed

Start:

25 Sep 2023

Due:

19 Oct 2023

Completion:

13 Oct 2023

Party impact assessment closed

Completed

Start:

19 Oct 2023

Due:

09 Nov 2023

Completion:

03 Nov 2023

Preliminary Change Report issued

Completed

Start:

09 Nov 2023

Due:

08 Dec 2023

Completion:

07 Dec 2023

Responsible Committee review

Completed

Start:

08 Dec 2023

Due:

19 Dec 2023

Completion:

19 Dec 2023

Consultation issued

Completed

Start:

19 Dec 2023

Due:

22 Dec 2023

Completion:

22 Dec 2023

Consultation closed

Completed

Start:

22 Dec 2023

Due:

23 Jan 2024

Completion:

23 Jan 2024

Final Change Report issued

Completed

Start:

23 Jan 2024

Due:

09 Feb 2024

Completion:

08 Feb 2024

Responsible Committee decision

Completed

Start:

09 Feb 2024

Due:

20 Feb 2024

Completion:

20 Feb 2024

Appeal window closure

Completed

Start:

20 Feb 2024

Due:

06 Mar 2024

Completion:

06 Mar 2024

Original submission

Change details

Daniel Tadecicco - St Clements Services
22 Aug 2022

Change details

Removal of ERDA meteringPointEnergyFlow change restriction
MPRS (ERDA) currently derives the Energy Direction (meteringPointEnergyFlow DI90033) from the MS Specific LLF Class Indicator (DI50370) which is an attribute of Line Loss Factor Class. From June 2023, BSC CP1558 Energy Direction will become an independent data item. As part of the Faster Switching Programme Enactment Phase change CR-E37 a restriction was applied to ERDA (then MPAS) stating that: “Any change in RMP would also have to be highlighted to the customer to ensure there would be no consequential effect on their switching experience. If DNOs can rectify errors retrospectively, the possibility of this risk can be mitigated by implementing this change. Any errors can be rectified once in the lifetime of an RMP, back to the creation of the RMP.” The CSS validation enforces the Effective Date rule, where the Energy Flow must be back dated to the original Effective Date. However, CSS allows multiple changes to Energy Flow. This change looks to align ERDA with CSS and only enforce the Effective Date rule. Allowing LDSOs to make more than one change to Energy Flow to improve data accuracy without requiring a new RMP.
To maintain accurate values for Settlement LDSOs must make regular changes to the LLF Class in ERDA. As the meteringPointEnergyFlow is tied to this data item, this can sometimes result in changes to the Energy Direction e.g. going from Import to Export. Where errors have been identified, the LDSO needs to be able to correct the LLF Class and meteringPointEnergyFlow back to the correct value. The restriction to one change of Energy Flow is preventing LDSOs from correcting the data and improving data accuracy. The resolution of Terminating the RMP and Creating a new RMP with the correct Energy Flow value has a detrimental impact on the Customer and Settlement. It is inconvenient for the customer to be assigned a new MPAN and Settlement relies on an accurate history which will be lost when a new MPAN is assigned. MHHS BSC CP1558 introduces an independent meteringPointEnergyFlow data item. By allowing more than one correction to this data item in ERDA will facilitate cleansing of Energy Flow data in ERDA to ensure high accuracy ahead of MHHS Transition.
• Change REC Schedule 27 6.2 (c ) to allow more than one change to meteringPointEnergyFlow: o an Electricity Retail Data Agent correcting an error by making a change to the Metering Point Energy Flow within the life of the RMP (provided that a change can only be made on one occasion). In this instance, the Effective From Date of the updated event must be equal to the Effective From Date of the event being corrected; • Configuration change to ERDA to increase the Limit on meteringPointEnergyFlow changes from 1 to 99. o No code change is required to make this change as it is a user configurable setting in MPRS. • No change required to CSS as this validation is not applied in CSS. See JIRA DI-4644 for Landmark Impact.
JIRA DI-4644

Impacts

Electricity
Billing accuracy
-
Schedule 27 - RMP Lifecycle
REC Schedule 27 - RMP Lifecycle
No details provided
-
No details provided
-
No details provided
-
No details provided
-
No details provided
-
Distribution Network Operators
-
No details provided
-
-
No details provided

Priority & timing

No
There is no code change required to implement this change in ERDA (MPRS). Once the Schedule has been ammended the configuration can be applied in production. This will start improviding settlement accuracy right away.
Configuration to be deployed in production ASAP
-
No details provided
-

Activity

Proposed solution summary changed to As a Consumer, I want any metering data issues to be resolved without the need for a new MPAN to be created, so that I am able to reference my current MPAN in any discussions with my Energy Supplier or other Mark…
Show more
Implementation Date has been updated to 12 Apr 2024.
harriet.truss has been allocated as Lead Analyst.
Orphaned SME: Lead Technical Analyst has been allocated as SME.