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 (documentation only changes) and modifications to the SEC that do have system impacts. System impacting 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; 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 its February 2018 meeting, the Panel approved the currentversion of the Panel Release Management Policy. The Panel Release Management Policy is available to download here.
Typically, new SEC content will be released three times a year. The scheduled release cycle will be:
|Release||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.
November 2017 (Release 1.4)
The November 2017 release (also referred to as Release 1.4) primarily contained Data and Communications Company (DCC) System changes. These changes fell 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 and the provision of Self-Service Interface Reporting).
In addition, the November 2017 release was supplemented by other internal DCC changes undertaken in accordance with the DCC Release Management Policy. Details on this release can be fold here.
Release 2.0 (expected in September 2018)
Release 2.0 contains DCC and SEC Party System impacting changes. The content of the release 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, Release 2.0 may be supplemented by internal DCC changes undertaken in accordance with the DCC Release Management Policy and approved Modification Proposals.
Release 2.0 also contains the approved SEC Modification Proposals:
- SECMP0006 ‘Specifying the number of digits for device display’; and
- SECMP0008 ‘Provision of DCC Alerts for Quarantined Service Requests’.
Release 2.0 Testing Documentation status tracker
In order to successfully test the content of Release 2.0 to ensure the changes and new functionality operate as expected, while ensuring that existing functionality and devices continue to operate release testing is required. A number of Testing Approach Documents for Release 2.0 have/are being produced which will set out how this testing will be undertaken. A tracker spreadsheet is provided below, and gives an overview of the current status of each testing document.
The below Release 2.0 Testing Approach Documents have been approved by the Secretary of State.
|Document Name||Date Approved||Document Link|
|System Integration Test Approach Document Release 2||22nd February 2018||Release 2 System Integration Test Approach Document|
|Device Integration Test Approach Document Release 2 v1.2||5th June 2018||Release 2 Device Integration Testing Approach Document v1.2|
|User integration Test Approach Document Release 2 v1.2||5th June 2018||Release 2 User Integration Testing Approach Document v1.2|
SMETS1 Services (Release 3.0)
Release 3.0 will contain DCC and/or SEC Party System impact changes. The content of the release will primarily be SoS (BEIS) executed changes, and is expected to take the form of:
- the deliver of SMETS1 Services (previously referred to as SMETS1 enrolment and adoption.
In addition, Release 3.0 may be supplemented by internal DCC changes undertaken in accordance with the DCC Release Management Policy and approved Modification Proposals.
SMETS1 Services Testing Documentation status tracker
In order to successfully test the content of the SMETS1 Services release, to ensure the changes and new functionality operate as expected, a number of Testing Approach Documents are being produced which will set out how this testing will be undertaken. A tracker spreadsheet is provided below, and gives an overview of the current status of each testing document.
June 2019 Release and beyond
The June 2019 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.
In addition it will contain changes to the Technical Specifications and GB Companion Specification (that were de-scoped from the changes included in Release 2.0).
DCC UIT Release Plan and Releases Content
The DCC has produced a spreadsheet setting out the plan and associated contents of maintenance releases for UIT defect fixes. The spreadsheet is available to view by SEC Parties.
(Please note that you will need to log in to the website in order to download the spreadsheet).
Please consider the following whilst assessing and consuming information provided in the Plan and Release Contents
1. Plan is indicative as of 20 November 2017 and may change as DCC progress these activities (as and when new versions of the spreadsheet are produced and provided by the DCC it will be published here).
2. Plan will be updated based on progress and notification will be sent to customers
3. Plan will be extended to include other Tranches as soon as defects are assigned to DCC
4. Content of each one of the releases planned in UIT is available in this document and the defect description is as being described by defect owner
5. Content of each release may be subjected to change and customers will be notified of changes
If you require any further information on UIT Release Plan and Releases content document please email your DCC Testing Representative.
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 will be updated when new content is added, target dates change or when a change has been approved.
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.