SDEP Review Improvements (2) - Usability
Summary
Following a comprehensive review, the Code Manager has identified functionality improvements with the SDEP system. These will introduce useability improvements to the system, to allow users to better filter workflow and queries and to improve notifications received by Parties, to enable resolution of raised issues. Feedback from SDEP users stated that filtering options are limited to particular attributes and notification emails contain minimal supportive information for the parent communication.
Latest update and next planned activity
Date of latest update
Latest Update
30/09/2026 - The Technical Expert Panel voted to approve R0122 for implementation on 25 June 2027.
Impacts Overview
Impacted REC Parties and Market Participants
Electricity Distribution Network Operator (R)
Energy Supplier (ES)
Impacted REC Services
Secure Data Exchange Service (SDES)
Priority and rationale
Standard
Change Reports, Impact Assessments, Consultations and Documents
Change Reports
Solution development
Problem Statement
Market Participants require functionality that improves efficiency, reporting and allows Consumer issues to be addressed sooner and more accurately.
Documents Library
02 Nov 2026
Download R0122 Legal Drafting for consultation
05 Jun 2026
Download R0122 Change Proposal Re-plan V2.0
There is currently no Change Plan.
Original submission
Change details
Ryan Dale - REC Code Manager
26 May 2023
Change details
SDEP Review Improvements (2) - Usability
Following a comprehensive review of the SDEP system, the Code Manager has identified 6 batches of functionality improvements with the SDEP system. This change represents the second of these batches.
This batch contains changes which introduce useability improvements to the SDEP system, to allow users to better filter workflow and queries and to improve notifications received by parties, to enable resolution of raised issues
This batch contains changes which introduce useability improvements to the SDEP system, to allow users to better filter workflow and queries and to improve notifications received by parties, to enable resolution of raised issues
SDEP Users stated that the filtering options are limited to particular attributes and notification emails contain generic and minimal supporting information for the parent communication.
Part 1 - Filters
a) Add an additional filter on the Secure Communications screen for unread messages.
Note that the read/unread status is at company group level rather than for an individual user. So if anyone in the same company group accesses the message it will be marked as read.
It would be an additional change to move the read status to the user, and may have unintended consequences in making it unclear when a query has been dealt with by someone else.
b) The SDEP system only allows a user to escalate a query after a fixed period of time (as per the REC SLA).
There is a report that provides this information - Secure Communications Messages Sent No Response. But users may want to be able to filter on screen to make accessing the relevant calls direct from the filtered list quicker that running the report then searching for the relevant communication. The information on when it can be escalated is held in the system. This information should be displayed on the secure communication page and be available to filter on.
c) Currently, the user can see if a communication has not been opened (unread) at a Company Group level. However, if you open a message but don't action it, it is marked as read, but not obvious to the user that they still need to action it.
Additional statuses can be introduced (applied to the communication at the company group level, i.e. not separate status for individual users).
It is proposed to either:
a) create a new icon that shows if a task has been actioned regardless of read/unread status. This will be clickable on the existing query page and will be reset when a new message is received for that communication; or
b) Create an option to manually return a communication to unread.
The audit history would show all status changes.
Part 2 – Notification emails
Notification emails should include all relevant cases separately, including the unique Case Number and Process Type to allow recipients to address the items promptly and manage workload.
a) Add an additional filter on the Secure Communications screen for unread messages.
Note that the read/unread status is at company group level rather than for an individual user. So if anyone in the same company group accesses the message it will be marked as read.
It would be an additional change to move the read status to the user, and may have unintended consequences in making it unclear when a query has been dealt with by someone else.
b) The SDEP system only allows a user to escalate a query after a fixed period of time (as per the REC SLA).
There is a report that provides this information - Secure Communications Messages Sent No Response. But users may want to be able to filter on screen to make accessing the relevant calls direct from the filtered list quicker that running the report then searching for the relevant communication. The information on when it can be escalated is held in the system. This information should be displayed on the secure communication page and be available to filter on.
c) Currently, the user can see if a communication has not been opened (unread) at a Company Group level. However, if you open a message but don't action it, it is marked as read, but not obvious to the user that they still need to action it.
Additional statuses can be introduced (applied to the communication at the company group level, i.e. not separate status for individual users).
It is proposed to either:
a) create a new icon that shows if a task has been actioned regardless of read/unread status. This will be clickable on the existing query page and will be reset when a new message is received for that communication; or
b) Create an option to manually return a communication to unread.
The audit history would show all status changes.
Part 2 – Notification emails
Notification emails should include all relevant cases separately, including the unique Case Number and Process Type to allow recipients to address the items promptly and manage workload.
The proposed changes were developed with input from a working group of SDEP users.
Impacts
Electricity, Gas
Switching experience, Trust and confidence, Other (please provide details in Additional information box below)
This change will improve operational efficiency for users of the SDEP system, thereby allowing consumer issues to be addressed sooner / more accurately.
Schedule 17 - Secure Data Exchange
Category 3 document – SDES User Guide
No details provided
-
No details provided
-
Data Item Catalogue
-
No details provided
-
Secure Data Exchange Service
-
Energy Suppliers, Distribution Network Operators
-
No details provided
-
-
No details provided
Priority & timing
No
-
-
-
No details provided
-