Proposal to modify the BSC to define DIP Manager data and how it can be shared

Proposal to modify the BSC to define DIP Manager data and how it can be shared | Ofgem Please enable JavaScript in your web browser to get the best experience. BETA This site is currently in BETA. Help us improve by giving us your feedback . Close alert: Proposal to modify the BSC to define DIP Manager data and how it can be shared Publication type: Code modification Publication date: 10 October 2025 Topic: Energy codes Print this page Share the page Share on Facebook Share on Twitter Share on LinkedIn Outcome of proposed changes to the Balancing and Settlement Code P496, clarifying that ‘transactional’ data from message headers (known as Common Blocks) is included within the definition of Data Integration Platform (DIP) Manager Data, and enabling the DIP Manager to share DIP Manager Data with code bodies for specified purposes on a continuous basis, consistent with the requirements of existing data protection legislation. Details of outcome Ofgem has approved BSC Modification P496. As part of Market-wide Half Hourly Settlement, the Data Integration Platform (DIP) has been established to support the exchange of data between electricity industry participants that enables them to meet obligations in multiple industry codes. In November 2024, BSC Modification P474 established a governance regime for the DIP known collectively as the DIP Rules. Under those DIP Rules, the DIP Manager may access ‘transactional’ information that facilitates message sending between senders and recipients across the DIP. ‘Common Block’ data is a type of transactional data that includes Meter Point Administration Numbers, which are classified as personal information under data protection law. The DIP Manager needs to access and use Common Block data so that it can manage the system efficiently, including tracking message flows and dealing effectively with operational issues that might arise for DIP Users. However, P474 did not explicitly define Common Block data as DIP Manager Data that the DIP Manager may - consistent with data protection legislation - access, use and, potentially, share with third parties. Under P474 the DIP Manager was permitted to provide Common Block data to Code Bodies, for purposes not related to the DIP service, only via open data access requests. Elexon and the Retail Energy Code Manager considered that they needed a continuous supply of Common Block data to carry out performance assurance activities efficiently. Start date The implementation date for Balancing and Settlement Code Modification P496 is 22 October 2025. Code change description The DIP Manager (‘the Proposer’) raised P496 on 7 August 2025. The purpose of the proposal was to clarify in the DIP Supplement that Common Block data was included in the definition of DIP Manager Data and to provide a mechanism, consistent with the requirements of data protection legislation, to enable the DIP Manager to share Common Block data with the code bodies on a continuous basis for specific purposes. Main document Decision to approve Balancing and Settlement Code Modification P496: ‘Defining DIP Manager Data and how it can be shared' [PDF, 227.99KB] Print this page Share the page Share on Facebook Share on Twitter Share on LinkedIn Close