MANAGING TECHNICAL
DOCUMENTATION UP TO RELEASE 4
SEC Panel discussion
9 June 2017
Issue to be addressed
- There will be multiple versions of the technical specifications being
developed in parallel (R1 for current issues, R2, R3 & R4 for changes)
- As a result of some resolution proposals not being delivered in Release
2 (DBCH), and industry keen for implementation as soon as possible,
we propose that they are included in the next appropriate release (which
will be Releases 3 (SMETS 1 E&A) and 4 in practice).
- Release 4 is now the first release expected to include a mix of changes
introduced by BEIS and changes arising from SEC Party modifications
- We wish to discuss with the Panel how Release 4 might best be
managed to maintain clarity for SEC Parties, given the different sources
of change.
2
Technical Documents by Release – current view
Release 1
Release 2
Release 3
Release 4
14 IRPs from RFC055
(including DBCH) and 78
from RFC052)
SMETS 1 E&A and RPs
that affect Devices & DSP
only (no CSP changes
possible)
Likely first Mod Release
plus remaining RP’s
GBCS V1.0
GBCS v2.0
GBCS v2.1
GBCS v3.0
SMETS V2.0
SMETS v3.0
SMETS v3.1
SMETS v4.0
CHTS V1.0
CHTS v1.1
CHTS v1.1 (unchanged)
CHTS v1.2
DUIS V1.0
DUIS V2.0
DUIS V3.0
DUIS V4.0
MMC V1.0
MMC V2.0
MMC V3.0
MMC V4.0
UISS V1.0
UISS V1.1
Other SSD changes
Other potential SSD changes
SRPD V1.0
SRPD V1.1
IEWP V1.1
IEWP V1.2?
3
Release 4: Two broad approaches
- BEIS has identified two broad approaches to managing multiple
sources of change to Release 4 technical documents:
- Option A:
BEIS designates Release 4 technical
documents (and also those for Release 2 and
3) into the SEC at an early stage allowing
BEIS and SEC Party modifications to proceed in
parallel
- Option B:
BEIS designates Release 4 technical documents at
the date of Release 4 “go-live” using a baselining
model as used at TBDG
4
Option A – Early Designation
• BEIS designates a draft version of the technical documents for
Release 2, 3 & 4 into the SEC in Summer/Autumn 2017
• Transitional variations made to switch off the legal effect of the
documents in the interim
• SEC modifications can then be raised against the draft Release
4 versions of the technical documents
• All agreed technical specification changes (whatever their
source) included within the SEC by BEIS for clarity
• At Release 4 “go-live” BEIS removes the transitional variations
and introduces the updated TS Applicability Tables
5
Option B – Late Designation
• The Release 4 documentation set containing a
consolidated set of changes is maintained through the
TBDG baseline process (consideration needed of whether
approved SEC modifications should be included)
• BEIS designates suite of changes into the SEC for
Release 4 that includes both the approved SEC
modifications and BEIS led changes
• Release baseline maintained outside of the SEC
6
Possible advantages/disadvantages of the options
Option A
Option B
SEC contains consolidated versions of all
planned changes (hence roadmap for DCC
Releases)

x
Simplifies the SEC Modification implementation
process

x
Minimises number of legal steps required to
implement
x

Provides greatest clarity to SEC Parties and
others
?
?
Formalises DCC forward work stream for all
parties

x
7
Suggested Next Steps
• Panel decision in support of either Option A or Option B, or
refinements thereof, on the basis of a paper for the July
Panel meeting
• BEIS to develop documentation updates for the chosen
option
8