Change Consultations

Consultations are used when the DIP Manager needs industry views to decide whether a proposed change should be approved. They ask for feedback on likely impacts and costs, how long it would take to implement, and how the change affects the DIP’s objectives.

Consultations normally run for at least 15 working days, unless the change is very urgent. Where a change also affects other Industry Codes, the DIP Manager will coordinate with other Code Bodies and try to run a single, combined consultation rather than separate ones.

List of Change Consultations

(Showing items 1-5 of 7)

Show 5 | 10 | 20 | All
View CDR0007 Consultation on Clarification of Self Testing Requirements

CDR0007 Consultation on Clarification of Self Testing RequirementsRead More

Amending DSD002, Annex 1, impacts Potential DIP Users and the DIP Manager. The requirement for Potential DIP Users to send and receive all messages for DIP interfaces is part of their testing requirements and system development. Changing this requirement during PIT could pose a risk if systems lack this functionality. However, the MHHS PIT Guidance Document confirms this as a system requirement, and the DIP Manager will test this under ‘MHHS Non-SIT Supplier & Agent Qualification Testing’.

The DIP Manager will shift focus from testing message functionality to assessing compliance with DIP Rules through PIT and evidence assurance. This may reduce assurance levels for the DIP Manager regarding Potential DIP Users’ capabilities. Nevertheless, the risk that users will not adhere to PIT Guidance remains low, and the DIP Manager can still request demonstrations of compliance. Therefore, amending DSD002, Annex 1, is unlikely to weaken the assurance provided by testing

View Urgent Consultation on P491 Amendment to Radio Teleswitch Service Funding Mechanism

Urgent Consultation on P491 Amendment to Radio Teleswitch Service Funding MechanismRead More

This urgent Modification aims to amend the charging methodology for the additional Radio Teleswitch Service (RTS) operational costs. The intention is to mitigate the risk of unfair distribution of these costs, which are currently funded equally between Suppliers and Generators.

View P487 Send Back Consultation Incentive of BSC Supplier Parties to meet the M15 MHHS Milestone

P487 Send Back Consultation Incentive of BSC Supplier Parties to meet the M15 MHHS MilestoneRead More

P487 seeks to to incentivise Parties to meet the MHHS Migration Plan by restricting their ability to register new Metering Systems if they fail to complete migration (Milestone 15) on time.

The proposed solution is to update Section C ‘BSCCo and its Subsidiaries’ to incentivise Parties (at a Party ID level) to meet the M15 Milestone and give assurance to all Parties who meet the M15 Milestone, and other BSC funding parties, that there will be consequences for those Parties that do not. Parties that do not meet the M15 Milestone will result in an extension in dual running of old and new Settlement systems, and delay to the implementation of a shorter Settlement timetable.

View P494 Ad Hoc Consultation Establishing the Smart Data Repository (SDR)

P494 Ad Hoc Consultation Establishing the Smart Data Repository (SDR)Read More

P494 proposes changes to the BSC to enable Elexon to establish and manage a Smart Data Repository (SDR). The changes will enable robust governance of the SDR, and will ensure Elexon remains compliant both with the UK General Data Protection Regulation (GDPR) when handling personal data, and with its obligations to BSC Parties in relation to their Settlement or commercial data.

The P494 Modification Workgroup is seeking views on potential funding options for the SDR.

View CP1615 Change Proposal Consultation

CP1615 Change Proposal ConsultationRead More

New versions of the P0287 and P0288 dataflows will be implemented at MHHS Milestone M11, consequently the IDD Part 1 spreadsheet must be amended to reflect the new versions of these dataflows. Suppliers, VLPs, VTPs and AMVLPs will need to amend their systems in time for 6 November 2025 so that they do not reject the new versions of the new versions of the P0287 and P0288 data flows.