Smart Metering Implementation
Programme
Smart Metering Equipment Technical
Specifications (SMETS)
Version 1.59: Release Note
18 November 2015
Release Note
This release note accompanies, but does not form part of SMETS v1.59. It describes the
revision history of SMETS.
Summary of main changes
This document is SMETS v1.59.
There are corrections of minor typographic errors throughout this document.
In addition, the sections of this document listed below incorporate specific changes and
updates to SMETS v1.58 that have been adopted through a number of Issue Resolution
Proposals (IRPs) and following the DECC Technical Specifications Issues Management
process.
Table of Section Changes
The sections of this document listed below incorporate changes and updates to SMETS
v1.58 as follows:
Section
Changes
Section 4:
Changes at Sections 4.2.3, 4.4.7.2, 4.5.3.5, 4.5.3.21, 4.6.2, 4.6.5.13 and
4.6.5.21 in summary as follows:
Section 5:
Section 7:

Aligning to the latest versions of the Security Characteristics documentation

The Adjust Debt Command shall not result in billing data log entry

Addition of the amount of payment-based debt payments in the Billing Data
Log for GSME, ESME and PPMIDs to calculate a ‘Debt to Clear’ amount

Additional wording added to implement the functional behaviour for any
credit amount that would reduce a Debt Register balance below zero

Removal of content of Section 4.6.2 and 4.6.2.1

Clarification of an ambiguity when a device should take a snapshot of
prepayment registers

Possible values for the Debt Recovery Frequency shall be limited to Hourly
and Daily
Changes at Sections 5.3.3, 5.5.7.2, 5.6.3.5, 5.6.3.34, 5.7.2, 5.7.5.10, 5.7.5.23,
5.7.5.36, 5.9.3, 5.11.2.2, 5.12.2.1 and 5.15.3 in summary as follows:

Aligning to the latest versions of the Security Characteristics documentation

The Adjust Debt Command should not result in billing data log entry

Addition of the amount of payment-based debt payments in the Billing Data
Log for GSME, ESME and PPMIDs to calculate a ‘Debt to Clear’ amount

Additional wording added to implement the functional behaviour for any
credit amount that would reduce a Debt Register balance below zero

Removal of Section 5.7.2 and 5.7.2.1

Clarification of an ambiguity on when a device should take a snapshot of
prepayment registers

Possible values for the Debt Recovery Frequency should be limited to
Hourly and Daily
Changes at Sections 7.4.3.1, 7.4.3.2, and 7.4.7.1 in summary as follows:

Addition of the amount of payment-based debt payments in the Billing Data
Log for GSME, ESME and PPMIDs to calculate a ‘Debt to Clear’ amount

Removal of requirement to generate key pairs or Certificate Signing
Requests for PPMID

Removal of content of Sections 7.6.2 and 7.6.2.1
Section 8:
Change at Section 8.2.3: Aligning reference to the latest versions of the Security
Characteristics documentation for HCALCS
Glossary
Addition of definition for Debt Register, SECAS and removal of definition for
Installation Credentials
Table of Revision History
Version
1.0
1.1
Date of Issue
18/12/12
24/01/13
Status
Final
Draft
1.2
23/08/13
Draft
1.3
1.4
13/09/13
04/12/13
Draft
Draft
1.5
23/12/13
Draft
1.51
13/02/14
Draft
1.52
30/04/14
Draft
1.53
28/05/14
Draft
1.54
25/06/14
Draft
1.55
30/06/14
Draft
1.56
03/07/14
Draft
1.57
10/07/14
Draft
1.57
1.58
29/07/14
28/11/14
Draft
Draft
1.59
18/11/2015
Draft
Change Summary
First version (SMETS 1) designated by the Secretary of State
Version notified to the European Commission as per the
requirements of the Technical Standards and Regulations Directive
(98/34/EC), as amended by Directive 98/48/EC.
Updated version incorporating legal review comments, internal review
comments arising from security and GBCS work, positions reflected
in July 2013 response, PPMID section, external review comments
from previous version of SMETS2.
Draft baselined version.
Updated version incorporating changes to support HAN Connected
Auxiliary Load Control Switches, agreed with TBDG and accepted by
DECC.
Draft version incorporating changes made following internal review
and previously suggested revisions.
Draft version which has removed three 1.5 revisions which require
further consultation prior to request for approval.
Draft version incorporating changes emerging following GBCS
review, previous TBDG review and CPA review.
Draft version incorporating comments on the changes proposed in
1.52.
Draft version for informal TBDG review incorporating changes
proposed in email to TBDG members on 10 June.
Draft version for informal TBDG review incorporating requirements to
support ‘engineering menu functions’ and modifications to Privacy
PIN requirements.
Draft version incorporating comments on the changes proposed in
1.54 and 1.55.
Draft version incorporating comments on the changes proposed in
1.54, 1.55 and 1.56.
Draft version clarifying Random Number Generator requirements.
Draft version to align with GBCS v0.8.1. Changes include removal
of Data Restriction Flag, replacement of Tamper Alert with
Unauthorised Physical Access, and clarifications for ALCS and for
the ESME non-disablement calendar structure.
Uplift incorporating changes and updates to SMETS v1.58 adopted
through the DECC Technical Specifications Issues Management
process.
This page is intentionally left blank.
Smart Metering Implementation
Programme
Smart Metering Equipment Technical
Specifications (SMETS)
Version 1.59
18 November 2015
DRAFT
SMETS
© Crown copyright 2015
You may re-use this information (not including logos) free of charge in any format or
medium, under the terms of the Open Government Licence.
To view this licence, visit www.nationalarchives.gov.uk/doc/open-government-licence/ or
write to the Information Policy Team, The National Archives, Kew, London TW9 4DU, or
email: psi@nationalarchives.gsi.gov.uk.
This document is also available from our website at www.gov.uk/decc.
Version: SMETS v1.59
Issued: 18 November 2015
Enquiries to:
Smart Metering Implementation Programme
Department of Energy & Climate Change
3 Whitehall Place, Area 1C
London, SW1A 2AW
Telephone: 0300 068 6659
Email: smartmetering@decc.gsi.gov.uk
Version 1.59
18 November 2015
Page 1
DRAFT
SMETS
Table of Contents
Note: Sections 1 and 2 of this document are not used.
3
Introduction ................................................................................................................ 4
4
Gas Smart Metering Equipment Technical Specifications ...................................... 6
4.1
4.2
4.3
4.4
4.5
4.6
5
Overview ................................................................................................................. 6
SMETS Testing and Certification Requirements ...................................................... 6
Physical requirements ............................................................................................. 6
Functional requirements .......................................................................................... 7
Interface requirements........................................................................................... 15
Data requirements ................................................................................................. 23
Electricity Smart Metering Equipment Technical Specifications.......................... 29
5.1
Introduction ........................................................................................................... 29
Part A - Single Element Electricity Metering Equipment .................................................. 30
5.2 Overview ............................................................................................................... 30
5.3 SMETS Testing and Certification Requirements .................................................... 30
5.4 Physical Requirements .......................................................................................... 30
5.5 Functional Requirements....................................................................................... 31
5.6 Interface Requirements ......................................................................................... 44
5.7 Data Requirements ............................................................................................... 52
Part B - Twin Element Electricity Metering Equipment .................................................... 61
5.8 Overview ............................................................................................................... 61
5.9 SMETS Testing and Certification Requirements .................................................... 61
5.10 Physical Requirements .......................................................................................... 61
5.11 Functional Requirements....................................................................................... 63
5.12 Interface Requirements ......................................................................................... 69
5.13 Data Requirements ............................................................................................... 70
Part C - Polyphase Electricity Metering Equipment ......................................................... 73
5.14 Overview ............................................................................................................... 73
5.15 SMETS Testing and Certification Requirements .................................................... 73
5.16 Physical Requirements .......................................................................................... 73
5.17 Functional Requirements....................................................................................... 74
5.18 Interface Requirements ......................................................................................... 78
5.19 Data Requirements ............................................................................................... 78
Part D - Auxiliary Load Control Switch ............................................................................ 80
5.20 Overview ............................................................................................................... 80
5.21 Functional Requirements....................................................................................... 80
5.22 Interface Requirements ......................................................................................... 80
5.23 Data Requirements ............................................................................................... 81
Part E - Boost Function ................................................................................................... 82
5.24 Overview ............................................................................................................... 82
5.25 Functional Requirements....................................................................................... 82
5.26 Data Requirements ............................................................................................... 82
6
In Home Display Technical Specifications ............................................................. 84
6.1
6.2
Overview ............................................................................................................... 84
SMETS Testing and Certification Requirements .................................................... 84
Version 1.59
18 November 2015
Page 2
DRAFT
6.3
6.4
6.5
6.6
7
Physical requirements ........................................................................................... 84
Functional requirements ........................................................................................ 84
Interface Requirements ......................................................................................... 88
Data requirements ................................................................................................. 88
Prepayment Interface Device Technical Specifications ........................................ 89
7.1
7.2
7.3
7.4
7.5
7.6
8
Overview ............................................................................................................... 89
SMETS Testing and Certification Requirements .................................................... 89
Physical Requirements .......................................................................................... 89
Functional Requirements....................................................................................... 90
Interface Requirements ......................................................................................... 93
Data Requirements ............................................................................................... 95
HAN Connected Auxiliary Load Control Switch Technical Specifications .......... 96
8.1
8.2
8.3
8.4
8.5
8.6
9
SMETS
Overview ............................................................................................................... 96
SMETS Testing and Certification Requirements .................................................... 96
Physical Requirements .......................................................................................... 96
Functional Requirements....................................................................................... 97
Interface Requirements ......................................................................................... 98
Data Requirements ............................................................................................... 99
Glossary ................................................................................................................. 101
Version 1.59
18 November 2015
Page 3
DRAFT
SMETS
1
3 Introduction1
2
3
4
5
The requirement to install metering equipment in Great Britain which complies with these
Smart Metering Equipment Technical Specifications (SMETS) arises from standard licence
conditions 39, 40 and 50.10 in electricity supply licences and standard conditions 33, 34 and
44.10 in gas supply licences.
6
7
8
Section 4 of this document describes the minimum physical, functional, interface, data,
testing and certification requirements of Gas Smart Metering Equipment that a gas Supplier
is required to install to comply with condition 33 (or 44.10) of its licence.
9
10
11
Section 5 of this document describes the minimum physical, functional, interface and data,
testing and certification requirements of Electricity Smart Metering Equipment that an
electricity Supplier is required to install to comply with condition 39 (or 50.10) of its licence.
12
13
14
15
Section 6 of this document constitutes the In-Home Display (IHD) Technical Specifications,
which describe the minimum physical, functional, interface, data, testing and certification
requirements of the IHD installed to comply with condition 34 of the gas supply licence or
condition 40 of the electricity supply licence.
16
17
18
19
Section 7 of this document constitutes the Prepayment Interface Device Technical
Specifications (PPMID), which describe the minimum physical, functional, interface, data,
testing and certification requirements of the PPMID installed to comply with condition 46 of
the gas supply licence or condition 52 of the electricity supply licence.
20
21
22
23
Section 8 of this document constitutes the HAN Connected Auxiliary Load Control Switch
(HCALCS) Technical Specifications, which describe the minimum physical, functional,
interface, testing and certification requirements of the HCALCS installed to comply with
condition 52 of the electricity supply licence.
24
25
26
27
28
29
30
31
This document has been brought into force by the Secretary of State on [ ] for the
purposes of the relevant licence conditions. SMETS2 v1.57 was notified to the European
Commission in accordance with the requirements of Article 8 of Directive 98/34/EC of the
European Parliament and of the Council laying down a procedure for the provision of
information in the field of technical standards and regulations (OJ L 204, 21.7.1998, p. 37) as
amended by Directive 98/48/EC of the European Parliament and of the Council (OJ L 217,
5.8.1998, p. 18). The Government is currently considering if re-notification is required due to
the changes made in this version (v1.59), compared to v1.57.
32
33
34
35
36
This document should be read in conjunction with any other relevant supply licence
conditions and with regard to the wider statutory and regulatory framework applying to
devices installed for the purpose of energy supply to Premises, for example; the Measuring
Instruments (Active Electrical Energy Meters) Regulations 2006 and the Measuring
Instruments (Gas Meters) Regulations 20062.
37
38
39
The Smart Metering technical and security architecture is based on a suite of agreed, open
standards, reflecting the UK Government strategy to facilitate the development of third party
innovative solutions for consumer devices.
40
41
42
Mutual recognition: Any requirement for a Communications Hub to comply with the CHTS
or any of the technical specifications contained or referred to in this document shall be
satisfied by compliance with:
43
44

a relevant standard or code of practice of a national standards body or equivalent body
of any EEA State or Turkey; or
45

any relevant international standard recognised for use in any EEA State or Turkey; or
1
2
Sections 1 and 2 of this document are not used
These regulations transpose the Measuring Instruments Directive (2004/22/EC)
Version 1.59
18 November 2015
Page 4
DRAFT
SMETS
46
47

48
49
50
51
in so far as compliance with the standard, code of practice or technical regulation in question
enables the equipment to achieve, in an equivalent manner, all of the physical, functional,
interface and data capabilities that are achieved by compliance with the requirements of any
of the technical specifications contained or referred to in this document.
any relevant technical regulation with mandatory or de facto mandatory application for
marketing or use in any EEA State or Turkey,
Version 1.59
18 November 2015
Page 5
DRAFT
SMETS
53
4 Gas Smart Metering Equipment
Technical Specifications
54
4.1 Overview
55
56
57
58
Section 4 of this document describes the minimum physical, minimum functional, minimum
interface, minimum data and minimum testing and certification requirements of Gas Smart
Metering Equipment (GSME) that a gas Supplier is required to install to comply with
condition 33 of its licence.
59
60
Any requirements to Lock, Enable, Disable or Arm Supply set out in this Section 4, only
apply to Gas Smart Metering Equipment installed at Domestic Premises.
61
4.2 SMETS Testing and Certification Requirements
62
4.2.1
63
64
GSME shall have been tested to ensure that it meets the requirements described in this
Section 4, and evidence must be available to confirm such testing and conformance.
65
66
4.2.2
67
68
GSME shall meet the requirements described in the current version of the Great Britain
Companion Specifications meaning v0.8.2 or later as published on the SECAS website.
69
70
71
GSME shall have been certified by the ZigBee Alliance as compliant with the ZigBee SEP
v1.2 requirements described in the Great Britain Companion Specifications v0.8.2 or later as
published on the SECAS website.
72
73
4.2.3
74
75
76
GSME shall meet the requirements described in the current version of the Commercial
Product Assurance Security Characteristic Gas Smart Metering Equipment meaning v1.2 or
later as published on CESG’s Website.
77
78
79
GSME shall be certified by CESG as compliant with the current version of the Commercial
Product Assurance Security Characteristic Gas Smart Metering Equipment meaning v1.2 or
later as published on CESG’s Website.
80
4.3 Physical requirements
81
GSME shall as a minimum include the following components:
52
82
83
84
85
86
87
88
89
90
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
Conformance with the SMETS
Conformance with the Great Britain Companion
Specifications3
Conformance with the Commercial Product Assurance
Security Characteristic for GB Smart Metering4
a Clock;
a Data Store;
a Gas Meter;
a HAN Interface;
a Random Number Generator;
a User Interface;
where installed at Domestic Premises, a Valve; and
where installed with a Communications Hub provided by the Data and
Communications Company, a Communications Hub Physical Interface (this may
3
The current version of Great Britain Companion Specification can be found here:
https://www.smartenergycodecompany.co.uk/sec/the-developing-sec
4
The current version of CPA Security Characteristics can be found here: https://www.cesg.gov.uk/servicecatalogue/ProductAssurance/CPA/Pages/Security-Characteristics.aspx
Version 1.59
18 November 2015
Page 6
DRAFT
91
92
SMETS
comprise a Communications Hub Physical Interface forming part of ESME where
present at the time of installation in the Premises).
93
94
95
96
The Communications Hub Physical Interface shall as a minimum include a physical interface
that meets the requirements defined by the Data and Communications Company at the time
of installation (available on the Data and Communications Company’s website) and includes
provision for a DC power supply to the Communications Hub.
97
98
GSME shall include a power source. GSME shall be capable of automatically resuming
operation after loss of power in its operating state prior to such failure.
99
100
101
102
To the extent that it is mains powered, GSME shall be capable of performing the minimum
functional, interface and data requirements set out in Sections 4.4, 4.5 and 4.6 respectively
operating at a nominal voltage of 230VAC without consuming more than an average of 1
watt of electricity under normal operating conditions.
103
GSME shall:
104
105
106
107
108
109
ix.
x.
permanently display the GSME Identifier(4.6.1.1) on the GSME; and
have a Secure Perimeter.
The HAN Interface of GSME shall be capable of joining a ZigBee SEP v1.2 Smart Metering
Home Area Network which:
xi.
xii.
operates within the 2400 – 2483.5 MHz harmonised frequency band; and
supports the Communications Links described in Sections 4.5.1 and 4.5.3.
110
111
On joining a ZigBee SEP v1.2 Smart Metering Home Area Network GSME shall be capable
of generating and sending an Alert to that effect via its HAN Interface.
112
113
114
GSME shall be designed taking all reasonable steps so as to prevent Unauthorised Physical
Access and Unauthorised communications through its Secure Perimeter that could
compromise the Confidentiality and / or Data Integrity of:
115
116
117
118
119
120
121
xiii.
xiv.
xv.
xvi.
xvii.
xviii.
xix.
122
stored or executing on GSME.
123
124
125
GSME shall be capable of detecting any attempt at Unauthorised Physical Access through
its Secure Perimeter that could compromise such Confidentiality and / or Data Integrity and
on such detection shall be capable of:
126
127
xx.
Personal Data;
Consumption data used for billing;
Security Credentials;
Random Number Generator;
Cryptographic Algorithms;
the Gas Meter; and
Firmware and data essential for ensuring its integrity,
providing evidence of such an attempt through the use of tamper evident coatings or
seals,
128
and where reasonably practicable:
129
130
131
132
133
xxi.
xxii.
xxiii.
134
4.4 Functional requirements
135
This section describes the minimum functions that GSME shall be capable of performing.
generating an entry to that effect in the Security Log(4.6.5.17);
generating and sending an Alert to that effect via its HAN Interface; and
where the Supply Tamper State(4.6.4.26) is configured to require Locking,
establishing a Locked state whereby the Supply is Disabled and can only be Armed
in response to a Command to Arm the Supply (as described in Section 4.5.3.7).
Version 1.59
18 November 2015
Page 7
DRAFT
SMETS
136
4.4.1
137
138
The Clock forming part of GSME shall be capable of operating so as to be accurate to within
10 seconds of the UTC date and time under normal operating conditions.
139
140
141
142
GSME shall be capable of comparing its date and time with the Communications Hub Date
and Time, and making adjustments to its date and time. Where the difference between
GSME date and time and the Communications Hub Date and Time is more than 10 seconds
GSME shall be capable of:
143
144
145
i.
ii.
iii.
Clock
not adjusting its date and time;
generating an entry in the Security Log(4.6.5.17) to that effect; and
generating and sending an Alert via its HAN interface.
146
147
Except when executing a Set Clock(4.5.3.20) Command, GSME shall not be capable of
making adjustments to its date and time more than once within any 24 hour time period.
148
4.4.2
149
150
151
GSME, and any Device forming part of it, shall be capable of ensuring that the security
characteristics of all Communications Links it establishes meet the requirements described
in Section 4.4.10.5.
152
153
154
155
GSME shall only be capable of establishing a Communications Link with a Gas Proxy
Function, and a PPMID with Security Credentials in the Device Log(4.6.4.11) and with the
exception of a Communications Hub Function shall not be capable of establishing a
Communications Link via its HAN Interface with any other Devices.
156
157
When any Command addressed to GSME is received via any Communications Link GSME
shall be capable of:
158
159
160
161
162
i.
ii.
iii.
Communications
using the Security Credentials GSME holds, Authenticating to a Trusted Source the
Command;
verifying in accordance with Section 4.4.10.2.3 that the sender of the Command is
Authorised to execute the Command; and
verifying the integrity of the Command.
163
164
165
166
On failure of any of (i) to (iii) above, GSME shall be capable of generating an entry in the
Security Log(4.6.5.17) to that effect, discarding the Command without execution and without
either generating or sending a Response, and generating and sending an Alert to that effect
via its HAN Interface.
167
168
169
When executing an immediate Command, GSME shall be capable of generating and
sending a Response via its HAN Interface, which shall either confirm successful execution of
the Command or shall detail why it has failed to execute the Command.
170
171
172
173
174
Where the Command is not due to be executed immediately, GSME shall be capable of
generating and sending a Response via its HAN Interface to confirm successful receipt.
When executing a future dated Command GSME shall be capable of generating and
sending an Alert via its HAN Interface which shall either confirm successful execution of the
Command or shall detail why it has failed to execute the Command.
175
176
GSME shall only be capable of addressing a Response to the sender of the relevant
Command.
177
178
GSME shall be capable of restricting the generation and sending of each Alert described in
this Section 4 according to the Alerts Configuration Settings(4.6.4.1).
179
4.4.2.1
180
181
GSME shall be capable of establishing and maintaining Communications Links via its HAN
Interface with a minimum of one PPMID.
Version 1.59
Communications Links with a PPMID via its HAN Interface
18 November 2015
Page 8
DRAFT
182
183
184
185
SMETS
GSME shall be capable of supporting the following types of Communications Links:
i.
ii.
receiving the Commands (set out in Section 4.5.3) from a PPMID every 30 minutes;
and
generating and sending the Responses (set out in Section 4.5.3) to a PPMID.
186
187
4.4.2.2
188
189
GSME shall be capable of establishing and maintaining Communications Links via its HAN
Interface with one Communications Hub Function.
190
191
GSME shall be capable of receiving the Communications Hub Date and Time from the
Communications Hub Function.
192
4.4.2.3
193
194
GSME shall be capable of establishing and maintaining a Communications Link via its HAN
Interface with a Gas Proxy Function.
195
196
GSME shall be capable of generating and sending the information (set out in Section 4.5.1)
to a Gas Proxy Function.
197
4.4.3
198
199
GSME shall be capable of retaining all information held in its Data Store at all times,
including on loss of power.
200
4.4.4
201
202
203
204
GSME shall be capable of preventing the display on the User Interface of items annotated
[PIN] in Section 4.4.5, and preventing access on the User Interface to the Commands
annotated [PIN] in Section 4.5.2, except on successful execution of an Allow Access to User
Interface Command (4.5.2.3) via the User Interface.
205
4.4.5
206
207
GSME shall be capable of displaying the following up to date information on its User
Interface:
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
xii.
xiii.
xiv.
xv.
xvi.
xvii.
xviii.
Communications Links with a Communications Hub Function via its HAN
Interface
Communications with a Gas Proxy Function via its HAN Interface
Data storage
Privacy PIN Protection
Display of information
the Payment Mode(4.6.4.21) currently in operation, being Prepayment Mode or
Credit Mode [PIN];
the Tariff TOU Register Matrix(4.6.5.20) and the Tariff Block Counter
Matrix(4.6.5.19);
the Consumption Register(4.6.5.4);
the Meter Balance(4.6.5.11) [PIN];
the Debt to Clear (calculated as set out in Section 4.4.7.2) [PIN];
the Customer Identification Number(4.6.4.7) [PIN];
whether Emergency Credit is available for activation [PIN];
whether GSME has suspended the Disablement of Supply during a period defined in
the Non-Disablement Calendar(4.6.4.20) (as set out in Section 4.4.7.2) [PIN];
the Emergency Credit Balance(4.6.5.8) where Emergency Credit is activated [PIN];
any low credit condition [PIN];
where GSME includes a Battery, any low battery condition;
the Supply State(4.6.5.18);
any time-based debts and Time-based Debt Recovery rates [PIN];
any payment-based debt [PIN];
any accumulated debt recorded in the Accumulated Debt Register(4.6.5.1) [PIN];
the Meter Point Reference Number (MPRN)(4.6.4.19) [PIN];
the Local Time;
any Standing Charge(4.6.4.23) [PIN];
Version 1.59
18 November 2015
Page 9
DRAFT
229
230
231
xix.
xx.
xxi.
SMETS
the Contact Details(4.6.4.4); and
the Active Tariff Price(4.6.5.2) [PIN];
the Event Log(4.6.5.9) (with the exception of any Personal Data).
232
233
GSME shall be capable of displaying the Security Log(4.6.5.17) on its User Interface
following physical access through the Secure Perimeter of GSME.
234
235
GSME shall be capable of displaying Currency Units in GB Pounds and European Central
Bank Euro.
236
4.4.6
237
4.4.6.1
238
239
240
Where GSME includes a Battery, it shall be capable of estimating the remaining Battery
capacity in days (to facilitate replacement of the Battery before it is fully depleted) and
storing the estimate in Remaining Battery Capacity(4.6.5.16).
241
242
If the Remaining Battery Capacity(4.6.5.16) falls below ten percent of the nominal Battery
capacity GSME shall be capable of:
Monitoring
Battery capacity
243
244
i.
ii.
245
4.4.6.2
246
Prior to or at the loss of power, GSME shall be capable of:
i.
generating an entry to that effect in the Event Log(4.6.5.9); and
generating and sending an Alert to that effect via its HAN Interface.
GSME power supply
247
248
249
250
251
ii.
252
4.4.7
253
254
GSME shall be capable of operating in Credit Mode and Prepayment Mode and of being
remotely switched from one mode to the other.
255
4.4.7.1
256
257
GSME, when operating in Credit Mode, shall be capable of maintaining a calculation of the
Meter Balance(4.6.5.11) based on:
i.
in circumstances where the Supply Depletion State(4.6.4.25) is configured to require
Locking, establishing a Locked state whereby the Supply is Disabled and can only
be Armed in response to a Command to Arm the Supply (as described in Section
4.5.3.7); and
generating and sending an Alert to that effect via its HAN Interface.
Payment Mode
Credit Mode
258
259
260
261
262
263
264
the Consumption in the Tariff TOU Register Matrix(4.6.5.20) converted by Calorific
Value(4.6.4.3) and Conversion Factor(4.6.4.5) and the Prices in the Tariff TOU Price
Matrix(4.6.4.32) and, if operating Time-of-use with Block Pricing, the Consumption in
the Tariff Block Counter Matrix(4.6.5.19) converted by Calorific Value(4.6.4.3) and
Conversion Factor(4.6.4.5) and the Prices in the Tariff Block Price Matrix(4.6.4.29);
and
the Standing Charge(4.6.4.23).
ii.
265
4.4.7.2
266
267
268
269
GSME shall be capable of operating in Prepayment Mode, including during periods of loss of
its Communications Link via its HAN Interface, and maintaining a balance of credit and
reflecting any reduction in credit based on Consumption, standing charge and Time-based
Debt Recovery.
270
271
272
GSME shall be capable of adding credit to the Meter Balance(4.6.5.11) (as set out in
Sections 4.5.2.2 and 4.5.3.3) and reducing the amount of credit in the Meter
Balance(4.6.5.11).
Version 1.59
Prepayment Mode
18 November 2015
Page 10
DRAFT
SMETS
273
274
275
276
277
278
279
280
281
282
283
GSME shall be capable of making Emergency Credit available to the Consumer (by means
of the Emergency Credit Balance(4.6.5.8)) if the Meter Balance(4.6.5.11) is below the
Emergency Credit Threshold(4.6.4.14). GSME shall be capable of displaying the availability
of Emergency Credit on its User Interface and of generating and sending an Alert indicating
the availability of Emergency Credit via its HAN Interface. The amount of Emergency Credit
made available to the Consumer shall be equal to the Emergency Credit Limit(4.6.4.13).
GSME shall be capable of reducing the amount of credit in the Emergency Credit
Balance(4.6.5.8) where Emergency Credit is activated by the Consumer (as set out in
Sections 4.5.2.1 and 4.5.3.1) and the Meter Balance(4.6.5.11) is exhausted. Any
Emergency Credit used shall be repaid when credit is added to GSME (as set out in
Sections 4.5.2.2 and 4.5.3.3).
284
285
286
GSME shall be capable of reducing the Meter Balance(4.6.5.11) until it reaches the
Disablement Threshold(4.6.4.12) followed by reducing the Emergency Credit
Balance(4.6.5.8), where activated, until exhausted, on the basis of:
287
288
289
290
291
292
293
294
i.
ii.
iii.
the Consumption in the Tariff TOU Register Matrix(4.6.5.20) converted by Calorific
Value(4.6.4.3) and Conversion Factor(4.6.4.5) and the Prices in the Tariff TOU Price
Matrix(4.6.4.32) and, if operating Time-of-use with Block Pricing, the Consumption in
the Tariff Block Counter Matrix(4.6.5.19) converted by Calorific Value(4.6.4.3) and
Conversion Factor(4.6.4.5) and the Prices in the Tariff Block Price Matrix(4.6.4.29);
the Standing Charge(4.6.4.23); and
the recovery of debt hourly or daily through each of the Time Debt Registers [1 …
2](4.6.5.21) at rates defined by the Debt Recovery Rates [1 … 2](4.6.4.9).
295
296
297
298
Where configured by Suspend Debt Emergency(4.6.4.28) to do so and when Emergency
Credit is in use, GSME shall be capable of suspending the application of (ii) and (iii) to the
Emergency Credit Balance(4.6.5.8), and accumulating (ii) and (iii) in the Accumulated Debt
Register(4.6.5.1).
299
300
GSME shall be capable of recording debt recovered, or accumulated in the Accumulated
Debt Register(4.6.5.1), in the Billing Data Log(4.6.5.3).
301
302
GSME shall be capable of monitoring the Meter Balance(4.6.5.11) and where activated the
Emergency Credit Balance(4.6.5.8) and:
303
304
305
306
307
308
iv.
v.
309
310
311
312
313
314
315
316
317
318
319
320
321
if the combined credit of the Meter Balance(4.6.5.11) and Emergency Credit
Balance(4.6.5.8) falls below the Low Credit Threshold(4.6.4.16), displaying an Alert
to that effect on its User Interface and generating and sending an Alert to that effect
via its HAN Interface;
if the combined credit of the Meter Balance(4.6.5.11) and Emergency Credit
Balance(4.6.5.8) falls below the Disablement Threshold(4.6.4.12):
a) receiving and executing Add Credit(4.5.3.3) and Activate Emergency
Credit(4.5.3.1) Commands from a PPMID and a Gas Proxy Function; and
b) once any such Commands have been executed if the combined credit of the
Meter Balance(4.6.5.11) and Emergency Credit Balance(4.6.5.8) remains
below the Disablement Threshold(4.6.4.12), Disabling the Supply, displaying an
Alert to that effect on its User Interface and generating and sending an Alert to
that effect via its HAN Interface;
vi.
where the Supply is Disabled (as set out in (b)) above):
c) where configured by Suspend Debt Disabled(4.6.4.27) not to suspend Timebased Debt Recovery, continuing to apply (ii) and (iii) above to reduce the
Meter Balance(4.6.5.11);
d) where configured by Suspend Debt Disabled(4.6.4.27) to suspend Time-based
Debt Recovery, suspending the application of (iii) above to the Meter
Version 1.59
18 November 2015
Page 11
DRAFT
SMETS
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
Balance(4.6.5.11) and continuing to apply (ii) above to reduce the Meter
Balance(4.6.5.11); and
vii.
if the Supply is Enabled, suspending the Disablement of Supply (as set out in (b))
above) during periods defined in the Non-Disablement Calendar(4.6.4.20),
continuing to reduce the Meter Balance(4.6.5.11) on the basis of (i), (ii) and (iii)
above, displaying on its User Interface an indication that the combined Meter
Balance(4.6.5.11) and Emergency Credit Balance(4.6.5.8) is below the Disablement
Threshold(4.6.4.12) and that Disablement of Supply due to insufficient credit has
been suspended, and generating and sending an Alert that Disablement of Supply
due to insufficient credit has been suspended via its HAN Interface.
If the Meter Balance(4.6.5.11) is equal to or below the Disablement Threshold(4.6.4.12)
GSME shall be capable of maintaining a calculation of the Debt to Clear based on:
viii.
ix.
x.
xi.
the difference between the Meter Balance(4.6.5.11) and the Disablement
Threshold(4.6.4.12);
amount of debt accumulated in the Accumulated Debt Register(4.6.5.1);
amount of Emergency Credit activated and used by the Consumer; and
the payment-based debt to be collected based on (viii), (ix) and (x) (as defined by
Debt Recovery per Payment(4.6.4.8) taking account of the amount remaining in the
Payment Debt Register(4.6.5.13), the payment-based debt payments in the Billing
Data Log(4.6.5.3) and the Debt Recovery Rate Cap(4.6.4.10)).
If the amount of debt to be collected from a Debt Register through Time-based Debt
Recovery, Payment-based Debt Recovery or an Adjust Debt Command is greater than the
amount in that Debt Register then GSME shall be capable of:
345
346
xii.
xiii.
adding the difference to the Meter Balance(4.6.5.11); and
setting the amount in that Debt Register to zero.
347
4.4.8
348
GSME shall be capable of applying Time-of-use Pricing and Time-of-use with Block Pricing.
349
GSME shall be capable of maintaining the Active Tariff Price(4.6.5.2).
350
4.4.8.1
351
352
GSME shall be capable of recording Consumption according to Time-of-use Bands in one of
four Tariff Registers in the Tariff TOU Register Matrix(4.6.5.20).
353
354
355
GSME shall be capable of switching between different Tariff Registers once per Day. The
switching between Time-of-use Bands and thus Tariff Registers shall be based on the
switching rules defined in the Tariff Switching Table(4.6.4.30).
356
4.4.8.2
357
358
GSME shall be capable of recording Consumption according to Time-of-use Bands in one of
four Tariff Registers in the Tariff TOU Register Matrix(4.6.5.20).
359
360
361
362
GSME shall also be capable of accumulating Consumption in one of four Block Counters in
the Tariff Block Counter Matrix(4.6.5.19) for the first Time-of-use Band. GSME shall be
capable of switching between Block Counters according to the Consumption thresholds in
the Tariff Threshold Matrix(4.6.4.31).
363
364
365
GSME shall be capable of switching between different Tariff Registers once per Day. The
switching between Time-of-use Bands and thus Tariff Registers shall be based on the
switching rules set out in the Tariff Switching Table(4.6.4.30).
Pricing
Version 1.59
Time-of-use Pricing
Time-of-use with Block Pricing
18 November 2015
Page 12
DRAFT
SMETS
366
4.4.9
Recording
367
4.4.9.1
Billing data
368
369
In accordance with the timetable set out in the Billing Calendar(4.6.4.2) GSME shall be
capable of taking a UTC date and time stamped copy of:
370
371
372
373
374
375
376
377
378
i.
ii.
iii.
the Tariff TOU Register Matrix(4.6.5.20);
the Tariff Block Counter Matrix(4.6.5.19); and
the Consumption Register(4.6.5.4),
and where in Prepayment mode:
iv.
v.
vi.
vii.
viii.
the Meter Balance(4.6.5.11);
the Emergency Credit Balance(4.6.5.8);
the Payment Debt Register(4.6.5.13);
the Time Debt Registers [1 … 2](4.6.5.21); and
the Accumulated Debt Register(4.6.5.1),
379
380
381
in the Billing Data Log(4.6.5.3), then immediately resetting the Block Counters in the Tariff
Block Counter Matrix(4.6.5.19) and if operating in Credit Mode immediately resetting the
Meter Balance(4.6.5.11).
382
4.4.9.2
383
384
GSME shall be capable of recording cumulative Consumption in the Consumption
Register(4.6.5.4).
385
386
GSME shall be capable of recording to the Cumulative and Historical Value Store(4.6.5.5) in
kWh:
387
388
389
390
391
i.
ii.
iii.
iv.
v.
Consumption data
Energy Consumption on each of the eight Days prior to the current Day;
Energy Consumption in the Week in which the calculation is performed;
Energy Consumption in each of the five Weeks prior to such Week;
Energy Consumption in the month in which the calculation is performed; and
Energy Consumption in the thirteen months prior to such month.
392
393
GSME shall be capable of recording to the Cumulative Current Day Value Store(4.6.5.6) in
kWh the Energy Consumption on the Day up to the Local Time.
394
4.4.9.3
395
396
GSME shall be capable of calculating and recording in the Cumulative and Historical Value
Store(4.6.5.5) the cost of:
397
398
399
400
401
i.
ii.
iii.
iv.
v.
Cost of Consumption data
Consumption on each of the eight Days prior to the current Day;
Consumption in the Week in which the calculation is performed;
Consumption in each of the five Weeks prior to such Week;
Consumption in the month in which the calculation is performed; and
Consumption in the thirteen months prior to such month.
402
403
GSME shall be capable of recording to the Cumulative Current Day Value Store(4.6.5.6) the
cost of Consumption on the Day up to the Local Time.
404
GSME shall be capable of calculating cost of Consumption as above on the basis of:
405
406
407
408
409
410
411
vi.
vii.
the Consumption in the Tariff TOU Register Matrix(4.6.5.20) converted by Calorific
Value(4.6.4.3) and Conversion Factor(4.6.4.5) and the Prices in the Tariff TOU Price
Matrix(4.6.4.32) and, if operating Time-of-use with Block Pricing, the Consumption in
the Tariff Block Counter Matrix(4.6.5.19) converted by Calorific Value(4.6.4.3) and
Conversion Factor(4.6.4.5) and the Prices in the Tariff Block Price Matrix(4.6.4.29);
and
the Standing Charge(4.6.4.23).
Version 1.59
18 November 2015
Page 13
DRAFT
SMETS
412
4.4.9.4
413
414
415
416
GSME shall be capable of taking a copy of and storing the Tariff TOU Register
Matrix(4.6.5.20), the Tariff Block Counter Matrix(4.6.5.19) and the Consumption
Register(4.6.5.4) together with a UTC date and time stamp in the Daily Read Log(4.6.5.4)
every day at midnight UTC.
417
418
419
420
If operating in Prepayment Mode GSME shall be capable of recording the Meter
Balance(4.6.5.11), Emergency Credit Balance(4.6.5.8), Accumulated Debt Register(4.6.5.1),
Payment Debt Register(4.6.5.13) and Time Debt Registers [1 … 2](4.6.5.21) in the
Prepayment Daily Read Log(4.6.5.14) every day at midnight UTC.
421
4.4.9.5
422
423
424
GSME shall be capable of recording Consumption in each thirty minute period (commencing
at the start of minutes 00 and 30 in each hour), including the UTC date and time at the end
of the 30 minute period to which the Consumption relates, in the Profile Data Log(4.6.5.15).
425
4.4.10 Security
426
4.4.10.1
427
428
429
430
GSME shall be designed taking all reasonable steps so as to ensure that any failure or
compromise of its integrity shall not compromise the Security Credentials or Personal Data
stored on it or compromise the integrity of any other Device to which it is connected by
means of a Communications Link.
431
432
GSME shall be capable of securely disabling Critical Commands other than those
Commands set out in Section 4.5 that are Critical Commands.
433
434
435
GSME shall be capable of verifying its Firmware at power-on and prior to activation of the
Firmware, to verify that the Firmware, at that time, is in the form originally received. On
failure of verification GSME shall be capable of:
436
437
438
439
440
441
442
443
i.
ii.
Daily read data
Half hour profile data
General
generating an entry to that effect in the Security Log(4.6.5.17); and
generating and sending an Alert to that effect via its HAN Interface.
Where GSME comprises more than one Device, each Device other than the Gas Meter shall
be capable of verifying its Firmware at power-on and prior to activation of the Firmware, to
verify that the Firmware, at that time, is in the form originally received. On failure of
verification GSME shall be capable of:
iii.
iv.
generating an entry to that effect in the Security Log(4.6.5.17); and
generating and sending an Alert to that effect via its HAN Interface.
444
445
GSME shall be capable of logging in the Security Log(4.6.5.17) the occurrence and type of
any Sensitive Event.
446
4.4.10.2
447
4.4.10.2.1
448
449
GSME shall be capable of generating Public-Private Key Pairs to support the Cryptographic
Algorithms set out in Section 4.4.10.3.
450
451
452
GSME shall be capable of securely storing such Private Keys and shall be capable of
formatting and sending via its HAN Interface a Certificate Signing Request containing the
corresponding Public Key and the GSME Identifier(4.6.1.1).
453
GSME shall be capable of securely storing Key Agreement values.
454
4.4.10.2.2
455
456
GSME shall be capable of securely storing Security Credentials from Certificates including
for use in the Cryptographic Algorithms as set out in Section 4.4.10.3.
Version 1.59
Security Credentials
Meter Private Keys
Public Key Certificates
18 November 2015
Page 14
DRAFT
SMETS
457
458
459
During the replacement of any GSME Security Credentials(4.6.4.15) (as set out in Section
4.5.3.18) GSME shall be capable of ensuring that the GSME Security Credentials(4.6.4.15)
being replaced remain usable until the successful completion of the replacement.
460
4.4.10.2.3
461
462
GSME shall be capable of restricting Authorisation to execute Commands and of issuing
Alerts according to Role permissions.
463
4.4.10.3
464
GSME shall be capable of supporting the following Cryptographic Algorithms:
465
466
467
468
469
470
471
472
473
474
i.
ii.
iii.
Role Based Access Control (RBAC)
Cryptographic Algorithms
Elliptic Curve DSA;
Elliptic Curve DH; and
SHA-256.
In executing and creating any Command, Response or Alert, GSME shall be capable of
applying Cryptographic Algorithms (alone or in combination) for:
iv.
v.
vi.
vii.
viii.
Digital Signing;
Digital Signature verification;
Hashing;
Message Authentication; and
Encryption and Decryption.
475
4.4.10.4
476
477
GSME shall only be capable of activating its Firmware on receipt of an Activate Firmware
Command (as set out in Section 4.5.3.2).
478
4.4.10.5
479
480
GSME shall be capable of preventing and detecting, on all of its interfaces, Unauthorised
access that could compromise the Confidentiality and / or Data Integrity of:
481
482
483
484
485
486
487
488
489
490
491
492
493
i.
ii.
iii.
iv.
Firmware
Communications
Personal Data whilst being transferred via an interface;
Consumption data used for billing whilst being transferred via an interface;
Security Credentials whilst being transferred via an interface; and
Firmware and data essential for ensuring its integrity whilst being transferred via an
interface,
and any Command that could compromise the Confidentiality and / or Data Integrity of:
v.
vi.
vii.
viii.
Personal Data;
Consumption data used for billing;
Security Credentials; and
Firmware and data essential for ensuring its integrity,
stored or executing on GSME, and on such detection shall be capable of:
ix.
x.
generating an entry to that effect in the Security Log(4.6.5.17); and
generating and sending an Alert to that effect via its HAN Interface.
494
495
GSME shall be capable of employing techniques to protect against Replay Attacks relating
to Commands received.
496
497
GSME shall not be capable of executing a Command to modify or delete entries from the
Security Log(4.6.5.17).
498
4.5 Interface requirements
499
500
501
This section describes the minimum required interactions which GSME shall be capable of
undertaking via its HAN Interface and its User Interface (including with Devices as set out in
Sections 4.4.2.1 and 4.4.2.3).
Version 1.59
18 November 2015
Page 15
DRAFT
SMETS
502
4.5.1
503
504
505
506
507
GSME shall be capable, immediately upon establishment of a Communications Link with a
Gas Proxy Function (as set out in Section 4.4.2.3), of providing the Constant and
Operational Data (set out in Sections 4.6.1 and 4.6.5) to that Gas Proxy Function (and with
the exception of the Cumulative and Historical Value Store(4.6.5.5) and the Profile Data
Log(4.6.5.15), updates of any changes in that data every 30 minutes thereafter).
508
4.5.2
509
510
GSME shall be capable of executing immediately the Commands set out in this Section
4.5.2 following their receipt via its User Interface.
511
512
GSME shall be capable of logging all such Commands received and Outcomes in the Event
Log(4.6.5.9).
513
4.5.2.1
514
515
A Command to activate Emergency Credit when GSME is operating in Prepayment Mode
where Emergency Credit is available (as set out in Section 4.4.7.2).
516
517
518
519
520
In executing the Command, if the Supply is Disabled, GSME shall be capable of Arming the
Supply if the combined credit of the Meter Balance(4.6.5.11) and Emergency Credit
Balance(4.6.5.8) rises above the Disablement Threshold(4.6.4.12) and displaying any such
change in the Supply State(4.6.5.18) on its User Interface and generating and sending an
Alert that the Supply has been Armed via its HAN Interface.
521
4.5.2.2
522
523
A Command to accept credit to be applied to GSME when GSME is operating in Prepayment
Mode on input of a UTRN. In executing the Command, GSME shall be capable of:
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
i.
ii.
iii.
iv.
v.
vi.
Gas Proxy Function information provision
User Interface Commands
Activate Emergency Credit [PIN]
Add Credit
comparing the credit value of the UTRN with the Maximum Credit
Threshold(4.6.4.17) and rejecting the UTRN where the credit value is greater than
that threshold;
comparing the projected new Meter Balance(4.6.5.11) (calculated on the basis of
(xii) to (xv) below and the credit value of the UTRN and rejecting the UTRN where
the projected new Meter Balance(4.6.5.11) is greater than the Maximum Meter
Balance Threshold(4.6.4.18);
verifying the Authenticity of the UTRN;
verifying that GSME is the intended recipient of the UTRN;
using the UTRN to generate a PTUT Counter, and comparing this against the last
100 verified PTUT Counters and rejecting duplicate presentation of verified UTRNs
and PTUTs; and
controlling the number of invalid UTRN entries entered and processed.
GSME shall be capable of generating an entry in the Security Log(4.6.5.17):
vii.
viii.
ix.
x.
xi.
where the UTRN is rejected as set out in (i) above;
where the UTRN is rejected as set out in (ii) above;
on failure of (iii) above;
on failure of (iv) above; and
where duplicates are rejected as set out in (v) above.
In executing the Command, GSME shall be capable of applying the credit added in the
following order:
xii.
xiii.
recovery of payment-based debt of an amount defined by Debt Recovery per
Payment(4.6.4.8) from the Payment Debt Register(4.6.5.13) subject to the Debt
Recovery Rate Cap(4.6.4.10);
recovery of debt accumulated in the Accumulated Debt Register(4.6.5.1);
Version 1.59
18 November 2015
Page 16
DRAFT
549
550
551
xiv.
xv.
SMETS
repayment of Emergency Credit activated and used by the Consumer; and
adding remaining credit (the credit after deduction of (xii), (xiii) and (xiv) above) to
the Meter Balance(4.6.5.11).
552
553
554
555
In executing the Command, GSME shall be capable of Arming the Supply if the Meter
Balance(4.6.5.11) rises above the Disablement Threshold(4.6.4.12) and displaying any such
change in the Supply State(4.6.5.18) on its User Interface and generating and sending an
Alert that the Supply has been Armed via its HAN Interface.
556
In executing the Command, GSME shall be capable of:
557
558
559
560
561
xvi.
xvii.
recording the credit applied to the Meter Balance(4.6.5.11) and the amount of
payment-based debt recovered (as set out in (xii)) in the Billing Data Log(4.6.5.3);
and
generating and sending an Alert containing the UTC date and time of the last update
of the Meter Balance(4.6.5.11) via its HAN Interface.
562
4.5.2.3
Allow Access to User Interface
563
564
565
566
Where Privacy PIN Protection is enabled, a Command to enable temporary access to the
restricted display items annotated [PIN] in Section 4.4.5 and the restricted User Interface
Commands annotated [PIN] in Section 4.5.2 on input of a number that matches the Privacy
PIN(4.6.3.1).
567
4.5.2.4
568
569
570
A Command to check immediately for any pending Add Credit(4.5.3.3) and Activate
Emergency Credit(4.5.3.1) Commands. If there are any such pending Commands GSME
shall be capable of executing the Commands as set out in Section 4.5.3.
571
4.5.2.5
572
A Command to disable Privacy PIN Protection.
573
4.5.2.6
574
A Command to Enable the Supply if the Supply is Armed.
575
576
577
578
In executing the Command, GSME shall be capable of detecting when the flow rate exceeds
a level defined by Uncontrolled Gas Flow Rate(4.6.4.33) and where the flow rate is
exceeded, of Disabling the Supply and then Arming the Supply and sounding an Alarm via
its User Interface.
579
4.5.2.7
580
581
A Command to reset the Remaining Battery Capacity(4.6.5.16). The Command shall only
be available following physical access through the Secure Perimeter of GSME.
582
In executing the Command GSME shall be capable of:
Check for HAN Interface Commands
Disable Privacy PIN Protection [PIN]
Enable Supply [PIN]
Reset Remaining Battery Capacity
583
584
i.
ii.
585
586
4.5.2.8
587
588
A Command to seek the frequency at which a ZigBee SEP v1.2 Smart Metering Home Area
Network is operating and then:
589
590
591
592
i.
ii.
iii.
generating an entry to that effect in the Security Log(4.6.5.17); and
generating and sending an Alert to that effect via its HAN Interface.
Find Smart Metering Home Area Network and Re-establish
Communications Links
re-establish the Communications Links set out in Sections 4.4.2.1, 4.4.2.2 and
4.4.2.3;
generate an entry to that effect in the Event Log(4.6.5.9); and
generate and send an Alert to that effect via its HAN Interface.
Version 1.59
18 November 2015
Page 17
DRAFT
SMETS
593
594
Where the GSME has Communications Links set out in (i) GSME shall be capable of not
executing the Command.
595
4.5.2.9
596
A Command to set a new value of the Privacy PIN(4.6.3.1).
597
598
In executing the Command where Privacy PIN Protection is disabled GSME shall be capable
of enabling Privacy PIN Protection.
599
4.5.2.10
600
Where GSME includes a Valve, a Command to:
601
602
603
604
605
606
607
608
i.
ii.
iii.
Set Privacy PIN [PIN]
Test Valve
where the Supply State(4.6.5.18) is Enabled, Disable the Supply for one minute and
then Arm the Supply and set the Supply State(4.6.5.18) accordingly;
where the Supply State(4.6.5.18) is Armed, Enable the Supply for one minute and
then Arm the Supply and set the Supply State(4.6.5.18) accordingly;
where the Supply State(4.6.5.18) is Disabled, Enable the Supply for one minute and
then Disable the Supply and set the Supply State(4.6.5.18) accordingly.
The Command shall only be available following physical access through the Secure
Perimeter of GSME. In executing the Command GSME shall be capable of:
609
610
iv.
v.
generating an entry to that effect in the Event Log(4.6.5.9); and
generating and sending an Alert to that effect via its HAN.
611
4.5.3
612
613
GSME shall be capable of executing the Commands set out in this section. GSME shall be
capable of logging all Commands received and Outcomes in the Event Log(4.6.5.9).
614
615
616
617
GSME shall be capable of executing Commands immediately on receipt (‘immediate
Commands’) and where specified in the Great Britain Companion Specification at a future
date (‘future dated Commands’). A future dated Command shall include the UTC date and
time at which the Command shall be executed by GSME.
618
619
620
621
GSME shall be capable of cancelling a future dated Command. A future dated Command
shall be capable of being cancelled by an Authorised party, subject to RBAC (as set out in
Section 4.4.10.2.3). GSME shall be capable of generating and sending a Response
acknowledging that a future dated Command has been successfully cancelled.
622
4.5.3.1
623
624
A Command to activate Emergency Credit when GSME is operating in Prepayment Mode
where Emergency Credit is available (as set out in Section 4.4.7.2).
625
626
627
628
629
In executing the Command where the Supply is Disabled GSME shall be capable of Arming
the Supply if the combined credit of the Meter Balance(4.6.5.11) and Emergency Credit
Balance(4.6.5.8) rises above the Disablement Threshold(4.6.4.12) and displaying any such
change in the Supply State(4.6.5.18) on its User Interface and generating and sending an
Alert that the Supply has been Armed via its HAN Interface.
630
631
When operating in Credit Mode, GSME shall be capable of not executing the Command and
generating and sending a Response to that effect via its HAN Interface.
632
4.5.3.2
633
A Command to activate Firmware.
634
635
In executing the Command GSME shall be capable of installing new Firmware using a
mechanism that is robust against failure and loss of data.
HAN Interface Commands
Version 1.59
Activate Emergency Credit
Activate Firmware
18 November 2015
Page 18
DRAFT
SMETS
636
637
638
The new Firmware shall include version information. Where new Firmware is successfully
installed, GSME shall be capable of recording the version information of that new Firmware
in Firmware Version(4.6.5.10).
639
4.5.3.3
640
641
A Command to accept credit to be applied to GSME when GSME is operating in Prepayment
Mode on receipt of a UTRN from a PPMID or a PTUT from an Authorised party.
642
643
In executing the Command following receipt of a UTRN from a PPMID GSME shall be
capable of applying credit as set out in Section 4.5.2.2.
644
645
In executing the Command following receipt of a PTUT from an Authorised party, GSME
shall be capable of:
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
i.
ii.
iii.
iv.
v.
vi.
Add Credit
comparing the credit value of the PTUT with the Maximum Credit
Threshold(4.6.4.17) and rejecting the PTUT where the credit value is greater than
that threshold;
comparing the projected new Meter Balance(4.6.5.11) (calculated on the basis of
(xii) to (xv) below and the credit value of the PTUT and rejecting the PTUT where
the projected new Meter Balance(4.6.5.11) is greater than the Maximum Meter
Balance Threshold(4.6.4.18);
verifying the Authenticity of the PTUT;
verifying that GSME is the intended recipient of the PTUT;
comparing the PTUT Counter against the last 100 verified PTUT Counters and
rejecting duplicate presentation of verified UTRNs and PTUTs; and
controlling the number of invalid PTUT entries entered and processed.
GSME shall be capable of generating an entry in the Security Log(4.6.5.17):
vii.
viii.
ix.
x.
xi.
where the PTUT is rejected as set out in (i) above;
where the PTUT is rejected as set out in (ii) above;
on failure of (iii) above;
on failure of (iv) above; and
where duplicates are rejected as set out in (v) above.
In executing the Command, GSME shall be capable of applying the credit added in the
following order:
xii.
xiii.
xiv.
xv.
recovery of payment-based debt of an amount defined by Debt Recovery per
Payment(4.6.4.8) from the Payment Debt Register(4.6.5.13) subject to the Debt
Recovery Rate Cap(4.6.4.10);
recovery of debt accumulated in the Accumulated Debt Register(4.6.5.1);
repayment of Emergency Credit activated and used by the Consumer; and
adding remaining credit (the credit after deduction of (xii), (xiii) and (xiv) above) to
the Meter Balance(4.6.5.11).
673
674
675
676
In executing the Command, GSME shall be capable of Arming the Supply if the Meter
Balance(4.6.5.11) rises above the Disablement Threshold(4.6.4.12), displaying any such
change in the Supply State(4.6.5.18) on its User Interface and generating and sending an
Alert that the Supply has been Armed via its HAN Interface.
677
678
679
In executing the Command, GSME shall be capable of recording the credit applied to the
Meter Balance(4.6.5.11) and the amount of payment-based debt recovered (as set out in
(xii)) in the Billing Data Log(4.6.5.3).
680
681
682
In executing the Command from a PPMID, GSME shall be capable of generating and
sending an Alert containing the UTC date and time stamp of the last update of the Meter
Balance(4.6.5.11) via its HAN Interface.
Version 1.59
18 November 2015
Page 19
DRAFT
SMETS
683
684
When operating in Credit Mode, GSME shall be capable of not executing the Command and
generating and sending a Response to that effect via its HAN Interface.
685
4.5.3.4
686
687
A Command to add Security Credentials for a PPMID or a Gas Proxy Function to the Device
Log(4.6.4.11).
688
In executing the Command, GSME shall be capable of:
Add Device Security Credentials
689
690
i.
ii.
691
4.5.3.5
692
693
A Command to apply positive and negative adjustments to the Time Debt Registers [1 …
2](4.6.5.21) and the Payment Debt Register(4.6.5.13) when operating in Prepayment Mode.
694
695
When operating in Credit Mode, GSME shall be capable of not executing the Command and
generating and sending a Response to that effect via its HAN Interface.
696
4.5.3.6
697
A Command to apply positive and negative adjustments to the Meter Balance(4.6.5.11).
698
699
700
701
702
In executing the Command where GSME is operating in Prepayment Mode and where,
following any such adjustment, the Meter Balance(4.6.5.11) rises above the Disablement
Threshold(4.6.4.12), GSME shall be capable of Arming the Supply, displaying any such
change in the Supply State(4.6.5.18) on its User Interface and generating and sending an
Alert that the Supply has been Armed via its HAN Interface.
703
4.5.3.7
704
A Command to return GSME from a Locked state to an Unlocked state.
705
In executing the Command:
706
707
708
709
710
711
i.
ii.
verifying the Security Credentials; and
recording the Command and Outcome to the Security Log(4.6.5.17).
Adjust Debt
Adjust Meter Balance
Arm Supply
where the state of the Supply as determined by GSME (in accordance with the
requirements to Arm and Disable Supply in this Section 4) is Disabled, GSME shall
not Arm the Supply and shall set the Supply State(4.6.5.18) to Disabled; and
where the state of the Supply as determined by GSME (in accordance with the
requirements to Arm and Disable Supply in this Section 4) is Enabled or Armed,
GSME shall Arm the Supply and shall set the Supply State(4.6.5.18) to Armed.
712
4.5.3.8
713
714
A Command to clear all entries from the Event Log(4.6.5.9). GSME shall be capable of
logging that the Command has been executed in the Security Log(4.6.5.17).
715
4.5.3.9
716
A Command to disable Privacy PIN Protection.
717
4.5.3.10
718
719
A Command to establish a Locked state whereby the Supply is Disabled and can only be
Armed in response to a Command to Arm the Supply (as described in Section 4.5.3.7).
720
721
In executing the Command GSME shall be capable of setting the Supply State(4.6.5.18) to
Disabled.
722
4.5.3.11
723
724
A Command to generate a Public-Private Key Pair and issue a corresponding Certificate
Signing Request.
Version 1.59
Clear Event Log
Disable Privacy PIN Protection
Disable Supply
Issue GSME Security Credentials
18 November 2015
Page 20
DRAFT
SMETS
725
4.5.3.12
Read Configuration Data
726
727
A Command to read the value of one or more of the configuration data items set out in
Section 4.6.4.
728
729
In executing the Command, GSME shall be capable of sending such value(s) in a Response
via its HAN Interface.
730
4.5.3.13
731
732
A Command to read the value of one or more of the constant data items set out in Section
4.6.1.
733
734
In executing the Command, GSME shall be capable of sending such value(s) in a Response
via its HAN Interface.
735
4.5.3.14
736
737
A Command to read the value of one or more of the operational data items set out in Section
4.6.5.
738
739
In executing the Command, GSME shall be capable of sending such value(s) in a Response
via its HAN Interface.
740
4.5.3.15
741
A Command to receive Firmware.
742
In executing the Command GSME shall be capable of:
Read Constant Data
Read Operational Data
Receive Firmware
743
744
i.
ii.
only accepting new Firmware from an Authorised and Authenticated source; and
verifying the Authenticity and integrity of new Firmware before installation.
745
4.5.3.16
746
747
A Command to initiate the recording of UTC date and time-stamped Consumption data for
each six minute interval over a period of four hours in the Network Data Log(4.6.5.12).
748
4.5.3.17
749
750
A Command to remove Security Credentials for a PPMID or a Gas Proxy Function from the
Device Log(4.6.4.11).
751
752
In executing the Command GSME shall be capable of recording the Command and
Outcome to the Security Log(4.6.5.17).
753
4.5.3.18
754
A Command to replace GSME Security Credentials(4.6.4.15).
755
In executing the Command GSME shall be capable of:
Record Network Data
Remove Device Security Credentials
Replace GSME Security Credentials
maintaining the Command’s Transactional Atomicity; and
recording the Command and Outcome to the Security Log(4.6.5.17).
756
757
i.
ii.
758
4.5.3.19
759
A Command to reset the Meter Balance(4.6.5.11) to zero.
760
761
In executing the Command, GSME shall reset the Accumulated Debt Register(4.6.5.1) and
the Emergency Credit Balance(4.6.5.8).
762
4.5.3.20
763
A Command to set the Clock date and time via its HAN Interface.
764
765
766
In executing the Command, GSME shall be capable of comparing the date and time
specified in the Command with the Communications Hub Date and Time. Where the
difference is:
Version 1.59
Reset Meter Balance
Set Clock
18 November 2015
Page 21
DRAFT
767
768
769
770
771
i.
ii.
SMETS
within the tolerance specified in the Command GSME shall be capable of adjusting
its date and time to the Communications Hub Date and Time and generating an
entry to that effect in the Event Log(4.6.5.9); and
outside the tolerance specified in the Command GSME shall be capable of not
adjusting its date and time and:
772
773
a) generating an entry to that effect in the Event Log(4.6.5.9); and
b) generating and sending an Alert to that effect via its HAN Interface.
774
775
GSME shall be capable of ensuring that any adjustments do not cause calendar-based
events to be missed or future-dated Commands to be missed or repeated.
776
4.5.3.21
777
778
A Command to set the payment mode as either Prepayment Mode or Credit Mode and to
record the mode of operation in Payment Mode(4.6.4.21).
779
780
In executing the Command, GSME shall be capable of taking a UTC date and time stamped
copy of:
781
782
783
784
785
786
787
788
789
i.
ii.
iii.
Set Payment Mode
the Tariff TOU Register Matrix(4.6.5.20);
the Tariff Block Counter Matrix(4.6.5.19); and
the Consumption Register(4.6.5.4),
and unless in Credit Mode both before and after execution of the Command:
iv.
v.
vi.
vii.
viii.
the Meter Balance(4.6.5.11);
the Emergency Credit Balance(4.6.5.8);
the Payment Debt Register(4.6.5.13);
the Time Debt Registers [1 … 2](4.6.5.21); and
the Accumulated Debt Register(4.6.5.1),
790
in the Billing Data Log(4.6.5.3).
791
4.5.3.22
792
793
A Command to accept new values for Tariff TOU Price Matrix(4.6.4.32), Tariff Block Price
Matrix(4.6.4.29), Tariff Switching Table(4.6.4.30) and Tariff Threshold Matrix(4.6.4.31).
794
795
In executing the Command, GSME shall be capable of taking a UTC date and time stamped
copy of:
796
797
798
799
800
801
802
803
804
i.
ii.
iii.
Set Tariff
the Tariff TOU Register Matrix(4.6.5.20);
the Tariff Block Counter Matrix(4.6.5.19); and
the Consumption Register(4.6.5.4),
and where in Prepayment mode:
iv.
v.
vi.
vii.
viii.
the Meter Balance(4.6.5.11);
the Emergency Credit Balance(4.6.5.8);
the Payment Debt Register(4.6.5.13); and
the Time Debt Registers [1 … 2](4.6.5.21); and
the Accumulated Debt Register(4.6.5.1),
805
in the Billing Data Log(4.6.5.3).
806
4.5.3.23
807
808
A Command to record one or more new values of the configuration data items set out in
Section 4.6.4.
809
810
In executing the Command, GSME shall be capable of generating an entry to that effect in
the Event Log(4.6.5.9).
Version 1.59
Write Configuration Data
18 November 2015
Page 22
DRAFT
SMETS
811
4.6 Data requirements
812
813
This section describes the minimum information which GSME shall be capable of holding in
its Data Store.
814
4.6.1
815
Describes data that remains constant and unchangeable at all times.
816
4.6.1.1
817
818
A globally unique identifier used to identify GSME based on the EUI-64 Institute of Electrical
and Electronic Engineers standard.
819
4.6.1.2
820
An identifier used to identify the manufacturer of GSME.
821
4.6.1.3
822
An identifier used to identify the model of GSME.
823
4.6.2
This section is not used
824
4.6.3
Locally Set Configuration Data
825
826
Describes data that is configured by execution of a User Interface Command and that is not
available outside GSME.
827
4.6.3.1
828
829
A number comprising four digits used by the Consumer to enable temporary access to a
specified set of display items and Commands via the User Interface of GSME.
830
4.6.4
831
Describes data that configures the operation of various functions of GSME.
832
4.6.4.1
833
Settings to control whether to generate and send an Alert.
834
4.6.4.2
835
836
A calendar defining billing dates for the storage of billing related information in the Billing
Data Log(4.6.5.3).
837
4.6.4.3
838
839
The value used in the conversion of gas volume to kWh usage, based on the energy stored
in one cubic metre of gas released when burnt at a standard temperature and pressure.
840
4.6.4.4
841
The name and contact telephone number of the current gas Supplier.
842
4.6.4.5
843
844
The value used in the conversion of gas volume to kWh usage, based on the temperature,
pressure and compressibility of the gas.
845
4.6.4.6
846
847
The Currency Units currently used by GSME, which shall be either GB Pounds or European
Central Bank Euro.
848
4.6.4.7
849
A number issued to GSME for display on the User Interface.
Constant data
GSME Identifier
Manufacturer Identifier
Model Type
Privacy PIN
Configuration data
Version 1.59
Alerts Configuration Settings
Billing Calendar
Calorific Value
Contact Details
Conversion Factor
Currency Units
Customer Identification Number
18 November 2015
Page 23
DRAFT
SMETS
850
4.6.4.8
851
852
The percentage of a payment to be recovered against debt when GSME is operating
Payment-based Debt Recovery in Prepayment Mode.
853
4.6.4.9
854
855
Two debt recovery rates in Currency Units per unit time for when GSME is using Time-based
Debt Recovery in Prepayment Mode.
856
4.6.4.10
857
858
The maximum amount in Currency Units per unit time that can be recovered through
Payment-based Debt Recovery when GSME is operating in Prepayment Mode.
859
4.6.4.11
860
861
The Security Credentials and Device identifier for each of the Gas Proxy Function and
PPMID with which GSME can establish Communications Links.
862
4.6.4.12
863
The threshold in Currency Units for controlling when to Disable the Supply.
864
4.6.4.13
865
866
The amount of Emergency Credit in Currency Units to be made available to a Consumer
where Emergency Credit is activated by the Consumer.
867
4.6.4.14
868
869
The threshold in Currency Units below which Emergency Credit Balance(4.6.5.8) may be
activated by the Consumer if so configured when GSME is operating in Prepayment Mode.
870
4.6.4.15
871
872
The Security Credentials for GSME and parties Authorised to establish Communications
Links with it.
873
4.6.4.16
874
The threshold in Currency Units below which a low credit Alert is signalled.
875
4.6.4.17
876
The maximum credit which can be applied by any Add Credit Command.
877
4.6.4.18
878
879
The Meter Balance(4.6.5.11) threshold in Currency Units above which an Add Credit
Command is rejected.
880
4.6.4.19
881
The reference number identifying a gas metering point.
882
4.6.4.20
883
884
885
886
A Switching Table comprising a set of rules specifying periods during which the Supply will
not be Disabled due to the combined credit of the Meter Balance(4.6.5.11) and Emergency
Credit Balance(4.6.5.8) falling below the Disablement Threshold(4.6.4.12) when GSME is
operating in Prepayment Mode.
887
888
The rules stored within the table shall specify which of five Day Profiles should be used to
specify Non-Disablement Periods for each day according to:
889
890
891
i.
ii.
Debt Recovery per Payment
Debt Recovery Rates [1 … 2]
Debt Recovery Rate Cap
Device Log
Disablement Threshold
Emergency Credit Limit
Emergency Credit Threshold
GSME Security Credentials
Low Credit Threshold
Maximum Credit Threshold
Maximum Meter Balance Threshold
Meter Point Reference Number (MPRN)
Non-Disablement Calendar
where the day is one of 20 Special Days, the Day Profile specified for that day; or
where the day is not a Special Day, the Day Profile specified by the active Season
Profile and Week Profile.
Version 1.59
18 November 2015
Page 24
DRAFT
SMETS
892
893
894
895
A Day Profile shall contain up to one contiguous time period during which the Supply may be
Disabled due to the combined credit of the Meter Balance(4.6.5.11) and Emergency Credit
Balance(4.6.5.8) falling below the Disablement Threshold(4.6.4.12) when GSME is operating
in Prepayment Mode.
896
897
The Switching Table shall support three Season Profiles and two Week Profiles. Each Week
Profile shall support two Day Profiles.
898
All dates and times shall be specified as UTC.
899
4.6.4.21
900
The current mode of operation, being Prepayment Mode or Credit Mode.
901
4.6.4.22
902
A store for Security Credentials relating to Public Keys.
903
4.6.4.23
904
905
A charge to be levied in Currency Units per unit time when operating in Credit Mode and
Prepayment Mode.
906
4.6.4.24
907
A message issued to, and held on, GSME for provision to the Consumer.
908
4.6.4.25
909
910
A setting to control the state of the Supply in the case of loss of power to GSME, being
Locked or unchanged.
911
4.6.4.26
912
913
A setting to control the state of the Supply in the case of Unauthorised Physical Access
being detected, being Locked or unchanged.
914
4.6.4.27
915
916
A setting controlling whether debt should be collected when GSME is operating in
Prepayment Mode and Supply is Disabled.
917
4.6.4.28
918
919
920
A setting controlling whether standing charges and debt should be deducted from the
Emergency Credit Balance(4.6.5.8) when GSME is operating in Prepayment Mode and
Emergency Credit is in use.
921
4.6.4.29
922
A 4 x 1 matrix containing Prices for Block Pricing.
923
4.6.4.30
924
925
926
A set of rules for allocating daily Consumption to a Tariff Register for Time-of-use Pricing
and Time-of-use with Block Pricing. The rules stored within the table shall specify which of
four Day Profiles should be used to allocate Consumption to a Tariff Register according to:
927
928
929
i.
ii.
Payment Mode
Public Key Security Credentials Store
Standing Charge
Supplier Message
Supply Depletion State
Supply Tamper State
Suspend Debt Disabled
Suspend Debt Emergency
Tariff Block Price Matrix
Tariff Switching Table
where the day is one of 20 Special Days, the Day Profile specified for that day; or
where the day is not a Special Day, the Day Profile specified by the active Season
Profile and Week Profile.
930
The Switching Table shall support three Season Profiles and two Week Profiles.
931
All dates shall be specified as UTC.
932
4.6.4.31
933
A 3 x 1 matrix capable of holding thresholds in kWh for controlling Block Tariffs.
Version 1.59
Tariff Threshold Matrix
18 November 2015
Page 25
DRAFT
SMETS
934
4.6.4.32
935
A 1 x 4 matrix containing Prices for Time-of-use Pricing.
936
4.6.4.33
937
938
The flow rate in units of volume per unit time used in the detection of uncontrolled flow of gas
on Enablement of Supply.
939
4.6.5
940
Describes data used by the functions of GSME for output of information.
941
4.6.5.1
942
943
944
The debt resulting from the collection of Standing Charge(4.6.4.23) and / or time-based debt
when Emergency Credit is in Use as configured by Suspend Debt Emergency(4.6.4.28),
when operating in Prepayment Mode.
945
4.6.5.2
946
The Price currently active.
947
4.6.5.3
948
A log capable of storing the following UTC date and time stamped entries:
949
950
951
952
953
954
955
956
i.
Tariff TOU Price Matrix
Uncontrolled Gas Flow Rate
Operational data
Accumulated Debt Register
Active Tariff Price
Billing Data Log
twelve entries comprising Tariff TOU Register Matrix(4.6.5.20), the Consumption
Register(4.6.5.4) and Tariff Block Counter Matrix(4.6.5.19);
and where in Prepayment mode:
ii.
iii.
iv.
five entries comprising the value of prepayment credits;
ten entries comprising the value of payment-based debt payments; and
twelve entries comprising Meter Balance(4.6.5.11), Emergency Credit
Balance(4.6.5.8), Accumulated Debt Register(4.6.5.1), Payment Debt
Register(4.6.5.13) and Time Debt Registers [1 … 2](4.6.5.21),
957
958
each of (i) to (iv) arranged as a circular buffer such that when full, further writes shall cause
the oldest entry to be overwritten.
959
4.6.5.4
960
The register recording cumulative Consumption.
961
4.6.5.5
962
A store capable of holding the following values:
963
964
965
966
967
968
i.
ii.
iii.
Consumption Register
Cumulative and Historical Value Store
eight Days of Energy Consumption comprising the prior eight Days, in kWh and
Currency Units;
six Weeks of Energy Consumption comprising the current Week and the prior five
Weeks, in kWh and Currency Units; and
fourteen months of Energy Consumption comprising the current month and the prior
thirteen months, in kWh and Currency Units.
969
4.6.5.6
970
971
A store capable of holding the value of Energy Consumption on the current Day, in kWh and
Currency Units.
972
4.6.5.7
973
974
975
976
A log capable of storing thirty one UTC date and time stamped entries of the Tariff TOU
Register Matrix(4.6.5.20), the Tariff Block Counter Matrix(4.6.5.19) and the Consumption
Register(4.6.5.4) arranged as a circular buffer such that when full, further writes shall cause
the oldest entry to be overwritten.
Version 1.59
Cumulative Current Day Value Store
Daily Read Log
18 November 2015
Page 26
DRAFT
SMETS
977
4.6.5.8
Emergency Credit Balance
978
979
The amount of Emergency Credit available to the Consumer after it has been activated by
the Consumer.
980
4.6.5.9
981
982
983
A log capable of storing one hundred UTC date and time stamped entries of non-security
related information for diagnosis and auditing, arranged as a circular buffer such that when
full, further writes shall cause the oldest entry to be overwritten.
984
4.6.5.10
985
The active version of Firmware of GSME.
986
4.6.5.11
987
988
989
990
991
The amount of money in Currency Units as determined by GSME. If operating in
Prepayment Mode, the Meter Balance represents GSME’s determination of the amount of
credit available to the Consumer (excluding any Emergency Credit Balance(4.6.5.8)). If
operating in Credit Mode, it represents GSME’s determination of the amount of money due
from the Consumer since the Meter Balance was last reset.
992
4.6.5.12
993
994
995
A log capable of storing four hours of UTC date and time stamped six minute Consumption
data arranged as a circular buffer such that when full, further writes shall cause the oldest
entry to be overwritten.
996
4.6.5.13
997
998
A Debt Register recording Debt to be recovered as a percentage of payment when using
Payment-based Debt Recovery in Prepayment Mode.
999
4.6.5.14
Event Log
Firmware Version
Meter Balance
Network Data Log
Payment Debt Register
Prepayment Daily Read Log
1000
1001
1002
1003
1004
A log capable of storing thirty one UTC date and time stamped entries of Meter
Balance(4.6.5.11), Emergency Credit Balance(4.6.5.8), Accumulated Debt Register(4.6.5.1),
Payment Debt Register(4.6.5.13) and Time Debt Registers [1 … 2](4.6.5.21) arranged as a
circular buffer such that when full, further writes shall cause the oldest entry to be
overwritten.
1005
4.6.5.15
1006
1007
1008
A log capable of storing a minimum of three months of UTC date and time stamped half
hourly Consumption data arranged as a circular buffer such that when full, further writes
shall cause the oldest entry to be overwritten.
1009
4.6.5.16
1010
Where GSME includes a Battery, the remaining Battery capacity in days.
1011
4.6.5.17
1012
1013
1014
A log capable of storing one hundred UTC date and time stamped entries of security related
information for diagnosis and auditing arranged as a circular buffer such that when full,
further writes shall cause the oldest entry to be overwritten.
1015
4.6.5.18
1016
The state of the Supply, being Enabled, Disabled or Armed.
1017
4.6.5.19
1018
A 4 x 1 matrix for storing Block Counters for Block Pricing.
Version 1.59
Profile Data Log
Remaining Battery Capacity
Security Log
Supply State
Tariff Block Counter Matrix
18 November 2015
Page 27
DRAFT
SMETS
1019
4.6.5.20
1020
A 1 x 4 matrix for storing Tariff Registers for Time-of-use Pricing.
1021
4.6.5.21
1022
1023
Two Debt Registers recording independent debts to be recovered over time when operating
Time-based Debt Recovery in Prepayment Mode.
Version 1.59
Tariff TOU Register Matrix
Time Debt Registers [1 … 2]
18 November 2015
Page 28
DRAFT
SMETS
1025
5 Electricity Smart Metering Equipment
Technical Specifications
1026
5.1 Introduction
1027
1028
1029
1030
Section 5 of this document describes the minimum physical, minimum functional, minimum
interface, minimum data and minimum testing and certification requirements of Electricity
Smart Metering Equipment that an electricity Supplier is required to install to comply with
condition 39 of its licence.
1031
Part A of this Section 5 applies to Single Element Electricity Metering Equipment.
1032
Part B of this Section 5 applies to Twin Element Electricity Metering Equipment.
1033
Part C of this Section 5 applies to Polyphase Electricity Metering Equipment.
1034
1035
1036
Where an Auxiliary Load Control Switch is installed within ESME, an electricity Supplier must
comply, in addition, with the minimum functional, interface and data requirements described
in Part D of this Section 5.
1037
1038
1039
Where the Boost Function is installed within ESME, an electricity Supplier must comply, in
addition, with the minimum functional and data requirements described in Part E of this
Section 5.
1024
Version 1.59
18 November 2015
Page 29
DRAFT
SMETS
1041
Part A - Single Element Electricity Metering
Equipment
1042
5.2 Overview
1043
In this Part A ESME shall mean Single Element Electricity Metering Equipment.
1044
5.3 SMETS Testing and Certification Requirements
1045
5.3.1
1046
1047
ESME shall have been tested to ensure that it meets the requirements described in this
Section 5, and evidence must be available to confirm such testing and conformance.
1048
1049
5.3.2
1050
1051
ESME shall meet the requirements described in the current version of the Great Britain
Companion Specification meaning v0.8.2 or later as published on the SECAS website.
1052
ESME shall have been certified:
1040
1053
1054
1055
1056
1057
1058
i.
ii.
Conformance with the SMETS
Conformance with the Great Britain Companion
Specifications
by the ZigBee Alliance as compliant with the ZigBee SEP v1.2 requirements
described in the current version of the Great Britain Companion Specifications
meaning v0.8.2 or later as published on the SECAS website; and
by the DLMS User Association as compliant with the DLMS COSEM requirements
described in the current version of the Great Britain Companion Specifications
meaning v0.8.2 or later as published on the SECAS website.
1059
1060
5.3.3
1061
1062
1063
ESME shall meet the requirements described in the current version of the Commercial
Product Assurance Security Characteristic Electricity Smart Metering Equipment meaning
v1.2 or later as published on CESG’s Website.
1064
1065
1066
ESME shall be certified by CESG as compliant with the current version of the Commercial
Product Assurance Security Characteristic Electricity Smart Metering Equipment meaning
v1.2 or later as published on CESG’s Website.
1067
5.4 Physical Requirements
1068
ESME shall as a minimum include the following components:
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
Conformance with the Commercial Product Assurance
Security Characteristic for GB Smart Metering
a Clock;
a Data Store;
an Electricity Meter containing one measuring element;
a HAN Interface;
a Load Switch;
a Random Number Generator;
a User Interface; and
where installed with a Communications Hub provided by the Data and
Communications Company, a Communications Hub Physical Interface (this may
comprise a Communications Hub Physical Interface forming part of GSME where
present at the time of installation in the Premises).
The Communications Hub Physical Interface shall as a minimum include a physical interface
that meets the requirements defined by the Data and Communications Company at the time
Version 1.59
18 November 2015
Page 30
DRAFT
SMETS
1082
1083
of installation (available on the Data and Communications Company’s website) and includes
provision for a DC power supply to the Communications Hub.
1084
1085
1086
1087
ESME shall be mains powered and be capable of performing the minimum functional,
interface and data requirements set out in Sections 5.5, 5.6 and 5.7 respectively operating at
a nominal voltage of 230VAC without consuming more than an average of 4 watts of
electricity under normal operating conditions.
1088
1089
ESME shall be capable of automatically resuming operation after a power failure in its
operating state prior to such failure.
1090
ESME shall:
1091
1092
1093
1094
1095
1096
ix.
x.
permanently display the ESME Identifier(5.7.1.1) on the ESME; and
have a Secure Perimeter.
The HAN Interface of ESME shall be capable of joining a ZigBee SEP v1.2 Smart Metering
Home Area Network which:
xi.
xii.
operates within the 2400 – 2483.5 MHz harmonised frequency band; and
supports the Communications Links described in Sections 5.6.1, 5.6.3 and 5.6.4.
1097
1098
On joining a ZigBee SEP v1.2 Smart Metering Home Area Network ESME shall be capable
of generating and sending an Alert to that effect via its HAN Interface.
1099
1100
1101
ESME shall be designed taking all reasonable steps so as to prevent Unauthorised Physical
Access and Unauthorised communications through its Secure Perimeter that could
compromise the Confidentiality and / or Data Integrity of:
1102
1103
1104
1105
1106
1107
1108
xiii.
xiv.
xv.
xvi.
xvii.
xviii.
xix.
1109
stored or executing on ESME.
1110
1111
1112
ESME shall be capable of detecting any attempt at Unauthorised Physical Access through
its Secure Perimeter that could compromise such Confidentiality and / or Data Integrity and
on such detection shall be capable of:
1113
1114
xx.
Personal Data;
Consumption data used for billing;
Security Credentials;
Random Number Generator;
Cryptographic Algorithms;
the Electricity Meter; and
Firmware and data essential for ensuring its integrity,
providing evidence of such an attempt through the use of tamper evident coatings or
seals,
1115
and where reasonably practicable:
1116
1117
1118
1119
1120
1121
xxi.
xxii.
xxiii.
1122
5.5 Functional Requirements
1123
This section describes the minimum functions that ESME shall be capable of performing.
1124
5.5.1
1125
1126
The Clock forming part of ESME shall be capable of operating so as to be accurate to within
10 seconds of the UTC date and time under normal operating conditions.
generating an entry to that effect in the Security Log(5.7.5.31);
generating and sending an Alert to that effect via its HAN Interface; and
where the Supply Tamper State(5.7.4.44) is configured to require Locking,
establishing a Locked state whereby the Supply is Disabled and can only be
Enabled or Armed in response to a Command to Arm the Supply (as described in
Section 5.6.3.7) or Enable the Supply (as described in Section 5.6.3.12).
Clock
Version 1.59
18 November 2015
Page 31
DRAFT
1127
1128
1129
1130
1131
1132
1133
SMETS
ESME shall be capable of comparing its date and time with the Communications Hub Date
and Time, and making adjustments to its date and time. Where the difference between
ESME date and time and the Communications Hub Date and Time is more than 10 seconds
ESME shall be capable of:
i.
ii.
iii.
not adjusting its date and time;
generating an entry in the Security Log(5.7.5.31) to that effect; and
generating and sending an Alert via its HAN Interface.
1134
1135
Except when executing a Set Clock(5.6.3.32) Command, ESME shall not be capable of
making adjustments to its date and time more than once within any 24 hour time period.
1136
5.5.2
1137
1138
1139
ESME, and any Device forming part of it, shall be capable of ensuring that the security
characteristics of all Communications Links it establishes meet the requirements described
in Section 5.5.10.5.
1140
1141
1142
1143
With the exception of a Communications Hub Function ESME shall only be capable of
establishing a Communications Link with a Device with Security Credentials in the Device
Log(5.7.4.14) and shall not be capable of establishing a Communications Link via its HAN
Interface with any other Devices.
1144
1145
When any Command addressed to ESME is received via any Communications Link ESME
shall be capable of:
1146
1147
1148
1149
1150
i.
ii.
iii.
Communications
using the Security Credentials ESME holds, Authenticating to a Trusted Source the
Command;
verifying in accordance with Section 5.5.10.2.3 that the sender of the Command is
Authorised to execute the Command; and
verifying the integrity of the Command.
1151
1152
1153
1154
On failure of any of (i) to (iii) above, ESME shall be capable of generating an entry in the
Security Log(5.7.5.31) to that effect, discarding the Command without execution and without
either generating or sending a Response, and generating and sending an Alert to that effect
via its HAN Interface.
1155
1156
1157
When executing an immediate Command ESME shall be capable of generating and sending
a Response via its HAN Interface which shall either confirm successful execution of the
Command or shall detail why it has failed to execute the Command.
1158
1159
1160
1161
1162
Where the Command is not due to be executed immediately, ESME shall be capable of
generating and sending a Response via its HAN Interface to confirm successful receipt.
When executing a future dated Command ESME shall be capable of generating and sending
an Alert via its HAN Interface which shall either confirm successful execution of the
Command or shall detail why it has failed to execute the Command.
1163
1164
ESME shall only be capable of addressing a Response to the sender of the relevant
Command.
1165
1166
ESME shall be capable of restricting the generation and sending of each Alert described in
this Section 5 according to the Alerts Configuration Settings(5.7.4.1).
1167
1168
5.5.2.1
1169
1170
ESME shall be capable of establishing and maintaining Communications Links via its HAN
Interface with one Communications Hub Function.
1171
1172
ESME shall be capable of receiving the Communications Hub Date and Time from a
Communications Hub Function.
Version 1.59
Communications Links with a Communications Hub Function via its HAN
Interface
18 November 2015
Page 32
DRAFT
SMETS
1173
5.5.2.2
1174
1175
1176
1177
ESME shall be capable of establishing and maintaining Communications Links via its HAN
Interface with a minimum of seven Type 1 Devices (including a minimum of one PPMID).
ESME shall be capable of supporting up to five Auxiliary Load Control Switches or HAN
Connected Auxiliary Load Control Switches.
1178
ESME shall be capable of supporting the following types of Communications Links:
i.
ii.
iii.
Communications Links with Type 1 Devices via its HAN Interface
1179
1180
1181
1182
1183
1184
receiving the Commands (set out in Section 5.6.3) from a Type 1 Device;
sending the Responses (set out in Section 5.6.3) to a Type 1 Device;
sending the Commands (set out in Section 5.6.4) to a Type 1 Device and acting on
the corresponding Responses from a Type 1 Device;
sending the information (set out in Section 5.6.1) to a Type 1 Device; and
sending Alerts to a Type 1 Device.
iv.
v.
1185
5.5.2.3
1186
1187
ESME shall be capable of establishing and maintaining Communications Links via its HAN
Interface with a minimum of four Type 2 Devices.
1188
ESME shall be capable of supporting the following types of Communications Links:
Communications Links with Type 2 Devices via its HAN Interface
1189
1190
i.
ii.
1191
5.5.3
1192
1193
ESME shall be capable of retaining all information held in its Data Store at all times,
including on loss of power.
1194
5.5.4
1195
1196
ESME shall be capable of displaying the following up to date information on its User
Interface:
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
xii.
xiii.
xiv.
xv.
xvi.
xvii.
xviii.
xix.
sending the information (set out in Section 5.6.1) to a Type 2 Device; and
sending Alerts to a Type 2 Device.
Data storage
Display of information
the Payment Mode [INFO](5.7.4.31) currently in operation, being Prepayment Mode
or Credit Mode [PIN];
the Tariff TOU Register Matrix [INFO](5.7.5.34), the Tariff TOU Block Register
Matrix(5.7.5.35) and the Tariff Block Counter Matrix [INFO](5.7.5.33);
the Active Import Register [INFO](5.7.5.3);
the Active Export Register [INFO](5.7.5.2);
the Meter Balance [INFO](5.7.5.22) [PIN];
the Debt to Clear (calculated as set out in Section 5.5.7.2) [PIN];
the Customer Identification Number [INFO](5.7.4.10) [PIN];
whether Emergency Credit is available for activation [PIN];
whether ESME has suspended the Disablement of Supply during a period defined in
the Non-Disablement Calendar [INFO](5.7.4.30) (as set out in Section 5.5.7.2) [PIN];
the Emergency Credit Balance [INFO](5.7.5.15) where Emergency Credit is
activated [PIN];
any low credit condition [PIN];
the Supply State [INFO](5.7.5.32);
any time-based debts and Time-based Debt Recovery rates [PIN];
any payment-based debt [PIN];
any accumulated debt recorded in the Accumulated Debt Register [INFO](5.7.5.1)
[PIN];
any Standing Charge [INFO](5.7.4.42);
the Meter Point Administration Numbers (MPAN) [INFO](5.7.4.28);
the Local Time;
the Contact Details [INFO](5.7.4.8);
Version 1.59
18 November 2015
Page 33
DRAFT
1221
1222
1223
xx.
xxi.
SMETS
the Active Tariff Price [INFO](5.7.5.5) [PIN]; and
the Event Log(5.7.5.16) and the Power Event Log(5.7.5.25) (with the exception of
any Personal Data).
1224
1225
1226
1227
ESME shall be capable of displaying the Security Log(5.7.5.31) on its User Interface
following physical access through the Secure Perimeter of ESME.
ESME shall be capable of displaying Currency Units in GB Pounds and European Central
Bank Euro.
1228
5.5.5
1229
1230
1231
1232
ESME shall be capable of preventing the display on the User Interface of items annotated
[PIN] in Section 5.5.4, and preventing access on the User Interface to the Commands
annotated [PIN] in Section 5.6.2, except on successful execution of an Allow Access to User
Interface(5.6.2.3) Command via the User Interface.
1233
5.5.6
1234
1235
1236
ESME shall be capable of determining when the Active Power Import [INFO](5.7.5.4) is
above, for the Load Limit Period(5.7.4.19), the Load Limit Power Threshold(5.7.4.20) and on
such an occurrence ESME shall be capable of:
1237
1238
1239
1240
1241
1242
1243
i.
ii.
iii.
iv.
Privacy PIN Protection
Load limiting
generating an entry to that effect in the Event Log(5.7.5.16);
generating and sending an Alert to that effect via its HAN Interface and its User
Interface;
counting the number of such occurrences in the Load Limit Counter(5.7.5.18); and
ignoring the Non-Disablement Calendar [INFO](5.7.4.30) and Disabling the Supply
in circumstances where the Load Limit Supply State(5.7.4.22) is configured to
require Disablement, and then:
1244
1245
1246
1247
1248
1249
1250
a) immediately Arming the Supply such that it can be Enabled as set out in
Section 5.6.2.5;
b) after the Load Limit Restoration Period(5.7.4.21) has elapsed Enabling the
Supply, and setting the Load Limit Supply State(5.7.4.22) to unchanged; and
c) displaying any such change in the Supply State [INFO](5.7.5.32) on its User
Interface and generating and sending an Alert indicating the change in state via
its HAN Interface.
1251
1252
1253
1254
1255
1256
Where ESME is in Prepayment Mode and the combined Meter Balance [INFO](5.7.5.22) and
Emergency Credit Balance [INFO](5.7.5.15) is below the Disablement Threshold
[INFO](5.7.4.15), ESME shall be capable of not executing (a), (b) and (c) above, but of
placing the Supply in such a state whereby Supply will be Armed where the combined Meter
Balance [INFO](5.7.5.22) and Emergency Credit Balance [INFO](5.7.5.15) rises above
Disablement Threshold [INFO](5.7.4.15).
1257
5.5.7
1258
1259
ESME shall be capable of operating in Credit Mode and Prepayment Mode and of being
remotely switched from one mode to the other.
1260
5.5.7.1
1261
1262
ESME, when operating in Credit Mode, shall be capable of maintaining a calculation of the
Meter Balance [INFO](5.7.5.22) based on:
1263
1264
1265
1266
1267
i.
ii.
Payment Mode
Credit Mode
the Consumption in the Tariff TOU Register Matrix [INFO](5.7.5.34) and the Prices
in the Tariff TOU Price Matrix [INFO](5.7.4.50) and, if operating Time-of-use with
Block Pricing, the Consumption in the Tariff TOU Block Register Matrix(5.7.5.35)
and the Prices in the Tariff Block Price Matrix [INFO](5.7.4.47); and
the Standing Charge [INFO](5.7.4.42).
Version 1.59
18 November 2015
Page 34
DRAFT
SMETS
1268
5.5.7.2
1269
1270
1271
1272
ESME shall be capable of operating in Prepayment Mode, including during periods of loss of
its Communications Link via its HAN Interface, and maintaining a balance of credit and
reflecting any reduction in credit based on Consumption, standing charge and Time-based
Debt Recovery.
1273
1274
1275
ESME shall be capable of adding credit to the Meter Balance [INFO](5.7.5.22) (as set out in
Sections 5.6.2.2 and 5.6.3.3) and reducing the amount of credit in the Meter Balance
[INFO](5.7.5.22).
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
ESME shall be capable of making Emergency Credit available to the Consumer (by means
of the Emergency Credit Balance [INFO](5.7.5.15) if the Meter Balance [INFO](5.7.5.22) is
below the Emergency Credit Threshold [INFO](5.7.4.17)). ESME shall be capable of
displaying the availability of Emergency Credit on its User Interface and of generating and
sending an Alert indicating the availability of Emergency Credit via its HAN Interface. The
amount of Emergency Credit made available to the Consumer shall be equal to the
Emergency Credit Limit [INFO](5.7.4.16). ESME shall be capable of reducing the amount of
credit in the Emergency Credit Balance [INFO](5.7.5.15) where Emergency Credit is
activated by the Consumer (as set out in Sections 5.6.2.1 and 5.6.3.1) and the Meter
Balance [INFO](5.7.5.22) is exhausted. Any Emergency Credit used shall be repaid when
credit is added to ESME (as set out in Sections 5.6.2.2 and 5.6.3.3).
1287
1288
1289
ESME shall be capable of reducing the Meter Balance [INFO](5.7.5.22) until it reaches the
Disablement Threshold [INFO](5.7.4.15) followed by reducing the Emergency Credit Balance
[INFO](5.7.5.15), where activated, until exhausted, on the basis of:
1290
1291
1292
1293
1294
1295
1296
1297
i.
ii.
iii.
Prepayment Mode
the Consumption in the Tariff TOU Register Matrix [INFO](5.7.5.34) and the Prices
in the Tariff TOU Price Matrix [INFO](5.7.4.50), and if operating Time-of-use with
Block Pricing the Consumption in the Tariff TOU Block Register Matrix(5.7.5.35) and
the Prices in the Tariff Block Price Matrix [INFO](5.7.4.47);
the Standing Charge [INFO](5.7.4.42); and
the recovery of debt hourly or daily through each of the Time Debt Registers [1 … 2]
[INFO](5.7.5.36) at rates defined by the Debt Recovery Rates [1 … 2]
[INFO](5.7.4.12).
1298
1299
1300
1301
Where configured by Suspend Debt Emergency(5.7.4.46) to do so and when Emergency
Credit is in use, ESME shall be capable of suspending the application of (ii) and (iii) to the
Emergency Credit Balance [INFO](5.7.5.15), and of accumulating (ii) and (iii) in the
Accumulated Debt Register [INFO](5.7.5.1).
1302
1303
ESME shall be capable of recording debt recovered, or accumulated in the Accumulated
Debt Register [INFO](5.7.5.1), in the Billing Data Log(5.7.5.10).
1304
1305
ESME shall be capable of monitoring the Meter Balance [INFO](5.7.5.22) and where
activated the Emergency Credit Balance [INFO](5.7.5.15) and:
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
iv.
v.
vi.
if the combined credit of the Meter Balance [INFO](5.7.5.22) and Emergency Credit
Balance [INFO](5.7.5.15) falls below the Low Credit Threshold [INFO](5.7.4.23),
displaying an Alert to that effect on its User Interface and generating and sending an
Alert to that effect via its HAN Interface;
if the combined credit of the Meter Balance [INFO](5.7.5.22) and Emergency Credit
Balance [INFO](5.7.5.15) falls below the Disablement Threshold [INFO](5.7.4.15),
Disabling the Supply, displaying an Alert to that effect on its User Interface and
generating and sending an Alert to that effect via its HAN Interface;
where the Supply is Disabled (as set out in (v) above):
a) where configured by Suspend Debt Disabled(5.7.4.45) not to suspend Timebased Debt Recovery, continuing to apply (ii) and (iii) above to reduce the
Meter Balance [INFO](5.7.5.22);
Version 1.59
18 November 2015
Page 35
DRAFT
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
SMETS
b) where configured by Suspend Debt Disabled(5.7.4.45) to suspend Time-based
Debt Recovery, suspending the application of (iii) above to the Meter Balance
[INFO](5.7.5.22), and continuing to apply (ii) to reduce the Meter Balance
[INFO](5.7.5.22); and
vii.
if the Supply is Enabled, suspending the Disablement of Supply (as set out in (v)
above) during periods defined in the Non-Disablement Calendar [INFO](5.7.4.30),
continuing to reduce the Meter Balance [INFO](5.7.5.22) on the basis of (i), (ii) and
(iii) above, displaying on its User Interface an indication that the combined Meter
Balance [INFO](5.7.5.22) and Emergency Credit Balance [INFO](5.7.5.15) is below
the Disablement Threshold [INFO](5.7.4.15) and that Disablement of Supply due to
insufficient credit has been suspended, and generating and sending an Alert that
Disablement of Supply due to insufficient credit has been suspended via its HAN
Interface.
If the Meter Balance [INFO](5.7.5.22) is equal to or below the Disablement Threshold
[INFO](5.7.4.15) ESME shall be capable of maintaining a calculation of the Debt to Clear
based on:
viii.
ix.
x.
xi.
the difference between the Meter Balance [INFO](5.7.5.22) and the Disablement
Threshold [INFO](5.7.4.15);
amount of debt accumulated in the Accumulated Debt Register [INFO](5.7.5.1);
amount of Emergency Credit activated and used by the Consumer; and
the payment-based debt to be collected based on (viii), (ix) and (x) (as defined by
Debt Recovery per Payment [INFO](5.7.4.11) taking account of the amount
remaining in the Payment Debt Register [INFO](5.7.5.23), the payment-based debt
payments in the Billing Data Log(5.7.5.10) and the Debt Recovery Rate Cap
[INFO](5.7.4.13)).
If the amount of debt to be collected from a Debt Register through Time-based Debt
Recovery, Payment-based Debt Recovery or an Adjust Debt Command is greater than the
amount in that Time Debt Register then ESME shall be capable of:
1346
1347
xii.
xiii.
adding the difference to the Meter Balance [INFO](5.7.5.22); and
setting the amount in that Debt Register to zero.
1348
5.5.8
1349
ESME shall be capable of applying Time-of-use Pricing and Time-of-use with Block Pricing.
1350
1351
When switching between Time-of-use Bands and Tariff Registers as set out in this section
ESME shall be capable of applying the Randomised Offset [INFO](5.7.5.28).
1352
ESME shall be capable of maintaining the Active Tariff Price [INFO](5.7.5.5).
1353
5.5.8.1
1354
1355
ESME shall be capable of recording Consumption according to Time-of-use Bands in one of
forty-eight Tariff Registers in the Tariff TOU Register Matrix [INFO](5.7.5.34).
1356
1357
1358
ESME shall be capable of switching between different Tariff Registers once every 30
minutes. The switching between Time-of-use Bands and thus Tariff Registers shall be
based on the switching rules defined in the Tariff Switching Table(5.7.4.48).
1359
5.5.8.2
1360
1361
ESME shall be capable of recording Consumption in one of four Block Registers for each of
eight Time-of-use Bands in the Tariff TOU Block Register Matrix(5.7.5.35).
1362
1363
1364
The switching between Time-of-use Bands and sets of Block Registers shall be based on
the switching rules set out in the Tariff Switching Table(5.7.4.48). ESME shall be capable of
switching between Time-of-use Bands once every 30 minutes.
Pricing
Version 1.59
Time-of-use Pricing
Time-of-use with Block Pricing
18 November 2015
Page 36
DRAFT
SMETS
1365
1366
1367
Switching between the Block Registers within each Time-of-use Band shall be based on
Consumption accumulated in the Tariff Block Counter Matrix [INFO](5.7.5.33) and
Consumption thresholds in the Tariff Threshold Matrix [INFO](5.7.4.49).
1368
1369
1370
1371
ESME shall also be capable of accumulating Consumption in one of four Block Counters in
the Tariff Block Counter Matrix [INFO](5.7.5.33) for each of the eight Time-of-use Bands.
ESME shall be capable of switching between Block Counters according to the Consumption
thresholds in the Tariff Threshold Matrix [INFO](5.7.4.49).
1372
1373
1374
ESME shall be capable of resetting the counters in the Tariff Block Counter Matrix
[INFO](5.7.5.33) once per Day and in accordance with the timetable set out in the Billing
Calendar(5.7.4.7).
1375
5.5.9
1376
5.5.9.1
1377
1378
ESME shall be capable of recording cumulative Active Energy Imported in the Active Import
Register [INFO](5.7.5.3).
1379
5.5.9.2
1380
1381
ESME shall be capable of recording cumulative Active Energy Exported in the Active Export
Register [INFO](5.7.5.2).
1382
5.5.9.3
1383
1384
In accordance with the timetable set out in the Billing Calendar(5.7.4.7) ESME shall be
capable of taking a UTC date and time stamped copy of:
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
i.
ii.
iii.
Recording
Active Energy Imported
Active Energy Exported
Billing data
the Tariff TOU Register Matrix [INFO](5.7.5.34);
the Tariff TOU Block Register Matrix(5.7.5.35); and
the Active Import Register [INFO](5.7.5.3),
and where in Prepayment mode:
iv.
v.
vi.
vii.
viii.
the Meter Balance [INFO](5.7.5.22);
the Emergency Credit Balance [INFO](5.7.5.15);
the Payment Debt Register [INFO](5.7.5.23);
the Time Debt Registers [1 … 2] [INFO](5.7.5.36); and
the Accumulated Debt Register [INFO](5.7.5.1),
in the Billing Data Log(5.7.5.10), and:
1395
1396
1397
1398
ix.
1399
5.5.9.4
1400
ESME shall be capable of recording to:
1401
x.
i.
1402
1403
1404
1405
1406
1407
1408
1409
generating and sending an Alert via its HAN Interface containing the most recent
entries in the Billing Data Log(5.7.5.10) of (i) to (iii) above; and
if operating in Credit Mode, immediately resetting the Meter Balance
[INFO](5.7.5.22).
Consumption data
the Cumulative and Historical Value Store [INFO](5.7.5.12) in kWh:
a)
b)
c)
d)
e)
f)
ii.
Consumption on the Day up to the Local Time;
Consumption on each of the eight Days prior to such Day;
Consumption in the Week in which the calculation is performed;
Consumption in each of the five Weeks prior to such Week;
Consumption in the month in which the calculation is performed; and
Consumption in the thirteen months prior to such month.
the Daily Consumption Log [INFO](5.7.5.14) in kWh, the Consumption on each of
the 731 Days prior to the current Day.
Version 1.59
18 November 2015
Page 37
DRAFT
SMETS
1410
5.5.9.5
1411
1412
ESME shall be capable of calculating and recording in the Cumulative and Historical Value
Store [INFO](5.7.5.12) the cost of:
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
i.
ii.
iii.
iv.
v.
vi.
Cost of Consumption data
Consumption on the Day up to the Local Time;
Consumption on each of the eight Days prior to such Day;
Consumption in the Week in which the calculation is performed;
Consumption in each of the five Weeks prior to such Week;
Consumption in the month in which the calculation is performed; and
Consumption in the thirteen months prior to such month.
ESME shall be capable of calculating cost of Consumption as above on the basis of:
vii.
viii.
the Consumption in the Tariff TOU Register Matrix [INFO](5.7.5.34) and the Prices
in the Tariff TOU Price Matrix [INFO](5.7.4.50) and, if operating Time-of-use with
Block Pricing, the Consumption in the Tariff TOU Block Register Matrix(5.7.5.35)
and the Prices in the Tariff Block Price Matrix [INFO](5.7.4.47); and
the Standing Charge [INFO](5.7.4.42).
1425
5.5.9.6
Cost of Instantaneous consumption
1426
1427
ESME shall be capable of calculating and recording the Cost of Instantaneous Active Power
Import(5.7.5.11) on the basis of:
1428
1429
i.
ii.
1430
5.5.9.7
1431
1432
1433
1434
ESME shall be capable of taking a copy of and storing the Tariff TOU Register Matrix
[INFO](5.7.5.34), the Tariff TOU Block Register Matrix(5.7.5.35), the Active Import
Register(5.7.5.3) and the Active Export Register [INFO](5.7.5.2) together with a UTC date
and time stamp in the Daily Read Log(5.7.5.13) every day at midnight UTC.
1435
1436
1437
1438
If operating in Prepayment Mode ESME shall be capable of recording the Meter Balance
[INFO](5.7.5.22), Emergency Credit Balance [INFO](5.7.5.15), Accumulated Debt Register
[INFO](5.7.5.1), Payment Debt Register [INFO](5.7.5.23) and Time Debt Registers [1 … 2]
[INFO](5.7.5.36) in the Prepayment Daily Read Log(5.7.5.26) every day at midnight UTC.
1439
5.5.9.8
1440
1441
1442
ESME shall be capable of calculating and storing Consumption for the previous Day together
with a UTC date stamp in the Daily Consumption Log [INFO](5.7.5.14) every Day at midnight
UTC.
1443
5.5.9.9
1444
1445
1446
1447
ESME shall be capable of recording in each 30 minute period (commencing at the start of
minutes 00 and 30 in each hour), the following information (including the UTC date and time
at the end of the 30 minute period to which the data relates) in the Profile Data Log
[INFO](5.7.5.27):
1448
1449
1450
1451
i.
ii.
iii.
iv.
the Active Power Import [INFO](5.7.5.4); and
the Active Tariff Price [INFO](5.7.5.5).
Daily read data
Daily Consumption data
Half hour profile data
Consumption;
Active Energy Exported;
Reactive Energy Imported; and
Reactive Energy Exported.
1452
5.5.9.10
1453
1454
1455
ESME shall be capable of calculating the average value of Active Power Import
[INFO](5.7.5.4) over each 30 minute period (commencing at the start of minutes 00 and 30 in
each hour) and recording:
Version 1.59
Maximum Demand Import data
18 November 2015
Page 38
DRAFT
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
i.
ii.
SMETS
to the Maximum Demand Active Power Import Value(5.7.5.19), the maximum value
so calculated since the Maximum Demand Active Power Import Value(5.7.5.19) was
last reset (as set out in Section 5.6.3.26) including the UTC date and time at the end
of the 30 minute period to which the data relates; and
to the Maximum Demand (Configurable Time) Active Power Import Value(5.7.5.20),
the maximum value so calculated in any 30 minute period (commencing at the start
of minutes 00 and 30 in each hour) within the time period specified in Maximum
Demand Configurable Time Period(5.7.4.26) (including the UTC date and time at the
end of the 30 minute period to which the data relates) since the Maximum Demand
(Configurable Time) Active Power Import Value(5.7.5.20) was last reset (as set out
in Section 5.6.3.28).
1467
5.5.9.11
1468
1469
1470
1471
1472
1473
ESME shall be capable of calculating the average value of Active Power Export over each
30 minute period (commencing at the start of minutes 00 and 30 in each hour) and recording
to the Maximum Demand Active Power Export Value(5.7.5.21) the maximum value so
calculated since the Maximum Demand Active Power Export Value(5.7.5.21) was last reset
(as set out in Section 5.6.3.27) including the UTC date and time at the end of the 30 minute
period to which the data relates.
1474
5.5.9.12
1475
1476
ESME shall be capable of comparing the Active Power Import [INFO](5.7.5.4) against
thresholds and:
1477
1478
1479
1480
1481
1482
1483
i.
ii.
iii.
Maximum Demand Export data
Power Threshold Status
if the Active Power Import [INFO](5.7.5.4) is equal to or lower than the Low Medium
Power Threshold [INFO](5.7.4.24), setting Power Threshold Status(5.7.5.24) to low;
if the Active Power Import [INFO](5.7.5.4) is higher than the Low Medium Power
Threshold [INFO](5.7.4.24) and equal to or lower than the Medium High Power
Threshold [INFO](5.7.4.29), setting Power Threshold Status(5.7.5.24) to medium;
and
otherwise, setting the Power Threshold Status(5.7.5.24) to high.
1484
5.5.9.13
1485
1486
ESME shall be capable of recording cumulative Reactive Energy Imported in the Reactive
Import Register(5.7.5.30).
1487
5.5.9.14
1488
1489
ESME shall be capable of recording cumulative Reactive Energy Exported in the Reactive
Export Register(5.7.5.29).
1490
5.5.10 Security
1491
5.5.10.1
1492
1493
1494
1495
ESME shall be designed taking all reasonable steps so as to ensure that any failure or
compromise of its integrity shall not compromise the Security Credentials or Personal Data
stored on it or compromise the integrity of any other Device to which it is connected by
means of a Communications Link.
1496
1497
ESME shall be capable of securely disabling Critical Commands other than those
Commands set out in Section 5.6 that are Critical Commands.
1498
1499
1500
ESME shall be capable of verifying its Firmware at power-on and prior to activation of the
Firmware, to verify that the Firmware, at that time, is in the form originally received. On
failure of verification ESME shall be capable of:
1501
1502
i.
ii.
Reactive Energy Imported
Reactive Energy Exported
General
generating an entry to that effect in the Security Log(5.7.5.31); and
generating and sending an Alert to that effect via its HAN Interface.
Version 1.59
18 November 2015
Page 39
DRAFT
1503
1504
1505
1506
1507
1508
SMETS
Where ESME comprises more than one Device, each Device other than the Electricity Meter
shall be capable of verifying its Firmware at power-on and prior to activation of the Firmware,
to verify that the Firmware, at that time, is in the form originally received. On failure of
verification ESME shall be capable of:
iii.
iv.
generating an entry to that effect in the Security Log(5.7.5.31); and
generating and sending an Alert to that effect via its HAN Interface.
1509
1510
ESME shall be capable of logging in the Security Log(5.7.5.31) the occurrence and type of
any Sensitive Event.
1511
5.5.10.2
1512
5.5.10.2.1
1513
1514
ESME shall be capable of generating Public-Private Key Pairs to support the Cryptographic
Algorithms set out in Section 5.5.10.3.
1515
1516
1517
ESME shall be capable of securely storing such Private Keys and shall be capable of
formatting and sending via its HAN Interface a Certificate Signing Request containing the
corresponding Public Key and the ESME Identifier(5.7.1.1).
1518
ESME shall be capable of securely storing Key Agreement values.
1519
5.5.10.2.2
1520
1521
ESME shall be capable of securely storing Security Credentials from Certificates including
for use in the Cryptographic Algorithms as set out in Section 5.5.10.3.
1522
1523
1524
During the replacement of any ESME Security Credentials(5.7.4.18) (as set out in Section
5.6.3.20), ESME shall be capable of ensuring that the ESME Security Credentials(5.7.4.18)
being replaced remain usable until the successful completion of the replacement.
1525
5.5.10.2.3
1526
1527
ESME shall be capable of restricting Authorisation to execute Commands and of issuing
Alerts according to Role permissions.
1528
5.5.10.3
1529
ESME shall be capable of supporting the following Cryptographic Algorithms:
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
i.
ii.
iii.
Security Credentials
Meter Private Keys
Public Key Certificates
Role-based Access Control (RBAC)
Cryptographic Algorithms
Elliptic Curve DSA;
Elliptic Curve DH; and
SHA-256.
In executing and creating any Command, Response or Alert, ESME shall be capable of
applying Cryptographic Algorithms (alone or in combination) for:
iv.
v.
vi.
vii.
viii.
Digital Signing;
Digital Signature verification;
Hashing;
Message Authentication; and
Encryption and Decryption.
1540
5.5.10.4
1541
1542
ESME shall only be capable of activating its Firmware on receipt of an Activate Firmware
Command (as set out in Section 5.6.3.2).
1543
5.5.10.5
1544
1545
ESME shall be capable of preventing and detecting, on all of its interfaces, Unauthorised
access that could compromise the Confidentiality and / or Data Integrity of:
1546
i.
Firmware
Communications
Personal Data whilst being transferred via an interface;
Version 1.59
18 November 2015
Page 40
DRAFT
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
ii.
iii.
iv.
SMETS
Consumption data used for billing whilst being transferred via an interface;
Security Credentials whilst being transferred via an interface; and
Firmware and data essential for ensuring its integrity whilst being transferred via an
interface,
and any Command that could compromise the Confidentiality and / or Data Integrity of:
v.
vi.
vii.
viii.
Personal Data;
Consumption data used for billing;
Security Credentials; and
Firmware and data essential for ensuring its integrity,
stored or executing on ESME, and on such detection shall be capable of:
ix.
x.
generating an entry to that effect in the Security Log(5.7.5.31); and
generating and sending an Alert to that effect via its HAN Interface.
1559
1560
ESME shall be capable of employing techniques to protect against Replay Attacks relating to
Commands received.
1561
1562
ESME shall not be capable of executing a Command to modify or delete entries from the
Security Log(5.7.5.31).
1563
5.5.11 Controlling Auxiliary Loads
1564
1565
ESME shall be capable of supporting up to a maximum combined total of five Auxiliary Load
Control Switches and HAN Connected Auxiliary Load Control Switches.
1566
5.5.11.1
1567
1568
ESME shall be capable of monitoring the Auxiliary Load Control Switch Calendar(5.7.4.2)
and at times defined in the calendar:
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
i.
ii.
iii.
Calendar-based switching of HAN Connected Auxiliary Loads
where a Set HAN Connected Auxiliary Load Control Switch [n] State(5.6.3.33)
Command has been issued and the time period has not elapsed, taking no further
action;
where the Supply State [INFO](5.7.5.32) is Disabled or Armed, taking no further
action; and
where the Supply State [INFO](5.7.5.32) is Enabled, applying the Randomised
Offset [INFO](5.7.5.28) and then issuing a Control HAN Connected Auxiliary Load
Control Switch(5.6.4.1) Command containing the time period remaining until the next
switching event defined in the calendar for HCALCS [n] (taking account of the
Randomised Offset [INFO](5.7.5.28)).
On receipt of a Request Control of HAN Connected Auxiliary Load Control Switch(5.6.3.21)
Command and on receipt of a Reset HAN Connected Auxiliary Load Control Switch [n]
State(5.6.3.24) Command ESME shall be capable of:
iv.
v.
where the Supply State [INFO](5.7.5.32) is Disabled or Armed, taking no further
action; and
where the Supply State [INFO](5.7.5.32) is Enabled, issuing a Control HAN
Connected Auxiliary Load Control Switch(5.6.4.1) Command to set the commanded
state of HCALCS [n] according to the rules defined in the Auxiliary Load Control
Switch Calendar(5.7.4.2) containing the time period remaining until the next
switching event defined in the calendar for HCALCS [n] (taking account of the
Randomised Offset [INFO](5.7.5.28)).
When controlling an HCALCS as set out in this Section 5.5.11, ESME shall be capable of
applying the Randomised Offset [INFO](5.7.5.28).
Version 1.59
18 November 2015
Page 41
DRAFT
SMETS
1592
5.5.12 Voltage Quality Measurements
1593
5.5.12.1
1594
1595
ESME shall be capable of calculating the average value of RMS voltage over a configurable
period as defined in the Average RMS Voltage Measurement Period(5.7.4.6) and:
1596
1597
1598
1599
1600
i.
ii.
Average RMS voltage
recording the value calculated (including the UTC date and time at the end of the
period to which the value relates) in the Average RMS Voltage Profile Data
Log(5.7.5.9);
detecting when the value calculated is above the Average RMS Over Voltage
Threshold(5.7.4.4), and on detection:
1601
1602
1603
1604
a) counting the number of such occurrences in the Average RMS Over Voltage
Counter(5.7.5.7);
b) where the value calculated in the prior configurable period was below the
Average RMS Over Voltage Threshold(5.7.4.4):


1605
1606
1607
1608
1609
iii.
detecting when the value calculated is below the Average RMS Over Voltage
Threshold(5.7.4.4), and where the value calculated in the prior configurable period
was above the Average RMS Over Voltage Threshold(5.7.4.4):
1610
1611
1612
1613
a) generating an entry to that effect in the Power Event Log(5.7.5.25); and
b) generating and sending an Alert to that effect via its HAN Interface.
iv.
detecting when the value calculated is below the Average RMS Under Voltage
Threshold(5.7.4.5), and on detection:
1614
1615
1616
1617
a) counting the number of such occurrences in the Average RMS Under Voltage
Counter(5.7.5.8);
b) where the value calculated in the prior configurable period was above the
Average RMS Under Voltage Threshold(5.7.4.5):


1618
1619
1620
1621
1622
generating an entry to that effect in the Power Event Log(5.7.5.25); and
generating and sending an Alert to that effect via its HAN Interface.
v.
generating an entry to that effect in the Power Event Log(5.7.5.25); and
generating and sending an Alert to that effect via its HAN Interface
detecting when the value is above the Average RMS Under Voltage
Threshold(5.7.4.5), and where the value calculated in the prior configurable period
was below the Average RMS Under Voltage Threshold(5.7.4.5):
1623
1624
a) generating an entry to that effect in the Power Event Log(5.7.5.25); and
b) generating and sending an Alert to that effect via its HAN Interface
1625
5.5.12.2
1626
ESME shall be capable of:
1627
1628
1629
i.
1630
1631
1632
1633
1634
1635
1636
RMS extreme over voltage detection
detecting when the RMS voltage rises above the RMS Extreme Over Voltage
Threshold(5.7.4.35) for a continuous period longer than the RMS Extreme Over
Voltage Measurement Period(5.7.4.34) and on detection:
a) generating an entry to that effect in the Power Event Log(5.7.5.25); and
b) generating and sending an Alert to that effect via its HAN Interface; and
ii.
detecting when the RMS voltage returns below the RMS Extreme Over Voltage
Threshold(5.7.4.35) for a continuous period longer than the RMS Extreme Over
Voltage Measurement Period(5.7.4.34) and on detection:
a) generating an entry to that effect in the Power Event Log(5.7.5.25); and
b) generating and sending an Alert to that effect via its HAN Interface;
Version 1.59
18 November 2015
Page 42
DRAFT
SMETS
1637
5.5.12.3
1638
ESME shall be capable of:
1639
1640
1641
i.
detecting when the RMS voltage falls below the RMS Extreme Under Voltage
Threshold(5.7.4.37) for a continuous period longer than the RMS Extreme Under
Voltage Measurement Period(5.7.4.36) and on detection:
1642
1643
1644
1645
1646
RMS extreme under voltage detection
a) generating an entry to that effect in the Power Event Log(5.7.5.25);
b) generating and sending an Alert to that effect via its HAN Interface;
ii.
detecting when the RMS voltage rises back above the RMS Extreme Under Voltage
Threshold(5.7.4.37) for a continuous period longer than the RMS Extreme Under
Voltage Measurement Period(5.7.4.36) and on detection:
1647
1648
a) generating an entry to that effect in the Power Event Log(5.7.5.25);
b) generating and sending an Alert to that effect via its HAN Interface;
1649
5.5.12.4
1650
ESME shall be capable of:
1651
1652
1653
i.
detecting when the RMS voltage falls below the RMS Voltage Sag
Threshold(5.7.4.40) for a continuous period longer than the RMS Voltage Sag
Measurement Period(5.7.4.38) and on detection:
1654
1655
1656
1657
1658
RMS voltage sag detection
a) generating an entry to that effect in the Power Event Log(5.7.5.25); and
b) generating and sending an Alert to that effect via its HAN Interface;
ii.
detecting when the RMS voltage returns above the RMS Voltage Sag
Threshold(5.7.4.40) for longer than the RMS Voltage Sag Measurement
Period(5.7.4.38) and on detection:
1659
1660
a) generating an entry to that effect in the Power Event Log(5.7.5.25); and
b) generating and sending an Alert to that effect via its HAN Interface.
1661
5.5.12.5
1662
ESME shall be capable of:
1663
1664
1665
i.
detecting when the RMS voltage rises above the RMS Voltage Swell
Threshold(5.7.4.41) for a continuous period longer than the RMS Voltage Swell
Measurement Period(5.7.4.39) and on detection:
1666
1667
1668
1669
1670
RMS voltage swell detection
a) generating an entry to that effect in the Power Event Log(5.7.5.25); and
b) generating and sending an Alert to that effect via its HAN Interface;
ii.
detecting when the RMS voltage returns below the RMS Voltage Swell
Threshold(5.7.4.41) for a continuous period longer than the RMS Voltage Swell
Measurement Period(5.7.4.39) and on detection:
1671
1672
a) generating an entry to that effect in the Power Event Log(5.7.5.25); and
b) generating and sending an Alert to that effect via its HAN Interface.
1673
5.5.12.6
1674
1675
ESME shall be capable of recording the UTC date and time at which the Supply is
interrupted and the UTC date and time when the Supply is restored and:
1676
1677
1678
1679
1680
1681
i.
ii.
iii.
Supply outage reporting
generating entries to that effect in the Power Event Log(5.7.5.25);
following restoration of the Supply, generating and sending an Alert to that effect via
its HAN Interface containing details of the UTC dates and times of interruption and
restoration; and
following restoration of the Supply, when the time difference between the Supply
being interrupted and restored is greater than or equal to three minutes, generating
Version 1.59
18 November 2015
Page 43
DRAFT
1682
1683
SMETS
and sending an Alert to that effect via its HAN Interface containing details of the
UTC dates and times of interruption and restoration.
1684
5.6 Interface Requirements
1685
1686
1687
This section describes the minimum required interactions which ESME shall be capable of
undertaking via its HAN Interface and its User Interface (including with Devices as set out in
Sections 5.5.2.2 and 5.5.2.3).
1688
5.6.1
1689
1690
1691
1692
ESME shall be capable, immediately upon establishment of a Communications Link with
Type 1 Devices (as set out in Section 5.5.2.2) and Type 2 Devices (as set out in Section
5.5.2.3), of providing the data annotated [INFO] set out in Sections 5.7.1, 5.7.4 and 5.7.5 to
Type 1 Devices and Type 2 Devices (with timely updates of any changes to all data).
1693
5.6.2
1694
1695
ESME shall be capable of executing immediately the Commands set out in this Section 5.6.2
following their receipt via its User Interface.
1696
1697
ESME shall be capable of logging all such Commands received and Outcomes in the Event
Log(5.7.5.16).
1698
5.6.2.1
1699
1700
A Command to activate Emergency Credit when ESME is operating in Prepayment Mode
where Emergency Credit is available (as set out in Section 5.5.7.2).
1701
1702
1703
1704
1705
In executing the Command, if the Supply is Disabled, ESME shall be capable of Arming the
Supply if the combined credit of the Meter Balance [INFO](5.7.5.22) and Emergency Credit
Balance [INFO](5.7.5.15) rises above the Disablement Threshold [INFO](5.7.4.15),
displaying any such change in the Supply State [INFO](5.7.5.32) on its User Interface and
generating and sending an Alert that the Supply has been Armed via its HAN Interface.
1706
5.6.2.2
1707
1708
A Command to accept credit to be applied to ESME when ESME is operating in Prepayment
Mode on input of a UTRN. In executing the Command, ESME shall be capable of:
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
i.
ii.
iii.
iv.
v.
vi.
Type 1 Devices and Type 2 Device information provision
User Interface Commands
Activate Emergency Credit [PIN]
Add Credit
comparing the credit value of the UTRN with the Maximum Credit
Threshold(5.7.4.25) and rejecting the UTRN where the credit value is greater than
that threshold;
comparing the projected new Meter Balance [INFO](5.7.5.22) (calculated on the
basis of (xii) to (xv) below and the credit value of the UTRN and rejecting the UTRN
where the projected new Meter Balance [INFO](5.7.5.22) is greater than the
Maximum Meter Balance Threshold(5.7.4.27);
verifying the Authenticity of the UTRN;
verifying that ESME is the intended recipient of the UTRN;
using the UTRN to generate a PTUT Counter, and comparing this against the last
100 verified PTUT Counters and rejecting duplicate presentation of verified UTRNs
and PTUTs; and
controlling the number of invalid UTRN entries entered and processed.
ESME shall be capable of generating an entry in the Security Log(5.7.5.31):
vii.
viii.
ix.
x.
xi.
where the UTRN is rejected as set out in (i) above;
where the UTRN is rejected as set out in (ii) above;
on failure of (iii) above;
on failure of (iv) above; and
where duplicates are rejected as set out in (v) above.
Version 1.59
18 November 2015
Page 44
DRAFT
1728
1729
1730
1731
1732
1733
1734
1735
1736
SMETS
In executing the Command, ESME shall be capable of applying the credit added in the
following order:
xii.
xiii.
xiv.
xv.
recovery of payment-based debt of an amount defined by Debt Recovery per
Payment [INFO](5.7.4.11) from the Payment Debt Register [INFO](5.7.5.23) subject
to the Debt Recovery Rate Cap [INFO](5.7.4.13);
recovery of debt accumulated in the Accumulated Debt Register [INFO](5.7.5.1);
repayment of Emergency Credit activated and used by the Consumer; and
adding remaining credit (the credit after deduction of (xii), (xiii) and (xiv) above) to
the Meter Balance [INFO] (5.7.5.22).
1737
1738
1739
1740
In executing the Command, ESME shall be capable of Arming the Supply if the Meter
Balance [INFO](5.7.5.22) rises above the Disablement Threshold [INFO](5.7.4.15) and
displaying any such change in the Supply State [INFO](5.7.5.32) on its User Interface and
generating and sending an Alert that the Supply has been Armed via its HAN Interface.
1741
In executing the Command, ESME shall be capable of:
1742
1743
1744
1745
1746
xvi.
xvii.
recording the credit applied to the Meter Balance [INFO](5.7.5.22) and the amount of
payment-based debt recovered (as set out in (xii)) in the Billing Data Log(5.7.5.10);
and
generating and sending an Alert containing the UTC date and time of the last update
of the Meter Balance [INFO](5.7.5.22) via its HAN Interface.
1747
5.6.2.3
1748
1749
1750
1751
Where Privacy PIN Protection is enabled, a Command to enable temporary access to the
restricted display items annotated [PIN] in Section 5.5.4 and the restricted User Interface
Commands annotated [PIN] in Section 5.6.2 on input of a number that matches the Privacy
PIN(5.7.3.1).
1752
5.6.2.4
1753
A Command to disable Privacy PIN Protection.
1754
5.6.2.5
1755
A Command to Enable the Supply if the Supply is Armed.
1756
1757
In executing the Command ESME shall be capable of setting the Supply State
[INFO](5.7.5.32) accordingly.
1758
1759
5.6.2.6
1760
1761
A Command to seek the frequency at which a ZigBee SEP v1.2 Smart Metering Home Area
Network is operating and then:
1762
1763
1764
1765
i.
ii.
iii.
Allow Access to User Interface
Disable Privacy PIN Protection [PIN]
Enable Supply [PIN]
Find Smart Metering Home Area Network and Re-establish
Communications Links
re-establish the Communications Links set out in Sections 5.5.2.1, 5.5.2.2 and
5.5.2.3;
generate an entry to that effect in the Event Log(5.7.5.16); and
generate and sending an Alert to that effect via its HAN Interface.
1766
1767
Where the ESME has Communications Links set out in (i) ESME shall be capable of not
executing the Command.
1768
5.6.2.7
1769
A Command to set a new value of the Privacy PIN(5.7.3.1).
1770
1771
In executing the Command where Privacy PIN Protection is disabled ESME shall be capable
of enabling Privacy PIN Protection.
Version 1.59
Set Privacy PIN [PIN]
18 November 2015
Page 45
DRAFT
SMETS
1772
5.6.3
1773
1774
ESME shall be capable of executing the Commands set out in this section. ESME shall be
capable of logging all Commands received and Outcomes in the Event Log(5.7.5.16).
1775
1776
1777
1778
ESME shall be capable of executing Commands immediately on receipt (‘immediate
Commands’) and where specified in the Great Britain Companion Specification at a future
date (‘future dated Commands’). A future dated Command shall include the UTC date and
time at which the Command shall be executed by ESME.
1779
1780
1781
1782
ESME shall be capable of cancelling a future dated Command. A future dated Command
shall be capable of being cancelled by an Authorised party, subject to RBAC (as set out in
Section 5.5.10.2.3). ESME shall be capable of generating and sending a Response
acknowledging that a future dated Command has been successfully cancelled.
1783
5.6.3.1
1784
1785
A Command to activate Emergency Credit when ESME is operating in Prepayment Mode
where Emergency Credit is available (as set out in Section 5.5.7.2).
1786
1787
1788
1789
1790
In executing the Command where the Supply is Disabled ESME shall be capable of Arming
the Supply if the combined credit of the Meter Balance [INFO](5.7.5.22) and Emergency
Credit Balance [INFO](5.7.5.15) rises above the Disablement Threshold [INFO](5.7.4.15),
displaying any such change in the Supply State [INFO](5.7.5.32) on its User Interface and
generating and sending an Alert that the Supply has been Armed via its HAN Interface.
1791
1792
When operating in Credit Mode, ESME shall be capable of not executing the Command and
generating and sending a Response to that effect via its HAN Interface.
1793
5.6.3.2
1794
A Command to activate Firmware.
1795
1796
In executing the Command ESME shall be capable of installing new Firmware using a
mechanism that is robust against failure and loss of data.
1797
1798
1799
The new Firmware shall include version information. Where new Firmware is successfully
installed, ESME shall be capable of recording the version information of that new Firmware
in Firmware Version(5.7.5.17).
1800
5.6.3.3
1801
1802
A Command to accept credit to be applied to ESME when ESME is operating in Prepayment
Mode on receipt of: a UTRN from a Type 1 Device or a PTUT from an Authorised party.
1803
1804
In executing the Command following receipt of a UTRN from a Type 1 Device ESME shall be
capable of applying credit as set out in Section 5.6.2.2.
1805
1806
In executing the Command following receipt of a PTUT from an Authorised party, ESME
shall be capable of:
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
i.
ii.
iii.
iv.
v.
vi.
HAN Interface Commands
Activate Emergency Credit
Activate Firmware
Add Credit
comparing the credit value of the PTUT with the Maximum Credit
Threshold(5.7.4.25) and rejecting the PTUT where the credit value is greater than
that threshold;
comparing the projected new Meter Balance [INFO](5.7.5.22) (calculated on the
basis of (xii) to (xv) below and the credit value of the PTUT and rejecting the PTUT
where the projected new Meter Balance [INFO](5.7.5.22) is greater than the
Maximum Meter Balance Threshold(5.7.4.27);
verifying the Authenticity of the PTUT;
verifying that ESME is the intended recipient of the PTUT;
comparing the PTUT Counter against the last 100 verified PTUT Counters and
rejecting duplicate presentation of verified UTRNs and PTUTs; and
controlling the number of invalid PTUT entries entered and processed.
Version 1.59
18 November 2015
Page 46
DRAFT
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
SMETS
ESME shall be capable of generating an entry in the Security Log(5.7.5.31):
vii.
viii.
ix.
x.
xi.
where the PTUT is rejected as set out in (i) above;
where the PTUT is rejected as set out in (ii) above;
on failure of (iii) above;
on failure of (iv) above; and
where duplicates are rejected as set out in (v) above.
In executing the Command, ESME shall be capable of applying the credit added in the
following order:
xii.
xiii.
xiv.
xv.
recovery of payment-based debt of an amount defined by Debt Recovery per
Payment [INFO](5.7.4.11) from the Payment Debt Register [INFO](5.7.5.23) subject
to the Debt Recovery Rate Cap [INFO](5.7.4.13);
recovery of debt accumulated in the Accumulated Debt Register [INFO](5.7.5.1);
repayment of Emergency Credit activated and used by the Consumer; and
adding remaining credit (the credit after deduction of (xii), (xiii) and (xiv) above) to
the Meter Balance [INFO](5.7.5.22).
1834
1835
1836
1837
In executing the Command, ESME shall be capable of Arming the Supply if the Meter
Balance [INFO](5.7.5.22) rises above the Disablement Threshold [INFO](5.7.4.15),
displaying any such change in the Supply State [INFO](5.7.5.32) on its User Interface and
generating and sending an Alert that the Supply has been Armed via its HAN Interface.
1838
1839
1840
In executing the Command, ESME shall be capable of recording the credit applied to the
Meter Balance [INFO](5.7.5.22) and the amount of payment-based debt recovered (as set
out in (xii)) in the Billing Data Log(5.7.5.10).
1841
1842
1843
In executing the Command from a Type 1 Device, ESME shall be capable of generating and
sending an Alert containing the UTC date and time stamp of the last update of the Meter
Balance [INFO](5.7.5.22) via its HAN Interface.
1844
1845
When operating in Credit Mode, ESME shall be capable of not executing the Command and
generating and sending a Response to that effect via its HAN Interface.
1846
5.6.3.4
1847
1848
A Command to add Security Credentials for a Type 1 Device or a Type 2 Device to the
Device Log(5.7.4.14).
1849
In executing the Command, ESME shall be capable of:
Add Device Security Credentials
1850
1851
i.
ii.
verifying the Security Credentials; and
recording the Command and Outcome to the Security Log(5.7.5.31).
1852
5.6.3.5
1853
1854
1855
A Command to apply positive and negative adjustments to the Time Debt Registers [1 … 2]
[INFO](5.7.5.36) and the Payment Debt Register [INFO](5.7.5.23) when operating in
Prepayment Mode.
1856
1857
When operating in Credit Mode, ESME shall be capable of not executing the Command and
generating and sending a Response to that effect via its HAN Interface.
1858
5.6.3.6
1859
1860
A Command to apply positive and negative adjustments to the Meter Balance
[INFO](5.7.5.22).
1861
1862
1863
1864
1865
In executing the Command where ESME is operating in Prepayment Mode and where,
following any such adjustment, the Meter Balance [INFO](5.7.5.22) rises above the
Disablement Threshold [INFO](5.7.4.15), ESME shall be capable of Arming the Supply and
displaying any such change in the Supply State [INFO](5.7.5.32) on its User Interface,
generating and sending an Alert that the Supply has been Armed via its HAN Interface.
Version 1.59
Adjust Debt
Adjust Meter Balance
18 November 2015
Page 47
DRAFT
SMETS
1866
5.6.3.7
1867
A Command to return ESME from a Locked state to an Unlocked state.
1868
In executing the Command ESME shall be capable of:
1869
1870
1871
1872
1873
1874
1875
1876
i.
ii.
Arm Supply
where the state of the Supply as determined by ESME (in accordance with the
requirements to Arm, Enable or Disable the Supply in this Section 5), is Disabled,
ESME shall not Arm the Supply and shall set the Supply State [INFO](5.7.5.32) as
Disabled; and
where the state of the Supply as determined by ESME (in accordance with the
requirements to Arm, Enable or Disable the Supply in this Section 5), is Enabled or
Armed, ESME shall Arm the Supply and set the Supply State [INFO](5.7.5.32) as
Armed.
1877
5.6.3.8
1878
1879
1880
A Command to clear all entries from the Auxiliary Load Control Switch Event Log(5.7.5.6).
ESME shall be capable of logging that the Command has been executed in the Security
Log(5.7.5.31).
1881
5.6.3.9
1882
1883
A Command to clear all entries from the Event Log(5.7.5.16). ESME shall be capable of
logging that the Command has been executed in the Security Log(5.7.5.31).
1884
5.6.3.10
1885
A Command to disable Privacy PIN Protection.
1886
5.6.3.11
1887
1888
1889
A Command to establish a Locked state whereby the Supply is Disabled and can only be
Enabled or Armed in response to a Command to Arm the Supply (as described in Section
5.6.3.7) or Enable the Supply (as described in Section 5.6.3.12)
1890
1891
In executing the Command ESME shall be capable of setting the Supply State(5.7.5.32) to
Disabled.
1892
5.6.3.12
1893
A Command to return ESME from a Locked state to an Unlocked state.
1894
In executing the Command:
1895
1896
1897
1898
1899
1900
1901
1902
i.
ii.
Clear Auxiliary Load Control Switch Event Log
Clear Event Log
Disable Privacy PIN Protection
Disable Supply
Enable Supply
where the state of the Supply as determined by ESME (in accordance with the
requirements to Arm, Enable and Disable Supply in this Section 5) is Disabled,
ESME shall not Enable the Supply and shall set the Supply State [INFO](5.7.5.32)
as Disabled; and
where the state of the Supply as determined by ESME (in accordance with the
requirements to Arm, Enable and Disable Supply in this Section 5) is Armed or
Enabled, ESME shall Enable the Supply and shall set the Supply State
[INFO](5.7.5.32) as Enabled.
1903
5.6.3.13
1904
1905
A Command to generate a Public-Private Key Pair and issue a corresponding Certificate
Signing Request.
1906
5.6.3.14
1907
1908
1909
A Command issued by a PPMID to Enable the Supply if the Supply is Armed. In executing
the Command ESME shall be capable of setting the Supply State [INFO](5.7.5.32)
accordingly.
Version 1.59
Issue ESME Security Credentials
PPMID Enable Supply
18 November 2015
Page 48
DRAFT
SMETS
1910
5.6.3.15
Read Configuration Data
1911
1912
A Command to read the value of one or more of the configuration data items set out in
Section 5.7.4.
1913
1914
In executing the Command, ESME shall be capable of sending such value(s) in a Response
via its HAN Interface.
1915
5.6.3.16
1916
1917
A Command to read the value of one or more of the constant data items set out in Section
5.7.1.
1918
1919
In executing the Command, ESME shall be capable of sending such value(s) in a Response
via its HAN Interface.
1920
5.6.3.17
1921
1922
A Command to read the value of one or more of the operational data items set out in Section
5.7.5.
1923
1924
In executing the Command, ESME shall be capable of sending such value(s) in a Response
via its HAN Interface.
1925
5.6.3.18
1926
A Command to receive Firmware.
1927
In executing the Command ESME shall be capable of:
Read Constant Data
Read Operational Data
Receive Firmware
1928
1929
i.
ii.
only accepting new Firmware from an Authorised and Authenticated source; and
verifying the Authenticity and integrity of new Firmware before installation.
1930
5.6.3.19
1931
1932
A Command to remove Security Credentials for a Type 1 Device or a Type 2 Device from
the Device Log(5.7.4.14).
1933
1934
In executing the Command ESME shall be capable of recording the Command and Outcome
to the Security Log(5.7.5.31).
1935
5.6.3.20
1936
A Command to replace ESME Security Credentials(5.7.4.18).
1937
In executing the Command ESME shall be capable of:
Remove Device Security Credentials
Replace ESME Security Credentials
maintaining the Command’s Transactional Atomicity; and
recording the Command and Outcome to the Security Log(5.7.5.31).
1938
1939
i.
ii.
1940
5.6.3.21
1941
1942
1943
A Command issued by a HCALCS requesting that an ESME issues a Control HAN
Connected Auxiliary Load Control Switch(5.6.4.1) Command according to the rules set out in
Section 5.5.11.
1944
5.6.3.22
1945
A Command to reset the Average RMS Over Voltage Counter(5.7.5.7) to zero.
1946
5.6.3.23
1947
A Command to reset the Average RMS Under Voltage Counter(5.7.5.8) to zero.
1948
5.6.3.24
1949
1950
A Command to revert to the state commanded by the Auxiliary Load Control Switch
Calendar(5.7.4.2). In executing the Command, according to the rules set out in Section
Version 1.59
Request Control of HAN Connected Auxiliary Load Control Switch
Reset Average RMS Over Voltage Counter
Reset Average RMS Under Voltage Counter
Reset HAN Connected Auxiliary Load Control Switch [n] State
18 November 2015
Page 49
DRAFT
SMETS
1951
1952
5.5.11.1, ESME shall be capable of issuing a Control HAN Connected Auxiliary Load Control
Switch(5.6.4.1) Command to HCALCS [n].
1953
5.6.3.25
1954
A Command to reset the Load Limit Counter(5.7.5.18) to zero.
1955
5.6.3.26
1956
A Command to reset the Maximum Demand Active Power Import Value(5.7.5.19).
1957
5.6.3.27
1958
A Command to reset the Maximum Demand Active Power Export Value(5.7.5.21).
1959
5.6.3.28
1960
1961
A Command to reset the Maximum Demand (Configurable Time) Active Power Import
Value(5.7.5.20).
1962
5.6.3.29
1963
A Command to reset the Meter Balance [INFO](5.7.5.22) to zero.
1964
1965
In executing the Command, ESME shall reset the Accumulated Debt Register
[INFO](5.7.5.1) and the Emergency Credit Balance [INFO](5.7.5.15).
1966
5.6.3.30
1967
A Command to reset the Tariff Block Counter Matrix [INFO](5.7.5.33) to zero.
1968
5.6.3.31
1969
1970
1971
A Command to restrict provision to Type 1 Devices and Type 2 Devices of all items of
Personal Data stored in ESME which have a UTC date and time stamp prior to the date and
time stamp specified in the Restrict Data Command.
1972
5.6.3.32
1973
A Command to set the Clock date and time via its HAN Interface.
1974
1975
1976
In executing the Command, ESME shall be capable of comparing the date and time
specified in the Command with the Communications Hub Date and Time. Where the
difference is:
1977
1978
1979
1980
1981
i.
ii.
Reset Load Limit Counter
Reset Maximum Demand Active Power Import Value
Reset Maximum Demand Active Power Export Value
Reset Maximum Demand (Configurable Time) Active Power Import Value
Reset Meter Balance
Reset Tariff Block Counter Matrix
Restrict Data
Set Clock
within the tolerance specified in the Command ESME shall be capable of adjusting
its date and time to the Communications Hub Date and Time and generating an
entry to that effect in the Event Log(5.7.5.16); and
outside the tolerance specified in the Command ESME shall be capable of not
adjusting its date and time and:
1982
1983
a) generating an entry to that effect in the Event Log(5.7.5.16); and
b) generating and sending an Alert to that effect via its HAN Interface.
1984
1985
ESME shall be capable of ensuring that any adjustments do not cause calendar-based
events to be missed or future-dated Commands to be missed or repeated.
1986
5.6.3.33
1987
1988
1989
1990
A Command to ignore the state defined in Auxiliary Load Control Switch Calendar(5.7.4.2)
and to issue a Control HAN Connected Auxiliary Load Control Switch (5.6.4.1) Command to
HCALCS [n] for a time period specified within the ‘Set HAN Connected Auxiliary Load
Control Switch [n] State Command’.
1991
1992
ESME shall only be capable of issuing a Command to set HCALCS [n] as closed when the
Supply State [INFO](5.7.5.32) is Enabled.
Version 1.59
Set HAN Connected Auxiliary Load Control Switch [n] State
18 November 2015
Page 50
DRAFT
SMETS
1993
5.6.3.34
1994
1995
A Command to set the payment mode as either Prepayment Mode or Credit Mode and to
record the mode of operation in Payment Mode [INFO](5.7.4.31).
1996
1997
In executing the Command, ESME shall be capable of taking a UTC date and time stamped
copy of:
1998
1999
2000
2001
2002
2003
2004
2005
2006
i.
ii.
iii.
Set Payment Mode
the Tariff TOU Register Matrix [INFO](5.7.5.34);
the Tariff TOU Block Register Matrix(5.7.5.35); and
the Active Import Register [INFO](5.7.5.3),
and unless in Credit Mode both before and after execution of the Command:
iv.
v.
vi.
vii.
viii.
the Meter Balance [INFO](5.7.5.22);
the Emergency Credit Balance [INFO](5.7.5.15);
the Payment Debt Register [INFO](5.7.5.23);
the Time Debt Registers [1 … 2] [INFO](5.7.5.36); and
the Accumulated Debt Register [INFO](5.7.5.1),
2007
in the Billing Data Log(5.7.5.10).
2008
5.6.3.35
2009
2010
2011
A Command to accept new values for Tariff TOU Price Matrix [INFO](5.7.4.50), Tariff Block
Price Matrix [INFO](5.7.4.47), Tariff Switching Table(5.7.4.48) and Tariff Threshold Matrix
[INFO](5.7.4.49).
2012
2013
In executing the Command, ESME shall be capable of taking a UTC date and time stamped
copy of:
2014
2015
2016
2017
2018
2019
2020
2021
2022
i.
ii.
iii.
Set Tariff
the Tariff TOU Register Matrix [INFO](5.7.5.34);
the Tariff TOU Block Register Matrix(5.7.5.35); and
the Active Import Register [INFO](5.7.5.3),
and where in Prepayment mode:
iv.
v.
vi.
vii.
viii.
the Meter Balance [INFO](5.7.5.22);
the Emergency Credit Balance [INFO](5.7.5.15);
the Payment Debt Register [INFO](5.7.5.23);
the Time Debt Registers [1 … 2] [INFO](5.7.5.36); and
the Accumulated Debt Register [INFO](5.7.5.1),
2023
in the Billing Data Log(5.7.5.10).
2024
5.6.3.36
2025
2026
A Command to record one or more new values of the configuration data items set out in
Section 5.7.3.
2027
2028
In executing the Command, ESME shall be capable of generating an entry to that effect in
the Event Log(5.7.5.16).
2029
5.6.4
2030
2031
ESME shall be capable of issuing the Commands set out in this section, receiving
corresponding Responses and, where required by a Response, taking the required actions.
2032
5.6.4.1
2033
2034
2035
2036
A Command requesting that a HAN Connected Auxiliary Load Control Switch either closes
or opens its switch for a time period specified within the Command. The ESME shall be
capable of issuing a Control HAN Connected Auxiliary Load Control Switch(5.6.4.1)
Command according to the rules set out in Section 5.5.11.1.
Write Configuration Data
HAN Interface Commands issued by ESME
Version 1.59
Control HAN Connected Auxiliary Load Control Switch
18 November 2015
Page 51
DRAFT
SMETS
2037
2038
In executing the Command, ESME shall be capable of recording the Command and
Outcome to the Auxiliary Load Control Switch Event Log(5.7.5.6).
2039
5.7 Data Requirements
2040
2041
This section describes the minimum information which ESME shall be capable of holding in
its Data Store.
2042
5.7.1
2043
Describes data that remains constant and unchangeable at all times.
2044
5.7.1.1
2045
2046
A globally unique identifier used to identify ESME based on the EUI-64 Institute of Electrical
and Electronic Engineers standard.
2047
5.7.1.2
2048
An identifier used to identify the manufacturer of ESME.
2049
5.7.1.3
2050
An identifier used to identify the model of ESME.
2051
5.7.1.4
2052
2053
A data item to indicate if ESME is Single Element Electricity Metering Equipment, Twin
Element Electricity Metering Equipment or Polyphase Electricity Metering Equipment.
2054
5.7.1.5
2055
A randomly generated value between 0 and 1.
2056
5.7.2
This section is not used
2057
5.7.3
Locally Set Configuration Data
2058
2059
Describes data that is configured by execution of a User Interface Command and that is not
available outside ESME.
2060
5.7.3.1
2061
2062
A number comprising four digits used by the Consumer to enable temporary access to a
specified set of display items and Commands via the User Interface of ESME.
2063
5.7.4
2064
Describes data that configures the operation of various functions of ESME.
2065
5.7.4.1
2066
Settings to control whether to generate and send an Alert.
2067
5.7.4.2
2068
2069
2070
A Switching Table containing a set of rules for setting the commanded state of up to five
Auxiliary Load Control Switches or HAN Connected Auxiliary Load Control Switches as open
and closed.
2071
2072
2073
The rules stored within the table shall specify which Day Profile should be used to set the
commanded state of each Auxiliary Load Control Switch or HAN Connected Auxiliary Load
Control Switch according to:
2074
2075
i.
Constant data
ESME Identifier
Manufacturer Identifier
Model Type
Meter Variant
Randomised Offset Number
Privacy PIN
Configuration data
Alerts Configuration Settings
Auxiliary Load Control Switch Calendar
where the day is one of 20 Special Days, the Day Profile specified for that day and
the Day Profile specified for that day of the Week; or
Version 1.59
18 November 2015
Page 52
DRAFT
2076
2077
ii.
SMETS
where the day is not a Special Day, the Day Profile specified for that day of the
Week.
2078
The Switching Table shall support up to 60 switching rules across all Day Profiles.
2079
All dates and times shall be specified in UTC.
2080
5.7.4.3
2081
2082
2083
For each Auxiliary Load Control Switch or HAN Connected Auxiliary Load Control Switch, a
description of the type of controlled load connected, the switch type and, for HAN Connected
Auxiliary Load Control Switches, the HCALCS Identifier(8.6.1.1).
2084
5.7.4.4
2085
2086
The average RMS voltage above which an over voltage condition is reported. The threshold
shall be configurable within the specified operating range of ESME.
2087
5.7.4.5
2088
2089
The average RMS voltage below which an under voltage condition is reported. The threshold
shall be configurable within the specified operating range of ESME.
2090
5.7.4.6
2091
The length of time in seconds over which the RMS voltage is averaged.
2092
5.7.4.7
2093
2094
A calendar defining billing dates for the storage of billing related information in the Billing
Data Log(5.7.5.10).
2095
5.7.4.8
2096
The name and contact telephone number of the Supplier.
2097
5.7.4.9
2098
2099
The Currency Units currently used by ESME, which shall be either GB Pounds or European
Central Bank Euro.
2100
5.7.4.10
2101
A number issued to ESME for display on the User Interface.
2102
5.7.4.11
2103
2104
The percentage of a payment to be recovered against debt when ESME is operating
Payment-based Debt Recovery in Prepayment Mode.
2105
5.7.4.12
2106
2107
Two debt recovery rates in Currency Units per unit time for when ESME is using Time-based
Debt Recovery in Prepayment Mode.
2108
5.7.4.13
2109
2110
The maximum amount in Currency Units per unit time that can be recovered through
Payment-based Debt Recovery when ESME is operating in Prepayment Mode.
2111
5.7.4.14
2112
2113
The Security Credentials for each of the Type 1 Devices and Type 2 Devices with which
ESME can establish Communications Links.
2114
5.7.4.15
2115
The threshold in Currency Units for controlling when to Disable the Supply.
Version 1.59
Auxiliary Load Control Switch [n] Description [INFO]
Average RMS Over Voltage Threshold
Average RMS Under Voltage Threshold
Average RMS Voltage Measurement Period
Billing Calendar
Contact Details [INFO]
Currency Units [INFO]
Customer Identification Number [INFO]
Debt Recovery per Payment [INFO]
Debt Recovery Rates [1 … 2] [INFO]
Debt Recovery Rate Cap [INFO]
Device Log
Disablement Threshold [INFO]
18 November 2015
Page 53
DRAFT
SMETS
2116
5.7.4.16
2117
2118
The amount of Emergency Credit in Currency Units to be made available to a Consumer
where Emergency Credit is activated by the Consumer.
2119
5.7.4.17
2120
2121
2122
The threshold in Currency Units below which Emergency Credit Balance [INFO](5.7.5.15)
may be activated by the Consumer if so configured when ESME is operating in Prepayment
Mode.
2123
5.7.4.18
2124
2125
The Security Credentials for ESME and parties Authorised to establish Communications
Links with it.
2126
5.7.4.19
2127
2128
2129
The length of time in seconds which the Active Power Import [INFO](5.7.5.4) needs to
continuously exceed the Load Limit Power Threshold(5.7.4.20) before a load limiting event is
deemed to have occurred.
2130
5.7.4.20
2131
2132
The Active Power threshold in kW above which the measurement of a Load Limit
Period(5.7.4.19) is commenced.
2133
5.7.4.21
2134
2135
The length of time in seconds after the Supply has been Armed following a Load Limiting
Event before the Supply is Enabled by ESME.
2136
5.7.4.22
2137
2138
A setting to control the state of the Supply in the case of a load limiting occurring, being
Disabled or unchanged.
2139
5.7.4.23
2140
The threshold in Currency Units below which a low credit Alert is signalled.
2141
5.7.4.24
2142
2143
A value in kW defining the threshold between an indicative low and medium Active Power
Import [INFO](5.7.5.4) level.
2144
5.7.4.25
2145
The maximum credit which can be applied by any Add Credit Command.
2146
5.7.4.26
2147
2148
2149
A single time period of up to 24 hours comprising a number of half-hour periods
(commencing at the start of minutes 00 and 30 in each hour) during which recording to the
Maximum Demand (Configurable Time) Active Power Import Value(5.7.5.20) is active.
2150
5.7.4.27
2151
2152
The Meter Balance [INFO](5.7.5.22) threshold in Currency Units above which an Add Credit
Command is rejected.
2153
5.7.4.28
2154
The reference numbers identifying an electricity metering point for Import and Export.
2155
5.7.4.29
2156
2157
A value in kW defining the threshold between an indicative medium and high Active Power
Import [INFO](5.7.5.4) level.
Version 1.59
Emergency Credit Limit [INFO]
Emergency Credit Threshold [INFO]
ESME Security Credentials
Load Limit Period
Load Limit Power Threshold
Load Limit Restoration Period
Load Limit Supply State
Low Credit Threshold [INFO]
Low Medium Power Threshold [INFO]
Maximum Credit Threshold
Maximum Demand Configurable Time Period
Maximum Meter Balance Threshold
Meter Point Administration Numbers (MPAN) [INFO]
Medium High Power Threshold [INFO]
18 November 2015
Page 54
DRAFT
SMETS
2158
5.7.4.30
2159
2160
2161
2162
A Switching Table comprising a set of rules specifying periods during which the Supply will
not be Disabled due to the combined credit of the Meter Balance [INFO](5.7.5.22) and
Emergency Credit Balance [INFO](5.7.5.15) falling below the Disablement Threshold
[INFO](5.7.4.15), when ESME is operating in Prepayment Mode.
2163
2164
The rules stored within the table shall specify which of five Day Profiles should be used to
specify Non-disablement Periods for each day according to:
2165
2166
2167
i.
ii.
Non-Disablement Calendar [INFO]
where the day is one of 20 Special Days, the Day Profile specified for that day; or
where the day is not a Special Day, the Day Profile specified by the active Season
Profile and Week Profile.
2168
2169
2170
2171
A Day Profile shall contain up to one contiguous time period during which the Supply may be
Disabled due to the combined credit of the Meter Balance [INFO](5.7.5.22) and Emergency
Credit Balance [INFO](5.7.5.15) falling below the Disablement Threshold [INFO](5.7.4.15),
when ESME is operating in Prepayment Mode.
2172
2173
The rules shall support three Season Profiles and two Week Profiles. Each Week Profile
shall support two Day Profiles.
2174
All dates and times shall be specified as UTC.
2175
5.7.4.31
2176
The current mode of operation, being Prepayment Mode or Credit Mode.
2177
5.7.4.32
2178
A store for Security Credentials relating to Public Keys.
2179
5.7.4.33
2180
A value in seconds in the range 0 to 1799.
2181
5.7.4.34
2182
The duration in seconds used to measure an extreme over voltage condition.
2183
5.7.4.35
2184
2185
The RMS voltage above which an extreme over voltage condition is reported. The threshold
shall be configurable within the specified operating range of ESME.
2186
5.7.4.36
2187
The duration in seconds used to measure an extreme under voltage condition.
2188
5.7.4.37
2189
2190
The RMS voltage below which an extreme under voltage condition is reported. The threshold
shall be configurable within the specified operating range of ESME.
2191
5.7.4.38
2192
The duration in seconds used to measure a voltage sag condition.
2193
5.7.4.39
2194
The duration in seconds used to measure a voltage swell condition.
2195
5.7.4.40
2196
2197
The RMS voltage below which a sag condition is reported. The threshold shall be
configurable within the specified operating range of ESME.
Version 1.59
Payment Mode [INFO]
Public Key Security Credentials Store
Randomised Offset Limit
RMS Extreme Over Voltage Measurement Period
RMS Extreme Over Voltage Threshold
RMS Extreme Under Voltage Measurement Period
RMS Extreme Under Voltage Threshold
RMS Voltage Sag Measurement Period
RMS Voltage Swell Measurement Period
RMS Voltage Sag Threshold
18 November 2015
Page 55
DRAFT
SMETS
2198
5.7.4.41
2199
2200
The RMS voltage above which a swell condition is reported. The threshold shall be
configurable within the specified operating range of ESME.
2201
5.7.4.42
2202
2203
A charge to be levied in Currency Units per unit time when operating in Credit Mode and
Prepayment Mode.
2204
5.7.4.43
2205
A message issued to, and held on, ESME for provision to the Consumer.
2206
5.7.4.44
2207
2208
A setting to control the state of the Supply in the case of Unauthorised Physical Access
being detected, being Locked or unchanged.
2209
5.7.4.45
2210
2211
A setting controlling whether standing charge and debt should be collected when ESME is
operating in Prepayment Mode and Supply is Disabled.
2212
5.7.4.46
2213
2214
2215
A setting controlling whether standing charge and debt should be deducted from the
Emergency Credit Balance [INFO](5.7.5.15) when ESME is operating in Prepayment Mode
and Emergency Credit is in use.
2216
5.7.4.47
2217
A 4 x 8 matrix containing Prices for Block Pricing.
2218
5.7.4.48
2219
2220
2221
2222
A set of rules for allocating half-hourly Consumption to a Tariff Register for Time-of-use
Pricing and Time-of-use with Block Pricing. The rules stored within the table shall specify
which of 16 Day Profiles should be used to allocate Consumption to Tariff Registers
according to:
2223
2224
2225
i.
ii.
RMS Voltage Swell Threshold
Standing Charge [INFO]
Supplier Message [INFO]
Supply Tamper State
Suspend Debt Disabled
Suspend Debt Emergency
Tariff Block Price Matrix [INFO]
Tariff Switching Table [INFO]
where the day is one of 50 Special Days, the Day Profile specified for that day; or
where the day is not a Special Day, the Day Profile specified by the active Season
Profile and Week Profile.
2226
2227
The Switching Table shall support four Season Profiles and four Week Profiles. The
Switching Table shall support up to 200 switching rules across all Day Profiles.
2228
All dates and times shall be specified as UTC.
2229
5.7.4.49
2230
A 3 x 8 matrix capable of holding thresholds in kWh for controlling Block Tariffs.
2231
5.7.4.50
2232
A 1 x 48 matrix containing prices for Time-of-use Pricing.
2233
5.7.5
2234
Describes data used by the functions of ESME for output of information.
2235
5.7.5.1
2236
2237
2238
The debt resulting from the collection of Standing Charge [INFO](5.7.4.42) and / or timebased debt when Emergency Credit is in use as configured by Suspend Debt
Emergency(4.6.4.28), when operating in Prepayment Mode.
Tariff Threshold Matrix [INFO]
Tariff TOU Price Matrix [INFO]
Operational data
Version 1.59
Accumulated Debt Register [INFO]
18 November 2015
Page 56
DRAFT
SMETS
2239
5.7.5.2
2240
The register recording the cumulative Active Energy Exported.
2241
5.7.5.3
2242
The register recording the cumulative Active Energy Imported.
2243
5.7.5.4
2244
The import of Active Power measured by ESME.
2245
5.7.5.5
2246
The Price currently active.
2247
5.7.5.6
2248
2249
2250
2251
A log capable of storing one hundred UTC date and time stamped entries of events related
to Auxiliary Load Control Switch(es) or HAN Connected Auxiliary Load Control Switch(es)
arranged as a circular buffer such that when full, further writes shall cause the oldest entry to
be overwritten.
2252
5.7.5.7
2253
2254
The number of times the average RMS voltage, as calculated in Section 5.5.12.1, has been
above the Average RMS Over Voltage Threshold(5.7.4.4) since last reset.
2255
5.7.5.8
2256
2257
The number of times the average RMS voltage, as calculated in Section 5.5.12.1, has been
below the Average RMS Under Voltage Threshold(5.7.4.5) since last reset.
2258
5.7.5.9
2259
2260
2261
2262
A log capable of storing 4320 entries (including the UTC date and time at the end of the
period to which the value relates) comprising the averaged RMS voltage for each Average
RMS Voltage Measurement Period(5.7.4.6) arranged as a circular buffer such that when full,
further writes shall cause the oldest entry to be overwritten.
2263
5.7.5.10
2264
A log capable of storing the following UTC date and time stamped entries:
2265
2266
2267
2268
2269
2270
2271
2272
i.
Active Export Register [INFO]
Active Import Register [INFO]
Active Power Import [INFO]
Active Tariff Price [INFO]
Auxiliary Load Control Switch Event Log
Average RMS Over Voltage Counter
Average RMS Under Voltage Counter
Average RMS Voltage Profile Data Log
Billing Data Log
twelve entries comprising Tariff TOU Register Matrix [INFO](5.7.5.34), Tariff TOU
Block Register Matrix(5.7.5.35), the Active Import Register [INFO](5.7.5.3);
and where in Prepayment mode:
ii.
iii.
iv.
five entries comprising the value of prepayment credits;
ten entries comprising the value of payment-based debt payments [INFO]; and
twelve entries comprising Meter Balance [INFO](5.7.5.22), Emergency Credit
Balance [INFO](5.7.5.15), Accumulated Debt Register [INFO](5.7.5.1), Payment
Debt Register [INFO](5.7.5.23) and Time Debt Registers [1 … 2] [INFO](5.7.5.36),
2273
2274
each of (i) to (iv) arranged as a circular buffer such that when full, further writes shall cause
the oldest entry to be overwritten.
2275
5.7.5.11
2276
2277
The indicative cost in Currency Units of maintaining the Active Power Import for an hour at
the Price(s) currently active.
2278
5.7.5.12
2279
A store capable of holding the following values:
Version 1.59
Cost of Instantaneous Active Power Import
Cumulative and Historical Value Store [INFO]
18 November 2015
Page 57
DRAFT
2280
2281
2282
2283
2284
2285
i.
ii.
iii.
SMETS
nine Days of Consumption comprising the current Day and the prior eight Days, in
kWh and Currency Units;
six Weeks of Consumption comprising the current Week and the prior five Weeks, in
kWh and Currency Units; and
fourteen months of Consumption comprising the current month and the prior thirteen
months, in kWh and Currency Units.
2286
5.7.5.13
2287
2288
2289
2290
2291
A log capable of storing thirty one UTC date and time stamped entries of the Tariff TOU
Register Matrix [INFO](5.7.5.34), the Tariff TOU Block Register Matrix(5.7.5.35), the Active
Import Register [INFO](5.7.5.3) and the Active Export Register [INFO](5.7.5.2) arranged as a
circular buffer such that when full, further writes shall cause the oldest entry to be
overwritten.
2292
5.7.5.14
2293
2294
A log capable of storing 731 date stamped entries of Consumption arranged as a circular
buffer such that when full, further writes shall cause the oldest entry to be overwritten.
2295
5.7.5.15
2296
2297
The amount of Emergency Credit available to the Consumer after it has been activated by
the Consumer.
2298
5.7.5.16
2299
2300
2301
A log capable of storing one hundred UTC date and time stamped entries of non-security
related information for diagnosis and auditing arranged as a circular buffer such that when
full, further writes shall cause the oldest entry to be overwritten.
2302
5.7.5.17
2303
The active version of Firmware of ESME.
2304
5.7.5.18
2305
2306
The number of times the Active Power Import [INFO](5.7.5.4) has exceeded, for the Load
Limit Period(5.7.4.19), the Load Limit Power Threshold(5.7.4.20) since last cleared.
2307
5.7.5.19
2308
2309
2310
2311
2312
2313
A store capable of holding the largest average value of Active Power Import [INFO](5.7.5.4)
recorded in any 30 minute period (commencing at the start of minutes 00 and 30 in each
hour and including the UTC date and time at the end of the 30 minute period to which the
data relates) since the value was last reset (as set out in Section 5.6.3.26), together with the
UTC date and time when the value was last reset, arranged such that the recording of a
larger value shall cause the previous entry to be overwritten.
2314
5.7.5.20
2315
2316
2317
2318
2319
2320
2321
A store capable of holding the largest average value of Active Power Import [INFO](5.7.5.4)
recorded in any 30 minute period (commencing at the start of minutes 00 and 30 in each
hour) within the time period specified in Maximum Demand Configurable Time
Period(5.7.4.26) (including the UTC date and time at the end of the 30 minute period to
which the data relates) since the value was last reset (as set out in Section 5.6.3.28),
together with the UTC date and time when the value was last reset, arranged such that the
recording of a larger value shall cause the previous entry to be overwritten.
2322
5.7.5.21
2323
2324
2325
A store capable of holding the largest average value of the Active Power Export recorded in
any 30 minute period (commencing at the start of minutes 00 and 30 in each hour and
including the UTC date and time at the end of the 30 minute period to which the data relates)
Version 1.59
Daily Read Log
Daily Consumption Log [INFO]
Emergency Credit Balance [INFO]
Event Log
Firmware Version
Load Limit Counter
Maximum Demand Active Power Import Value
Maximum Demand (Configurable Time) Active Power Import Value
Maximum Demand Active Power Export Value
18 November 2015
Page 58
DRAFT
SMETS
2326
2327
2328
since the value was last reset (as set out in Section 5.6.3.27), together with the UTC date
and time when the value was last reset, arranged such that the recording of a larger value
shall cause the previous entry to be overwritten.
2329
5.7.5.22
2330
2331
2332
2333
2334
The amount of money in Currency Units as determined by ESME. If operating in Prepayment
Mode, the Meter Balance represents ESME’s determination of the amount of credit available
to the Consumer (excluding any Emergency Credit Balance [INFO](5.7.5.15)). If operating in
Credit Mode, it represents ESME’s determination of the amount of money due from the
Consumer since the Meter Balance was last reset.
2335
5.7.5.23
2336
2337
A Debt Register recording debt to be recovered as a percentage of payment when using
Payment-based Debt Recovery in Prepayment Mode.
2338
5.7.5.24
2339
An indication of the Active Power level, being low, medium or high.
2340
5.7.5.25
2341
2342
2343
A log capable of storing one hundred UTC date and time stamped entries of non-security
related information for diagnosis and auditing arranged as a circular buffer such that when
full, further writes shall cause the oldest entry to be overwritten.
2344
5.7.5.26
2345
2346
2347
2348
2349
A log capable of storing thirty one UTC date and time stamped entries of Meter Balance
[INFO](5.7.5.22), Emergency Credit Balance [INFO](5.7.5.15), Accumulated Debt Register
[INFO](5.7.5.1), Payment Debt Register [INFO](5.7.5.23) and Time Debt Registers [1 … 2]
[INFO](5.7.5.36) arranged as a circular buffer such that when full, further writes shall cause
the oldest entry to be overwritten.
2350
5.7.5.27
2351
2352
2353
2354
A log capable of storing UTC date and time-stamped half hourly data (the amount of energy
Imported or Exported in a half hour period) arranged as a circular buffer such that when full,
further writes shall cause the oldest entry to be overwritten. The log shall be capable of
storing:
2355
2356
2357
2358
i.
ii.
iii.
iv.
Meter Balance [INFO]
Payment Debt Register [INFO]
Power Threshold Status [INFO]
Power Event Log
Prepayment Daily Read Log
Profile Data Log [INFO]
13 months of Consumption;
3 months of Active Energy Exported;
3 months of Reactive Energy Imported; and
3 months of Reactive Energy Exported.
2359
5.7.5.28
2360
2361
2362
2363
The product of the Randomised Offset Limit(5.7.4.33) and the Randomised Offset
Number(5.7.1.5) rounded to the nearest second. This value is used to delay the Tariff
Switching Table times, the Auxiliary Load Control Switch switching times, and HAN
Connected Auxiliary Load Control Switch switching times.
2364
5.7.5.29
2365
The register recording the cumulative Reactive Energy Exported.
2366
5.7.5.30
2367
The register recording the cumulative Reactive Energy Imported.
Version 1.59
Randomised Offset [INFO]
Reactive Export Register
Reactive Import Register
18 November 2015
Page 59
DRAFT
SMETS
2368
5.7.5.31
2369
2370
2371
A log capable of storing one hundred UTC date and time stamped entries of security related
information for diagnosis and auditing arranged as a circular buffer such that when full,
further writes shall cause the oldest entry to be overwritten.
2372
5.7.5.32
2373
The state of the Supply being Enabled, Disabled or Armed.
2374
5.7.5.33
2375
A 4 x 8 matrix for storing Block Counters for Block Pricing.
2376
5.7.5.34
2377
A 1 x 48 matrix for storing Tariff Registers for Time-of-use Pricing.
2378
5.7.5.35
2379
A 4 x 8 matrix for storing Tariff Registers for Time-of-use with Block Pricing.
2380
5.7.5.36
2381
2382
Two Debt Registers recording independent debts to be recovered over time when operating
Time-based Debt Recovery in Prepayment Mode.
Version 1.59
Security Log
Supply State [INFO]
Tariff Block Counter Matrix [INFO]
Tariff TOU Register Matrix [INFO]
Tariff TOU Block Register Matrix
Time Debt Registers [1 … 2] [INFO]
18 November 2015
Page 60
DRAFT
SMETS
2384
Part B - Twin Element Electricity Metering
Equipment
2385
5.8 Overview
2386
In this Part B ESME shall mean Twin Element Electricity Metering Equipment.
2387
2388
ESME shall comply with the requirements of Part A save as set out in the remainder of this
Part B.
2389
5.9 SMETS Testing and Certification Requirements
2390
5.9.1
2391
2392
ESME shall have been tested to ensure that it meets the requirements described in this
Section 5, and evidence must be available to confirm such testing and conformance.
2393
2394
5.9.2
2395
2396
ESME shall meet the requirements described in the Great Britain Companion Specifications
v0.8.1.
2397
ESME shall have been certified:
2383
2398
2399
2400
2401
2402
2403
i.
ii.
Conformance with the SMETS
Conformance with the Great Britain Companion
Specifications
by the ZigBee Alliance as compliant with the ZigBee SEP v1.2 requirements
described in the current version of the Great Britain Companion Specifications
meaning v0.8.2 or later as published on the SECAS website; and
by the DLMS User Association as compliant with the DLMS COSEM requirements
described in the current version of the Great Britain Companion Specifications
meaning v0.8.2 or later as published on the SECAS website.
2404
2405
5.9.3
2406
2407
2408
ESME shall meet the requirements described in the current version of the Commercial
Product Assurance Security Characteristic for Electricity Smart Metering Equipment meaning
v1.2 or later as published on CESG’s Website.
2409
2410
2411
ESME shall be certified by CESG as compliant with the current version of the Commercial
Product Assurance Security Characteristic for Electricity Smart Metering Equipment meaning
v1.2 or later as published on CESG’s Website.
2412
5.10 Physical Requirements
2413
Physical Requirements(5.4) in Part A shall not apply to ESME.
2414
ESME shall as a minimum include the following components:
2415
2416
2417
2418
2419
2420
2421
2422
2423
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
Conformance with the Commercial Product Assurance
Security Characteristic for GB Smart Metering
a Clock;
a Data Store;
an Electricity Meter containing two measuring elements;
a HAN Interface;
a Load Switch;
a Random Number Generator;
a User Interface; and
where installed with a Communications Hub provided by the Data and
Communications Company, a Communications Hub Physical Interface (this may
Version 1.59
18 November 2015
Page 61
DRAFT
2424
2425
SMETS
comprise a Communications Hub Physical Interface forming part of GSME where
present at the time of installation in the Premises).
2426
2427
2428
2429
The Communications Hub Physical Interface shall as a minimum include a physical interface
that meets the requirements defined by the Data and Communications Company at the time
of installation (available on the Data and Communications Company’s website) and includes
provision for a DC power supply to the Communications Hub.
2430
2431
2432
2433
ESME shall be mains powered and be capable of performing the minimum functional,
interface and data requirements set out in Sections 5.11, 5.12 and 5.13 respectively
operating at a nominal voltage of 230VAC without consuming more than an average of 4
watts of electricity under normal operating conditions.
2434
2435
ESME shall be capable of automatically resuming operation after a power failure in its
operating state prior to such failure.
2436
ESME shall:
2437
2438
2439
2440
2441
2442
2443
ix.
x.
permanently display the ESME Identifier(5.7.1.1) on the ESME; and
have a Secure Perimeter.
The HAN Interface of ESME shall be capable of joining a ZigBee SEP v1.2 Smart Metering
Home Area Network which:
xi.
xii.
operates within the 2400 – 2483.5 MHz harmonised frequency band; and
supports the Communications Links described in Sections 5.6.3, 5.6.4., 5.12.1 and
5.12.2.
2444
2445
On joining a ZigBee SEP v1.2 Smart Metering Home Area Network ESME shall be capable
of generating and sending an Alert to that effect via its HAN Interface.
2446
2447
2448
ESME shall be designed taking all reasonable steps so as to prevent Unauthorised Physical
Access and Unauthorised communications through its Secure Perimeter that could
compromise the Confidentiality and / or Data Integrity of:
2449
2450
2451
2452
2453
2454
2455
xiii.
xiv.
xv.
xvi.
xvii.
xviii.
xix.
2456
stored or executing on ESME.
2457
2458
2459
ESME shall be capable of detecting any attempt at Unauthorised Physical Access through
its Secure Perimeter that could compromise such Confidentiality and / or Data Integrity and
on such detection shall be capable of:
2460
2461
xx.
Personal Data;
Consumption data used for billing;
Security Credentials;
Random Number Generator;
Cryptographic Algorithms;
the Electricity Meter; and
Firmware and data essential for ensuring its integrity,
providing evidence of such an attempt through the use of tamper evident coatings or
seals,
2462
and where reasonably practicable:
2463
2464
2465
2466
2467
2468
2469
xxi.
xxii.
xxiii.
generating an entry to that effect in the Security Log(5.7.5.31);
generating and sending an Alert to that effect via its HAN Interface; and
where the Supply Tamper State(5.7.4.44) is configured to require Locking,
establishing a state whereby the Supply is Disabled and can only be Enabled or
Armed in response to a Command to Arm the Supply (as described in Section
5.6.3.7) or Enable the Supply (as described in Section 5.6.3.12), and setting the
Supply State [INFO](5.7.5.32) to Locked.
Version 1.59
18 November 2015
Page 62
DRAFT
SMETS
2470
5.11 Functional Requirements
2471
5.11.1 Display of information
2472
Display of information(5.5.4) in Part A shall not apply to ESME.
2473
2474
ESME shall be capable of displaying the following up to date information on its User
Interface:
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
xii.
xiii.
xiv.
xv.
xvi.
xvii.
xviii.
xix.
xx.
xxi.
xxii.
the Payment Mode [INFO](5.7.4.31) currently in operation, being Prepayment Mode
or Credit Mode [PIN];
the Tariff TOU Register Matrix [INFO](5.7.5.34), the Secondary Tariff TOU Register
Matrix [INFO](5.13.2.10), Tariff TOU Block Register Matrix(5.7.5.35) and the Tariff
Block Counter Matrix [INFO](5.7.5.33);
the Active Import Register [INFO](5.7.5.3);
the Secondary Active Import Register [INFO](5.13.2.11);
the Meter Balance [INFO](5.7.5.22) [PIN];
the Debt to Clear (calculated as set out in Section 5.11.2.2) [PIN];
the Customer Identification Number [INFO](5.7.4.10) [PIN];
whether Emergency Credit is available for activation [PIN];
whether ESME has suspended the Disablement of Supply during a period defined in
the Non-Disablement Calendar [INFO](5.7.4.30) (as set out in Section 5.11.2.2)
[PIN];
the Emergency Credit Balance [INFO](5.7.5.15) where Emergency Credit is
activated [PIN];
any low credit condition [PIN];
the Supply State [INFO](5.7.5.32);
any time-based debts and Time-based Debt Recovery rates [PIN];
any payment-based debt [PIN];
any accumulated debt recorded in the Accumulated Debt Register [INFO](5.7.5.1);
any Standing Charge [INFO](5.7.4.42) [PIN];
the Meter Point Administration Numbers (MPAN) [INFO]( 5.7.4.28) [PIN];
the Local Time;
the Contact Details [INFO](5.7.4.8);
the Primary Active Tariff Price [INFO](5.13.2.6) [PIN];
the Secondary Active Tariff Price [INFO](5.13.2.9) [PIN]; and
the Event Log(5.7.5.16) and the Power Event Log(5.7.5.25) (with the exception of
any Personal Data).
2504
2505
ESME shall be capable of displaying the Security Log(5.7.5.31) on its User Interface
following physical access through the Secure Perimeter of ESME.
2506
2507
ESME shall be capable of displaying Currency Units in GB Pounds and European Central
Bank Euro.
2508
5.11.2 Payment Mode
2509
Payment Mode(5.5.7) in Part A shall not apply to ESME.
2510
2511
ESME shall be capable of operating in Credit Mode and Prepayment Mode and of being
remotely switched from one mode to the other.
2512
5.11.2.1
2513
2514
ESME, when operating in Credit Mode, shall be capable of maintaining a calculation of the
Meter Balance [INFO](5.7.5.22) based on:
2515
2516
i.
Credit Mode
the Consumption in the Tariff TOU Register Matrix [INFO](5.7.5.34) and the Prices
in the Tariff TOU Price Matrix [INFO](5.7.4.50) and if operating Time-of-use with
Version 1.59
18 November 2015
Page 63
DRAFT
2517
2518
2519
2520
2521
ii.
iii.
SMETS
Block Pricing, the Consumption in the Tariff TOU Block Register Matrix(5.7.5.35)
and the Prices in the Tariff Block Price Matrix [INFO](5.7.4.47);
the Consumption in the Secondary Tariff TOU Register Matrix [INFO](5.13.2.10) and
the Prices in Secondary Tariff TOU Price Matrix [INFO](5.13.1.1); and
the Standing Charge [INFO](5.7.4.42).
2522
5.11.2.2
2523
2524
2525
2526
ESME shall be capable of operating in Prepayment Mode, including during periods of loss of
its Communications Link via its HAN Interface, and maintaining a balance of credit and
reflecting any reduction in credit based on Consumption, standing charge and Time-based
Debt Recovery.
2527
2528
2529
ESME shall be capable of adding credit to the Meter Balance [INFO](5.7.5.22) (as set out in
Sections 5.6.2.2 and 5.6.3.3) and reducing the amount of credit in the Meter Balance
[INFO](5.7.5.22).
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
ESME shall be capable of making Emergency Credit available to the Consumer (by means
of the Emergency Credit Balance [INFO](5.7.5.15) if the Meter Balance [INFO](5.7.5.22) is
below the Emergency Credit Threshold [INFO](5.7.4.17)). ESME shall be capable of
displaying the availability of Emergency Credit on its User Interface and of generating and
sending an Alert indicating the availability of Emergency Credit via its HAN Interface. The
amount of Emergency Credit made available to the Consumer shall be equal to the
Emergency Credit Limit [INFO](5.7.4.16). ESME shall be capable of reducing the amount of
credit in the Emergency Credit Balance [INFO](5.7.5.15) where Emergency Credit is
activated by the Consumer (as set out in Sections 5.6.2.1 and 5.6.3.1) and the Meter
Balance [INFO](5.7.5.22) is exhausted. Any Emergency Credit used shall be repaid when
credit is added to ESME (as set out in Sections 5.6.2.2 and 5.6.3.3).
2541
2542
2543
ESME shall be capable of reducing the Meter Balance [INFO](5.7.5.22) until it reaches the
Disablement Threshold [INFO](5.7.4.15) followed by reducing the Emergency Credit Balance
[INFO](5.7.5.15), where activated, until exhausted on the basis of:
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
i.
ii.
iii.
iv.
Prepayment Mode
the Consumption in the Tariff TOU Register Matrix [INFO](5.7.5.34) and the Prices
in the Tariff TOU Price Matrix [INFO](5.7.4.50), and if operating Time-of-use with
Block Pricing the Consumption in the Tariff TOU Block Register Matrix(5.7.5.35) and
the Prices in the Tariff Block Price Matrix [INFO](5.7.4.47);
the Consumption in the Secondary Tariff TOU Register Matrix [INFO](5.13.2.10) and
the Prices in the Secondary Tariff TOU Price Matrix [INFO](5.13.1.1);
the Standing Charge [INFO](5.7.4.42); and
the recovery of debt hourly and daily through each of the Time Debt Registers [1 …
2] [INFO](5.7.5.36) at rates defined by the Debt Recovery Rates [1 … 2]
[INFO](5.7.4.12).
2554
2555
2556
2557
Where configured by Suspend Debt Emergency(5.7.4.46) to do so and when Emergency
Credit is in use, ESME shall be capable suspending the application of (iii) and (iv) to the
Emergency Credit Balance [INFO](5.7.5.15), and of accumulating (iii) and (iv) in the
Accumulated Debt Register [INFO](5.7.5.1).
2558
2559
ESME shall be capable of recording debt recovered, or accumulated in the Accumulated
Debt Register [INFO](5.7.5.1), in the Billing Data Log(5.13.2.3).
2560
2561
ESME shall be capable of monitoring the Meter Balance [INFO](5.7.5.22) and where
activated the Emergency Credit Balance [INFO](5.7.5.15) and:
2562
2563
2564
2565
v.
if the combined credit of the Meter Balance [INFO](5.7.5.22) and Emergency Credit
Balance [INFO](5.7.5.15) falls below the Low Credit Threshold [INFO](5.7.4.23),
displaying an Alert to that effect on its User Interface and generating and sending an
Alert to that effect via its HAN Interface;
Version 1.59
18 November 2015
Page 64
DRAFT
2566
2567
2568
2569
2570
vi.
vii.
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
SMETS
if the combined credit of the Meter Balance [INFO](5.7.5.22) and Emergency Credit
Balance [INFO](5.7.5.15) falls below the Disablement Threshold [INFO](5.7.4.15),
Disabling the Supply, displaying an Alert to that effect on its User Interface and
generating and sending an Alert to that effect via its HAN Interface;
where the Supply is Disabled (as set out in (vi) above):
a) where configured by Suspend Debt Disabled(5.7.4.45) not to suspend Timebased Debt Recovery, continuing to apply (iii) and (iv) above to reduce the
Meter Balance [INFO](5.7.5.22);
b) where configured by Suspend Debt Disabled(5.7.4.45) to suspend Time-based
Debt Recovery, suspending the application of (iv) above to the Meter Balance
[INFO](5.7.5.22), and continuing to apply (iii) above to reduce the Meter
Balance [INFO](5.7.5.22); and
viii.
if the Supply is Enabled, suspending the Disablement of Supply (as set out in (vi)
above) during periods defined in the Non-Disablement Calendar [INFO](5.7.4.30),
continuing to reduce the Meter Balance [INFO](5.7.5.22) on the basis of (i) to (iv)
above, displaying on its User Interface an indication that the combined Meter
Balance [INFO](5.7.5.22) and Emergency Credit Balance [INFO](5.7.5.15) is below
the Disablement Threshold [INFO](5.7.4.15) and that Disablement of Supply due to
insufficient credit has been suspended, and generating and sending an Alert that
Disablement of Supply due to insufficient credit has been suspended via its HAN
Interface.
If the Meter Balance [INFO](5.7.5.22) is equal to or below the Disablement Threshold
[INFO](5.7.4.15) ESME shall be capable of maintaining a calculation of the Debt to Clear
based on:
ix.
x.
xi.
xii.
the difference between the Meter Balance [INFO](5.7.5.22) and the Disablement
Threshold [INFO](5.7.4.15);
the amount of debt accumulated in the Accumulated Debt Register [INFO](5.7.5.1)
the amount of Emergency Credit activated and used by the Consumer; and
the payment-based debt to be collected based on (ix), (x) and (xi) (as defined by
Debt Recovery per Payment [INFO](5.7.4.11) taking account of the amount
remaining in the Payment Debt Register [INFO](5.7.5.23), the payment-based debt
payments in the Billing Data Log(5.13.2.3) and the Debt Recovery Rate Cap
[INFO](5.7.4.13).
If the amount of debt to be collected from a Debt Register through Time-based Debt
Recovery, Payment-based Debt Recovery or an Adjust Debt Command is greater than the
amount in that Time Debt Register then ESME shall be capable of:
xiii.
xiv.
adding the difference to the Meter Balance [INFO](5.7.5.22); and
setting the amount in that Debt Register to zero.
2604
5.11.3 Pricing
2605
Pricing(5.5.8) in Part A shall not apply to ESME.
2606
ESME shall be capable of applying Time-of-use Pricing and Time-of-use with Block Pricing.
2607
2608
When switching between Time-of-use Bands and Tariff Registers as set out in this section
ESME shall be capable of applying the Randomised Offset [INFO](5.7.5.28).
2609
2610
ESME shall be capable of maintaining the Primary Active Tariff Price [INFO](5.13.2.6) and
the Secondary Active Tariff Price [INFO](5.13.2.9).
Version 1.59
18 November 2015
Page 65
DRAFT
SMETS
2611
5.11.3.1
2612
2613
2614
ESME shall be capable of recording Consumption via the primary measuring element of its
Electricity Meter according to Time-of-use Bands in one of forty-eight Tariff Registers in the
Tariff TOU Register Matrix [INFO](5.7.5.34).
2615
2616
2617
ESME shall be capable of recording Consumption via the secondary measuring element of
its Electricity Meter according to Time-of-use Bands in one of four Tariff Registers in the
Secondary Tariff TOU Register Matrix [INFO](5.13.2.10).
2618
2619
2620
ESME shall be capable of switching between different Tariff Registers once every 30
minutes. The switching between Time-of-use Bands and thus Tariff Registers shall be based
on the switching rules defined in the Tariff Switching Table(5.13.1.2).
2621
5.11.3.2
2622
2623
2624
ESME shall be capable of recording Consumption via the primary measuring element of its
Electricity Meter in one of four Block Registers for each of eight Time-of-use Bands in the
Tariff TOU Block Register Matrix(5.7.5.35).
2625
2626
2627
The switching between Time-of-use Bands and sets of Block Registers shall be based on
the switching rules set out in the Tariff Switching Table [INFO](5.13.1.2). ESME shall be
capable of switching between Time-of-use Bands once every 30 minutes.
2628
2629
2630
2631
Switching between the Block Registers within each Time-of-use Band shall be based on
Consumption via the primary measuring element of its Electricity Meter accumulated in the
Tariff Block Counter Matrix [INFO](5.7.5.33) and Consumption thresholds in the Tariff
Threshold Matrix [INFO](5.7.4.49).
2632
2633
2634
2635
2636
ESME shall also be capable of accumulating Consumption via the primary measuring
element of its Electricity Meter in one of four Block Counters in the Tariff Block Counter
Matrix [INFO](5.7.5.33) for each of the eight Time-of-use Bands. ESME shall be capable of
switching between Block Counters according to the Consumption thresholds in the Tariff
Threshold Matrix [INFO](5.7.4.49).
2637
2638
2639
ESME shall be capable of resetting the counters in the Tariff Block Counter Matrix
[INFO](5.7.5.33) once per Day and in accordance with the timetable set out in the Billing
Calendar(5.7.4.7).
2640
5.11.4 Recording
2641
Recording(5.5.9) in Part A shall not apply to ESME.
2642
5.11.4.1
2643
ESME shall be capable of recording:
2644
2645
2646
2647
i.
ii.
Time-of-use Pricing
Time-of-use with Block Pricing
Active Energy Imported
cumulative Active Energy Imported via the primary measuring element of its
Electricity Meter in the Active Import Register [INFO](5.7.5.3); and
cumulative Active Energy Imported via the secondary measuring element of its
Electricity Meter in the Secondary Active Import Register [INFO](5.13.2.11).
2648
5.11.4.2
2649
2650
ESME shall be capable of recording cumulative Active Energy Exported via the primary
measuring element of its Electricity Meter in the Active Export Register [INFO](5.7.5.2).
2651
5.11.4.3
2652
2653
In accordance with the timetable set out in the Billing Calendar(5.7.4.7) ESME shall be
capable of taking a UTC date and time stamped copy of:
2654
2655
i.
ii.
Active Energy Exported
Billing data
the Tariff TOU Register Matrix [INFO](5.7.5.34);
the Secondary Tariff TOU Register Matrix [INFO](5.13.2.10);
Version 1.59
18 November 2015
Page 66
DRAFT
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
iii.
iv.
v.
SMETS
the Tariff TOU Block Register Matrix(5.7.5.35);
the Active Import Register [INFO](5.7.5.3); and
the Secondary Active Import Register [INFO](5.13.2.11),
and where in Prepayment mode:
vi.
vii.
viii.
ix.
x.
the Meter Balance [INFO](5.7.5.22);
the Emergency Credit Balance [INFO](5.7.5.15);
the Payment Debt Register [INFO](5.7.5.23);
the Time Debt Registers [1 … 2] [INFO](5.7.5.36); and
the Accumulated Debt Register [INFO](5.7.5.1),
in the Billing Data Log(5.13.2.3), and:
xi.
xii.
generating and sending an Alert via its HAN Interface containing the most recent
entries in the Billing Data Log(5.13.2.3) of (i) to (v) above; and
if operating in Credit Mode immediately resetting the Meter Balance
[INFO](5.7.5.22).
2670
5.11.4.4
2671
2672
ESME shall be capable of calculating Consumption via the primary and secondary
measuring elements of its Electricity Meter and recording:
2673
i.
Consumption Data
to the Cumulative and Historical Value Store [INFO](5.7.5.12) in kWh:
2674
2675
2676
2677
2678
2679
a)
b)
c)
d)
e)
f)
Consumption on the Day up to the Local Time;
Consumption on each of the eight Days prior to such Day;
Consumption in the Week in which the calculation is performed;
Consumption in each of the five Weeks prior to such Week;
Consumption in the month in which the calculation is performed; and
Consumption in the thirteen months prior to such month.
2680
2681
ii.
2682
5.11.4.5
2683
2684
ESME shall be capable of calculating and recording to the Cumulative and Historical Value
Store [INFO](5.7.5.12) the cost of:
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
i.
ii.
iii.
iv.
v.
vi.
the Daily Consumption Log [INFO](5.7.5.14) in kWh the Consumption on each of the
731 Days prior to the current Day.
Cost of Consumption Data
Consumption on the Day up to the Local Time;
Consumption on each of the eight Days prior to such Day;
Consumption in the Week in which the calculation is performed;
Consumption in each of the five Weeks prior to such Week;
Consumption in the month in which the calculation is performed; and
Consumption in the thirteen months prior to such month.
ESME shall be capable of calculating cost of Consumption as above on the basis of:
vii.
viii.
ix.
the Consumption in the Tariff TOU Register Matrix [INFO](5.7.5.34) and the Prices
in the Tariff TOU Price Matrix [INFO](5.7.4.50), and if operating Time-of-use with
Block Pricing the Consumption in the Tariff TOU Block Register Matrix(5.7.5.35) and
the Prices in the Tariff Block Price Matrix [INFO](5.7.4.47);
the Consumption in the Secondary Tariff TOU Register Matrix [INFO](5.13.2.10) and
the Prices in the Secondary Tariff TOU Price Matrix [INFO](5.13.1.1); and
the Standing Charge [INFO](5.7.4.42).
2699
5.11.4.6
2700
2701
ESME shall be capable of calculating and recording the Cost of Instantaneous Active Power
Import(5.7.5.11) on the basis of:
2702
i.
Cost of Instantaneous Consumption
the Primary Active Power Import [INFO](5.13.2.5);
Version 1.59
18 November 2015
Page 67
DRAFT
2703
2704
2705
ii.
iii.
iv.
SMETS
the Primary Active Tariff Price [INFO](5.13.2.6);
the Secondary Active Power Import [INFO](5.13.2.8); and
the Secondary Active Tariff Price [INFO](5.13.2.9).
2706
5.11.4.7
2707
2708
2709
2710
2711
2712
ESME shall be capable of taking a copy of and storing the Tariff TOU Register Matrix
[INFO](5.7.5.34), the Secondary Tariff TOU Register Matrix [INFO](5.13.2.10), the Tariff
TOU Block Register Matrix(5.7.5.35), the Active Import Register [INFO](5.7.5.3), the
Secondary Active Import Register [INFO](5.13.2.11) and the Active Export Register
[INFO](5.7.5.2), together with a UTC date and time stamp in the Daily Read Log(5.13.2.4)
every day at midnight UTC.
2713
2714
2715
2716
If operating in Prepayment Mode ESME shall be capable of recording the Meter Balance
[INFO](5.7.5.22), Emergency Credit Balance [INFO](5.7.5.15), Accumulated Debt Register
[INFO](5.7.5.1), Payment Debt Register [INFO](5.7.5.23) and Time Debt Registers [1 … 2]
[INFO](5.7.5.36) in the Prepayment Daily Read Log(5.7.5.26) every day at midnight UTC.
2717
5.11.4.8
2718
2719
2720
2721
ESME shall be capable of recording in each 30 minute period (commencing at the start of
minutes 00 and 30 in each hour), the following information (including the UTC date and time
at the end of the 30 minute period to which the data relates) in the Profile Data Log
[INFO](5.13.2.7):
2722
2723
2724
2725
2726
2727
2728
i.
ii.
iii.
iv.
v.
Daily read data
Half hour profile data
Active Energy Imported via the primary measuring element of its Electricity Meter;
Active Energy Exported via the primary measuring element of its Electricity Meter;
Reactive Energy Imported via the primary and secondary measuring elements of its
Electricity Meter;
Reactive Energy Exported via the primary measuring element of its Electricity Meter;
and
Active Energy Imported via the secondary measuring element of its Electricity Meter.
2729
5.11.4.9
2730
2731
2732
ESME shall be capable of calculating the average value of Active Power Import
[INFO](5.13.2.1) over each 30 minute period (commencing at the start of minutes 00 and 30
in each hour) and recording:
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
i.
ii.
Maximum Demand Import data
to the Maximum Demand Active Power Import Value(5.7.5.19), the maximum value
so calculated since the Maximum Demand Active Power Import Value(5.7.5.19) was
last reset (as set out in Section 5.6.3.26) including the UTC date and time at the end
of the 30 minute period to which the data relates; and
to the Maximum Demand (Configurable Time) Active Power Import Value(5.7.5.20)
the maximum value so calculated in any 30 minute period (commencing at the start
of minutes 00 and 30 in each hour) within the time period specified in Maximum
Demand Configurable Time Period(5.7.4.26) (including the UTC date and time at the
end of the 30 minute period to which the data relates) since the Maximum Demand
(Configurable Time) Active Power Import Value(5.7.5.20) was last reset (as set out
in Section 5.6.3.28).
2744
5.11.4.10 Maximum Demand Export data
2745
2746
2747
2748
2749
2750
ESME shall be capable of calculating the average value of Active Power Export over each
30 minute period (commencing at the start of minutes 00 and 30 in each hour) and recording
to the Maximum Demand Active Power Export Value(5.7.5.21) the maximum value so
calculated since the Maximum Demand Active Power Export Value(5.7.5.21) was last reset
(as set out in Section 5.6.3.27) including the UTC date and time at the end of the 30 minute
period to which the data relates.
Version 1.59
18 November 2015
Page 68
DRAFT
SMETS
2751
5.11.4.11 Power Threshold Status
2752
2753
ESME shall be capable of comparing the Active Power Import [INFO](5.13.2.1) against
thresholds and:
2754
2755
2756
2757
2758
2759
2760
i.
ii.
iii.
if the Active Power Import [INFO](5.13.2.1) is equal to or lower than the Low Medium
Power Threshold [INFO](5.7.4.24), setting Power Threshold Status(5.7.5.24) to low;
if the Active Power Import [INFO](5.13.2.1) is higher than the Low Medium Power
Threshold [INFO](5.7.4.24) and equal to or lower than the Medium High Power
Threshold [INFO](5.7.4.29), setting Power Threshold Status(5.7.5.24) to medium;
and
otherwise, setting the Power Threshold Status(5.7.5.24) to high.
2761
5.11.4.12 Reactive Energy Imported
2762
2763
2764
ESME shall be capable of recording cumulative Reactive Energy Imported via the primary
and secondary measuring elements of its Electricity Meter in the Reactive Import
Register(5.7.5.30).
2765
5.11.4.13 Reactive Energy Exported
2766
2767
ESME shall be capable of recording cumulative Reactive Energy Exported via the primary
measuring element of its Electricity Meter in the Reactive Export Register(5.7.5.29).
2768
5.12 Interface Requirements
2769
5.12.1 HAN Interface information provision
2770
2771
Type 1 Devices and Type 2 Device information provision(5.6.1) in Part A shall not apply to
ESME.
2772
2773
2774
2775
2776
ESME shall be capable, immediately upon establishment of a Communications Link with
Type 1 Devices (as set out in Section 5.5.2.2) and Type 2 Devices (as set out in Section
5.5.2.3), of providing the Data annotated [INFO] in Sections 5.7.1, 5.7.4, 5.7.5, 5.13.1 and
5.13.2 to Type 1 Devices and Type 2 Devices (with timely updates of any changes to all
data).
2777
5.12.2 HAN Interface Commands
2778
5.12.2.1
2779
Set Payment Mode(5.6.3.34) in Part A shall not apply to ESME.
2780
2781
A Command to set the payment mode as either Prepayment Mode or Credit Mode and to
record the mode of operation in Payment Mode [INFO](5.7.4.31).
2782
2783
In executing the Command, ESME shall be capable of taking a UTC date and time stamped
copy of:
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
i.
ii.
iii.
iv.
v.
Set Payment Mode
the Tariff TOU Register Matrix [INFO](5.7.5.34);
the Secondary Tariff TOU Register Matrix [INFO](5.13.2.10);
the Tariff TOU Block Register Matrix(5.7.5.35);
the Active Import Register [INFO](5.7.5.3); and
the Secondary Active Import Register [INFO](5.13.2.11),
and unless in Credit Mode both before and after execution of the Command:
vi.
vii.
viii.
ix.
x.
the Meter Balance [INFO](5.7.5.22);
the Emergency Credit Balance [INFO](5.7.5.15);
the Payment Debt Register [INFO](5.7.5.23);
the Time Debt Registers [1 … 2] [INFO](5.7.5.36); and
the Accumulated Debt Register [INFO](5.7.5.1),
in the Billing Data Log(5.13.2.3).
Version 1.59
18 November 2015
Page 69
DRAFT
SMETS
2796
5.12.2.2
2797
Set Tariff(5.6.3.35) in Part A shall not apply to ESME.
2798
2799
2800
2801
A Command to accept new values for the Tariff TOU Price Matrix [INFO](5.7.4.50), the
Secondary Tariff TOU Price Matrix [INFO](5.13.1.1), the Tariff Block Price Matrix
[INFO](5.7.4.47), the Tariff Switching Table [INFO](5.13.1.2) and the Tariff Threshold Matrix
[INFO](5.7.4.49).
2802
2803
In executing the Command, ESME shall be capable of taking a UTC date and time stamped
copy of:
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
i.
ii.
iii.
iv.
v.
Set Tariff
the Tariff TOU Register Matrix [INFO](5.7.5.34);
the Secondary Tariff TOU Register Matrix [INFO](5.13.2.10);
the Tariff TOU Block Register Matrix(5.7.5.35);
the Active Import Register [INFO](5.7.5.3); and
the Secondary Active Import Register [INFO](5.13.2.11),
and where in Prepayment mode:
vi.
vii.
viii.
ix.
x.
the Meter Balance [INFO](5.7.5.22);
the Emergency Credit Balance [INFO](5.7.5.15);
the Payment Debt Register [INFO](5.7.5.23);
the Time Debt Registers [1 … 2] [INFO](5.7.5.36); and
the Accumulated Debt Register [INFO](5.7.5.1),
2815
in the Billing Data Log(5.13.2.3).
2816
5.13 Data Requirements
2817
5.13.1 Configuration Data
2818
5.13.1.1
2819
2820
A 1 x 4 matrix containing Prices for Time-of-use Pricing Tariffs relating to Supply via the
secondary measuring element of the Electricity Meter.
2821
5.13.1.2
2822
Tariff Switching Table(5.7.4.48) in Part A shall not apply to ESME.
2823
A set of rules for allocating:
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
i.
ii.
Secondary Tariff TOU Price Matrix [INFO]
Tariff Switching Table [INFO]
half-hourly Consumption via the primary measuring element of the Electricity Meter
to a Tariff Register in the Tariff TOU Register Matrix [INFO](5.7.5.34) if applying
Time-of-use Pricing, and in the Tariff TOU Block Register Matrix(5.7.5.35) if applying
Time-of-use with Block Pricing; and
half-hourly Consumption via the secondary measuring element of the Electricity
Meter to a Tariff Register in the Secondary Tariff TOU Register Matrix
[INFO](5.13.2.10).
The rules stored within the table shall specify which of 16 Day Profiles should be used to
allocate Consumption to Tariff Registers for Consumption via each of the primary and
secondary measuring elements of the Electricity Meter according to:
iii.
iv.
where the day is one of 50 Special Days, the Day Profile(s) specified for that
measuring element for that day; or
where the day is not a Special Day, the Day Profile(s) specified by the active
Season Profile and Week Profile for that measuring element for that day.
2838
2839
The Switching Table shall support four Season Profiles and four Week Profiles. The
Switching Table shall support up to 200 switching rules across all Day Profiles.
2840
All dates and times shall be specified as UTC.
Version 1.59
18 November 2015
Page 70
DRAFT
SMETS
2841
5.13.2 Operational Data
2842
5.13.2.1
2843
Active Power Import [INFO](5.7.5.4) in Part A shall not apply to ESME.
2844
The sum of:
2845
2846
2847
2848
i.
ii.
Active Power Import [INFO]
the Primary Active Power Import [INFO](5.13.2.5) on the primary measuring element
of the Electricity Meter; and
the Secondary Active Power Import [INFO](5.13.2.8) on the secondary measuring
element of the Electricity Meter.
2849
5.13.2.2
2850
Active Tariff Price [INFO](5.7.5.5) in Part A shall not apply to ESME.
2851
5.13.2.3
2852
Billing Data Log(5.7.5.10) in Part A shall not apply to ESME.
2853
A log capable of storing the following UTC date and time stamped entries:
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
i.
Active Tariff Price [INFO]
Billing Data Log
twelve entries comprising the Tariff TOU Register Matrix [INFO](5.7.5.34), the
Secondary Tariff TOU Register Matrix [INFO](5.13.2.10), the Tariff TOU Block
Register Matrix(5.7.5.35), the Active Import Register [INFO](5.7.5.3), the Secondary
Active Import Register [INFO](5.13.2.11);
and where in Prepayment mode:
ii.
iii.
iv.
five entries comprising the value of prepayment credits;
ten entries comprising the value of payment-based debt payments; and
twelve entries comprising Meter Balance [INFO](5.7.5.22), Emergency Credit
Balance [INFO](5.7.5.15), Accumulated Debt Register [INFO](5.7.5.1), Payment
Debt Register [INFO](5.7.5.23) and Time Debt Registers [1 … 2] [INFO](5.7.5.36),
2864
2865
each of (i) to (iv) arranged as a circular buffer such that when full, further writes shall cause
the oldest entry to be overwritten.
2866
5.13.2.4
2867
Daily Read Log(5.7.5.13) in Part A shall not apply to ESME.
2868
2869
2870
2871
2872
2873
A log capable of storing thirty one UTC date and time stamped entries of the Tariff TOU
Register Matrix [INFO](5.7.5.34), the Secondary Tariff TOU Register Matrix
[INFO](5.13.2.10), the Tariff TOU Block Register Matrix(5.7.5.35), the Active Import Register
[INFO](5.7.5.3), the Secondary Active Import Register [INFO](5.13.2.11) and the Active
Export Register [INFO](5.7.5.2) arranged as a circular buffer such that when full, further
writes shall cause the oldest entry to be overwritten.
2874
5.13.2.5
2875
2876
The import of Active Power measured via the primary measuring element of the Electricity
Meter.
2877
5.13.2.6
2878
2879
The Price currently active for Consumption via the primary measuring element of the
Electricity Meter.
2880
5.13.2.7
2881
Profile Data Log [INFO](5.7.5.27) in Part A shall not apply to ESME.
2882
2883
A log capable of storing UTC date and time-stamped half hourly data (the amount of energy
Imported or Exported in a half hour period) arranged as a circular buffer such that when full,
Version 1.59
Daily Read Log
Primary Active Power Import [INFO]
Primary Active Tariff Price [INFO]
Profile Data Log [INFO]
18 November 2015
Page 71
DRAFT
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
SMETS
further writes shall cause the oldest entry to be overwritten. The log shall be capable of
storing a minimum of:
i.
ii.
iii.
iv.
v.
13 months of Active Energy Imported via the primary measuring element of the
Electricity Meter;
13 months of Active Energy Imported via the secondary measuring element of the
Electricity Meter;
3 months of Active Energy Exported via the primary measuring element of the
Electricity Meter;
3 months of Reactive Energy Imported via the primary and secondary measuring
elements of the Electricity Meter; and
3 months of Reactive Energy Exported via the primary measuring element of the
Electricity Meter.
2896
5.13.2.8
2897
2898
The import of Active Power measured via the secondary measuring element of the Electricity
Meter.
2899
5.13.2.9
2900
2901
The Price currently active for Consumption via the secondary measuring element of the
Electricity Meter.
2902
5.13.2.10 Secondary Tariff TOU Register Matrix [INFO]
2903
2904
A 1 x 4 matrix for storing Tariff Registers for Time-of-use Pricing relating to Supply via the
secondary measuring element of the Electricity Meter.
2905
5.13.2.11 Secondary Active Import Register [INFO]
2906
2907
The register recording the cumulative Active Energy Imported via the secondary measuring
element of the Electricity Meter.
Version 1.59
Secondary Active Power Import [INFO]
Secondary Active Tariff Price [INFO]
18 November 2015
Page 72
DRAFT
SMETS
2909
Part C - Polyphase Electricity Metering
Equipment
2910
5.14 Overview
2911
In this Part C ESME shall mean Polyphase Electricity Metering Equipment.
2912
ESME shall meet the requirements of Part A save as set out in the remainder of this Part C.
2913
5.15 SMETS Testing and Certification Requirements
2914
5.15.1 Conformance with the SMETS
2915
2916
ESME shall have been tested to ensure that it meets the requirements described in this
Section 5, and evidence must be available to confirm such testing and conformance.
2917
2918
5.15.2 Conformance with the Great Britain Companion
Specifications
2919
2920
ESME shall meet the requirements described in the Great Britain Companion Specifications
v0.8.1.
2921
ESME shall have been certified:
2908
2922
2923
2924
2925
2926
2927
i.
ii.
by the ZigBee Alliance as compliant with the ZigBee SEP v1.2 requirements
described in the current version of the Great Britain Companion Specifications
meaning v0.8.2 or later as published on the SECAS website; and
by the DLMS User Association as compliant with the DLMS COSEM requirements
described in the current version of the Great Britain Companion Specifications
meaning v0.8.2 or later as published on the SECAS website.
2928
2929
5.15.3 Conformance with the Commercial Product Assurance
Security Characteristic for GB Smart Metering
2930
2931
2932
ESME shall meet the requirements described in the current version of the Commercial
Product Assurance Security Characteristic Electricity Smart Metering Equipment meaning
v1.2 or later as published on CESG’s Website.
2933
2934
2935
ESME shall be certified by CESG as compliant with the current version of the Commercial
Product Assurance Security Characteristic Electricity Smart Metering Equipment meaning
v1.2 or later as published on CESG’s Website.
2936
5.16 Physical Requirements
2937
Physical Requirements(5.4) in Part A shall not apply to ESME.
2938
ESME shall as a minimum include the following components:
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
a Clock;
a Data Store;
an Electricity Meter containing three measuring elements;
a HAN Interface;
a Load Switch;
a Random Number Generator;
a User Interface; and
where installed with a Communications Hub provided by the Data and
Communications Company, a Communications Hub Physical Interface (this may
comprise a Communications Hub Physical Interface forming part of GSME where
present at the time of installation in the Premises).
Version 1.59
18 November 2015
Page 73
DRAFT
SMETS
2950
2951
2952
2953
The Communications Hub Physical Interface shall as a minimum include a physical interface
that meets the requirements defined by the Data and Communications Company at the time
of installation (available on the Data and Communications Company’s website) and includes
provision for a DC power supply to the Communications Hub.
2954
2955
2956
2957
ESME shall be mains powered and be capable of performing the minimum functional,
interface and data requirements set out in Sections 5.17, 5.18 and 5.23 respectively
operating at a nominal voltage of 230VAC without consuming more than an average of 7
watts of electricity under normal operating conditions.
2958
2959
ESME shall be capable of automatically resuming operation after a power failure in its
operating state prior to such failure.
2960
ESME shall:
2961
2962
2963
2964
2965
2966
2967
ix.
x.
permanently display the ESME Identifier(5.7.1.1) on the ESME; and
have a Secure Perimeter.
The HAN Interface of ESME shall be capable of joining a ZigBee SEP v1.2 Smart Metering
Home Area Network which:
xi.
xii.
operates within the 2400 – 2483.5 MHz harmonised frequency band; and
supports the Communications Links described in Sections 5.6.1, 5.6.3, 5.6.4 and
5.18.1.
2968
2969
On joining a ZigBee SEP v1.2 Smart Metering Home Area Network ESME shall be capable
of generating and sending an Alert to that effect via its HAN Interface.
2970
2971
2972
ESME shall be designed taking all reasonable steps so as to prevent Unauthorised Physical
Access and Unauthorised communications through its Secure Perimeter that could
compromise the Confidentiality and / or Data Integrity of:
2973
2974
2975
2976
2977
2978
2979
xiii.
xiv.
xv.
xvi.
xvii.
xviii.
xix.
2980
stored or executing on ESME.
2981
2982
2983
ESME shall be capable of detecting any attempt at Unauthorised Physical Access through
its Secure Perimeter that could compromise such Confidentiality and / or Data Integrity and
on such detection shall be capable of:
2984
2985
xx.
Personal Data;
Consumption data used for billing;
Security Credentials;
Random Number Generator;
Cryptographic Algorithms;
the Electricity Meter; and
Firmware and data essential for ensuring its integrity,
providing evidence of such an attempt through the use of tamper evident coatings or
seals,
2986
and where reasonably practicable:
2987
2988
2989
2990
2991
2992
xxi.
xxii.
xxiii.
2993
5.17 Functional Requirements
2994
2995
ESME shall be capable of calculating Active Power Import, Consumption, Reactive Energy
Import, Active Energy Export and Reactive Energy Export values as follows:
generating an entry to that effect in the Security Log(5.7.5.31);
generating and sending an Alert to that effect via its HAN Interface; and
where the Supply Tamper State(5.7.4.44) is configured to require Locking,
establishing a Locked state whereby the Supply is Disabled and can only be
Enabled or Armed in response to a Command to Arm the Supply (as described in
Section 5.6.3.7) or Enable the Supply (as described in Section 5.6.3.12).
Version 1.59
18 November 2015
Page 74
DRAFT
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
i.
ii.
iii.
iv.
v.
SMETS
Active Power Import shall be the sum of the Active Power Import on the importing
measuring element(s) of its Electricity Meter less the sum of the Active Power Export
on the exporting measuring element(s) of its Electricity Meter;
Consumption shall be the sum of the cumulative Active Energy Imported on the
importing measuring element(s) of its Electricity Meter less the sum of the
cumulative Active Energy Exported on the exporting measuring element(s) of its
Electricity Meter;
Reactive Energy Import shall be the sum of the cumulative Reactive Energy Import
on the importing measuring element(s) of its Electricity Meter less the sum of the
cumulative Reactive Energy Export on the exporting measuring element(s) of its
Electricity Meter;
Active Energy Export shall be the sum of the cumulative Active Energy Export on the
exporting measuring element(s) of its Electricity Meter less the sum of the
cumulative Active Energy Import on the importing measuring element(s) of its
Electricity Meter; and
Reactive Energy Export shall be the sum of the cumulative Reactive Energy Export
on the exporting measuring element(s) of its Electricity Meter less the sum of the
cumulative Reactive Energy Import on the importing measuring element(s) of its
Electricity Meter.
3015
If the result of any of the calculations (i) to (v) is negative then it shall be deemed to be zero.
3016
5.17.1 Phase Measurements
3017
ESME shall be capable of measuring:
3018
3019
3020
3021
3022
3023
i.
ii.
iii.
iv.
three phase four wire unbalanced supplies operating at a nominal voltage of
230VAC phase-to-neutral (400VAC phase-to-phase);
two phases of a three phase four wire system;
two phases of a three wire system 230-0-230VAC phase-to-neutral-to-phase
(460VAC phase-to-phase); and
the sum of two distinct one phase two wire 230VAC services with a common neutral.
3024
5.17.2 Voltage Quality Measurements
3025
Voltage Quality Measurements(5.5.12) in Part A shall not apply to ESME.
3026
5.17.2.1
3027
3028
3029
ESME shall be capable of calculating the average value of RMS voltage for phase [n] over a
configurable period as defined in the Phase [n] Average RMS Voltage Measurement
Period(5.19.1.3) and:
3030
3031
3032
3033
3034
3035
3036
3037
3038
i.
ii.
Average RMS voltage phase [n]
recording the values calculated (including the UTC date and time at the end of the
period to which the values relate) in the Phase [n] Average RMS Voltage Profile
Data Log(5.19.2.3);
detecting when the value calculated for phase [n] is above the Phase [n] Average
RMS Over Voltage Threshold(5.19.1.1) and on detection:
a) counting the number of such occurrences in the Phase [n] Average RMS Over
Voltage Counter(5.19.2.1);
b) where the value calculated in the prior configurable period was below the
Phase [n] Average RMS Over Voltage Threshold(5.19.1.1):

3039
3040
3041
3042

Version 1.59
generating an entry to that effect (including identification of the relevant
phase) in the Power Event Log(5.7.5.25); and
generating and sending an Alert to that effect (including identification of the
relevant phase) via its HAN Interface.
18 November 2015
Page 75
DRAFT
3043
3044
3045
3046
iii.
SMETS
detecting when the value calculated for phase [n] is below the Phase [n] Average
RMS Over Voltage Threshold(5.19.1.1) and where the value calculated in the prior
configurable period was above the Phase [n] Average RMS Over Voltage
Threshold(5.19.1.1):
3047
3048
3049
3050
3051
3052
a) generating an entry to that effect (including identification of the relevant phase)
in the Power Event Log(5.7.5.25); and
b) generating and sending an Alert to that effect (including identification of the
relevant phase) via its HAN Interface.
iv.
detecting when the value calculated for phase [n] is below the Phase [n] Average
RMS Under Voltage Threshold(5.19.1.2) and on detection:
3053
3054
3055
3056
a) counting the number of such occurrences in the Phase [n] Average RMS Under
Voltage Counter(5.19.2.2);
b) where the value calculated for phase [n] in the prior configurable period was
above the Phase [n] Average RMS Under Voltage Counter(5.19.2.2):

3057
3058
3059
3060
3061
3062
3063
3064

v.
generating an entry to that effect (including identification of the relevant
phase) in the Power Event Log(5.7.5.25); and
generating and sending an Alert to that effect (including identification of the
relevant phase) via its HAN Interface
detecting when the value calculated for phase [n] is above the Phase [n] Average
RMS Under Voltage Threshold(5.19.1.2) and where the value calculated in the prior
configurable period was below the Phase [n] Average RMS Under Voltage
Threshold(5.19.1.2):
3065
3066
3067
3068
a) generating an entry to that effect (including identification of the relevant phase)
in the Power Event Log(5.7.5.25); and
b) generating and sending an Alert to that effect (including identification of the
relevant phase) via its HAN Interface.
3069
5.17.2.2
3070
ESME shall be capable of:
3071
3072
3073
i.
detecting when the RMS voltage for phase [n] rises above the RMS Extreme Over
Voltage Threshold(5.7.4.35) for a continuous period longer than the RMS Extreme
Over Voltage Measurement Period(5.7.4.34) and on detection:
3074
3075
3076
3077
3078
3079
3080
RMS extreme over voltage detection
a) generating an entry to that effect (including identification of the relevant phase)
in the Power Event Log(5.7.5.25); and
b) generating and sending an Alert to that effect (including identification of the
relevant phase) via its HAN Interface.
ii.
detecting when the RMS voltage for phase [n] returns below the RMS Extreme Over
Voltage Threshold(5.7.4.35) for a continuous period longer than the RMS Extreme
Over Voltage Measurement Period(5.7.4.34) and on detection:
3081
3082
3083
3084
a) generating an entry to that effect (including identification of the relevant phase)
in the Power Event Log(5.7.5.25); and
b) generating and sending an Alert to that effect (including identification of the
relevant phase) via its HAN Interface.
3085
5.17.2.3
3086
ESME shall be capable of:
3087
3088
3089
i.
RMS extreme under voltage detection
detecting when the RMS voltage for phase [n] falls below the RMS Extreme Under
Voltage Threshold(5.7.4.37) for longer than the RMS Extreme Under Voltage
Measurement Period(5.7.4.36) and on detection:
Version 1.59
18 November 2015
Page 76
DRAFT
SMETS
3090
3091
3092
3093
3094
3095
3096
a) generating an entry to that effect (including identification of the relevant phase)
in the Power Event Log(5.7.5.25); and
b) generating and sending an Alert to that effect (including identification of the
relevant phase) via its HAN Interface.
ii.
detecting when the RMS voltage for phase [n] returns above the RMS Extreme
Under Voltage Threshold(5.7.4.37) for longer than the RMS Extreme Under Voltage
Measurement Period(5.7.4.36) and on detection:
3097
3098
3099
3100
a) generating an entry to that effect (including identification of the relevant phase)
in the Power Event Log(5.7.5.25); and
b) generating and sending an Alert to that effect (including identification of the
relevant phase) via its HAN Interface.
3101
5.17.2.4
3102
ESME shall be capable of:
3103
3104
3105
i.
detecting when the RMS voltage for phase [n] falls below the RMS Voltage Sag
Threshold(5.7.4.40) for a continuous period longer than the RMS Voltage Sag
Measurement Period(5.7.4.38) and on detection:
3106
3107
3108
3109
3110
3111
3112
RMS voltage sag detection
a) generating an entry to that effect (including identification of the relevant phase)
in the Power Event Log(5.7.5.25); and
b) generating and sending an Alert to that effect (including identification of the
relevant phase) via its HAN Interface.
ii.
detecting when the RMS voltage for phase [n] returns above the RMS Voltage Sag
Threshold(5.7.4.40) for a continuous period longer than the RMS Voltage Sag
Measurement Period(5.7.4.38) and on detection:
3113
3114
3115
3116
a) generating an entry to that effect (including identification of the relevant phase)
in the Power Event Log(5.7.5.25); and
b) generating and sending an Alert to that effect (including identification of the
relevant phase) via its HAN Interface.
3117
5.17.2.5
3118
ESME shall be capable of:
3119
3120
3121
i.
detecting when the RMS voltage for phase [n] rises above the RMS Voltage Swell
Threshold(5.7.4.41) for a continuous period longer than the RMS Voltage Swell
Measurement Period(5.7.4.39) and on detection:
3122
3123
3124
3125
3126
3127
3128
RMS voltage swell detection
a) generating an entry to that effect (including identification of the relevant phase)
in the Power Event Log(5.7.5.25); and
b) generating and sending an Alert to that effect (including identification of the
relevant phase) via its HAN Interface.
ii.
detecting when the RMS voltage for phase [n] returns below the RMS Voltage Swell
Threshold(5.7.4.41) for a continuous period longer than the RMS Voltage Swell
Measurement Period(5.7.4.39) and on detection:
3129
3130
3131
3132
a) generating an entry to that effect (including identification of the relevant phase)
in the Power Event Log(5.7.5.25); and
b) generating and sending an Alert to that effect (including identification of the
relevant phase) via its HAN Interface.
3133
5.17.2.6
3134
3135
ESME shall be capable of recording the UTC date and time at which the Supply via phase
[n] is interrupted and:
3136
i.
Supply outage reporting phase [n]
generating entries to that effect in the Power Event Log(5.7.5.25);
Version 1.59
18 November 2015
Page 77
DRAFT
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
ii.
SMETS
where Supply via phase [n] has not been restored 3 minutes after interruption, and
ESME still has a power Supply, generating and sending an Alert to that effect via its
HAN Interface.
ESME shall be capable of recording the UTC date and time at which the Supply via phase
[n] is restored and:
iii.
iv.
v.
generating entries to that effect in the Power Event Log(5.7.5.25);
following restoration of the Supply via phase [n], generating and sending an Alert to
that effect via its HAN Interface containing details of the UTC dates and times of
interruption and restoration; and
following restoration of the Supply via phase [n], when the time difference between
the Supply being interrupted and restored is greater than or equal to three minutes,
generating and sending an Alert to that effect via its HAN Interface containing details
of the UTC date and time of interruption and restoration.
3150
5.18 Interface Requirements
3151
5.18.1 HAN Interface Commands
3152
5.18.1.1
3153
A Command to reset the Phase [n] Average RMS Over Voltage Counter(5.19.2.1) to zero.
3154
5.18.1.2
3155
A Command to reset the Phase [n] Average RMS Under Voltage Counter(5.19.2.2) to zero.
3156
5.19 Data Requirements
3157
5.19.1 Configuration Data
3158
5.19.1.1
3159
3160
The average RMS voltage for phase [n] above which an over voltage condition is reported.
The threshold shall be configurable within the specified operating range of ESME.
3161
5.19.1.2
3162
3163
The average RMS voltage for phase [n] below which an under voltage condition is reported.
The threshold shall be configurable within the specified operating range of ESME.
3164
5.19.1.3
3165
The length of time in seconds over which the RMS voltage is averaged for phase [n].
3166
5.19.2 Operational Data
3167
5.19.2.1
3168
3169
3170
The number of times the average RMS voltage for phase [n], as calculated in Section
5.17.2.1, has been above the Phase [n] Average RMS Over Voltage Threshold(5.19.1.1)
since this counter was last reset.
3171
5.19.2.2
3172
3173
3174
The number of times the average RMS voltage for phase [n], as calculated in accordance
with Section 5.17.2.1, has been below the Phase [n] Average RMS Under Voltage
Threshold(5.19.1.2) since this counter was last reset.
3175
5.19.2.3
3176
3177
A log capable of storing 4320 entries (including the UTC date and time at the end of the
period to which the values relate) comprising the averaged RMS voltage for phase [n] for
Version 1.59
Reset Phase [n] Average RMS Over Voltage Counter
Reset Phase [n] Average RMS Under Voltage Counter
Phase [n] Average RMS Over Voltage Threshold
Phase [n] Average RMS Under Voltage Threshold
Phase [n] Average RMS Voltage Measurement Period
Phase [n] Average RMS Over Voltage Counter
Phase [n] Average RMS Under Voltage Counter
Phase [n] Average RMS Voltage Profile Data Log
18 November 2015
Page 78
DRAFT
3178
3179
SMETS
each Phase [n] Average RMS Voltage Measurement Period(5.19.1.3) arranged as a circular
buffer such that when full, further writes shall cause the oldest entry to be overwritten.
Version 1.59
18 November 2015
Page 79
DRAFT
SMETS
3180
Part D - Auxiliary Load Control Switch
3181
5.20 Overview
3182
3183
This Part D describes the minimum additional functional, interface and data requirements of
ESME where one or more Auxiliary Load Control Switches are installed within ESME.
3184
5.21 Functional Requirements
3185
5.21.1 Switching Auxiliary Loads
3186
3187
ESME shall be capable of monitoring the Auxiliary Load Control Switch Calendar(5.7.4.2)
and opening or closing Auxiliary Load Control Switch [n] at times defined in the calendar.
3188
3189
3190
3191
ESME shall only be capable of closing Auxiliary Load Control Switch [n] if the Supply is
Enabled. If the Supply is Disabled, then on Enablement ESME shall be capable of causing
the Auxiliary Load Control Switch [n] to open, close or maintain its state as defined in the
Auxiliary Load Control Switch Calendar(5.7.4.2).
3192
When switching Auxiliary Loads as set out in this Section 5.21.1, ESME shall be capable of:
3193
3194
i.
ii.
applying the Randomised Offset [INFO](5.7.5.28); and
setting the Auxiliary Load Control Switch [n] - Status(5.23.1.1) to open and closed.
3195
5.22 Interface Requirements
3196
5.22.1 User Interface Commands
3197
5.22.1.1
3198
3199
3200
A Command to cause an Auxiliary Load Control Switch [n] to change its state for 5 minutes
and then to revert to normal operation in accordance with the Auxiliary Load Control Switch
Calendar(5.7.4.2).
3201
3202
In executing the Command ESME shall be capable of recording the Command and Outcome
to the Auxiliary Load Control Switch Event Log(5.7.5.6).
3203
5.22.2 HAN Interface Commands
3204
5.22.2.1
3205
3206
3207
3208
A Command to cause Auxiliary Load Control Switch [n] to close immediately. The
Command shall include a time period. When this time period has elapsed, ESME shall be
capable of causing the switch to open or remain closed as defined in the Auxiliary Load
Control Switch Calendar(5.7.4.2).
3209
3210
3211
3212
A Command to close an Auxiliary Load Control Switch [n] shall be executed only if the
Supply is Enabled. If the Supply is Armed or Disabled, the Command shall be executed
when the Supply is Enabled if, on Enablement, the time period included in the Command
has not elapsed.
3213
In executing the Command, ESME shall be capable of:
3214
3215
3216
3217
i.
ii.
Test Auxiliary Load Control Switch [n]
Close Auxiliary Load Control Switch [n]
recording the Command and Outcome to the Auxiliary Load Control Switch Event
Log(5.7.5.6); and
updating the corresponding Auxiliary Load Control Switch [n] - Status(5.23.1.1) to
indicate whether the switch is now open or closed.
3218
5.22.2.2
3219
3220
A Command to cause Auxiliary Load Control Switch [n] to open immediately. The Command
shall include a time period. When this time period has elapsed, ESME shall be capable of
Version 1.59
Open Auxiliary Load Control Switch [n]
18 November 2015
Page 80
DRAFT
SMETS
3221
3222
causing the switch to close or remain open as defined in the Auxiliary Load Control Switch
Calendar(5.7.4.2).
3223
In executing the Command, ESME shall be capable of:
3224
3225
3226
3227
i.
ii.
recording the Command and Outcome to the Auxiliary Load Control Switch Event
Log(5.7.5.6); and
updating the corresponding Auxiliary Load Control Switch [n] - Status(5.23.1.1) to
indicate whether the switch is now open or closed.
3228
5.22.2.3
3229
3230
A Command to cause the Auxiliary Load Control Switch [n] to open, close or maintain its
state, as defined in the Auxiliary Load Control Switch Calendar(5.7.4.2).
3231
3232
3233
A Command to close an Auxiliary Load Control Switch [n] shall be executed only if the
Supply is Enabled. If the Supply is Armed or Disabled, the Command shall be executed
when the Supply is Enabled.
3234
In executing the Command, ESME shall be capable of:
3235
3236
3237
3238
i.
ii.
Reset Auxiliary Load Control Switch [n]
recording the Command and Outcome to the Auxiliary Load Control Switch Event
Log(5.7.5.6); and
updating the corresponding Auxiliary Load Control Switch [n] - Status(5.23.1.1) to
indicate whether the switch is now open or closed.
3239
5.23 Data Requirements
3240
5.23.1 Operational Data
3241
5.23.1.1
3242
3243
The current status (being ‘open’ or ‘closed’) of Auxiliary Load Control Switch [n] as
commanded by ESME.
Version 1.59
Auxiliary Load Control Switch [n] - Status
18 November 2015
Page 81
DRAFT
SMETS
3244
Part E - Boost Function
3245
5.24 Overview
3246
3247
This Part E describes the minimum additional functional and data requirements of ESME
where a Boost Function is installed within ESME.
3248
5.25 Functional Requirements
3249
5.25.1 User Interface Commands
3250
3251
3252
In executing the Commands in this Section 5.25.1 ESME shall be capable of recording UTC
date and time at the beginning and end of any Boost Period in the Boost Function Event
Log(5.26.3.1).
3253
5.25.1.1
3254
3255
3256
A Command to cause the Auxiliary Load Control Switch(es) specified in Boost Function
Control [n](5.26.2.1) to close for 15, 30, 45 or 60 minutes and then to revert to normal
operation in accordance with the Auxiliary Load Control Switch Calendar(5.7.4.2).
3257
3258
ESME shall only be capable of executing this Command if no Boost Period is currently
active.
3259
5.25.1.2
3260
3261
3262
A Command to cause the Auxiliary Load Control Switch(es) specified in Boost Function
Control [n](5.26.2.1) to revert to normal operation in accordance with the Auxiliary Load
Control Switch Calendar(5.7.4.2).
3263
ESME shall only be capable of executing this Command if a Boost Period is active.
3264
3265
In executing the Command ESME shall be capable of generating an entry in the Boost
Function Event Log(5.26.3.1) to the effect that the active Boost Period has been cancelled.
3266
5.25.1.3
3267
3268
3269
A Command to cause the Auxiliary Load Control Switch(es) specified in Boost Function
Control [n](5.26.2.1) to remain closed for an additional 15, 30, 45 minutes, and then to revert
to normal operation in accordance with the Auxiliary Load Control Switch Calendar(5.7.4.2).
3270
3271
3272
ESME shall only be capable of executing this Command if a Boost Period is active. In
executing the Command ESME shall be capable of limiting any active Boost Period to a
maximum of 60 minutes.
3273
5.26 Data Requirements
3274
5.26.1 Constant Data
3275
5.26.1.1
3276
A data item to identify if ESME has a configured Boost Function.
3277
5.26.2 Configuration Data
3278
5.26.2.1
3279
3280
A data item to identify whether Auxiliary Load Control Switch [n] is to be controlled by the
Boost Function.
Version 1.59
Activate Boost Period
Cancel Boost Period
Extend Boost Period
Boost Function Availability
Boost Function Control [n]
18 November 2015
Page 82
DRAFT
SMETS
3281
5.26.3 Operational Data
3282
5.26.3.1
3283
3284
A single log capable of storing entries for the most recent 25 Boost Periods including the
UTC date and time of the beginning and end of the Boost Period.
Version 1.59
Boost Function Event Log
18 November 2015
Page 83
DRAFT
SMETS
3286
6 In Home Display Technical
Specifications
3287
6.1 Overview
3288
3289
3290
3291
3292
Section 6 of this document describes the minimum physical, minimum functional, minimum
interface, minimum data and minimum testing and certification requirements of the In-home
Display installed to comply with the smart metering roll-out licence conditions (standard
licence condition 34 of gas supply licences and standard licence condition 40 of electricity
supply licences).
3293
6.2 SMETS Testing and Certification Requirements
3294
6.2.1
3295
3296
An IHD shall have been tested to ensure that it meets the requirements described in this
Section 6, and evidence must be available to confirm such testing and conformance.
3297
6.2.2
3298
3299
3300
An IHD shall have been certified by the ZigBee Alliance as compliant with the ZigBee SEP
v1.2 requirements described in the current version of the Great Britain Companion
Specifications meaning v0.8.2 or later.
3301
6.3 Physical requirements
3302
The IHD shall as a minimum include the following components:
3285
3303
3304
3305
i.
ii.
iii.
Conformance with the SMETS
ZigBee Alliance Certification
a Data Store;
a HAN Interface; and
a User Interface.
3306
3307
3308
3309
The IHD shall be mains powered and shall be capable of performing the minimum functional,
interface and data requirements set out in Sections 6.4, 6.5 and 6.6 respectively operating at
a nominal voltage of 230VAC without consuming more than an average of 0.6 watts of
electricity under normal operating conditions.
3310
The IHD shall:
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
iv.
permanently display the IHD Identifier(6.6.1.1) on the IHD;
The HAN Interface of the IHD shall be capable of joining a ZigBee SEP v1.2 Smart Metering
Home Area Network which:
v.
vi.
operates within the 2400 – 2483.5 MHz harmonised frequency band; and
supports the Communications Links described in Section 6.5.
The IHD shall be designed to enable the information displayed on it to be easily accessed
and presented in a form that is clear and easy to understand including by Consumers with
impaired:
vii.
viii.
ix.
x.
sight;
memory and learning ability;
perception and attention; or
dexterity.
3323
6.4 Functional requirements
3324
This section describes the minimum functions that the IHD shall be capable of performing.
Version 1.59
18 November 2015
Page 84
DRAFT
SMETS
3325
6.4.1
3326
The IHD shall be capable of establishing Communications Links via its HAN Interface.
3327
3328
The IHD shall be capable of ensuring that the security characteristics of all Communications
Links it establishes meet the requirements described in Section 6.4.5.2.
3329
3330
6.4.1.1
3331
3332
The IHD shall be capable of establishing and maintaining Communications Links via its HAN
Interface with one ESME and one Gas Proxy Function.
3333
3334
In establishing the Communications Link, the IHD shall be capable of using its Security
Credentials to enable it to be Authenticated.
3335
The IHD shall be capable of supporting the following types of Communications Links:
3336
3337
i.
ii.
Communications
Communications Links with ESME and the Gas Proxy Function via the HAN
Interface
receiving Pricing and Consumption information from ESME; and
receiving Pricing and Consumption information from a Gas Proxy Function.
3338
3339
3340
3341
The IHD shall be capable of detecting a failure of a Communications Link and on detection
of a failure, shall be capable of clearing or suitably annotating the information displayed on
its User Interface (set out in Sections 6.4.2, 6.4.3 and 6.4.4) to indicate that the information
may be out of date.
3342
6.4.2
3343
3344
3345
3346
The IHD shall be capable immediately upon establishment of a Communications Link with
ESME and a Gas Proxy Function (as set out in Section 6.4.1.1), of providing the following
information on its User Interface and providing updates of any changes to the information
every 10 seconds thereafter.
3347
6.4.2.1
3348
The signal strength of its HAN Interface.
3349
6.4.2.2
3350
Time as UTC with adjustment for British Summer Time.
3351
6.4.3
3352
3353
3354
The IHD shall be capable immediately upon establishment of a Communications Link with a
Gas Proxy Function (as set out in Section 6.4.1.1), of providing the following information5 on
its User Interface and providing timely updates of any changes to the information thereafter.
3355
3356
The IHD shall be capable of displaying Currency Units in GB Pounds and European Central
Bank Euro.
3357
6.4.3.1
3358
The active Tariff Price for Energy Consumption in Currency Units per kWh.
3359
6.4.3.2
3360
3361
3362
3363
3364
3365
i.
ii.
iii.
iv.
General Information
Connection Link Quality
Local Time
Information pertaining to the Supply of gas to the Premises
Active Tariff Price [NUM]
Cumulative Consumption [NUM]
Current Day cumulative Energy Consumption;
Current Day cost to the Consumer of cumulative Energy Consumption in Currency
Units;
Current Week cumulative Energy Consumption;
Current Week cost to the Consumer of cumulative Energy Consumption in Currency
Units;
5
Information that shall be capable of being provided in numerical form is annotated [NUM]. Information that shall be capable of
being provided in Ambient form is annotated [AMB]. Where information is not annotated the information may be provided in any
visual format.
Version 1.59
18 November 2015
Page 85
DRAFT
SMETS
3366
3367
3368
v.
vi.
Current month cumulative Energy Consumption; and
Current month cost to the Consumer of cumulative Energy Consumption in Currency
Units.
3369
6.4.3.3
3370
A number issued to the IHD for display on the User Interface.
3371
6.4.3.4
3372
3373
Either Aggregate Debt or time-based and payment-based debt when GSME is operating in
Prepayment Mode.
3374
6.4.3.5
3375
3376
Either Aggregate Debt Recovery Rate or each Time-based Debt Recovery rate when GSME
is operating in Prepayment Mode.
3377
6.4.3.6
3378
3379
The Emergency Credit balance where Emergency Credit is activated (including a clear
indication that Emergency Credit has been activated).
3380
6.4.3.7
3381
3382
3383
3384
3385
3386
3387
i.
ii.
iii.
iv.
v.
vi.
Customer Identification Number [NUM]
Debt [NUM]
Debt Recovery Rate [NUM]
Emergency Credit Balance [NUM]
Historic Consumption
D-1 to D-8 historic Energy Consumption;
D-1 to D-8 cost to the Consumer of historic Energy Consumption in Currency Units;
W-1 to W-5 historic Energy Consumption;
W-1 to W-5 cost to the Consumer of historic Energy Consumption in Currency Units;
M-1 to M-13 historic Energy Consumption; and
M-1 to M-13 cost to the Consumer of historic Energy Consumption in Currency
Units.
3388
3389
where: D-1 = current Day minus 1, D-2 = current Day minus 2, W-1 = current Week minus 1,
M-1 = current month minus 1, etc.
3390
6.4.3.8
3391
3392
An indication that the combined Meter Balance [NUM](6.4.3.9) and Emergency Credit
Balance [NUM](6.4.3.6) has fallen below a low credit threshold.
3393
6.4.3.9
3394
3395
3396
3397
3398
The amount of money in Currency Units as determined by GSME. If operating in
Prepayment Mode, the Meter Balance represents GSME’s determination of the amount of
credit available to the Consumer (excluding any Emergency Credit Balance [NUM](6.4.3.6)).
If operating in Credit Mode, it represents GSME’s determination of the amount of money due
from the Consumer since the Meter Balance was last reset.
3399
6.4.3.10
3400
The current mode of operation of GSME, being Prepayment Mode or Credit Mode.
3401
3402
6.4.4
3403
3404
3405
The IHD shall be capable, upon establishment of a Communications Link with ESME (as set
out in Section 6.4.1.1), of providing the following information6 on its User Interface and
providing updates of any changes to the information every 10 seconds thereafter.
Low Credit Alert
Meter Balance [NUM]
Payment Mode
Information pertaining to the Supply of electricity to the
Premises
6
Information that shall be capable of being provided in numerical form is annotated [NUM]. Information that shall be capable of
being provided in Ambient form is annotated [AMB]. Where information is not annotated the information may be provided in any
visual format.
Version 1.59
18 November 2015
Page 86
DRAFT
SMETS
3406
3407
The IHD shall be capable of displaying Currency Units in GB Pounds and European Central
Bank Euro.
3408
6.4.4.1
3409
The active Tariff Price for Consumption in Currency Units per kWh.
3410
6.4.4.2
3411
3412
3413
3414
3415
3416
i.
ii.
iii.
iv.
v.
vi.
3417
6.4.4.3
3418
A number issued to the IHD for display on the User Interface.
3419
6.4.4.4
3420
3421
Either Aggregate Debt or time-based and payment-based debt when ESME is operating in
Prepayment Mode.
3422
6.4.4.5
3423
3424
Either Aggregate Debt Recovery Rate or each Time-based Debt Recovery rate when ESME
is operating in Prepayment Mode.
3425
6.4.4.6
3426
3427
The Emergency Credit balance where Emergency Credit is activated in ESME (including a
clear indication that the Emergency credit has been activated).
3428
6.4.4.7
3429
3430
3431
3432
3433
3434
i.
ii.
iii.
iv.
v.
vi.
Active Tariff Price [NUM]
Cumulative Consumption [NUM]
Current Day cumulative Consumption;
Current Day cost to the Consumer of cumulative Consumption in Currency Units;
Current Week cumulative Consumption;
Current Week cost to the Consumer of cumulative Consumption in Currency Units;
Current month cumulative Consumption; and
Current month cost to the Consumer of cumulative Consumption in Currency Units.
Customer Identification Number [NUM]
Debt [NUM]
Debt Recovery Rate [NUM]
Emergency Credit Balance [NUM]
Historic Consumption
D-1 to D-8 historic Consumption;
D-1 to D-8 cost to the Consumer of historic Consumption in Currency Units;
W-1 to W-5 historic Consumption;
W-1 to W-5 cost to the Consumer of historic Consumption in Currency Units;
M-1 to M-13 historic Consumption; and
M-1 to M-13 cost to the Consumer of historic Consumption in Currency Units.
3435
3436
where: D-1 = current Day minus 1, D-2 = current Day minus 2, W-1 = current Week minus 1,
M-1 = current month minus 1 etc.
3437
6.4.4.8
3438
3439
A near real-time indication of the Active Power Import in kW and the cost to the Consumer of
maintaining that Instantaneous Active Power Import for one hour.
3440
6.4.4.9
3441
3442
An indication that the combined Meter Balance [NUM](6.4.4.10) and Emergency Credit
Balance(6.4.4.6) has fallen below a low credit threshold.
3443
6.4.4.10
3444
3445
3446
3447
3448
The amount of money in Currency Units as determined by ESME. If operating in
Prepayment Mode, the Meter Balance represents ESME’s determination of the amount of
credit available to the Consumer (excluding any Emergency Credit Balance(6.4.4.6)). If
operating in Credit Mode, it represents ESME’s determination of the amount of money due
from the Consumer since the Meter Balance was last reset.
Version 1.59
Instantaneous Active Power Import [NUM]
Low Credit Alert
Meter Balance [NUM]
18 November 2015
Page 87
DRAFT
SMETS
3449
6.4.4.11
3450
The current mode of operation of ESME, being Prepayment Mode or Credit Mode.
3451
6.4.4.12
3452
An indication of the level of Active Power Import as high, medium or low.
3453
6.4.5
Security
3454
6.4.5.1
General
3455
3456
3457
3458
The IHD shall be designed taking all reasonable steps so as to ensure that any failure or
compromise of its integrity shall not compromise the Security Credentials or Personal Data
stored on it or compromise the integrity of any other Device to which it is connected by
means of a Communications Link.
3459
6.4.5.2
3460
3461
The IHD shall be capable of preventing and detecting, on all of its interfaces, Unauthorised
access that could compromise the Confidentiality and / or Data Integrity of:
3462
3463
3464
i.
ii.
iii.
Payment Mode
Power Threshold Status [AMB]
Communications
Personal Data whilst being transferred via an interface;
Consumption data used for billing whilst being transferred via an Interface; and
Security Credentials whilst being transferred via an interface.
3465
6.5 Interface Requirements
3466
3467
This section describes the minimum required interactions which the IHD shall be capable of
undertaking with ESME and a Gas Proxy Function as appropriate via its HAN Interface.
3468
6.5.1
3469
3470
The IHD shall be capable, immediately upon establishment of a Communications Link with
ESME and a Gas Proxy Function (as set out in Section 6.4.1.1) of:
3471
3472
3473
3474
3475
3476
3477
3478
i.
ii.
iii.
Receipt of information via the HAN Interface
receiving information (and updates of any changes of this information every 10
seconds thereafter) required to meet the display requirements described in Section
6.4.2;
receiving information (and timely updates of any changes to the information
thereafter) required to meet the display requirements described in Section 6.4.3; and
receiving information (and updates of any changes of this information every 10
seconds thereafter) required to meet the display requirements described in Section
6.4.4.
3479
6.6 Data requirements
3480
3481
This section describes the minimum information which the IHD shall be capable of holding in
its Data Store.
3482
6.6.1
3483
Describes data that remains constant and unchangeable at all times.
3484
6.6.1.1
3485
3486
A globally unique identifier used to identify the IHD based on the EUI-64 Institute of Electrical
and Electronic Engineers standard.
Constant data
Version 1.59
IHD Identifier
18 November 2015
Page 88
DRAFT
SMETS
3488
7 Prepayment Interface Device
Technical Specifications
3489
7.1 Overview
3490
3491
3492
Section 7 of this document describes the minimum physical, minimum functional, minimum
interface, minimum data and minimum testing and certification requirements of a
Prepayment Interface Device (PPMID), where it is installed by a Supplier.
3493
7.2 SMETS Testing and Certification Requirements
3494
7.2.1
3495
3496
A PPMID shall have been tested to ensure that it meets the requirements described in this
Section 7, and evidence must be available to confirm such testing and conformance.
3497
3498
7.2.2
3499
3500
A PPMID shall meet the requirements described in the current version of the Great Britain
Companion Specifications meaning v0.8.2 or later as published on the SECAS website.
3501
3502
3503
A PPMID shall have been certified by the ZigBee Alliance as compliant with the ZigBee SEP
v1.2 requirements described in the current version of the Great Britain Companion
Specifications meaning v0.8.2 or later as published on the SECAS website.
3504
7.3 Physical Requirements
3505
A PPMID shall as a minimum include the following components:
3487
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
i.
ii.
iii.
Conformance with the SMETS
Conformance with the Great Britain Companion
Specifications
a Data Store;
a HAN Interface; and
a User Interface.
A PPMID shall:
iv.
v.
permanently display the PPMID Identifier(7.6.1.1) on the PPMID; and
have a Secure Perimeter.
The HAN Interface of a PPMID shall be capable of joining a ZigBee SEP v1.2 Smart
Metering Home Area Network which:
vi.
vii.
operates within the 2400 – 2483.5 MHz harmonised frequency band; and
supports the Communications Links described in Sections 7.5.1, 7.5.2, 7.5.4 and
7.5.5.
The PPMID shall be designed taking all reasonable steps so as to prevent Unauthorised
Physical Access and Unauthorised communications through its Secure Perimeter that could
compromise the Confidentiality and / or Data Integrity of:
viii.
ix.
x.
xi.
Personal Data;
Security Credentials;
Cryptographic Algorithms; and
Firmware and data essential for ensuring its integrity,
3524
stored or executing on the PPMID.
3525
3526
3527
The PPMID shall be capable of detecting any attempt at Unauthorised Physical Access
through its Secure Perimeter that could compromise such Confidentiality and / or Data
Integrity and on such detection shall be capable of:
Version 1.59
18 November 2015
Page 89
DRAFT
3528
3529
3530
3531
xii.
SMETS
providing evidence of such an attempt through the use of tamper evident coatings or
seals;
and where reasonably practicable:
xiii.
generating and sending an Alert to that effect via its HAN Interface.
3532
7.4 Functional Requirements
3533
This section describes the minimum functions that a PPMID shall be capable of performing.
3534
7.4.1
3535
A PPMID shall be capable of establishing Communications Links via its HAN Interface.
3536
3537
A PPMID shall be capable of ensuring that the security characteristics of all Communications
Links it establishes meet the requirements described in Section 7.4.7.4.
3538
3539
When any Command addressed to the PPMID is received via any Communications Link the
PPMID shall be capable of:
3540
3541
3542
3543
3544
i.
ii.
iii.
Communications
using the Security Credentials the PPMID holds, Authenticating to a Trusted Source
the Command;
verifying in accordance with Section 7.4.7.2.3 that the sender of the Command is
Authorised to execute the Command; and
verifying the integrity of the Command.
3545
3546
3547
On failure of any of (i) to (iii) above, the PPMID shall be capable of discarding the Command
without execution and without either generating or sending a Response, and generating and
sending an Alert to that effect via its HAN Interface.
3548
3549
Where the Command is not due to be executed immediately, the PPMID shall be capable of
generating and sending a Response via its HAN Interface to confirm its successful receipt.
3550
3551
A PPMID shall only be capable of addressing a Response to the sender of the relevant
Command.
3552
3553
7.4.1.1
3554
3555
A PPMID shall be capable of establishing Communications Links via its HAN Interface with a
minimum of one ESME, one GSME and one Gas Proxy Function.
3556
3557
A PPMID shall only be capable of establishing Communications Links via its HAN Interface
with GSME and ESME with Security Credentials in the Device Log(7.6.3.1).
3558
3559
In establishing any Communications Link via its HAN Interface, the PPMID shall be capable
of using its Security Credentials to enable it to be Authenticated.
3560
A PPMID shall be capable of supporting the following types of Communications Links:
3561
3562
3563
3564
i.
ii.
iii.
iv.
Communications Links with ESME, GSME and Gas Proxy Function via the
HAN interface
receiving Price and Consumption information from ESME;
receiving Price and Consumption information from a Gas Proxy Function;
generating and sending the Commands (set out in Section 7.5.4) to GSME; and
generating and sending the Commands (set out in Section 7.5.5) to ESME.
3565
3566
3567
3568
A PPMID shall be capable of detecting a failure of a Communications Link and on detection
of a failure, shall be capable of clearing or suitably annotating the information displayed on
its User Interface (set out in Sections 7.4.5 and 7.4.6) to indicate that the information may be
out of date.
3569
7.4.2
3570
3571
A PPMID shall be capable of retaining all information held in its Data Store at all times,
including on loss of power.
Data storage
Version 1.59
18 November 2015
Page 90
DRAFT
SMETS
3572
7.4.3
3573
7.4.3.1
3574
3575
If the Meter Balance(4.6.5.11) is equal to or below the Disablement Threshold(4.6.4.12) a
PPMID shall be capable of maintaining a calculation of the Debt to Clear based on:
3576
3577
3578
3579
3580
3581
3582
3583
i.
ii.
iii.
iv.
Debt to Clear Calculations
Debt to Clear GSME
the difference between the Meter Balance(4.6.5.11) and the Disablement
Threshold(4.6.4.12);
amount of debt accumulated in the Accumulated Debt Register(4.6.5.1);
amount of Emergency Credit activated and used by the Consumer; and
the payment-based debt to be collected based on (i), (ii) and (iii) (as defined by Debt
Recovery per Payment(4.6.4.8) taking account of the amount remaining in the
Payment Debt Register(4.6.5.13), the payment-based debt payments in the Billing
Data Log(4.6.5.3) and the Debt Recovery Rate Cap(4.6.4.10)).
3584
7.4.3.2
3585
3586
3587
If the Meter Balance [INFO](5.7.5.22) is equal to or below the Disablement Threshold
[INFO](5.7.4.15) a PPMID shall be capable of maintaining a calculation of the Debt to Clear
based on:
3588
3589
3590
3591
3592
3593
3594
3595
i.
ii.
iii.
iv.
Debt to Clear ESME
the difference between the Meter Balance [INFO](5.7.5.22) and the Disablement
Threshold [INFO](5.7.4.15);
amount of debt accumulated in the Accumulated Debt Register [INFO](5.7.5.1);
amount of Emergency Credit activated and used by the Consumer; and
the payment-based debt to be collected based on (i), (ii) and (iii) (as defined by Debt
Recovery per Payment [INFO](5.7.4.11) taking account of the amount remaining in
the Payment Debt Register [INFO](5.7.5.23), the payment-based debt payments in
the Billing Data Log(5.7.5.10) and the Debt Recovery Rate Cap [INFO](5.7.4.13)).
3596
7.4.4
3597
3598
3599
3600
A PPMID shall be capable immediately upon establishment of a Communications Link with
an ESME and a Gas Proxy Function (as set out in Section 7.4.1.1), of displaying the
following up to date information on its User Interface, and displaying updates of any changes
to the information every 10 seconds thereafter.
3601
7.4.4.1
3602
The signal strength of its HAN Interface.
3603
3604
The PPMID shall be capable of displaying Currency Units in GB Pounds and European
Central Bank Euro.
3605
7.4.4.2
3606
The UTC date and time adjusted for British Summer Time.
3607
7.4.5
3608
3609
3610
3611
A PPMID shall be capable immediately upon establishment of a Communications Link with a
Gas Proxy Function (as set out in Section 7.4.1.1), of displaying the following up to date
information on its User Interface, and displaying timely updates of any changes to the
information thereafter:
3612
3613
3614
3615
3616
3617
i.
ii.
iii.
iv.
v.
General Information
Connection Link Quality
Local Time
Information Pertaining to the Supply of Gas to the Premises
the Active Tariff Price(4.6.5.2);
the Emergency Credit Balance(4.6.5.8) where Emergency Credit is activated
(including a clear indication that Emergency Credit has been activated);
whether Emergency Credit is available for activation on GSME;
any low credit condition;
the Meter Balance(4.6.5.11);
Version 1.59
18 November 2015
Page 91
DRAFT
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
vi.
vii.
viii.
ix.
x.
xi.
xii.
SMETS
the Debt to Clear;
whether GSME has suspended the Disablement of Supply during a period defined in
the Non-Disablement Calendar(4.6.4.20) (as set out in Section 4.4.7.2);
either Aggregate Debt or time-based and payment-based debts when GSME is
operating in Prepayment Mode;
either Aggregate Debt Recovery Rate or each Time-based Debt Recovery rate when
GSME is operating in Prepayment Mode;
any Standing Charge(4.6.4.23);
the Contact Details(4.6.4.4); and
the Supply State(4.6.5.18).
3628
3629
7.4.6
3630
3631
3632
A PPMID shall be capable, upon establishment of a Communications Link with ESME (as
set out in Section 7.4.1.1), of displaying the following information on its User Interface, and
displaying updates of any changes to the information every 10 seconds thereafter:
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
xii.
Information Pertaining to the Supply of Electricity to the
Premises
the Active Tariff Price [INFO](5.7.5.5);
the Emergency Credit Balance [INFO](5.7.5.15) where Emergency Credit is
activated (including a clear indication that Emergency Credit has been activated);
whether Emergency Credit is available for activation on ESME;
any low credit condition;
the Meter Balance [INFO](5.7.5.22);
the Debt to Clear when ESME is operating in Prepayment Mode;
whether ESME has suspended the Disablement of Supply during a period defined in
the Non-Disablement Calendar [INFO](5.7.4.30) (as set out in Section 5.5.7.2);
either Aggregate Debt or time-based and payment-based debts when ESME is
operating in Prepayment Mode;
either Aggregate Debt Recovery Rate or each Time-based Debt Recovery rate when
ESME is operating in Prepayment Mode;
any Standing Charge [INFO](5.7.4.42);
Contact Details [INFO](5.7.4.8); and
the Supply State [INFO](5.7.5.32).
3649
7.4.7
Security
3650
7.4.7.1
General
3651
3652
3653
3654
A PPMID shall be designed taking all reasonable steps to ensure that any failure or
compromise of its integrity shall not compromise the Security Credentials or Personal Data
stored on it or compromise the integrity of any other Device to which it is connected by
means of a Communications Link.
3655
7.4.7.2
3656
7.4.7.2.1
3657
The PPMID shall be capable of securely storing Private Keys.
3658
The PPMID shall be capable of securely storing Key Agreement values.
3659
7.4.7.2.2
3660
3661
The PPMID shall be capable of securely storing Security Credentials from Certificates
including for use in the Cryptographic Algorithms as set out in Section 7.5.2.4.
3662
3663
3664
3665
During the replacement of any PPMID Security Credentials(7.6.3.2) (as set out in Section
7.5.2.4), the PPMID shall be capable of ensuring that the PPMID Security
Credentials(7.6.3.2) being replaced remain usable until the successful completion of the
replacement.
Version 1.59
Security Credentials
PPMID Private Keys
Public Key Certificates
18 November 2015
Page 92
DRAFT
SMETS
3666
7.4.7.2.3
3667
3668
The PPMID shall be capable of restricting Authorisation to execute Commands according to
Role permissions.
3669
7.4.7.3
3670
The PPMID shall be capable of supporting the following Cryptographic Algorithms:
3671
3672
3673
3674
3675
i.
ii.
iii.
Role Based Access Control (RBAC)
Cryptographic Algorithms
Elliptic Curve DSA;
Elliptic Curve DH; and
SHA-256.
In executing and generating any Command or Response or Alert, the PPMID shall be
capable of applying Cryptographic Algorithms (alone or in combination) for:
3676
3677
3678
3679
iv.
v.
vi.
vii.
3680
7.4.7.4
3681
3682
A PPMID shall be capable of preventing and detecting, on all of its interfaces, Unauthorised
access that could compromise the Confidentiality and / or Data Integrity of:
3683
3684
3685
3686
3687
i.
ii.
iii.
iv.
Digital Signing;
Digital Signature verification;
Hashing; and
Message Authentication.
Communications
Personal Data whilst being transferred via an interface;
Consumption data used for billing whilst being transferred via an interface;
Security Credentials whilst being transferred via an interface; and
Firmware and data essential for ensuring its integrity whilst being transferred via an
interface.
3688
7.5 Interface Requirements
3689
3690
3691
This section describes the minimum required interactions which a PPMID shall be capable of
undertaking with ESME, GSME and a Gas Proxy Function as appropriate via its HAN
Interface.
3692
7.5.1
3693
3694
A PPMID shall be capable, immediately upon establishment of a Communications Link with
ESME and a Gas Proxy Function (as set out in Section 7.4.1.1) of:
3695
3696
3697
3698
3699
3700
3701
i.
ii.
iii.
Receipt of Information via the HAN Interface
receiving information required to meet the display requirements set out in Section
7.4.3;
receiving information (and timely updates of any changes to the information
thereafter) required to meet the display requirements set out in Section 7.4.5; and
receiving information (and updates of any changes of this information every 10
seconds thereafter) required to meet the display requirements set out in Section
7.4.6.
3702
7.5.2
HAN Interface Commands
3703
3704
A PPMID shall be capable of executing immediately the Commands set out in this Section
7.5.2 following their receipt via its HAN Interface.
3705
7.5.2.1
3706
A Command to add Security Credentials for ESME or GSME to the Device Log(7.6.3.1).
3707
In executing the Command, a PPMID shall be capable of verifying the Security Credentials.
Version 1.59
Add Device Security Credentials
18 November 2015
Page 93
DRAFT
SMETS
3708
7.5.2.2
Read Configuration Data
3709
3710
A Command to read the value of one or more of the configuration data items set out in
Section 7.6.3.
3711
3712
In executing the Command, a PPMID shall be capable of sending such value(s) in a
Response via its HAN Interface.
3713
7.5.2.3
3714
3715
A Command to remove Security Credentials for ESME or GSME from the Device
Log(7.6.3.1).
3716
7.5.2.4
3717
A Command to replace PPMID Security Credentials(7.6.3.2) held within the PPMID.
3718
3719
In executing the Command the PPMID shall be capable of maintaining the Command’s
Transactional Atomicity.
3720
7.5.3
3721
3722
A PPMID shall be capable of executing immediately the Commands set out in this Section
7.5.3 following their receipt via its User Interface.
3723
7.5.3.1
3724
A Command to issue a Request Emergency Credit Activation(7.5.5.1) to ESME.
3725
7.5.3.2
3726
A Command to issue a Request Emergency Credit Activation(7.5.4.1) to GSME.
3727
7.5.3.3
3728
3729
A Command to generate and issue a Request to Add Credit(7.5.5.2) when ESME is
operating in Prepayment Mode on input of a PTUT.
3730
7.5.3.4
3731
3732
A Command to generate and issue a Request to Add Credit(7.5.4.2) when GSME is
operating in Prepayment Mode on input of a PTUT.
3733
7.5.3.5
3734
A Command to issue a Request to Enable ESME Supply(7.5.5.3) to ESME.
3735
7.5.4
3736
3737
A PPMID shall be capable of generating and issuing to GSME the Commands set out in this
Section 7.5.4.
3738
7.5.4.1
3739
A Command requesting that GSME Activates Emergency Credit.
3740
7.5.4.2
3741
A Command including a UTRN requesting that GSME accepts Credit.
3742
7.5.5
3743
3744
A PPMID shall be capable of generating and issuing to ESME the Commands set out in this
Section 7.5.5.
3745
7.5.5.1
3746
A Command requesting that ESME Activates Emergency Credit.
Remove Device Security Credentials
Replace PPMID Security Credentials
User Interface Commands
Activate ESME Emergency credit
Activate GSME Emergency credit
Add Credit to ESME
Add Credit to GSME
Enable ESME Supply
HAN Interface Commands issued by PPMID to GSME
Request Emergency Credit Activation
Request to Add Credit
HAN Interface Commands issued by PPMID to ESME
Version 1.59
Request Emergency Credit Activation
18 November 2015
Page 94
DRAFT
SMETS
3747
7.5.5.2
Request to Add Credit
3748
A Command including a UTRN requesting that ESME accepts credit.
3749
7.5.5.3
3750
A Command requesting that ESME Enables Supply.
3751
7.6 Data Requirements
3752
3753
This section describes the minimum information which a PPMID shall be capable of holding
in its Data Store.
3754
7.6.1
3755
Data that shall remain constant and unchangeable at all times.
3756
7.6.1.1
3757
3758
A globally unique identifier used to identify the PPMID based on the EUI-64 Institute of
Electrical and Electronic Engineers standard.
3759
7.6.2
This section is not used
3760
7.6.3
Configuration data
3761
Data that configures the operation of various functions of the PPMID.
3762
7.6.3.1
3763
3764
The Security Credentials and Device identity details for each of the Devices with which the
PPMID can communicate.
3765
7.6.3.2
3766
The Security Credentials for the PPMID and parties Authorised to interact with it.
Request to Enable ESME Supply
Constant data
PPMID Identifier
Version 1.59
Device Log
PPMID Security Credentials
18 November 2015
Page 95
DRAFT
SMETS
3769
8 HAN Connected Auxiliary Load
Control Switch Technical
Specifications
3770
8.1 Overview
3771
3772
3773
Section 8 of this document describes the minimum physical, minimum functional, minimum
interface, minimum data and minimum testing and certification requirements of a HAN
Connected Auxiliary Load Control Switch (HCALCS), where it is installed by a Supplier.
3774
8.2 SMETS Testing and Certification Requirements
3775
8.2.1
3776
3777
An HCALCS shall have been tested to ensure that it meets the requirements described in
this Section 8, and evidence must be available to confirm such testing and conformance.
3778
3779
8.2.2
3780
3781
3782
An HCALCS shall meet the requirements described in the current version of the Great
Britain Companion Specification meaning v0.8.2 or later as published on the SECAS
website.
3783
3784
3785
An HCALCS shall have been certified by the ZigBee Alliance as compliant with the ZigBee
SEP v1.2 requirements described in the current version of the Great Britain Companion
Specification meaning v0.8.2 or later as published on the SECAS website.
3786
3787
8.2.3
3788
3789
3790
An HCALCS shall meet the requirements described in the current version of the Commercial
Product Assurance Security Characteristic Smart Metering - HAN Connected Auxiliary Load
Control Switch meaning v1.2 or later as published on CESG’s Website.
3791
3792
3793
An HCALCS shall be certified by CESG as compliant with the current version of the
Commercial Product Assurance Security Characteristic Smart Metering - HAN Connected
Auxiliary Load Control Switch meaning v1.2 or later as published on CESG’s Website.
3794
8.3 Physical Requirements
3795
An HCALCS shall as a minimum include the following components:
3767
3768
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
i.
ii.
iii.
iv.
Conformance with the SMETS
Conformance with the Great Britain Companion
Specifications
Conformance with the Commercial Product Assurance
Security Characteristic for GB Smart Metering
a HAN Interface;
a Data Store
an Auxiliary Load Control Switch; and
a Timer.
An HCALCS shall:
v.
permanently display the HCALCS Identifier(8.6.1.1) on the HCALCS.
The HAN Interface of a HCALCS shall be capable of joining a ZigBee SEP v1.2 Smart
Metering Home Area Network which:
vi.
vii.
operates within the 2400 – 2483.5 MHz harmonised frequency band; and
supports the Communications Links described in Sections 8.5.1 and 8.5.2.
Version 1.59
18 November 2015
Page 96
DRAFT
3806
3807
3808
3809
3810
3811
SMETS
An HCALCS shall be designed taking all reasonable steps so as to prevent Unauthorised
Physical Access and Unauthorised communications that could compromise the
Confidentiality and / or Data Integrity of:
viii.
ix.
x.
Security Credentials;
Cryptographic Algorithms; and
Firmware and data essential for ensuring its integrity,
3812
stored or executing on the HCALCS.
3813
8.4 Functional Requirements
3814
This section defines the minimum functions that an HCALCS shall be capable of performing.
3815
8.4.1
3816
3817
The Timer shall be capable of measuring a configurable period of up to 24 hours with a
minimum resolution of 1 minute.
3818
8.4.2
3819
3820
3821
An HCALCS shall be capable of establishing Communications Links via its HAN Interface.
An HCALCS shall be capable of ensuring that the security characteristics of all
Communications Links it establishes meet the requirements described in Section 8.4.4.4.
3822
3823
When any Command addressed to the HCALCS is received via any Communications Link
the HCALCS shall be capable of:
3824
3825
3826
3827
3828
i.
ii.
iii.
Timer
Communications
using the Security Credentials the HCALCS holds, Authenticating to a Trusted
Source the Command;
verifying in accordance with Section 8.4.4.2.3 that the sender of the Command is
Authorised to execute the Command; and
verifying the integrity of the Command.
3829
3830
3831
On failure of any of (i) to (iii) above, the HCALCS shall be capable of discarding the
Command without execution and without either generating or sending a Response, and
generating and sending an Alert to that effect via its HAN Interface.
3832
3833
An HCALCS shall only be capable of addressing a Response to the sender of the relevant
Command.
3834
8.4.2.1
3835
3836
An HCALCS shall be capable of establishing Communications Links via its HAN Interface
with one ESME.
3837
3838
An HCALCS shall only be capable of establishing Communications Links via its HAN
Interface with one ESME with Security Credentials in the Device Log(8.6.2.1).
3839
3840
3841
In establishing the Communications Link, the HCALCS shall be capable of using its own,
unique Security Credentials to enable it to be Authenticated by the ESME.
The HCALCS shall be capable of supporting the following types of Communications Links:
Communications Links with ESME via the HAN interface
3842
3843
i.
ii.
receiving HAN Interface Commands (set out in Section 8.5.1) from ESME; and
sending the Commands (set out in Section 8.5.1.6) to ESME.
3844
8.4.3
3845
3846
An HCALCS shall be capable of retaining all information held in its Data Store at all times,
including on loss of power.
Data storage
Version 1.59
18 November 2015
Page 97
DRAFT
SMETS
3847
8.4.4
Security
3848
8.4.4.1
General
3849
3850
3851
3852
An HCALCS shall be designed taking all reasonable steps to ensure that any failure or
compromise of its integrity shall not compromise the Security Credentials stored on it or
compromise the integrity of any other Device to which it is connected by means of a
Communications Link.
3853
3854
An HCALCS shall be capable of securely disabling Critical Commands other than those
Commands set out in Section 8.5 that are Critical Commands.
3855
8.4.4.2
3856
8.4.4.2.1
3857
The HCALCS shall be capable of securely storing Private Keys.
3858
The HCALCS shall be capable of securely storing Key Agreement values.
3859
8.4.4.2.2
3860
3861
The HCALCS shall be capable of securely storing Security Credentials from Public Key
Certificates including for use in the Cryptographic Algorithms as set out in Section 8.4.4.3.
3862
3863
3864
3865
During any replacement of HCALCS Security Credentials(8.6.2.2) (as set out in Section
8.5.1.3) the HCALCS shall be capable of ensuring that the HCALCS Security
Credentials(8.6.2.2) being replaced remain usable until the successful completion of the
replacement.
3866
8.4.4.2.3
3867
3868
The HCALCS shall be capable of restricting Authorisation to execute Commands according
to Role permissions.
3869
8.4.4.3
3870
The HCALCS shall be capable of supporting the following Cryptographic Algorithms:
3871
3872
3873
3874
3875
i.
ii.
iii.
Security Credentials
HCALCS Private Keys
Public Key Certificates
Role Based Access Control (RBAC)
Cryptographic Algorithms
Elliptic Curve DSA;
Elliptic Curve DH; and
SHA-256.
In creating any Command, the HCALCS shall be capable of applying Cryptographic
Algorithms (alone or in combination) for:
3876
3877
3878
iv.
v.
vi.
3879
8.4.4.4
3880
3881
An HCALCS shall be capable of preventing and detecting, on all of its interfaces,
Unauthorised access that could compromise the Confidentiality and / or Data Integrity of:
3882
3883
3884
i.
ii.
Digital Signature verification;
Hashing; and
Message Authentication.
Communications
Security Credentials whilst being transferred via an interface; and
Firmware and data essential for ensuring its integrity whilst being transferred via an
interface.
3885
8.5 Interface Requirements
3886
3887
This section sets out the minimum required interactions which a HCALCS shall be capable
of undertaking with ESME via its HAN Interface.
Version 1.59
18 November 2015
Page 98
DRAFT
SMETS
3888
8.5.1
3889
3890
An HCALCS shall be capable of executing immediately the Commands set out in this section
following their receipt via its HAN Interface.
3891
8.5.1.1
3892
A Command to add Security Credentials for ESME to the Device Log(8.6.2.1).
3893
3894
In executing the Command, the HCALCS shall be capable of verifying the Security
Credentials.
3895
8.5.1.2
3896
A Command to control the HCALCS, for the time period specified within the Command.
3897
In executing the Command, the HCALCS shall be capable of:
3898
3899
3900
3901
i.
ii.
iii.
HAN Interface Commands
Add Device Security Credentials
Control HAN Connected Auxiliary Load Control Switch
performing the specified control operation for the specified time period;
send a Response detailing the Outcome via its HAN Interface; and
at the end of the control time period, issuing a Request Control of HAN Connected
Auxiliary Load Control Switch(8.5.2.1) to the ESME.
3902
3903
When not subject to control through this Command, the HCALCS shall default its state to
open.
3904
8.5.1.3
3905
3906
A Command to read the value of one or more of the configuration data items set out in
Section 8.6.2.
3907
3908
In executing the Command, the HCALCS shall be capable of sending such value(s) in a
Response via its HAN Interface.
3909
8.5.1.4
3910
A Command to remove Security Credentials for an ESME from the Device Log(8.6.2.1).
3911
8.5.1.5
3912
A Command to replace HCALCS Security Credentials(8.6.2.2) held within the HCALCS.
3913
3914
In executing the Command the HCALCS shall be capable of maintaining the Command’s
Transactional Atomicity.
3915
8.5.1.6
3916
3917
A Command to record one or more new values of the configuration data items set out in
Section 8.6.2.
3918
8.5.2
3919
3920
An HCALCS shall be capable of issuing the Commands set out in this section, receiving
corresponding Responses and, where required by a Response, taking the required actions.
3921
8.5.2.1
3922
3923
A Command requesting that the ESME issues an updated Control HAN Connected Auxiliary
Load Control Switch(5.6.4.1) Command.
3924
3925
An HCALCS shall be capable of issuing this Command after completing the execution of a
Control HAN Connected Auxiliary Load Control Switch(8.5.1.2).
3926
8.6 Data Requirements
3927
3928
This section describes the minimum information which an HCALCS is to be capable of
holding in its Data Store.
Read Configuration Data
Remove Device Security Credentials
Replace HCALCS Security Credentials
Write Configuration Data
HAN Interface Commands issued by an HCALCS to ESME
Version 1.59
Request Control of HAN Connected Auxiliary Load Control Switch
18 November 2015
Page 99
DRAFT
SMETS
3929
8.6.1
Constant Data
3930
Describes data that remains constant and unchangeable at all times.
3931
8.6.1.1
3932
3933
A globally unique identifier used to identify the HCALCS based on the EUI-64 Institute of
Electrical and Electronic Engineers standard.
3934
8.6.2
3935
Data that configures the operation of functions of the HCALCS.
3936
8.6.2.1
3937
3938
The Security Credentials and Device identity details for the ESME with which HCALCS can
communicate.
3939
8.6.2.2
3940
The Security Credentials for the HCALCS and parties Authorised to interact with it.
HCALCS Identifier
Configuration Data
Version 1.59
Device Log
HCALCS Security Credentials
18 November 2015
Page 100
DRAFT
SMETS
3941
9 Glossary
3942
Active Energy
3943
3944
The integral with respect to time of the Active Power in units of watt-hours (Wh) or standard
multiples thereof (for example, kWh).
3945
Active Power
3946
3947
The product of voltage and the in-phase component of alternating current measured in units
of watts (W) or standard multiples thereof (for example, kW).
3948
Aggregate Debt
3949
3950
The sum of all time-based and payment-based debt registers on ESME or GSME operating
in Prepayment Mode.
3951
Aggregate Debt Recovery Rate
3952
3953
The sum of the Time-based Debt Recovery rates on ESME or GSME operating in
Prepayment Mode.
3954
Alarm
3955
A short-lived audible signal.
3956
Alert
3957
3958
A message generated by a Device including in response to a problem or the risk of a
potential problem.
3959
Ambient
3960
The representation of information in a form that can be understood at a glance.
3961
Arm
3962
3963
To establish a state whereby Supply will be Enabled in response to a Command to Enable
Supply; ‘Armed’ and ‘Arming’ shall be construed accordingly.
3964
Authentication
3965
3966
The method used to confirm the identity of entities or Devices wishing to communicate and
‘Authenticated’ and ‘Authenticity’ shall be construed accordingly.
3967
Authorisation
3968
3969
The process of granting access to a resource and ‘Authorised’ shall be construed
accordingly.
3970
Auxiliary Load Control Switch (ALCS)
3971
A switch or other means of controlling a load on the Supply.
3972
Battery
3973
A component that produces electricity from a chemical reaction.
3974
Block Counter
3975
3976
Storage for recording Consumption for the purposes of combined Time-of-use and Block
Pricing.
3977
Block Pricing
3978
3979
A pricing scheme used in conjunction with Time-of-use Pricing where Price varies based on
Consumption over a given time period.
3980
Block Register
Version 1.59
18 November 2015
Page 101
DRAFT
SMETS
3981
3982
A Tariff Register for recording Consumption for the purposes of combined Time-of-use and
Block Pricing.
3983
Block Tariff
3984
A Tariff for Block Pricing.
3985
Certificate
3986
3987
An electronic document that binds an identity, and possibly other information, to a Public
Key.
3988
Certificate Signing Request
3989
A message requesting the issue of a Certificate by a Certification Authority.
3990
Certification Authority (CA)
3991
A trusted entity which issues Certificates.
3992
CESG
3993
The UK Government's national technical authority for information assurance.
3994
Clock
3995
A timing mechanism that has a minimum resolution of 1 second.
3996
Command
3997
An instruction to perform a function received or sent via any interface.
3998
Commercial Product Assurance Security Characteristics for GB Smart Metering
3999
4000
4001
The documents forming part of the Smart Energy Code describing the requirements for
evaluation and certification of ESME, GSME, HCALCS and Communications Hubs under
CESG’s Commercial Product Assurance scheme.
4002
Communications Hub Date and Time
4003
4004
The date and time held on the Communications Hub as described at Section 4 in the
Communications Hub Technical Specifications.
4005
Communications Hub Physical Interface
4006
A physical interface to connect to the Communications Hub.
4007
Communications Hub Date and Time
4008
The date and time provided by the Communication Hub
4009
Communications Hub Technical Specifications (CHTS)
4010
4011
The document designated by the Secretary of State to describe the minimum capabilities of
communications hubs.
4012
Communications Link
4013
4014
4015
The exchange of Commands, Responses, Alerts and other information between a system or
Device and another system or Device which is independent of the transport mechanism
used.
4016
Confidentiality
4017
4018
The state of information, in transit or at rest, where there is assurance that it is not
accessible by Unauthorised parties through either unintentional means or otherwise.
4019
Consumer
4020
A person who lawfully resides at the Premises that is being Supplied.
Version 1.59
18 November 2015
Page 102
DRAFT
SMETS
4021
Consumption
4022
4023
In the context of GSME Gas Consumption and in the context of ESME Electricity
Consumption.
4024
Contact Details
4025
4026
The name and contact telephone number of the current gas or electricity Supplier (as
appropriate).
4027
Credit Mode
4028
4029
A mode of operation of GSME or ESME whereby Consumers are billed for some or all of
their Consumption retrospectively.
4030
Critical Commands
4031
4032
Those Commands which relate to Supply being affected, financial fraud or the compromise
of the security of Devices in Consumer Premises.
4033
Cryptographic Algorithm
4034
4035
4036
An algorithm for performing one or more cryptographic functions which may include:
Encryption, Decryption, Digital Signing or Hashing of information, data, or messages; or
exchange of Security Credentials.
4037
Currency Units
4038
The units of monetary value in major and minor units.
4039
Customer Identification Number
4040
4041
A number used to verify that an individual requesting a service is present in the Consumer
Premises.
4042
Data Integrity
4043
4044
The state of data where there is assurance that it has not been altered by Unauthorised
parties.
4045
Data Store
4046
An area of a Device capable of storing information for future retrieval.
4047
Day
4048
The period commencing 00:00:00 Local Time and ending at the next 00:00:00.
4049
Day Profile
4050
4051
4052
4053
4054
For the purposes of Time-of-use Pricing and Time-of-use with Block Pricing, the rules
defined in a Switching Table specifying the Tariff Register to which Consumption is allocated
for the day (in the context of GSME Time-of-use Pricing and Time-of-use with Block Pricing)
and for each half-hour period within the day (in the context of the ESME Time-of-use Pricing
and Time-of-use with Block Pricing).
4055
4056
4057
4058
For the purposes of setting the commanded state of Auxiliary Load Control Switches or HAN
Connected Auxiliary Load Control Switches, the rules defined in a Switching Table
specifying the commanded state of each Auxiliary Load Control Switch or HAN Connected
Auxiliary Load Control Switch, for all times within the day.
4059
4060
For the purposes of Non-Disablement Periods the rules defined in a Switching Table
specifying the times during the day when a Non-Disablement Period is active.
4061
Debt Register
4062
Storage for recording an amount of debt to be recovered.
Version 1.59
18 November 2015
Page 103
DRAFT
SMETS
4063
Debt to Clear
4064
4065
The amount of credit the consumer needs to add to ESME or GSME to cause the Meter
Balance to rise to the disablement threshold when operating in Prepayment Mode.
4066
Decryption
4067
4068
The process of converting Encrypted information by an Authorised party to recover the
original information and like terms shall be construed accordingly.
4069
Device
4070
GSME, ESME, a GPF, a CHF, a Type 1 Device or a Type 2 Device.
4071
4072
Device Language Message Specification (DLMS) Companion Specification for Energy
Metering (COSEM)
4073
4074
The Green Book (DLMS User Association 1000-2 Edition 8) and the Blue Book (DLMS User
Association 1000-1 Edition 12.0).
4075
Digital Signature
4076
4077
4078
4079
The piece of information appended to a message which is created using the sender’s Private
Key, can be verified using the Public Key contained in the sender's Certificate and provides
the receiver with assurance that the sender is who they claim to be, the message is as sent
by the sender and that the sender sent the message.
4080
Digital Signing
4081
The creation of a Digital Signature.
4082
Disable
4083
4084
4085
In the context of GSME the act of interrupting the flow of gas by closing the Valve and in the
context of ESME the act of interrupting the flow of electricity by opening the Load Switch(es)
and like terms shall be construed accordingly.
4086
Domestic Premises
4087
4088
4089
Shall in the context of GSME have the meaning given to that term in standard condition 1 of
gas supply licences, and in the context of ESME shall have the meaning given to that term in
standard condition 1 of electricity supply licences.
4090
Electricity Consumption
4091
4092
The Active Energy Imported into the Premises and ‘Consumed’ shall be construed
accordingly.
4093
Electricity Meter
4094
4095
An instrument used to measure, store and display the amount of electrical energy passing
through an electrical circuit or circuits.
4096
Elliptic Curve DH
4097
4098
The Elliptic Curve Diffie–Hellman Algorithm forming part of the NSA Suite B standard (see
http://www.nsa.gov/ia/programs/suiteb_cryptography/index.shtml).
4099
Elliptic Curve DSA
4100
4101
The Elliptic Curve Digital Signature Algorithm forming part of the NSA Suite B standard (see
http://www.nsa.gov/ia/programs/suiteb_cryptography/index.shtml).
4102
Emergency Credit
4103
4104
Credit that can be made available to ensure that the Supply is not interrupted in
circumstances (including situations of emergency) defined by the Supplier to the Premises.
Version 1.59
18 November 2015
Page 104
DRAFT
SMETS
4105
Enable
4106
4107
4108
In the context of GSME the act of restoring the flow of gas to the Premises by opening the
Valve and in the context of ESME the act of restoring the flow of electricity to the Premises
by closing the Load Switch and like terms shall be construed accordingly.
4109
Encryption
4110
4111
The process of converting information in order to make it unintelligible other than to
Authorised parties and like terms shall be construed accordingly.
4112
Energy Consumption
4113
The amount of gas in kWh or electricity in kWh Supplied to the Premises.
4114
ESME
4115
Electricity Smart Metering Equipment.
4116
Export
4117
The flow of electricity out of the Premises, and like terms shall be construed accordingly.
4118
Firmware
4119
The embedded software programmes and / or data structures that control Devices.
4120
Gas Consumption
4121
4122
The volume of gas in cubic metres (m3) Supplied to the Premises and ‘Consumed’ shall be
construed accordingly.
4123
Gas Meter
4124
4125
An instrument designed to measure, memorise and display the quantity of gas (volume or
mass) that has passed through it.
4126
Gas Proxy Function
4127
Gas Proxy Function as defined in the Communications Hub Technical Specifications.
4128
Great Britain Companion Specification
4129
4130
4131
4132
The document forming part of the Smart Energy Code describing nature of Communications
Links that ESME, GSME, HCALCS, IHD and PPMID must be capable of forming via their
HAN Interfaces. The current version of Great Britain Companion Specification can be found
here: https://www.smartenergycodecompany.co.uk/sec/the-developing-sec
4133
GSME
4134
Gas Smart Metering Equipment.
4135
Hashing
4136
4137
A repeatable process to create a fixed size and condensed representation of a message of
any arbitrary data. Hash and like terms shall be construed accordingly.
4138
HCALCS
4139
HAN Connected ALCS, which is a Type 1 Device.
4140
HCALCS Technical Specifications
4141
4142
The document brought into force by the Secretary of State to describe the minimum
capabilities of equipment installed to satisfy the HCALCS licence conditions.
4143
Home Area Network Interface (HAN Interface)
4144
4145
A component of GSME, ESME, IHD or other Device that is capable of sending and receiving
information to and from other Devices.
Version 1.59
18 November 2015
Page 105
DRAFT
SMETS
4146
Key
4147
Data used to determine the output of a cryptographic operation.
4148
Key Agreement
4149
A means to calculate a shared Key between two parties.
4150
IHD
4151
In-home Display.
4152
IHD Source Device
4153
ESME or the Gas Proxy Function.
4154
IHD Technical Specifications
4155
4156
The document brought into force by the Secretary of State to describe the minimum
capabilities of equipment installed to satisfy the IHD licence conditions.
4157
Import
4158
The flow of electricity into the Premises, and like terms shall be construed accordingly.
4159
Load Switch
4160
4161
A component or combination of components that can close or open (including on receipt of a
Command to that effect) to Enable or Disable the flow of electricity to and from the Premises.
4162
Local Time
4163
The UTC date and time adjusted for British Summer Time.
4164
Lock
4165
4166
4167
To establish a state whereby the Supply is Disabled and can only be Enabled or Armed in
response to a Command to Arm or Enable the Supply; ‘Locked’ and ‘Locking’ shall be
construed accordingly.
4168
Message Authentication
4169
4170
The process by which the receiver of a message is provided with assurance that the sender
is who they claim to be and that the message is in the form originally sent.
4171
MPAN
4172
Meter Point Administration Number.
4173
MPRN
4174
Meter Point Reference Number.
4175
Non-Disablement Period
4176
4177
4178
A period of time during which the combined credit of the meter balance and Emergency
Credit balance falling below the disablement threshold will not be cause the Supply to be
Disabled when ESME or GSME is operating in Prepayment Mode.
4179
Outcome
4180
The result of executing a Command, expressed as success or failure.
4181
Payment-based Debt Recovery
4182
A means of recovering debt based on a percentage of a payment.
4183
Personal Data
4184
4185
Any information comprising Personal Data as such term is defined in the Data Protection Act
1998 at the date the SMETS is brought into force.
Version 1.59
18 November 2015
Page 106
DRAFT
SMETS
4186
Polyphase Electricity Metering Equipment
4187
4188
Electricity metering equipment containing three measuring elements suitable for a polyphase
Supply with up to three phases and neutral.
4189
PPMID Technical Specifications
4190
4191
The document brought into force by the Secretary of State to describe the minimum
capabilities of equipment installed to satisfy the PPMID licence conditions.
4192
Prepayment Interface Device (PPMID)
4193
4194
A Type 1 Device that provides a User Interface for Prepayment Mode related information
and Commands.
4195
Prepayment Top-up Transaction (PTUT)
4196
4197
A cryptographic code used to convey credit to GSME or ESME operating in Prepayment
Mode.
4198
Premises
4199
The premises which is Supplied.
4200
Prepayment Mode
4201
4202
A mode of operation of GSME or ESME whereby payment is generally made in advance of
Consumption.
4203
Price
4204
4205
The amount of money in Currency Units charged for one kWh unit of gas Consumed for
GSME or one kWh of electricity Consumed via the relevant measuring element for ESME.
4206
Privacy PIN Protection
4207
4208
The prevention of the display of information and access to Commands on the User Interface
of GSME or ESME.
4209
Private Key
4210
4211
The Key in a Public-Private Key Pair which must be kept secure by the entity to which it
relates.
4212
PTUT Counter
4213
A number derived from a PTUT or a UTRN.
4214
Public Key
4215
The Key in a Public-Private Key Pair which can be distributed to other parties.
4216
Public-Private Key Pair
4217
Two mathematically related numbers that are used in Cryptographic Algorithms.
4218
Random Number Generator
4219
4220
A component used to generate a sequence of numbers or symbols that lack any predictable
pattern.
4221
Reactive Energy
4222
4223
The integral with respect to time of Reactive Power in units of volt-amperes reactive-hours
(varh) or standard multiples thereof (for example, kvarh).
4224
Reactive Power
4225
4226
The product of voltage and the out of phase component of current measured in units of voltamperes reactive (var) or standard multiples thereof (for example, kvar).
Version 1.59
18 November 2015
Page 107
DRAFT
SMETS
4227
Replay Attack
4228
4229
A form of attack on a Communications Link in which a valid information transmission is
repeated through interception and retransmission.
4230
Response
4231
4232
Sent on, or received from the User Interface or HAN Interface or any other interface
containing information in response to a Command.
4233
RMS
4234
Root mean squared.
4235
Role
4236
The entitlement of a party to execute one or more Commands.
4237
Season Profile
4238
Rules defined in a Switching Table specifying a Week Profile for each week of a season.
4239
SECAS
4240
The Smart Energy Code Administrator and Secretariat.
4241
Secure Perimeter
4242
A physical border surrounding GSME, ESME or the PPMID.
4243
Security Credentials
4244
Information used to identify and / or Authenticate a Device, party or system.
4245
Sensitive Event
4246
Each of the following events:
4247

a failed Authentication or Authorisation;
4248

a change in the executing Firmware version; and
4249

unusual numbers of malformed, out-of-order or unexpected Commands received.
4250
SHA-256
4251
4252
The Hashing algorithm of that name approved by the NIST (see
http://csrc.nist.gov/groups/ST/toolkit/secure_hashing.html).
4253
Single Electricity Metering Equipment
4254
Electricity metering equipment containing a single measuring element.
4255
Smart Metering Equipment Technical Specifications (SMETS)
4256
4257
The document brought into force by the Secretary of State to describe the minimum
capabilities of equipment installed to satisfy the roll-out licence conditions.
4258
Smart Metering Home Area Network
4259
A communications network allowing the exchange of information between Devices.
4260
Special Day
4261
4262
4263
4264
A day defined in a Switching Table where allocation to Tariff Registers, setting the
commanded state of Auxiliary Load Control Switches or HAN Connected Auxiliary Load
Control Switches, or specifying Non-Disablement Periods is based on a specified Day
Profile.
4265
Supplier
Version 1.59
18 November 2015
Page 108
DRAFT
SMETS
4266
4267
A person authorised by licence to Supply gas to Premises for GSME and a person
authorised by licence to Supply electricity to Premises for ESME.
4268
Supply
4269
4270
The supply of gas to Premises for GSME and the supply of electricity to Premises for ESME
and ‘Supplied’ shall be construed accordingly.
4271
Switching Table
4272
Separate rules for:
4273

allocating Consumption to Tariff Registers for the purposes of Time-of-use Pricing;
4274
4275

setting the commanded state of Auxiliary Load Control Switches or HAN Connected
Auxiliary Load Control Switches; and
4276

the purposes of specifying Non-Disablement Periods.
4277
Tariff
4278
The structure of Prices and other charges relating to a Supply.
4279
Tariff Register
4280
Storage for recording Consumption for the purposes of Time-of-use Pricing.
4281
Time-based Debt Recovery
4282
A means of recovering debt based on an amount in Currency Units per unit time.
4283
Time-of-use Band
4284
4285
A contiguous or non-contiguous number of Days for GSME or half-hour periods for ESME
over which Tariff Prices are constant.
4286
Time-of-use Pricing
4287
A pricing scheme with one or more Time-of-use Bands.
4288
Time-of-use Tariff
4289
A Tariff for Time-of-use Pricing.
4290
Timer
4291
A mechanism for measuring a time period.
4292
TOU
4293
Time-of-use.
4294
Transactional Atomicity
4295
The type and order of the constituent parts of a Command.
4296
Trusted Source
4297
A source whose identity is confidentially and reliably validated.
4298
Twin Element Electricity Metering Equipment
4299
Electricity metering equipment containing two measuring elements.
4300
Type 1 Device
4301
4302
4303
A Device, other than GSME, ESME, Communications Hub Function or Gas Proxy Function,
that stores and uses the Security Credentials of other Devices for the purposes of
communicating with them via its HAN Interface.
4304
Type 2 Device
Version 1.59
18 November 2015
Page 109
DRAFT
SMETS
4305
4306
A Device that does not store or use the Security Credentials of other Devices for the
purposes of communicating with them via its HAN Interface.
4307
Unauthorised
4308
Not Authorised.
4309
Unauthorised Physical Access
4310
4311
Unauthorised access to the internal components of GSME, ESME or the PPMID through its
Secure Perimeter.
4312
Unique Transaction Reference Number (UTRN)
4313
A truncated PTUT.
4314
Unlocked
4315
4316
To establish a state whereby the state of the Supply is determined by GSME or ESME;
‘Unlocked’ and ‘Unlocking’ shall be construed accordingly.
4317
User Interface
4318
4319
An interface for providing local human interaction with GSME, ESME, IHD or PPMID which
supports input and visual output.
4320
UTC
4321
Coordinated Universal Time.
4322
Valve
4323
4324
A component that can open or close (including on receipt of a Command to that effect) to
Enable or Disable the flow of gas to Premises.
4325
Week
4326
4327
The seven day period commencing 00:00:00 Monday Local Time and ending at 00:00:00 on
the immediately following Monday.
4328
Week Profile
4329
Rules defined in the Switching Table specifying the Day Profile for each day of a week.
4330
ZigBee Smart Energy Profile (SEP) Version 1.2
4331
4332
The ZigBee Smart Energy Profile Specification 1.2a v1.0 (reference 07-5356r19:
http://zigbee.org/About/GBCSPartner.aspx).
Version 1.59
18 November 2015
Page 110
Crown copyright 2015
Department of Energy & Climate Change
3 Whitehall Place
London SW1A 2AW
www.gov.uk/decc
URN 15D/503