The Data Integration Platform supports the exchange of data between electricity industry participants and will revolutionise how data is exchanged within our industry.

This page explains what the DIP is and how it will work.

How the DIP works

The Data Integration Platform (DIP)  is an industry-wide system created to support multiple Industry Code obligations on Market Participants, beyond just BSC obligations.

The DIP uses a cloud-based Event Driven Architecture (EDA) designed to deliver real-time message exchange.

Market Participants will use the DIP to share data with each other, including Elexon from April 2025 onwards.

Elexon’s role as DIP Manager

Elexon was appointed by Ofgem in 2022 to develop the DIP and begin operating it in September 2025.

As directed by Ofgem, the DIP is developed and operated independently of other systems and processes. This ensures that the DIP operates autonomously, managed by a dedicated team within Elexon known as the ‘DIP Manager.’ This team works alongside Elexon colleagues while maintaining a level of separation to ensure independent operations.

The DIP Manager will be responsible for all decisions related to the DIP unless a material change or BSC change is required, in which case the DIP Change and Advisory Board (DCAB) or Ofgem (following the BSC Panel’s recommendation) will make the decision. This governance structure is designed to facilitate a smoother and quicker change process.

Changes to the DIP

Between now and MHHS Programme M10, any changes to the design of the DIP itself should follow the MHHS Design Review Process. Any potential changes DIP Messages should also follow this process.

Any changes to the DIP Rules, that do not require a change to the DIP itself (a non-system change) should follow the DIP Change process as laid out in DSD004 of the DIP Rules. Such changes can be raised by submitting a DIP Change Request (CR) Proposal Form to the DIP Manager.

DIP Change Register

The DIP Change Register contains an up-to-date high level overview of active and closed DIP CRs. To view public documents relating to a specific DIP CR, select that change from the list and click on the relevant link within the timetable. 

DIP change meetings, including DCAB meetings and DIP CR Workgroup meetings, are listed in the second page of the report. Public documents for each meeting can be accessed through the hyperlink on the meeting title. 

DIP Rules

The DIP Rules were implemented on 1 October 2024.

The DIP Rules introduced graduated effective dates i.e. different parts of the DIP Rules will come into effect at different times to align with MHHS Milestones.

Further information on the graduated introduction of the DIP Rules can be found in DSD001 Annex One of the DIP Rules:

  • The DIP Rules concerning General Provisions, Governance and Change came into effect on 1 October 2024
  • The rules concerning DIP Operations (including On-boarding), Data Management
  • Assurance will come into force at MHHS Milestone Ten (M10)
  • The final part of the DIP Rules, concerning funding arrangements, will come into force at M16

DIP Manager communication

Should you wish to contact the DIP Manager, e-mail [email protected].

DIP Publication – the DIP Manager will send e-mails whenever anything new is published, should you wish to be included in these e-mails, please e-mail [email protected].

Maximising the Potential of the DIP

While the DIP will not be fully operational until 2026, we are already planning for its future development. Our goal is to maximise the industry’s investment by fully using the DIP’s capabilities.

Initially, we will manage the 40 (plus six optional) message channels related to MHHS, which will be implemented during the first phase. We will then focus on migrating the remaining Data Transfer Network (DTN) flows to the DIP. This migration will reduce costs for the industry and enhance the platform’s functionality.

The DIP also holds potential for use in other markets beyond the domestic smart meter arena, such as the flexibility market, where its messaging capabilities can support functions like dispatch notification and demand side response.

 Roadmap

Further information