Programme Change Control
The Programme has received queries on how the MHHS Target Operating Model (TOM) and Design/Code change control is managed post-M10. These activities are now managed via Code Body BAU change control processes.
Who do I contact?
For support in raising:
Balancing & Settlement Code (BSC) changes, please visit the following pages of the Elexon website or email bsc.change@elexon.co.uk:
Retail Energy Code (REC) changes, please visit the following pages of the REC Portal or email the REC Code Manager ahead of raising a change at change.management@recmanager.co.uk:
Distribution Connection and Use of System Agreement (DCUSA) please visit the DCUSA Change Proposal Register on the DCUSA website, or email dcusa@electralink.co.uk
Data Integration Platform (DIP) changes, please visit the DIP Change Requests page of the DIP Manager website, or email DIPManager@elexon.co.uk
The Programme actively monitors external code changes to ensure that they do not adversely impact Programme delivery, specifically migration dependent changes. We maintain a log of all upcoming industry changes which includes the pipeline of BSC and DIP changes, plus raised BSC, REC, DCUSA and DIP changes. You can view this log below:
The MHHS PMO now operates the Change Control process for milestone changes only and ensures that all milestone Change Requests are communicated clearly and efficiently throughout the Programme.
For Programme-related milestone changes, this page is designed to provide an overview of the Programme Change Control procedures. For the benefit of participants, you can view Change Control guidance and forms further down this page. Please note that this process only applies to Programme milestone changes.
The Programme has defined and embedded a Change Control process to assess and manage any proposed changes that could impact the successful delivery of the Programme.
New Change Requests are assessed through the Programme’s Change Board. The Change Board can reject the Change Request, request further information, or ask the Change Raiser to attend the Change Board to present the proposed change. Please ensure you read the Change Request Guidance before completing a change request.
Following review with the Change Board, the Change Request is then designated to the appropriate Advisory Group for triage. The Advisory Group, in line with the Senior Responsible Owner (SRO), recommends whether the Change Request should proceed for industry Impact Assessment or not.
The MHHS PMO share the Change Request with the principal contacts of each Programme participant, with a request to complete an Impact Assessment within the 10-day window. To enable swift and informed decision-making, it is critical that the Programme receives as many Impact Assessment responses as possible.
Once Impact Assessments are submitted to the Programme, they are consolidated into a single view and presented back to the Change Board and subsequently to the Advisory Group for decision.
Change Requests exceeding certain thresholds (as laid out in the MHHS Governance Framework, available on the MHHS Programme Governance page of this website, are raised to Ofgem for a decision.
MHHS Change Control Framework
| Short Name | Doc Number |
|---|---|
| Release Management Implementation Process | DEL2060 |
| Change Control Form Guidance for participants | DEL174 |
| Change Request Form Template | DEL173 |
| Programme Change Control Process | DEL172 |
| Change Control Approach | DEL171 |
