CP1493 – Add a form and associated process steps to BSCP15 for registering Non-Standard BM Unit configurations
Formal title: Add a form and associated process steps to BSCP15 for registering Non-Standard BM Unit configurations
Current Status
Summary
BSCP15 section 3.1 currently states that if a Party wishes to apply for a non-standard BM Unit configuration for the relevant Plant and Apparatus, it must write a letter to BSCCo (Elexon). This letter must set out the justification and ‘additional information’ that explains why its proposed non-standard configuration should be agreed.
Currently, the BSCP does not detail what ‘additional information’ the Party should provide; what Elexon then does with that information; or what the next steps are for progressing the non-standard BM Unit configuration application. Elexon is often asked by Parties what information needs to be included in the letter, or if we can provide a sample or template letter. This highlights a lack of clarity in the process, creating the potential for inconsistency and delays in applications.
This CP will amend BSCP15 in order to create a new form to be used by Parties when applying for non-standard BM Units; change the existing process steps for non-standard BM Unit registrations, so that they require Parties to complete this application form rather than submit a letter; add extra steps to the registration process, reflecting how Elexon then progresses the non-standard BM Unit application to the ISG for decision; add definitions of Non-Standard BM Unit and Standard BM Unit; and make a number of housekeeping changes, including re-ordering process steps.
Progression
CP1493 was raised by Elexon on 8 September 2017. The CP Progression paper was presented to the ISG and SVG for information at its meetings on 26 September 2017 and 3 October 2017 respectively. The CP was issued for CP Consultation on 9 October 2017, with responses due by 3 November 2017.
CP1493 was approved by the SVG and ISG at its meetings on 5 December 2017 and 11 December 2017 respectively. CP1493 was implemented on 22 February 2018 as part of the February 2018 Release.
Next Events
CP1493 was implemented on 22 February 2018 as part of the February 2018 Release.