What is a release?
The term ‘release’, in the context of the Smart Energy Code (SEC), is used in reference to any modifications or suite of modifications that are made to the SEC on the same implementation date. A release can include modifications to the SEC that have no system-impacts, i.e. documentation only changes, and modifications to the SEC that do have system-impacts. System Impact modifications are those that affect DCC and/or User Systems and/or Devices. System impacting modifications to the SEC can come from two sources:
- Modification Proposals raised by those that can raise them (as set out in Section D1.3) or by Panel Sub-Committees; and
- modifications made by the Secretary of State (SoS) using Section 88 powers.
Why are releases needed?
Releases provide a mechanism by which multiple approved modifications to the SEC are implemented at once in a coordinated manner.
Panel Release Management Policy
SEC Section D10 (Release Management) requires the SEC Panel to establish a Panel Release Management Policy. The Panel Release Management Policy informs how implementation timetables are developed as part of the progression of a Modification Proposal. It also indicates and informs how approved Modification Proposals or suites of Modification Proposals are implemented via releases.
At their December 2015 meeting, the Panel approved the first version of the Panel Release Management Policy. The Panel Release Management Policy is available to download on the right-hand side of this SEC Webpage.
Typically, new SEC content will be released three times a year. The scheduled release cycle will be:
Timing of Release
If required, additional ad-hoc releases of new SEC content may also occur outside of the scheduled release cycle. Such changes may relate to Modification Proposals that can be implemented in short timescales or where it relates to a specific point in the year, such as the beginning of a new regulatory year.
The November 2017 release (also referred to as Release 1.4) will primarily contain Data and Communications Company (DCC) System changes. These changes will fall into two types:
- DCC Internal changes (for example Recovery Procure Changes and Anomaly Detection SMETS Objects Limits); and
- resolution of SoS Variations (for example Use of EUI-64 (User) Identifiers).
In addition, the November 2017 release may be supplemented by other internal DCC changes undertaken in accordance with the DCC Release Management Policy.
February 2018 (Release 2)
The February 2018 'Release 2' will contain DCC and/or SEC Party System impacting changes. The content of the February 2018 will primarily be SoS (BEIS) executed changes, and is expected to take the form of:
- changes to support Dual Band Communications Hubs, and
- changes to the Technical Specifications and GB Companion Specification (referred to as the TSG2 changes).
In addition, the February 2018 release may be supplemented by internal DCC changes undertaken in accordance with the DCC Release Management Policy.
June 2018 Release and beyond
The June 2018 release is now likely to be the first enduring release to contain any DCC System and/or User System and/or Device impacting modifications arising from SEC Modification Proposals raised by those entitled to do so as set out in SEC Section D1.3.
Forward Release Look
To give SEC Parties and other interested parties an indication of the earliest point when different types of changes could be implemented an Indicative Release Content Overview has been prepared. It is available from the document list on the left. It will be updated when new content is added, target dates change or when a change has been approved.
For Further Information
If you would like to further detail on releases or the Panel Release Management Policy, please email the SECAS Helpdesk or call us on 020 7090 7755.