This page provides full details of the proposed change, relevant dates and decisions.
What is the issue?
The DIP is a middleware service that operates an industry-wide system used by Market Participants to send and receive real-time messages. The requirements of the DIP, its Users and Manager, are set out in the DIP Rules; the DIP Rules are detailed in the DIP Supplement and the DIP Subsidiary Document (DSDs).
However, the DIP rules do not set out how to handle a major incident that affects the operation of the DIP. This issue has come into focus as the Market-wide Half-Hourly Settlement Programme (MHHSP) progresses to Milestone 8 (M8) (22 September 2025), whereby the DIP will be used by all Market Participants.
What is the proposed solution?
In order to ensure that the DIP Manager can effectively manage major incidents to the DIP it is proposed the desired outcome is:
- Introducing a framework that has provisions to assign and define actions from the DIP Manager, DIP Users, and/or their Contracted Service provider during a Major Incident;
- Introducing Service Level Agreement (SLAs) to be agreed, which are enforceable;
- Developing an central record of agreed actions;
- Incident review process to determine if an enduring solution shall be developed to prevent future issue
Status
Reviewing consultation responses and incorporating the feedback into the DIP Rules
Next steps
| Stage | Date |
|---|---|
| Submission | 12.08.2025 |
| Initial Assessment | 09.09.2025 |
| Workgroup | |
| Consultation | |
| Final Assessment | |
| Decision | |
| Implementation |