MP107 SMETS1 Validation of SRV 6.15.1

Proposer Gemma Slaney
Lead Analyst Mike Fenn
Date raised 13/01/2020
Implementation date 3 November 2022
Latest update On 11 October 2021, SECAS officially received notification from the Proposer of MP107 ‘SMETS1 Validation of SRV 6.15.1’ that they have decided to withdraw the Modification Proposal, in accordance with the Right to Withdraw provisions in SEC Section D5.1. This is due to a new route becoming available to resolve the issue, which doesn’t require a SEC modification.

What is the issue?

To send a Critical Command to a SMETS1 Device, the user must be the owner of the relevant certificate on the Device and the owner of the Device in the RDP data. If a Network Operator updates the Network Operator Certificate with another in error, this error cannot be corrected.

The full issue can be found in the Modification Report can be found here.

Does this issue affect your company? Send us your comments to

What is the solution?

This modification will remove a validation step for Service Reference Variant (SRV) 6.15.1 ‘Update Security Credentials (KRP)’ which will allow any errors to be corrected.

What SEC documents are affected?

Appendix AB ‘Service Request Processing Document’


13 Jan 2020
Draft Proposal Raised
20 Apr 2020
DCC Preliminary Assessment requested
05 Aug 2020
Present to Working Group for discussion
14 Sep 2020
Modification submitted for RC on 14 September 2020.
25 Nov 2020
Present to Change Board
25 Nov 2020
DCC Impact Assessment requested
14 Jun 2021
DCC Impact Assessment received
01 Jul 2021
Present to TABASC
07 Jul 2021
Present to Working Group for discussion

Modification documents

MP107 July 2021 Working Group summary
MP107 Legal Text v0.1
MP107 Business Requirements v0.3
MP107 DCC Impact Assessment response v0.5
MP107 Modification Report v0.4
MP107 Refinement Consultation Responses
MP107 Refinement Consultation
MP107 DCC Preliminary Assessment response v0.5
DP107 Modification Report
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.