Addition of key information to all Service Now tickets

Date of latest update
Type
Change
ID
R0063
Change Category
Change Path
Priority
Urgent
No
Latest Update
The code elements of this change were implemented on the 12 April 2024. The technical solution will be delivered as part of the June 2024 REC Release.
Summary
This Change seeks to improve the key business information, required by the DNOs, included in the SNOW tickets produced by CSS Service Desk for CSS Asynchronously rejected messages
Proposer
Chris Price
Change Plan

Solution Analysis and Development

Completed

Start:

22 Aug 2022

Due:

07 Feb 2023

Completion:

07 Feb 2023

Service Provider Impact Assessment - Preliminary

Completed

Start:

07 Feb 2023

Due:

20 Mar 2023

Completion:

20 Mar 2023

Service Provider Detailed Impact Assessments

Completed

Start:

20 Mar 2023

Due:

10 Jul 2023

Completion:

27 Jun 2023

Preliminary Change Report issued

Completed

Start:

10 Jul 2023

Due:

14 Jul 2023

Completion:

14 Jul 2023

Responsible Committee review

Completed

Start:

14 Jul 2023

Due:

26 Jul 2023

Completion:

26 Jul 2023

Consultation trigger

Completed

Start:

26 Jul 2023

Due:

28 Jul 2023

Completion:

28 Jul 2023

Consultation close

Completed

Start:

28 Jul 2023

Due:

18 Aug 2023

Completion:

18 Aug 2023

Final Change Report issued

Completed

Start:

18 Aug 2023

Due:

15 Sep 2023

Completion:

14 Sep 2023

Responsible Committee decision

Completed

Start:

15 Sep 2023

Due:

27 Sep 2023

Completion:

27 Sep 2023
Status
Implementation Date
Status Live
EMAR Version 12.04.2024_live
Included changes Affected REC Items
R0105 Review of ONAGE SLAs
  • Schedule 14 - Metering Operations
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
  1. 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.
  2. 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.
  3. 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.
Proposed Solution Document
Document title
Schedule 26 - Switching Service Management_R0063_FCR 15.09.2023
Archive
Off
Problem Statement
The SNOW tickets received by ERDS and GRDS for messages that CSS has asynchronously rejected (e.g., for business rule reasons) currently do not contain the relevant data for the SDSPs to triage and take any necessary action to resolve the underlying issue(s).This may delay the resolution of the SNOW tickets, potentially having an impact on aConsumers Switch.
SME
SME Role
Lead Technical Analyst
R0063 - Change Proposal Form
R0063 - Change Proposal Plan v1.0 (Approved)
R0063 - Initial Assessment Report v1.0 (Approved)
R0063 - Change Proposal Plan v2.0 (Approved) 21.02.2023
R0063 - Extension to Change Plan 2.0 (Approved) 04.04.2023
R0063 - Preliminary Change Report v1.0 (Approved) 26.07.2023
R0063 - Consolidated Consultation Responses
R0063 - Final Change Report v2.0 (Approved) 27.09.2023
Company Name
-
Review status
Review required

Removal of ERDA meteringPointEnergyFlow change restriction

Date of latest update
Type
Change
ID
R0062
Change Category
Change Path
Priority
Urgent
No
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.*
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
Proposer
Daniel Tadecicco
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
Status
Implementation Date
Status Live
EMAR Version 12.04.2024_live
Included changes Affected REC Items
R0105 Review of ONAGE SLAs
  • Schedule 14 - Metering Operations
Implementation Status
Date Raised
REC Decision Maker
Lead Analyst
Harriet Truss
Date of Update to Priority
Solution Development
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.
Proposed Solution Document
Document title
R0062 - Solution Development Report 13.10.2023
Archive
Off
Document title
R0062 - Solution Development Report v3.0 06.12.2023
Archive
Off
Document title
R0062 Draft Legal text 07.12.2023
Archive
Off
Document title
R0062 - Approved Legal Text 20.02.2024
Archive
Off
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.
SME
SME Role
Lead Technical Analyst
R0062 - Change Proposal Form
R0062 Removal of ERDA meteringPointEnergyFlow change restriction
R0062 - Change Proposal Plan v1.0 (Approved) 04.07.2023
R0062 - Initial Assessment Report v1.0 (Approved) 04.07.2023
R0062 Consolidated Impact Assessment Responses v1.0 07.12.2023
R0062 Preliminary Change Report v1.0 (Approved) 19.12.2023
R0062 Consolidated Consultation Responses v1.0 PUBLIC
R0062 - Final Change Report (Post-Vote) v2.0 20.02.2024
Company Name
-
Review status
Review required

Resolution of invalid CSS data by Data Owners

Date of latest update
Type
Change
ID
R0061
Change Category
Other Industry Codes impacted
Change Path
Priority
Urgent
No
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.
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).
Proposer
Elise Handy
Change Plan

Solution Analysis and Development

Completed

Start:

22 Aug 2022

Due:

15 Aug 2023

Completion:

15 Aug 2023

Service Provider Impact Assessment Due

Completed

Start:

15 Aug 2023

Due:

19 Oct 2023

Completion:

19 Oct 2023
Impacted Consumers
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
  1. 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.
  2. 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.
Proposed Solution Document
Document title
R0061 Solution - Service Desk Guidance Article
Archive
Off
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.
Stages Selection
SME
SME Role
Lead Technical Analyst
R0061 - Change Proposal Form
R0061 - Initial Assessment Report v1.0 (Approved) - 18.07.2023
R0061 - Change Proposal Plan v1.0 (Approved) - 18.07.2023
R0061 Change Proposal Re-Plan (Approved) v1.0 - 19.10.23
Company Name
St Clements Services
Review status
Review required

ERDS Service Definition timezone correction

Date of latest update
Type
Change
ID
R0060
Change Category
Change Path
Priority
Urgent
No
Latest Update
This Change Proposal was implemented as part of the 7 November 2025 REC Release.
Summary
This change seeks to specify timezones within the ERDS Service Definition. For example: Data received by the ERDA shall be included within the ERDS Total Daily Processing on the basis that all data received prior to 23:00hrs is made available to the SMRA, EES Provider or CSS Provider (as applicable) by 06:00hrs the following Working Day. Data received after 23:00hrs will be made available to the SMRA, EES Provider or CSS Provider (as applicable) by the second Working Day
Proposer
Daniel Tadecicco
Change Plan

Change Proposal Plan and Impact Assessment Report Published

Completed

Start:

22 Aug 2022

Due:

18 Jun 2024

Completion:

18 Jun 2024

Change report and Consultation issued

Completed

Start:

18 Jun 2024

Due:

28 Jun 2024

Completion:

27 Jun 2024

Consultation closed

Completed

Start:

28 Jun 2024

Due:

19 Jul 2024

Completion:

19 Jul 2024

Responsible Committee decision

Completed

Start:

19 Jul 2024

Due:

28 Aug 2024

Completion:

28 Aug 2024

Appeal Window Closure

Not Started

Start:

28 Aug 2024

Due:

12 Sep 2024

Completion:

Impacted Consumers
Impacted REC Parties and Market Participants
Status
Implementation Date
Status Live
EMAR Version 07.11.2025_live
Included changes Affected REC Items
R0003 Market-wide Half-Hourly Settlement Implementation
Implementation Status
Date Raised
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
  1. As a Supplier, I want to have confidence that the data in the systems is aligned and accurate.
  2. As ERDS Provider, I want to be able to provide accurate and appropriately labelled data that can be aligned with data from other systems.
Proposed Solution Document
Document title
R0060 Proposed legal text for decision 15.08.24.zip
Archive
Off
Document title
R0060 Proposed legal text 27.06.24
Archive
Off
Document title
R0060 Legal Text ERDS Service Definition v1.0 06.06.2024
Archive
Off
Document title
R0060 Approved legal text 28.08.24
Archive
Off
Problem Statement
The ERDS Service Definition does not specify the time with a specified time zone. This has led to some instances of MPRS close of day running at 22:00GMT instead of 23:00GMT. A confirmation of time zone is required within the ERDS Service Definition to negate any confusion or delays in flow processing and systems becoming misaligned.
SME
SME Role
Lead Assurance Analyst
SME User
beth.brown@capgemini.com
SME Role
Lead Assurance Analyst
R0060 - Change Proposal Form
R0060 Consolidated RFI Responses v1.0 (05.03.2024)
R0060 Change Proposal Plan (Approved) v1.0 18.06.2024
R0060 - Initial Assessment Report v1.0 (Approved) 18.06.2024
R0060 Preliminary Change Report v1.0 (For Consultation) 27.06.2024
R0060 Consolidated Consultation Responses v1.0 (15.08.24)
R0060 Change Report (Final Recommendation - Approved) v2.0
Company Name
St Clements Services
Review status
Review required

Maintenance of Qualification Schedule Change

Date of latest update
Type
Change
ID
R0059
Change Category
Change Path
Priority
Urgent
No
Latest Update
03/11/23 - This change was implemented on 03 November 2023 as part of the November 2023 REC Release
Summary
This change seeks to clarify, strengthen and simplify a number of requirements within REC Schedule 9 – Qualification and Maintenance.
Proposer
Georgina Scott-Picton
Change Plan

Solution Development

Completed

Start:

05 Aug 2022

Due:

01 Mar 2023

Completion:

01 Mar 2023

Impact Assessment Start

Completed

Start:

01 Mar 2023

Due:

10 Mar 2023

Completion:

10 Mar 2023

Impact Assessment End

Completed

Start:

10 Mar 2023

Due:

24 Mar 2023

Completion:

24 Mar 2023

Preliminary Change Report Issued

Completed

Start:

24 Mar 2023

Due:

14 Apr 2023

Completion:

14 Apr 2023

Responsible Committee Review

Completed

Start:

14 Apr 2023

Due:

25 Apr 2023

Completion:

25 Apr 2023

Consultation Start

Completed

Start:

25 Apr 2023

Due:

28 Apr 2023

Completion:

28 Apr 2023

Consultation End

Completed

Start:

28 Apr 2023

Due:

22 May 2023

Completion:

22 May 2023

Final Change Report Issued

Completed

Start:

22 May 2023

Due:

16 Jun 2023

Completion:

15 Jun 2023

Responsible Committee Decision

Completed

Start:

16 Jun 2023

Due:

27 Jun 2023

Completion:

27 Jun 2023

Appeal Window Closure

Not Started

Start:

27 Jun 2023

Due:

11 Jul 2023

Completion:

Impacted REC Parties and Market Participants
Status
Implementation Date
Status Live
EMAR Version 03.11.2023_live

Documents

Name Version Last updated Actions
317 bytes
Version 1.0 - 08 Jun 2026 PDF - 317 bytes
1.0 08 Jun 2026
317 bytes
Version 1.0 - 08 Jun 2026 PDF - 317 bytes
1.0 08 Jun 2026
Implementation Status
Date Raised
REC Decision Maker
Lead Analyst
Jonathan Holland
Date of Update to Priority
Solution Development
Proposed solution summary
  1. As an Energy Supplier, DNO, GT, MEM and REC Service User, I want to understand precisely what obligations apply to me under the Schedule 9 – Qualification and Maintenance, so that I can provide the required information to the Code Manager in a timely manner and be compliant.
  2. As the REC Code Manager, I want REC Parties and REC Service Users to have a clear understanding of the information they need to submit relating to the maintenance of their qualification, so that necessary information can be submitted for review and consideration in the most efficient way.
Proposed Solution Document
Document title
R0059 - Draft legal text for IA v1.0 10.03.2023
Archive
Off
Document title
R0059 - Draft legal text for Consultation v1.0 14.04.2023
Archive
Off
Document title
R0059 - Draft legal text for FCR v1.0 01.06.2023
Archive
Off
Document title
R0059 - Final approved draft legal text v1.0 27.06.2023
Archive
Off
Document title
EMAR Link - R0059 - Draft legal text for FCR v1.0 01.06.2023
Archive
Off
Problem Statement
REC Service Users are required to submit Maintenance of Qualification Annual Statements to the Code Manager, the requirements differ depending on the User category. The lack of clear obligations for REC Service Users surrounding the Maintenance of Qualification reporting, set out in Schedule 9 – Qualification and Maintenance results in missing or partially completed submissions. Considerable time is spent by the Code Manager requesting and following up on individual submissions.
R0059 - Change Proposal Form
R0059 - Change Proposal Plan v1.0 (Approved) 07.02.2023
R0059 - Initial Assessment Report v1.0 (Approved) 07.02.2023
R0059 - Impact Assessment Responses V1.0 14.04.2023
R0059 - Preliminary Change Report v1.0 (approved) 25.04.2023
R0059 - Consolidated Consultation Responses v1.0 23.05.2023
R0059 - Final Change Report v2.0 (post-vote) 27.06.23
Company Name
-
Review status
Review required

REC Services Procurement Clarification

Date of latest update
Type
Change
ID
R0058
Priority
Urgent
No
Latest Update
04/10/2023 - Following the approval of R0138, this change has been withdrawn.
Summary
This change proposes amendments to Clause 5.3 of the Main Body, to clarify that all provision of REC Services to the REC Service Users (including the Centralised Registration Service is procured by, and from, the CRS Provider) and are procured from the REC Service Providers by RECCo.
Proposer
admin
Impacted REC Documents
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Date of Update to Priority
Solution Development
Stages Selection
R0058 - Change Proposal Form
Proposed legal text submitted with the CP
Company Name
-
Review status
Review required

Clarification of Supplier of Last Resort Obligations under the REC

Date of latest update
Type
Change
ID
R0057
Change Category
Change Path
Priority
Urgent
No
Latest Update
04/08/2023 - Change Proposal has been withdrawn as agreed with the Proposer. The Problem Statement was addressed through C3-0047 - Updates to PAB Procedures.
Summary
Within Schedule 19 – Market Exit and Supplier of Last Resort there is currently no consideration of circumstances where the Replacement Supplier is unable to fulfil its REC obligations in respect of Consumers transferred to them, due to them having little or no control over the processes of the failed supplier or it’s administrator. This change seeks to define when the Replacement Supplier is responsible for obligations relating to the Consumers gained through a Supplier of Last Resort (SoLR) Process.
Proposer
admin
Impacted Consumers
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
  1. As a Consumer when my Energy Supplier goes out of business and I am transferred to a Replacement Supplier, I want my supply transfer to be handled quickly and have confidence that my new Supplier has all the necessary data to set up my account and bill me correctly from the transfer date, and if the Replacement Supplier fails to provide the expected level of service they will be appropriately held accountable.
  2. As a Replacement Supplier, I want the limitations affecting my ability to meet my REC obligations to be understood by the REC Code Manager and the Performance Assurance Board, so that any breaches of obligations are considered fairly and any limitations are taken into consideration.
  3. As the Code Manager I want to apply appropriate and proportionate Performance Assurance Techniques, taking in to account the ability of a Replacement Supplier to meet their obligations under the REC.
Proposed Solution Document
Document title
R0057 Draft Legal Text
Archive
Off
Problem Statement
Currently, Replacement Suppliers are responsible for all obligations of the failed supplier from the date and time set out in the Last Resort Supply Direction, this includes a period of time prior to Consumer accounts transferring to the Replacement Supplier’s systems, limiting their ability to fulfil these obligations. This means that a Replacement Supplier may experience issues with the Performance Assurance obligations for which they are responsible, but do not have direct control over. Any breaches of obligations by a Replacement Supplier need to be considered fairly and any limitations the Replacement Supplier may face are taken into consideration.
Stages Selection
R0057 - Change Proposal Form
R0057 - Solution Options
R0057 - Consolidated Impact Assessment Responses
R0057 - Change Proposal Plan v1.0
R0057 - Initial Assessment Report v1.0 (Approved)
R0057 - Preliminary Change Report V1.0 (Approved)
Company Name
EDF
Review status
Review required

EES/GES Additional Service Request for Housing Associations to be added to the Data Access Matrix

Date of latest update
Type
Change
ID
R0056
Change Category
Change Path
Priority
Urgent
No
Latest Update
21/11/24 - Change Proposal withdrawn.
Summary
Housing Associations need to validate supply point information to ensure that they have the most up to date and accurate data against each property in their portfolio and also to complement their internal safety inspection processes. This change has been raised to enable Housing Associations to have access to data in EES and GES, to understand and confirm which of their properties contain live supply points, the meter locations, asset data and last inspection checks. This will also enable Housing Associations to update the industry where gas safety information is not accurate against their site data.
Proposer
Fay Morris
Status
Implementation Status
Date Raised
Fuel
Date of Update to Priority
Solution Development
Stages Selection
HA REC Requested Data Items.xlsx
Company Name
-
Review status
Review required

Switching Operator Outage Notification Lead time

Date of latest update
Type
Change
ID
R0055
Change Category
Change Path
Priority
Urgent
No
Latest Update
30/11/2022 - The REC Technical Expert Panel voted to approve R0055 for implementation on 24 February 2023.
Summary
Within the Switching Operator Service Definition, the Central Switching Service (CSS) Provider is required to provide 10 Working Days’ (WDs) notice of planned system outages. However, within the CSS Provider’s processes and the Switching Operator Change Management Process Category 3 document, an 8 WD lead time is set out. This change seeks to address this discrepancy.
Proposer
Cordelia Grey
Change Plan

Service Provider Impact Assessment

Completed

Start:

06 Jul 2022

Due:

19 Aug 2022

Completion:

19 Sep 2022

Party Impact Assessment

Completed

Start:

19 Aug 2022

Due:

26 Aug 2022

Completion:

13 Sep 2022

Preliminary Change Report Issued

Completed

Start:

26 Aug 2022

Due:

14 Oct 2022

Completion:

14 Oct 2022

Consultation Issued

Completed

Start:

14 Oct 2022

Due:

14 Oct 2022

Completion:

14 Oct 2022

Final Change Report Issued

Completed

Start:

14 Oct 2022

Due:

18 Nov 2022

Completion:

18 Nov 2022

Responsible Committee Decision

Not Started

Start:

18 Nov 2022

Due:

30 Nov 2022

Completion:

Status
Implementation Date
Status Live
EMAR Version 24.02.2023_live
Included changes Affected REC Items
R0130 Updates to the Data Access Matrix
  • Schedule 12 - Data Access
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
  1. As the CSS Provider, I want the service levels to be consistently defined across relevant REC Products. This will ensure that I am clear on the lead time I need to provide for planned outages and can meet the defined service level.
  2. As a CSS User, I want to understand how much notice I will get for planned outages of the CSS, so I am able to appropriately plan my activity reliant on this service.
  3. As a Switching Data Service Provider, I want to understand how much notice I will get for planned outages of the CSS. This will ensure I am able to appropriately plan my Operational Switching Service Changes and associated activities.
Proposed Solution Document
Document title
R0055 - Proposed Legal Text
Archive
Off
Problem Statement
Across REC products there is an inconsistency in the defined lead time for the CSS Provider to provide notification of scheduled maintenance and system outages. This may result in uncertainty for Switching Data Service Providers around when they should submit an Operational Switching Service Change. This is to ensure there is sufficient lead time for any change to be included within a planned maintenance release, and for CSS Users planning their operational activity around CSS availability.
SME
SME Role
Lead Technical Analyst
SME User
beth.brown@capgemini.com
R0055 - Change Proposal Plan v1.0 (Approved)
R0055 - Initial Assessment Report v1.0 (Approved)
R0055 - Consolidated Consultation Responses
R0055 - Preliminary Change Report (Published for Consultation) v1.0
R0055 - Final Change Report v1.0 (Approved)
Company Name
DCC
Review status
Review required

EES Access for Virtual Lead Parties

Date of latest update
Type
Change
ID
R0054
Change Category
Change Path
Priority
Urgent
No
Latest Update
03/04/2023 - The Data Access Matrix changes went live on 04 November 2022, the technical changes to EES were implemented alongside R0022 on 03 April 2023.
Summary
This Change Proposal seeks to allow Virtual Lead Parties (VLP) access to the Electricity Enquiry Service (EES), to allow them to efficiently register their customers for balancing services under the Balancing and Settlement Code (BSC).
Proposer
Ann Perry
Change Plan

Service Provider Impact Assessment

Completed

Start:

17 Jun 2022

Due:

22 Jul 2022

Completion:

22 Aug 2022

Preliminary Change Report Issued

Completed

Start:

22 Jul 2022

Due:

02 Sep 2022

Completion:

02 Sep 2022

Consultation Issued

Completed

Start:

02 Sep 2022

Due:

02 Sep 2022

Completion:

02 Sep 2022

Consultation Complete

Completed

Start:

02 Sep 2022

Due:

16 Sep 2022

Completion:

16 Sep 2022

Final Change Report Issued

Completed

Start:

16 Sep 2022

Due:

14 Oct 2022

Completion:

14 Oct 2022

Responsible Committee Decision

Completed

Start:

14 Oct 2022

Due:

26 Oct 2022

Completion:

26 Oct 2022
Impacted Consumers
Impacted REC Services
Status
Implementation Date
Status Live
EMAR Version 01.04.2023_live
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
  1. As an Energy Consumer, I want my VLP to have access to the data needed to correctly register me in a timely manner, so there aren’t delays in the delivery of my service.
  2. As a VLP, I want to have access to all the data I need to register my customers so I can deliver the service they have requested, without delay.
  3. As a VLP, I want to be able to use the EES to find the MPAN of a customer using their address information, to enable me to reliably gather this data to without delay or further engagement with my customer.
Proposed Solution Document
Document title
R0054 - Draft DAM Change
Archive
Off
Document title
R0054 - Draft Legal Text
Archive
Off
Problem Statement
VLPs are required to provide their customer’s MPAN as part of the registration process, as per the Balancing and Settlement Code (BSC). VLPs do not currently have access to the EES to enable an MPAN search and they have no reliable means to acquire the MPAN, other than asking their customer to provide it. This could potentially lead to delays in the registration process and may result in an increased risk of inaccurate data, detrimentally impacting the service VLPs are able to provide to their customers.
R0054 - Initial Assessment Report v1.0 (Approved)
R0054 - Change Proposal Plan v1.0 (Approved)
R0054 - Preliminary Change Report v1.0 (Published for Consultation)
R0054 - Non-Confidential Consultation Responses
R0054 - Final Change Report v2.0
Company Name
-
Review status
Review required