UK Smart MeteringKnowledge ProjectStructured SRV and specimen referenceBrowse SRVs

SMETS1 Supporting Requirements

4.4.3 · Retrieve Billing Calendar Triggered Billing Data Log

Section 18 requirements joined to the Device Model Variations to Equivalent Steps Matrix.

How the data is joined

Source model and interpretation

The matrix identifies one or more Section 18 references in column B and one or more SRVs in column C. Where a row lists several references, this page uses the PDF section owner to select the reference for the current SRV. A single reference explicitly listed with several SRVs is treated as applying to each of those SRVs. Only profiles marked x are displayed below; the complete source status remains preserved in the generated data.

x · Affectedn/a · Not applicablep · PPMID onlyText · Conditional noteBlank · No variation recorded
Requirements source
SEC-Appendix-AM-SMETS1-Supporting-Requirements-v17.0.pdf · v17.0 · Section 18, PDF pages56–110
Matrix source
SEC-Appendix-AM-Annex-A-Device-Model-Variations-to-Equivalent-Steps-Matrix-v12.4.xlsx · v12.4 · worksheetDMVES

Annex A matrix

Device-model applicability

Select one or more values in each filter. Values within a filter are matched as OR; different filters are combined as AND against the same device combination. Options that cannot match the selections in the other filters are disabled automatically.

Manufacturer
Device Type
Model
Firmware

18.18a · source row 163

Retrieve Billing Calendar Triggered Billing Data Log

18.18a · The provisions of Clauses 18.17 18.17(b) to 18.17(c) apply to this Service Request

Affected device and firmware combinations

Manufacturer
Honeywell
Device Type
ESME
Model
AS300P
Firmware
ASP 04.04.01-55497
Manufacturer
Honeywell
Device Type
ESME
Model
AS300P
Firmware
ASP 04.04.01-60250
Manufacturer
Itron
Device Type
GSME
Model
RF1 Sv ZB
Firmware
012-00.292/10D6
Manufacturer
Landis+Gyr
Device Type
GSME
Model
G470
Firmware
xxxxxxxxx

18.18b · source row 164

Retrieve Billing Calendar Triggered Billing Data Log

18.18b · Where the target SMETS1 ESME or SMETS1 GSME may record such Billing Data Log (with its SMETS1 meaning) entries after midnight UTC even when the Billing Calendar (with its SMETS1 meaning) specifies midnight UTC then the SMETS1 Response may contain Timestamps (with their MMC meanings) reflecting the delayed recording.

Affected device and firmware combinations

Manufacturer
Secure Meters
Device Type
ESME
Model
Liberty 100 (with aux)
Firmware
P4X9G01
Manufacturer
Secure Meters
Device Type
GSME
Model
EG4v11
Firmware
Q4X2G0E

18.18c · source row 165

Retrieve Billing Calendar Triggered Billing Data Log

18.18c · The provision of Clause 18.17 18.17(b) apply to this Service Request

Affected device and firmware combinations

Manufacturer
Landis+Gyr
Device Type
GSME
Model
G470
Firmware
xxxxxxxxx

18.18d · source row 166

Retrieve Billing Calendar Triggered Billing Data Log

18.18d · Where, pursuant to clause 18.42(e), the target SMETS1 GSME has stored LogEntries (with its MMC meaning) at different date-times than required by the Billing Calendar (with its SMETS1 meaning), the SMETS1 Response shall contain corresponding LogEntries.

Affected device and firmware combinations

Manufacturer
Landis+Gyr
Device Type
GSME
Model
G470
Firmware
xxxxxxxxx

18.18e · source row 167

Retrieve Billing Calendar Triggered Billing Data Log

18.18e · The provisions of Clause 18.17(g) apply to this Service Request.

Affected device and firmware combinations

Manufacturer
Landis+Gyr
Device Type
GSME
Model
G470
Firmware
xxxxxxxxx

18.18f · source row 168

Retrieve Billing Calendar Triggered Billing Data Log

18.18f · The provisions of Clause 18.21(e) apply to this Service Request.

Affected device and firmware combinations

Manufacturer
Landis+Gyr
Device Type
GSME
Model
G470
Firmware
xxxxxxxxx

18.18g · source row 169

Retrieve Billing Calendar Triggered Billing Data Log

18.18g · Where an Update Device Configuration (Billing Calendar) (SRV 6.8) Service Request has never been successfully executed in relation to the target SMETS1 ESME the S1SP shall return a SMETS1 Alert indicating failure.

Affected device and firmware combinations

Manufacturer
Landis+Gyr
Device Type
GSME
Model
G470
Firmware
xxxxxxxxx

18.18h · source row 170

Retrieve Billing Calendar Triggered Billing Data Log

18.18h · The provisions of Clause 18.17(j) also apply to this Service Request.

Affected device and firmware combinations

Manufacturer
Landis+Gyr
Device Type
ESME
Model
E470
Firmware
xxxxxxx

18.18i · source row 171

Retrieve Billing Calendar Triggered Billing Data Log

18.18i · The provisions of Clause 18.17(m) also apply to this Service Request.

Affected device and firmware combinations

Manufacturer
Honeywell
Device Type
ESME
Model
AS300P
Firmware
ASP 04.04.01-55497
Manufacturer
Honeywell
Device Type
ESME
Model
AS300P
Firmware
ASP 04.04.01-60250

18.18j · source row 172

Retrieve Billing Calendar Triggered Billing Data Log

18.18j · The provisions of Clause 18.17(n) also apply to this Service Request.

Affected device and firmware combinations

Manufacturer
Honeywell
Device Type
ESME
Model
AS300P
Firmware
ASP 04.04.01-55497
Manufacturer
Honeywell
Device Type
ESME
Model
AS300P
Firmware
ASP 04.04.01-60250
Manufacturer
Itron
Device Type
ESME
Model
EM425-UK
Firmware
03.00.03.46/53.17

18.18k · source row 173

Retrieve Billing Calendar Triggered Billing Data Log

18.18k · The provisions of Clause 18.17(o) also apply to this Service Request.

Affected device and firmware combinations

Manufacturer
Honeywell
Device Type
GSME
Model
BK-G4E EI2
Firmware
0.10.94

18.18l · source row 174

Retrieve Billing Calendar Triggered Billing Data Log

18.18l · Where the SMETS1 ESME has, according to the EPCL, a GroupID = “EA” (with its EPCL meaning) then the SMETS1 Response shall not contain any LogEntries (with its MMC meaning) where the SMETS1 ESME has been configured with an ElectricityBillingCalendar Periodicity of Daily (with their DUIS meanings).

Affected device and firmware combinations

Manufacturer
Landis+Gyr
Device Type
ESME
Model
E470
Firmware
xxxxxxx