MP207 Allowing Registered Supplier Agents to Maintain Meter Firmware

Proposer Tom Woolley (SMS Plc)
Lead Analyst Elizabeth Woods
Date raised 10/05/2022
StageRefinement Process
Implementation date Targeted for June 2025 SEC Release
Latest update This modification is currently on the waiting list.

What is the issue?

Supplier Parties authorise Meter Operators (MOPs) and Meter Asset Managers (MAMs) to install and maintain Smart Meters as Registered Supplier Agents (RSAs). However, the Smart Energy Code (SEC) does not allow MOPs and MAMs to use the Data Communications Company (DCC) System to remotely manage the meters’ firmware.
Device firmware management is integral to the health of the Smart Metering ecosystem. The Proposer believes that MOPs and MAMs are in a better position than Suppliers to facilitate this, and that enabling Suppliers to outsource these operations to their RSAs will improve the overall Smart Metering service.

What is the solution?

The Proposed Solution aims to add capability for RSAs to send Service Reference Variant (SRV) 11.1 to Electricity Smart Metering Equipment (ESMEs) and Gas Smart Metering Equipment (GSMEs) where they are the appointed RSA for the Device. RSAs will receive all the Alerts related to the firmware distribution if they send the SRV 11.1 and will also receive copies of the firmware receipt Device Alerts sent from the Device to the Supplier. RSAs will also receive DCC Alerts relating to changes of firmware on Devices. RSAs and Suppliers will be able to see the firmware tracking for Devices where the other Party has sent the SRV 11.1 using the Self-Service Interface (SSI).

The definition of invalid Device check W110101 (used when Device does not exist, or sender is not the Registered Supplier) will be extended to include checking that an RSA is appointed to the Device (which must be an ESME or GSME).

Who is impacted?

Large Suppliers
Small Suppliers
DCC
Other SEC Parties

What SEC documents are affected?

SEC Appendix E ‘DCC User Interface Services Schedule’
SEC Appendix AD ‘DCC User Interface Specification’

Timeline

10 May 2022
Draft Proposal raised
17 May 2022
Presented to CSC for initial comment
18 May 2022
Developing business requirements with the Proposer
01 Jul 2022
to
31 Jul 2022
Presented to SEC Sub-Committees for initial comment
11 Jul 2022
Modification discussed at Requirements Workshop
13 Jul 2022
Modification discussed with SSC
16 Aug 2022
CSC converted Draft Proposal to Modification Proposal
07 Sep 2022
Modification discussed with Working Group
06 Oct 2022
Modification discussed with TABASC
01 Nov 2022
DCC Preliminary Assessment requested
30 Nov 2022
DCC Preliminary Assessment returned
01 Feb 2023
Modification discussed with Working Group
26 Apr 2023
Modification discussed with SSC
31 May 2023
to
22 Jun 2023
05 Jul 2023
Modification discussed with Working Group
20 Sep 2023
Change Board rejected DCC Impact Assessment request

Modification documents

MP207 Modification Report v0.6
13/09/2023
MP207 Working Group meeting summary – July 2023
19/07/2023
Annex D - MP207 Refinement Consultation responses
26/06/2023
MP207 Refinement Consultation
31/05/2023
MP207 Working Group meeting summary – May 2023
15/05/2023
MP207 Working Group meeting summary - February 2023
16/02/2023
Annex C - MP207 EUK Consultation Responses v0.4
26/01/2023
Annex B - MP207 DCC Preliminary Assessment Response v0.3
30/11/2022
Annex A - MP207 - Business Requirements v0.5
02/11/2022
MP207 Working Group meeting summary - September 2022
28/09/2022
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.