SECMP0065 SMETS1 Security Obligations

Proposer Gordon Hextall
Lead Analyst SEC Change
Date raised 05/10/2018
StageImplemented
Implementation date 08/11/2018 (November 2018 SEC Release)
Latest update This modification was implemented on 8 November 2018 as part of the November 2018 SEC Release.

What is the issue?

SEC Sections G3.26 to G3.28 outline the security obligations for SMETS1 Smart Metering Systems and changes were made to these paragraphs in order to implement the obligations as a result of a BEIS consultation. The wording introduced into the SEC could, however, be interpreted to apply to pre-enrolment meters as it does not specify that the obligations only apply post enrolment. The legal effect is that the obligations apply now and do not allow time for the necessary planning by Users, the Security Sub-Committee (SSC) and the User Independent Security Assurance Service Provider.

What is the solution?

This modification seeks to enable the Smart Energy Code (SEC) to meet the original policy intent for the Smart Metering Equipment Technical Specifications 1 (SMETS1) security obligations in SEC Section G, to apply only from the date on which SMETS1 Devices start to be enrolled into the Data Communications Company (DCC). This will avoid the potential for Supplier Parties to be in breach of SEC obligations.

Who is impacted?

Large Suppliers
Small Suppliers

What SEC documents are affected?

Section G 'Security'

Timeline

05 Oct 2018
Modification Proposal raised
12 Oct 2018
Modification Report approved by the Panel
15 Oct 2018
to
19 Oct 2018
Modification Report Consultation
24 Oct 2018
Change Board vote
08 Nov 2018
Implemented

Modification documents

SECMP0065 Modification Report
25/10/2018
SECMP0065 Change Board vote
25/10/2018
SECMP0065 Modification Report Consultation responses
22/10/2018
SECMP0065 Modification Report Consultation
15/10/2018
SECMP0065 Initial Modification Report
15/10/2018
SECMP0065 Modification Proposal
08/10/2018
No files
No files
No files
No files
No files

If you believe there is a problem with this modification, please let us know HERE.