The Release and Implementation Process
How do we implement change?
We implement change to BSC Systems through a programme of “Releases”. BSC Systems include Code Subsidiary Documents (CSDs) and other Configurable Items (CIs), BSC Agent Software systems and associated documentation.
What is a Release?
A Release is a packet of approved changes (Modifications and / or Change Proposals) which are usually all implemented on the same date, although sometimes Releases may have more than one implementation date.
What are the Release Dates?
The Release Strategy provides for three “Planned” Releases each year, in February, June and November. But we do occasionally deliver “Special” Releases on other dates – usually for Modifications that need to be implemented on a specific date. A planned Release will not take place if there are no approved Modifications or Change Proposals to implement.
Where an approved Modification requires a specific implementation date, it may be delivered via a Special Release that does not conform to the Release Strategy.
You can find the planned release dates for the next three years here.
If a small number of Change Proposals are scheduled for inclusion in a Release but there is no business case for implementing that Release, the Release won’t take place and the changes will be implemented in the next appropriate Release.
Why do we use Releases?
We use Releases to allow Parties and Party Agents sufficient time to plan changes to their systems and processes which are required to meet the new and amended requirements.
How and what do Releases communicate with Industry?
We use our website to publish the details for Releases, CVA and SVA Change Circulars to provide important information and to request document reviews, and Newscasts to remind you of any important events.
What information do we publish on each Release?
For each Release, we’ll publish information that you’ll need to know to ensure that you will be ready on the Release implementation date:
- The scope and impact of the Release;
- The Implementation Date(s);
- Business Requirements Solution (BRS) documents for complex changes;
- Key dates for industry input;
- An Impact Matrix identifying all impacted CSDs & CIs;
- An Interface Impact Matrix, which lists all interfaces between BSC Central Services and Parties and / or Party Agents and an explanation of how they will change – e.g. structure, valid set(s) for individual data items or data content;
- The Release Test Strategy and any test files for use in Participant Testing of BSC Central Systems and / or to assist participants test their own systems; and
- A separate page where we will publish new and / or amended CSDs and CI documents.
Please note that not all of the above information will be published on each Release web page from the outset – it will be updated regularly during the lifetime of the Release.
Visit the Changes Awaiting Implementation page to see what is currently happening with Releases and Implementation.
What is the governance for Releases?
Each Release is managed by a Release Manager and is directed by the BSC Systems Programme Board, which includes industry representatives and ELEXON Change and Operational management.
The current BSC Systems Programme Board members are:
|Phil Eyre (Npower)
||Senior SVA User
|Tim Johnson (E.ON Energy Trading)
||Senior CVA User
|John Sykes (Scottish & Southern)
||Senior User ELEXON Operations
The BSC Systems Programme Board Terms of Reference, which sets out the responsibilities of the Programme Board, is available to download from the related content menu on the right of this page.
The documents below outline the requirements for testing and communication
BSC Participant Test Service User Guide [286 Kb]
Version: 5.0Issued On: 07-January-2009
ELEXON Testing Guidelines
Version: 11.0 Issued On: 16-July-2012
Participant Test Service Booking Form
Version: 2.0 Issued On: 15-Oct-2012