4.4.2 · Retrieve Change Of Mode / Tariff Triggered Billing Data Log

18.17a · Where the target SMETS1 ESME or SMETS1 GSME does not support the recording of the values in the Tariff Block Counter Matrix when actioning a Set Payment Mode or Set Tariff command (with their SMETS meanings), the S1SP shall omit the TariffBlockCounterMatrix element in the SMETS1 Response (with its Message Mapping Catalogue meaning).

18.17b · Where the SMETS1 GSME reports tariff Block Counters (with their SMETS1 meaning) in kWh, the values returned in BlockRegisterMatrixValue or TariffBlockCounterMatrix (with their Message Mapping Catalogue meanings) shall, contrary to Message Mapping Catalogue Sections , 5.23.2.2.4, 6.2.2.4 or 5.27.2.2 be in units of kWh rather than meters cubed.

18.17c · Where the SMETS1 ESME does not report values in these logs for the Tariff Block Counter Matrix (with its SMETS1 meaning), the S1SP shall create a SMETS1 Response with zero occurrences of TariffTOUBlock1RegisterMatrixValue TariffTOUBlock2RegisterMatrixValue TariffTOUBlock3RegisterMatrixValue and TariffTOUBlock4RegisterMatrixValue.

18.17d · Where the target SMETS1 ESME or SMETS1 GSME adds entries to the Billing Data Log (with its SMETS1 meaning) both before and after each triggering event, the SMETS1 Response shall contain details of both entries.

18.17e · Where it is not possible to retrieve all of the values from the target SMETS1 GSMEs log (with its SMETS1 meaning) then, in the SMETS1 Response: (i) The values in TariffTOURegisterMatrixValue or TariffTOURegisterMatrix with indices 1 and 2 will be the values from the Device and the values with indices 3 and 4 will be 0 meaning that the values from the Device cannot be retrieved (with their MMC meanings); and (ii) The value in BlockRegisterMatrixValue or BlockRegisterMatrix with index 1 will be the value from the Device and the values with indices 2, 3 and 4 will be 0 meaning that the values from the Device cannot be retrieved (with their MMC meanings).

18.17f · Where, pursuant to clause 18.42(e), the target SMETS1 GSME has stored additional LogEntries (with its MMC meaning), the SMETS1 Response shall contain details of these extra LogEntries where the period requested includes the corresponding timestamps.

18.17g · Where the time period specified in the Service Request should result in more than one LogEntry being returned from the target SMETS1 GSME, the S1SP shall return a single LogEntry that has a timestamp that is the first entry after the ReadLogPeriod StartDateTime (with their DUIS meanings).

18.17h · Where, pursuant to clauses 18.5(jj) and 18.7(o), the target SMETS1 ESME has stored additional LogEntries (with its MMC meaning), the SMETS1 Response shall contain details of these extra LogEntries where the period requested includes the corresponding timestamps.

18.17i · Where an Update Import Tariff (Primary Element) (SRV 1.1.1) or Update Payment Mode (SRV 1.6) Service Request has never been successfully executed in relation to the target SMETS1 ESME the S1SP shall return a SMETS1 Alert indicating failure.

18.17j · Where the target SMETS1 ESME does not reset block counters in accordance with the Billing Calendar timetable, the SMETS1 Response will contain Block Counters (with their SMETS1 meanings) that are always increasing in value and are never reset.

18.17k · Where the target SMETS1 ESME or SMETS1 GSME adds entries to the Billing Data Log (with its SMETS1 meaning) before the triggering event, the SMETS1 Response shall, where an Update Import Tariff (Primary Element) (SRV 1.1.1) has never been executed since the DateCommissioned (with its DUIS meaning), only contain details of consumption based on the tariff configuration that was configured before the Update Import Tariff (Primary Element) (SRV 1.1.1) was executed on the Device.

18.17l · Where the target SMETS1 ESME does not store any items within the Billing Data Log (with its SMETS1 meaning) when executing Update Price (Primary Element) (SRV 1.2.1), the SMETS1 Response shall not contain any LogEntries (with its MMC meaning) as a result of any execution of the Update Price (Primary Element) (SRV 1.2.1) Service Request.

18.17m · Where the target SMETS1 ESME supports a maximum of four or Eight Tariff Registers (with their SMETS1 meaning) then any SMETS1 Response will only contain consumption in either the first four or the first eight entries of the TariffTOURegisterMatrixValue (with its MMC meaning).

18.17n · Where the target SMETS1 ESME adds entries to the Billing Data Log (with its SMETS1 meaning) at midnight every day, the SMETS1 Response shall contain details of these extra LogEntries (with its MMC meaning) where the period requested includes the corresponding timestamps.

18.17o · Where the target SMETS1 GSME does not allow the reading of Operational data when performing an update to the Configuration data (with their SMETS1 meanings) then the SMETS1 response will return zero LogEntries (with its MMC meaning) where the device is still updating its Configuration data (with its SMETS1 meaning).