Introduction of SDEP and EES User Maintenance API
Summary
This Change Proposal is to introduce an Application Programming Interface (API) interface to allow: • SDEP Users to send/receive/respond automatically to messages through the Secure Data Exchange Portal (SDEP) • EES and Secure Data Exchange Service (SDES) Users to carry out automated Electricity Enquiry Service (EES) Authorised Person Maintenance
Latest update and next planned activity
Date of latest update
Latest Update
On the 24 August 2023, the Authority issued its decision to the REC Code Manager to reject an appeal raised
Impacts Overview
Impacted Consumers
Electricity
Impacted REC Parties and Market Participants
Energy Supplier
Distribution Network Operator
Impacted REC Services
Electricity Enquiry Service (EES)
Secure Data Exchange Service (SDES)
Priority and rationale
Standard
Priority last updated on 29 May 2026
Solution development
Problem Statement
It is not possible to automate the sending and receiving messages through the SDEP. It is also not possible to manage Authorised Person’s permissions in the EES and SDES in bulk where there is a high volume of changes required. This requires processes to be managed manually by an Authorised Person and doesn’t allow EES and SDES Users to identify more efficient ways of working.
Proposed solution summary
- As a consumer, I want to ensure the data held by my supplier and other industry parties is correct so that I receive accurate and timely bills so that I understand what I need to pay and by when with no surprises.
- As a consumer, I want to be able to switch my energy supply without experiencing significant delays whilst my new and old supplier resolve any issues. So that I can see the benefits of switching at the earliest opportunity.
- As an SDEP User, I want to be able to automate processes that use the SDEP, so I can meet my obligations as efficiently and effectively as possible. As an EES or SDES User, I want to be able to automate certain user maintenance requests, so I can manage user maintenance activities as efficiently as possible.
No documents available.
Change Plan
Initial Assessment Report published
Completed
Start:
08 Sep 2021Due:
25 Oct 2021Completion:
25 Oct 2021Analysis and Solution Development activity
Completed
Start:
25 Oct 2021Due:
15 Feb 2022Completion:
15 Feb 2022Service Provider Impact Assessment completion
Completed
Start:
15 Feb 2022Due:
04 Apr 2022Completion:
04 Apr 2022Preliminary Change Report issued
Completed
Start:
13 May 2022Due:
16 Dec 2022Completion:
16 Dec 2022Technical Expert Panel review
Completed
Start:
16 Dec 2022Due:
21 Dec 2022Completion:
21 Dec 2022Consultation Starts
Completed
Start:
21 Dec 2022Due:
23 Dec 2022Completion:
23 Dec 2022Consultation Ends
Completed
Start:
23 Dec 2022Due:
27 Jan 2023Completion:
27 Jan 2023Final Change Report issued
Completed
Start:
27 Jan 2023Due:
10 Feb 2023Completion:
10 Feb 2023Appeal Window Closure
Completed
Start:
22 Feb 2023Due:
15 Mar 2023Completion:
15 Mar 2023Party Impact Assessment Issued
Completed
Start:
04 Apr 2022Due:
13 May 2022Completion:
13 May 2022Technical Expert Panel review
Completed
Start:
10 Feb 2023Due:
22 Feb 2023Completion:
22 Feb 2023Original submission
Change details
Jonathan Holland - -
8 Sep 2021
Change details
Introduction of SDEP and EES User Maintenance API (ECOES change)
The Secure Data Exchange Portal (SDEP) was introduced in Summer 2020 and requires parties to use SDEP when sending operational queries and escalations across the industry. However, the functionality doesn’t currently allow parties to send automated communications as a user is required to send these manually. However, the requirement to send each communication manually requires significant operational resources resulting in increased costs.
Within Electricity Enquiry Service (EES) there is no functionality to carry out user maintenance in bulk. Currently the Master Admin User (MAU) must amend/create/deactivate each user one by one. Also, in the event of team transfers and relocation, either voluntary or due to Supplier of Last Resort (SoLR), user accounts must be deactivated and new users created with their new email address rather than just updating their email address
Within Electricity Enquiry Service (EES) there is no functionality to carry out user maintenance in bulk. Currently the Master Admin User (MAU) must amend/create/deactivate each user one by one. Also, in the event of team transfers and relocation, either voluntary or due to Supplier of Last Resort (SoLR), user accounts must be deactivated and new users created with their new email address rather than just updating their email address
Any REC Party that had automated process communications prior to the introduction of SDEP needed to introduce manual working following SDEP. This introduced additional operational costs and diverted resources from providing benefits to consumers in other high value/high impact areas. This increased operational resource remains whilst manual communications need to be sent through SDEP..
The appointed MAU must carry out user maintenance to each user account one by one this manual activity is time consuming.
The appointed MAU must carry out user maintenance to each user account one by one this manual activity is time consuming.
The use of an API, to allow SDEP integration directly with REC Party IT systems.
The functionality to automate the management of user maintenance requests rather than making manual amendments
The functionality to automate the management of user maintenance requests rather than making manual amendments
Significant work was completed during the MIF analysis and solution development activity, to develop an API design. The EES and SDES Service Provider has previously engaged with the industry to understand and impact assess the requirements, meaning full design and impact assessment should not be required.
Impacts
Electricity
Switching experience, Trust and confidence, Other (please provide details in Additional information box below)
The introduction of automation and the ability to carry out bulk actions/updates in the EES and SDEP will significantly reduce the time taken by REC Parties when carrying out actions/updates allowing that resource to be better used elsewhere within the organisation
This Change Proposal has been raised to address issues originally identified under the Master Registration Agreement (MRA): MIF 322 - Automating sending communications on the Secure Data Exchange Portal (SDEP) MIF 340 - Bulk Change of ECOES User Information
This Change Proposal has been raised to address issues originally identified under the Master Registration Agreement (MRA): MIF 322 - Automating sending communications on the Secure Data Exchange Portal (SDEP) MIF 340 - Bulk Change of ECOES User Information
No details provided
-
No details provided
-
No details provided
-
No details provided
-
No details provided
-
Secure Data Exchange Service
-
Energy Suppliers, Distribution Network Operators, EES Users
-
No details provided
-
No
No details provided
Priority & timing
No
n/a
No
No
No details provided
-
Activity
Proposed solution summary changed to As a consumer, I want to ensure the data held by my supplier and other industry parties is correct so that I receive accurate and timely bills so that I understand what I need to pay and by when with no surprises…
Proposed solution summary changed to As a consumer, I want to ensure the data held by my supplier and other industry parties is correct so that I receive accurate and timely bills so that I understand what I need to pay and by when with no surprises.As a consumer, I want to be able to switch my energy supply without experiencing significant delays whilst my new and old supplier resolve any issues. So that I can see the benefits of switching at the earliest opportunity.As an SDEP User, I want to be able to automate processes that use the SDEP, so I can meet my obligations as efficiently and effectively as possible. As an EES or SDES User, I want to be able to automate certain user maintenance requests, so I can manage user maintenance activities as efficiently as possible..
Show morejonathan.holland has been allocated as Lead Analyst.
beth.brown has been allocated as SME.