CONSULTATION. DCC User Interface Specification (DUIS) Message Mapping Catalogue (MMC)

Transcription

1 CONSULTATION DCC User Interface Specification (DUIS) Message Mapping Catalogue (MMC) GBCS v0.8.1-aligned versions Consultation opens: 27 March 2015 Consultation closes: 24 April 2015 DCC Public Page 1 of 26

2 Contents 1 Executive summary Overview of DUIS and the MMC Scope of the DUIS and the MMC Scope of this consultation Consultation Part A: DCC User Interface Specification (DUIS) DUIS overview Overview of DUIS changes Service Request definition changes Tariffs and Price Billing Calendar Read Billing Data Log ALCS and HCALCS Low impact changes Future Dated Device processing pattern changes Alert recipients Other changes to DUIS Service Request renaming Changes to the format of Service Reference Variant description Service Reference Variant 8.4 Update Inventory Service Reference Variant 6.22 ConfigureAlertBehaviour Service Reference Variant Retrieve Device Security Credentials (Device) Definition of Service Requests Consultation Part B: Message Mapping Catalogue (MMC) MMC Overview DCC Public Page 2 of 26

3 4.2 Overview of MMC amendments Service Responses and Alerts requiring significant amendments Tariffs and Prices Read Billing Data Log Responses relating to ALCS and HCALCS Billing Calendar Other changes to MMC How to respond Referenced Documents Appendix A Summary of DUIS amendments Appendix B Summary of MMC amendments Appendix C Consequential changes to DUIS if change proposed in section 3.4 of this consultation is implemented DCC Public Page 3 of 26

4 1 Executive summary The Data and Communications Company (DCC) is committed to a safe and secure smart metering environment to allow all electricity and gas consumers in Great Britain to enjoy the benefits of being in control of their energy usage. A critical part of the smart metering environment relates to how communications are managed to and from smart metering devices (via the DCC User Interface). The DCC User Interface Specification (DUIS) sets out the technical details of the DCC User Interface, which is the means by which Users interact with Devices. Communications from Devices are received by the User via the DCC User Interface, in a format as set out in the Great Britain Companion Specification (GBCS). The Message Mapping Catalogue (MMC) specifies the translation of data created by Devices in GBCS format, into a format that is standardised and interpretable (the MMC Output Format ). The DUIS and the MMC were initially developed to align with GBCS v0.8, issued for consultation, updated following consultation responses and submitted to the Secretary of State as complete, interim GBCS v0.8-aligned, draft SEC Subsidiary Documents. This consultation relates to updates to the DUIS and the MMC made primarily in response to updates emerging from GBCS v0.8 to v GBCS v0.8.1 was accepted into the Technical and Business Design Group (TBDG) document baseline on 26 November 2014, together with updated versions of SMETS 2 (v1.58) and CHTS 3 (v1.46). These versions will be used as the basis of System Integration Testing (SIT) and, as such, it is necessary for the DUIS to be updated to align to GBCS v In this context, stakeholders should understand that the GBCS describes the detailed requirements for communications between Smart Metering Devices in consumers premises, and between Smart Metering Devices and DCC. Additionally, stakeholders should note that GBCS v0.8.1 builds on GBCS v0.8 to: reduce potential ambiguity by incorporating clarifications and amplifications arising from the consultation and other stakeholder queries; address identified defects; and maintain alignment with SMETS and CHTS. These changes to GBCS are significant enough to warrant a further consultation on the consequential changes required to the DUIS and the MMC. Stakeholders are advised that DCC is not consulting on GBCS v0.8.1, as it is already included in the TBDG baseline. DCC would add that the production and maintenance of GBCS (and consultations on it) is a matter for the Department of Energy and Climate Change (DECC). 1 Issued 28 November 2014 and can be found here. 2 Smart Metering Equipment Technical Specifications. 3 Communications Hub Technical Specifications. DCC Public Page 4 of 26

5 Stakeholders are reminded that both DUIS and MMC have previously been the subject of consultations, so this consultation relates specifically to the changes which are necessary to the DUIS and MMC to align to GBCS v0.8.1, along with a limited number of clarifications identified since the previous DUIS/MMC consultations. In addition, we have identified an issue in the previous version of DUIS submitted to the Secretary of State, in respect of the definition of five Service Requests, upon which the DCC is now seeking stakeholders views on whether not to make these Critical Service Requests available to Users via the Future Dated Response Pattern (DSP) mode of operation. We present drafting for both options and invite views. This consultation paper: provides an overview of the changes to DUIS and the MMC in response to the GBCS updates from v0.8 to v0.8.1, along with other changes that are not directly as a result of GBCS changes; asks pertinent questions on the changed content of the DUIS and MMC to guide and assist stakeholders in reviewing the documents, and to which DCC would welcome responses; and informs stakeholders of how to respond and by when. Following this consultation, and taking respondents feedback into account, the GBCS aligned DUIS and the MMC will be submitted to the Secretary of State for approval as being fit for inclusion in the Smart Energy Code (SEC) and posted on the DCC website for information. Once approved, the DUIS and the MMC will subsequently be designated as SEC Subsidiary Documents. DCC Public Page 5 of 26

6 2 Overview of DUIS and the MMC 2.1 Scope of the DUIS and the MMC The DUIS defines the DCC User Interface, covering communications from Users via DCC to Devices (using Service Requests), and from Devices via DCC to Users (using Service Responses, Device Alerts and DCC Alerts). The DUIS details the format of all Service Requests, Service Responses, Device Alerts and DCC Alerts. The MMC details the MMC Output Format: a standard and interpretable format based on the corresponding GBCS format for the relevant subset of Service Responses and Device Alerts. Translation of messages from GBCS format to MMC Output Format can be performed by the Parse and Correlate Software (provided by DCC) or by alternative systems. The DUIS and the MMC each include an XML Schema, defining the XML elements that are relevant to either the DCC User Interface (for the DUIS) or the MMC Output Format (for the MMC). 2.2 Scope of this consultation The scope of this consultation is to review the DUIS and the MMC for alignment with GBCS v The DUIS and the MMC, as aligned to GBCS v0.8, were issued separately for consultation on 31 October 2014 and 22 December 2014 respectively. Revised versions following the consultation were produced by DCC, submitted to the Secretary of State on 29 January 2015 and 2 March 2015 respectively and are published on the DCC website. In response to feedback on the GBCS v0.8-aligned versions of DUIS and MMC, DCC is consulting on these documents together to assist stakeholders understanding of the totality of changes. The consultation is split into two parts: Part A of the consultation (section 0 of this document) covers the DUIS; and Part B of the consultation (section 4 of this document) covers the MMC. These consultation versions of the DUIS and the MMC have been drafted to reflect DCC s understanding of the latest SEC drafting that is being developed by DECC. DCC understands that DECC will be consulting on the provisions of new SEC Subsidiary Documents under sections H4, H5 and H6 of the SEC in due course. Further information regarding the scope of this Government consultation can be found in DECC s March 2015 SEC Government Response. Questions regarding the content and timing of this consultation should be directed to DECC. DCC Public Page 6 of 26

7 3 Consultation Part A: DCC User Interface Specification (DUIS) 3.1 DUIS overview DUIS places rights and obligations on DCC and Users in respect of access to, and the use of, the DCC User Interface. DUIS provides information to enable prospective DCC Users to integrate their IT infrastructure with DCC Systems, request services from DCC, and operate their Smart Metering Devices, via Service Requests and Signed Pre-Commands. It further sets out the manner in which Users will receive Service Responses, Device Alerts and DCC Alerts. The DUIS includes elements relating to: the DUIS interface to DCC Systems, and the mechanisms by which connections over the interface are established and maintained; web service definitions including how messages are sent and received by prospective Users, their defined structure and content; access controls in relation to the authentication, validation and authorisation checks made on messages sent and received by prospective Users; and the DUIS XML Schema which details all of the XML elements that can be used within Service Requests. DCC has worked closely with parties and DECC to develop the DUIS through regular DCC Design Forum meetings. With respect to this consultation, DCC has held two DCC Design Forums 4, at which the planned changes to the DUIS as a result of the uplift of GBCS from v0.8 to v0.8.1 were presented and discussed. Sections 3.2 and 3.3 outline the changes made to DUIS, either as a result of the updates to GBCS from v0.8 to v0.8.1, or to address issues or errors identified. A summary of all changes made to the consultation version of DUIS to align with GBCS is provided in Appendix A to this document. The extent of the changes can be broadly categorised as high, medium and low impact, as follows: high new or substantially re-written functional requirements; medium structural changes to existing functionality or definition changes; low minor amendments, typographical corrections etc February 2015 and 11 March DCC Public Page 7 of 26

8 3.2 Overview of DUIS changes The changes made to the DUIS can be categorised into three main areas: Section of this document outlines changes to DUIS Service Request definitions which result from changes to Use Case definitions in GBCS v0.8.1 (see section 3.8 of the DUIS); Section of this document outlines changes to processing patterns; and Section of this document describes the addition of new Device Alerts for receipt by the Access Control Broker Service Request definition changes In total, GBCS v0.8.1 included changes to 62 Use Cases (out of 166), although not all of these impact Users via the DCC User Interface. Service Requests with high or medium impacts are described under functional headings in sections to below Tariffs and Price All tariff and price Use Cases have been substantially changed and updated within GBCS v0.8.1, which has resulted in changes to the associated Service Request Definitions in the DUIS. In addition, a new Use Case has been introduced for ECS01d Set Price on ESME Secondary Element, resulting in the addition of a new Service Reference Variant ( UpdatePrice(SecondaryElement)). The affected Service Reference Variants are: UpdateImportTariff(Primary Element) UpdateImportTariff(SecondaryElement) UpdatePrice(Primary Element) UpdatePrice(SecondaryElement) Billing Calendar Changes have been made to the Billing Calendar data items within GBCS Use Cases ECS30 and GCS25, to align the data items between fuel types for Electricity and Gas. This has resulted in corresponding DUIS changes to align Service Request Definitions items between fuel types for Electricity and Gas, to create a more common format for Users of the DCC User Interface. Service Reference Variants affected are: 6.8 UpdateDeviceConfiguration(BillingCalendar) Read Billing Data Log DUIS v0.8 exposed Service Request 4.4 (Retrieve Billing Data Log) to Users via five separate Service Reference Variants, to match the GBCS Use Case definitions contained within GBCS v0.8. DCC Public Page 8 of 26

9 GBCS v0.8.1 makes changes to the associated Use Cases for these Service Requests with the aim of aligning Use Case functionality between fuel types for Electricity and Gas in Use Cases ECS20 and GCS15 and all sub-variants (i.e. a, b, c). The Electricity Use Cases in GBCS v0.8.1 have been updated to align with equivalent Gas Use Cases. This has resulted in changes in the DUIS to reflect the new alignment and Use Case definitions: Service Reference Variant (Retrieve Debt and Credit Billing Data Log) has been removed from DUIS v Service Reference Variant (Retrieve Billing Data Log (Payment Based Debt Payments)). The functionality for this Service Request has been moved such that it is requested via Service Reference Variants and This aligns the functionality between Gas and Electricity using similar GBCS Use Cases. This change includes a new Use Case for ECS20d (Read ESME Billing Data Log (Prepayment Credits)) which has been mapped to Service Reference Variant (Retrieve Billing Data Log (Prepayment Credits)) ALCS and HCALCS The majority of the GBCS Use Cases related to ALCS and HCALCS have been rewritten in GBCS v0.8.1 in order to fix a known issue and particularly to align with SMETS changes. This has resulted in changes in the DUIS to reflect these GBCS v0.8.1 Use Case definition changes. The affected Service Reference Variants are: 7.5 Activate Auxiliary Load 7.6 Deactivate Auxiliary Load 7.7 ReadAuxiliaryLoadControlSwitchData 7.8 Reset Auxiliary Load 7.9 Add Auxiliary Load To Boost Button 7.10 Remove Auxiliary Load From Boost Button Update Device Configuration (Auxiliary Load Control Descriptions) Update Device Configuration(Auxiliary Load Control Scheduler) Low impact changes Other smaller impact changes generally relate to small changes in items such as attributes, constant values and command construction, as summarised below. Affected Service Reference Variant Name Description of Change Service Reference Variant 1.6 Update Payment Mode Changes to input items 2.1 Update Prepayment Configuration Changes to Non Disablement calendars 2.3 Update Debt Change to the way debt recovery rates are set DCC Public Page 9 of 26

10 Affected Service Reference Variant Service Reference Variant Name Read Instantaneous Import TOU Matrices Read Instantaneous Import TOU With Blocks Matrices Retrieve Billing Data Log (Payment Based Debt Payments) Retrieve Billing Data Log (Prepayment Credits) Configure Alert Behaviour Device Pre-notification Description of Change Changes have been made to some Eligible User Roles to align with GBCS Use Case changes for Service Reference Variants Read Meter Balance Service Reference Variant renamed from Read Meter Balance for Credit Mode Smart Meter to Read Meter Balance as a result of changes to associated GBCS use cases 6.13 Read Event Security Log Read event logs for ALCS / HCALCS read via this SR not SR7.7 as previously defined Future Dated Device processing pattern changes GBCS v0.8.1 introduced a change to the processing pattern for Commands that are capable of being Future Dated on Devices, as defined by GBCS. Where these Commands are executed as Future Dated Commands, then the outcome of the Command is returned to Users as a Device Alert and not as a Service Response format. Where the original Command contains multiple processing instructions, the execution of each Instruction within the Command shall generate a separate Device Alert. Changes have been made within the DUIS to the Service Response (from Device) FutureDatedDeviceAlertMessage: Format defined in section of the DUIS to include two additional XML attributes within each Device Alert; and Response to assist Users in managing the number of instructions expected to be returned as a result of Command processing and to which instruction the Device Alert relates to: 1. An InstructionNumber to indicate which instruction number the FutureDatedDeviceAlertMessage relates to; and 2. A TotalCommandInstructions value, indicating how many instructions are expected to be received by the DCC Systems relating to the FutureDatedDeviceAlertMessage received. DCC Public Page 10 of 26

11 This change affects 11 Service Reference Variants: a) Update Import Tariff (Primary Element) b) Update Import Tariff (Secondary Element) c) Update Price (Primary Element) d) Update Price (Secondary Element) e) 1.6 Update Payment Mode f) 2.1 Update Prepay Configuration g) Update Device Configuration (Load Limiting General Settings) h) Update Device Configuration (Auxiliary Load Control Scheduler) i) Update Security Credentials (KRP) j) 6.23 Update Security Credentials (CoS) k) 11.3 Activate Firmware Alert recipients There are six Device Alerts from a pre-payment interface device (PPMID) for which the recipient (as defined in GBCS v0.8.1) is now the Access Control Broker, but which still require onward distribution to the relevant User. These Device Alerts therefore require equivalent DCC Alerts and rules for determining the relevant User to which the Device Alert should be distributed. 0x801E Integrity check of content or format of command failed 0x8030 Source Does not have Authority for Command 0x803D Trusted Source Authentication Failure 0x803E Unauthorised Communication Access attempted 0x803F Unauthorised Physical Access - Tamper Detect 0x8078 Unauthorised Physical Access Other A new DCC Alert type (N39) has been created for PPMID Alert (see DUIS section ) and the content will contain the Device Identifier and Alert Code from the original Device Alert. The PPMID Alert will be sent to the Responsible Supplier for the Electricity Smart Meter (ESME) and Gas Smart Meter (GSME) Devices for the relevant Smart Metering System (where these Devices exist in the Smart Metering Inventory). 3.3 Other changes to DUIS In addition to the changes that have been made to the DUIS as a result of alignment to GBCS v0.8.1, a number of other changes have been necessitated, as a result of: various updates to Service Request Definitions to correct inconsistencies and errors identified in definitions from the DUIS v0.8 aligned version; and general updates to content as part of solution design changes discussed with Users through DCC User Design Forums. A summary of all changes included within this consulted version of DUIS is provided in Appendix A. DCC Public Page 11 of 26

12 3.3.1 Service Request renaming Service Reference Variant has been renamed from Commission Device (Synchronise Clock) to Commission Device, to reflect the changes made as part of the DUIS v0.8 consultation response to remove Service Reference Variant (Commission Device (Set Import MPxN)). This change was omitted erroneously from the previous published version of the DUIS Changes to the format of Service Reference Variant description As requested by prospective Users as part of DCC User Design Forums, DCC has implemented some changes to the format of Service Reference Variant descriptions within section 3.8 of this DUIS v For each Service Reference Variant definition, where appropriate, DCC has enhanced the definitions with the addition of two new sub headings for Additional Obligations and Additional DCC System Processing to enhance clarity. These sections contain any additional actions that DCC takes as a result of the Service Reference Variant that the User would need to be aware of (e.g. updates to the Smart Metering Inventory or deletion of DCC Schedules) Service Reference Variant 8.4 Update Inventory Additions to the Service Reference Variant definition have been made, to clarify what the Service Request can and cannot be used for and by which Eligible User Roles Service Reference Variant 6.22 ConfigureAlertBehaviour This Service Reference Variant has been re-designed from the version contained in DUIS v0.8 and is therefore new for DUIS v DCC believes that this updated definition better reflects the GBCS v0.8.1 Use Cases and provides a better User interaction to the underlying SMETS and GBCS functionality. DCC recognises that Users have requested further GBCS changes to the associated Use Cases, however such changes cannot be included within DUIS until they are defined and agreed. The change in Service Request definition should enhance clarity and make the Service Request more manageable for Users and clearer for DCC Service Reference Variant Retrieve Device Security Credentials (Device) Service Reference Variant (Retrieve Device Security Credentials (Device)) has been redefined as Critical in this version of DUIS (v0.8.1). This Service Reference Variant was defined as Non Critical in the DUIS v0.8 aligned version. This Service Request has been transformed into the format as defined by GBCS Use Case (CS02e - Provide Device Certificates from Device). According to the GBCS v0.8.1 definition, this Use Case is a variant message as per the message type category so it is not clear if this is a Critical or Non Critical Command from the definition, causing an inconsistency of Criticality definition of the Service Request. The drafting within the CS02e Use Case definition within GBCS v0.8.1 states that the construction of the Command shall be as required for Message Category SME.C.C. From this, DCC has determined that this should be defined as a Critical Command and not Non Critical. This therefore means that this Service Reference Variant is now included as requiring a Pre-Command to be returned to the User for Digitally Signing and returning to DCC as a Signed Pre-Command. DCC Public Page 12 of 26

13 DCC User Interface Specification (DUIS) alignment with GBCS v0.8.1 changes Q1 Do you agree that this version of DUIS accurately reflects GBCS v0.8.1? If not, please provide a rationale for your answer. DCC User Interface Specification (DUIS) other comments Q2 Do you have any other comments regarding the content as presented in the DUIS? If so, please details of your comments. DCC Public Page 13 of 26

14 3.4 Definition of Service Requests As part of DCC s development of the GBCS v0.8.1 aligned version of the DUIS, DCC has identified an issue with the previous version of DUIS in respect of the definition of five Service Requests as both Critical Service Requests and being available to Users via the Future Dated Response Pattern (DSP) mode of operation. DCC has not made any change for this issue in the consulted version of DUIS, as we are seeking the views of consultees as to whether the changes are appropriate and acceptable. Whether or not the changes set out in Appendix C are made to the version of DUIS (and associated XML schema) that will be submitted to the Secretary of State will be considered by DCC in light of the comments received in response to this consultation. The affected Service Reference Variants are: a) 6.6 Update Device Configuration (Gas Conversion) b) 6.7 Update Device Configuration (Gas Flow) c) Update Device Configuration (Auxiliary Load Control Description) d) 6.17 Issue Security Credentials e) 7.12 Set Randomised Offset Limit DCC believes that these Critical commands should not be available as Future-Dated and were incorrectly stated as such in the previous version of the DUIS. DCC asserts that storing Critical Service Requests as Signed Pre-Commands within the DCC solution is not appropriate, as it: a) introduces additional security risks to the overall DCC solution by storing Signed Pre-Commands within the DCC Systems for a period of time prior to sending to the specified Device; b) causes additional complexity with any re-validation upon release; c) may create issues for Users with Execution Counters on Devices (as defined in GBCS) which may result in an increased number of Service Request being retuned with Response Codes that indicate failure; and d) would result in additional costs. DCC proposes that the definition for this set of Service Reference Variants is amended such that it is available to Users only via the On Demand mode of operation. The consequential changes that would be required to the DUIS (if the change is approved for implementation) are outlined in Appendix C DCC User Interface Specification (DUIS) Future Dated Response Pattern (DSP) for Critical Service Requests Q3 Do you agree with DCC s proposal to remove the Future Dated Response Pattern (DSP) mode of operation for the following five Critical Service Requests, such that Users will only be able to request these Service Requests via the On Demand mode of operation only? a) Service Reference Variant 6.6 Update Device Configuration (Gas Conversion) b) Service Reference Variant 6.7 Update Device Configuration (Gas Flow) c) Service Reference Variant Update Device Configuration (Auxiliary Load Control Description) d) Service Reference Variant 6.17 Issue Security Credentials e) Service Reference Variant 7.12 Set Randomised Offset Limit DCC Public Page 14 of 26

15 DCC User Interface Specification (DUIS) Future Dated Response Pattern (DSP) for Critical Service Requests If not, please provide a rationale for your answer. 4 Consultation Part B: Message Mapping Catalogue (MMC) 4.1 MMC Overview The MMC provides information to enable prospective DCC Users to integrate their IT infrastructure with DCC Systems, in respect of the translation of the message information that is produced by Devices and is received by a User, into a defined MMC Output Format. Message information produced by Devices comprises Service Responses and Device Alerts, received by the User via the DCC User Interface. The MMC includes the MMC XML Schema which details all of the XML elements that are relevant to the translation of GBCS-formatted data into the MMC Output Format. The MMC is only relevant to Service Responses and Device Alerts emanating from a Device and received by a User. In the case of Service Responses, these messages are sent in response to a Service Request. Where the Service Response contains information from the Device, it is sent by the Device to DCC and DCC forwards the message to the relevant User. Similarly, Device Alerts not generated in direct response to a Service Request, sent by the Device in GBCS format will be forwarded by DCC to the relevant User. 4.2 Overview of MMC amendments The changes to the MMC Service Response definitions to align with GBCS v0.8.1 mirror the associated updates that have been made to the corresponding Service Requests in the DUIS. The changes to Service Responses within the MMC are summarised in the sections below. A summary of all changes to the MMC from the version submitted to the Secretary of State in early March 2015 (and published on the DCC Website) is found in Appendix B to this consultation paper Service Responses and Alerts requiring significant amendments The changes to the MMC Service Response definitions to align with GBCS v0.8.1 mirror the associated updates that have been made in DUIS to the corresponding Service Requests. The changes to Service Responses are summarised in the sections below; a summary of all changes to the GBCS v0.8-aligned version of the MMC is found in Appendix B to this consultation paper. DCC Public Page 15 of 26

16 Tariffs and Prices Tariffs and pricing elements have been substantially updated as part of the GBCS update to v In addition, a Service Response has been added ( SR1.2.2 Update Price (Secondary Element) ) to correspond with new GBCS Use Case ECS01d ( Set Price on ESME Secondary Element ). The following Service Responses are affected: a) Update Price (Secondary Element) b) Read Tariff (Primary Element) c) 11.2 Read Tariff (Secondary Element) d) 4.18 Read Meter Balance Read Billing Data Log GBCS Use Cases for electricity (ESME) have been updated to align with equivalent gas (GSME) Use Cases. The changes include the addition of a new GBCS Use Case ( ECS20d, Read ESME Billing Data Log (prepayment credits) ). a) (removed) Retrieve Debit and Credit Billing Data log b) Retrieve Change Of Mode / Tariff Triggered Billing Data Log c) Retrieve Billing Data Log (Payment Based Debt Payments) d) Retrieve Billing Data Log (Prepayment Credits) Responses relating to ALCS and HCALCS The majority of the GBCS Use Cases related to ALCS (Auxiliary Load Control Switch) and HCALCS (HAN Connected Auxiliary Load Control Switch) have been significantly restructured in GBCS v0.8.1, affecting the following Service Responses: a) 6.13 Read Event or Security Log b) 7.5 Activate Auxiliary Load c) 7.6 Deactivate Auxiliary Load d) 7.7 Read Auxiliary Load Switch Data e) 7.8 Reset Auxiliary Load f) 7.9 Add Auxiliary Load to Boost Button g) 7.10 Remove Auxiliary Load from Boost Button Billing Calendar The Billing Calendar data items have been changed to align with GBCS v0.8.1; this affects the following Service Responses: a) Update Import Tariff (Primary Element) b) Update Import Tariff (Secondary Element) c) Read Device Configuration (Billing Calendar) d) 6.8 Update Device Configuration (Billing Calendar) DCC Public Page 16 of 26

17 4.2.3 Other changes to MMC In addition to the broad changes made across multiple Service Responses there are a number of smaller changes made to specific Service Responses and Device Alerts, as set out in the table below and further detailed in Appendix B to this document. Affected Service Response Name Service Response Read Instantaneous Import TOU Matrices Read Maximum Demand Import Description of Change A total for Gas TOU registers has been added The last reset date time has been added Registers Read Maximum Demand Export Registers 4.13 Read Prepayment Configuration A change of codes and an additional payment mode item have been added 6.11 Synchronise Clock The response to Synchronise Clock has been split between Gas and Electricity Read Device Configuration (Identity Status Code enumerations updated Exc MPxN) 7.4 Read Supply Status Codes or data types updated Various Various Various typo corrections and nonmaterial clarifications Message Mapping Catalogue (MMC) alignment with GBCS v0.8.1 changes Q4 Do you agree that this version of MMC accurately reflects GBCS v0.8.1? If not, please provide a rationale for your answer. Message Mapping Catalogue (MMC) other comments Q5 Do you have any other comments regarding the content as presented in the MMC? If so, please details of your comments. DCC Public Page 17 of 26

18 5 How to respond Please provide responses in the attached template by 24 April 2015 to DCC at If you have any questions about the consultation documents, please contact Consultation responses may be published on DCC s website Please state whether all, or any part, of your consultation response is confidential. Please note that responses in their entirety (including any text marked confidential) may be made available to the Department of Energy and Climate Change (DECC) and the Gas and Electricity Markets Authority (the Authority). If you have questions about our approach to consultations, please contact DCC s Regulation Manager at richard.sullivan@smartdcc.co.uk. 6 Referenced Documents Document Title Issue Dated Smart Energy Code (SEC) SEC /03/2015 Smart Energy Code (SEC) SEC 4A Consultation 30/06/2014 Great Britain Companion Specification /11/2014 DCC User Interface Specification (DUIS) v0.8-aligned submission to Secretary of State 12/09/2014 Message Mapping Catalogue (MMC) v0.8-aligned submission to Secretary of State 02/03/2015 March 2015 SEC Government Response N/a DECC expected publish March 2015 to in Table 1 Referenced Documents DCC Public Page 18 of 26

19 Consultation on GBCSv0.8.1-aligned documents: DCC User Interface Specification (DUIS) and Message Mapping Catalogue (MMC) Appendix A Summary of DUIS amendments DUIS Summary of Changes Section 1 No changes 2 Changes Made (see text below) 2.1 No changes 2.2 No changes 2.3 No changes 2.4 No changes 2.5 No changes 2.6 Section Addition of Note Under table to introduce New CV value of 9 for DCC internal only use. Section Addition of some new clarification words for Future Dated Response Patterns (Device) and (DSP). Section Addition of some new clarification words for sequencing of Future Dated Service Requests. 2.7 No changes 2.8 No changes 2.9 No changes 2.10 Change of definition of the term Initial Retry period to be a more generic and reflective of Command Processing Times. Definition change for how DCC processes Responses received after TIMEOUT notifications have been sent. Now records Response in Service Audit Trail and Event Log instead of just Event log which is not visible to Users. 3 Changes Made (see text below) 3.1 Addition of new Service Reference Variant Update Price (Secondary Element). Removal of Service Reference Variant This functionality has been moved to Service Reference Variants and as a result of GBCS use case changes to align Gas and Electricity GBCS use cases. Change of Criticality of Service Reference Variant Retrieve Device Security Credentials (Device) from Non Critical to Critical following GBCS clarification. Changes to Eligible User Roles to align with GBCS Use Case changes for Service Reference Variants, 4.1.2, 4.1.3, 4.4.4, 4.4.5, 6.22, 12.2 Renaming of Service Reference Variant 4.18 from Commission Device (Synchronise Clock) to Commission Device. Renaming of Service Reference Variant from Read Meter Balance for Credit Mode Smart Meter to Read Meter Balance as a result of changes to associated GBCS use cases. 3.2 Section Addition of some clarification words for Response Codes E4, E5 and E19. Section Addition of some clarification words for Response Codes E11 Section Addition of three new Response Codes E52, E53 and E54 to support DCC validation checks. 3.3 No changes 3.4 No changes DCC Public Page 19 of 26

20 Consultation on GBCSv0.8.1-aligned documents: DCC User Interface Specification (DUIS) and Message Mapping Catalogue (MMC) DUIS Summary of Changes Section 3.5 General Clarification added to GBCS Payload data item to confirm that the data item type is xs:base64binary rather than just See GBCS. Section Addition of clarification words that an Acknowledgment is sent when responding to Non Device Service Requests when no data is to be returned. Section Change of Data item type for DSPScheduleID and addition of valid set to definition. Section Definition change with additional data items for Service Response (from Device) - FutureDatedDeviceAlertMessage Format responses. Section Addition of three new Response Codes E52, E53 and E54 and associated references to Error Handling Strategy Procedure 3.6 General - Change of Data item types for a few Data Items, AlertCode, GBCS Payload, DCC Alert. Section Addition of clarification words to some DCC Alert Codes. Section Addition of seven new DCC Alert Codes from N33 to N39 inclusive. Section addition on new section and associated text to clarify the Relationship between DCC Alert Codes and Response Codes which was previously missing. 3.7 No changes 3.8 General Several changes to Service Request Definitions to reflect changes made in associated GBCS v0.8.1 use cases. General Some updates to Service Request Definitions to correct inconsistencies and errors in definitions from previous DUIS v0.8. General For each Service Reference Variant definition, where appropriate, the addition of two new sub headings for Additional Obligations and Additional DCC System Processing to add clarity for Users. General of the 115 Service Reference Variants included in DUIS v0.8.1; Service Reference Variants with a large number of Service Request Definition changes - 9 (8%) Service Reference Variants with a medium number of Service Request Definition changes - 11 (10%) Service Reference Variants with a low number of Service Request Definition changes - 58 (50%) DCC Public Page 20 of 26

21 Consultation on GBCSv0.8.1-aligned documents: DCC User Interface Specification (DUIS) and Message Mapping Catalogue (MMC) DUIS Section Summary of Changes Service Reference Variants with no Service Request Definition changes 37 (32%) Service Reference Variant 6.23 UpdateSecurityCredentials(CoS) - Introduction of constraint for Command Variants 2 and 3 which are only available to Users with an ExecutionDateTime on or after the CoS Date. 3.9 General A few updates/corrections to Type and Unit definitions for some Data Items across this section Section Addition of a new DCCAlert Definition (PPMID Alert) to support the new N39 DCC Alert General Update of some Data item type definitions to allow for a new NoType type definition. Section Update to Command Variant definition to show CV=9 for DCC Internal use only. Section Update to Date definition to clarify where wildcards may be used within Service Requests. Section Update to ReadLogPeriodOffSet definition to use a revised data type. Section new data type definition added for ScheduleID. Section New Response Code E1008 added Section Updates to Response Code descriptions to add clarity. Appendix Addition of some new clarification words for alignment to XML standards 1 DCC Public Page 21 of 26

22 Consultation on GBCSv0.8.1-aligned documents: DCC User Interface Specification (DUIS) and Message Mapping Catalogue (MMC) Appendix B Summary of MMC amendments MMC Summary of Changes section Figure 1 removed DebugInfo from DeviceAlertMessage element Clarification that the number of ZIGBEEClusterResponse elements will correspond with the ZigBee clusters in the GBCS Command Clarification that the number of COSEMResponse elements will correspond with the number of DLMS/COSEM instructions in the GBCS Command; elements will be returned in the order supplied by the Device Removed SR8.9 (ReadFailure) 4.2 Valid values for GBCSHexAlertCode from 0x Updated Table 9 Alert Codes for Message Code 0x0061 Updated Table 9 Alert Codes for Message Code 0x0067 Updated Table 9 Alert Codes for Message Code 0x008B Added Message Codes 0x00CA (Future Dated Firmware Activation Alert) and 0x00CB (Future Dated Updated Security Credentials Alert) Replaced Alert Codes for GBCS Use Cases 5.4 Added Service Reference Variant SR1.2.2 (UpdatePrice(SecondaryElement)) 5.17 Clarification of different structures returned for: (previously Gas (ConsumptionRegister) 5.16) Electricity (ActiveImportRegister, ReactiveImportRegister, SecondaryActiveImportRegister) 5.18 (previously 5.17) 5.19 (previously 5.18) 5.20 (previously 5.19) 5.21 (previously 5.20) Clarification of different structures returned for: Gas (TariffTOURegisterMatrix, GasTotal) Electricity (TariffTOURegisterCollection) Restructured to clarify the ordering of items within the TariffBlock Clarification of items returned Clarification of different structures returned for: ActiveExportRegister, ReactiveExportRegister 5.22 Removed SR4.4 (variant 4.4.1) 5.23 Clarification of different structures returned for: Electricity (LogEntryConsumptionAndTariffRegistersData, LogEntryPrepaymentData) Gas (LogEntryConsumptionRegister, LogEntryPrepaymentData) DCC Public Page 22 of 26

23 Consultation on GBCSv0.8.1-aligned documents: DCC User Interface Specification (DUIS) and Message Mapping Catalogue (MMC) MMC Summary of Changes section 5.24 Clarification of different structures returned for: Electricity (ESMEBillingDataLogEntry) Gas (GSMEBillingDataLogentry) 5.25 Added Electricity response GBCS Code Further detail on elements contained within LogEntry element 5.26 Added Electricity response GBCS Code Further detail on elements contained within LogEntry element 5.27 Clarification that the LogEntry Group elements may be appear up to 31 times 5.29 Updated Units to be Wh or m3 for PrimaryValue 5.33 Amended to account for separate structures for Electricity and Gas 5.34 Updated Type value for TariffTOUPriceMatrix, TariffSwitchingTable, TariffSwitchingTableSpecialDays 5.35 Updated Type value for MaxDemandConfigurableTimePeriod (removed table containing elements no longer relevant) Added LastResetDateTime to MaxDemandRegisterDataType data items 5.37 Clarification of potential values for DebtRecoveryPeriod1 and DebtRecoveryPeriod2 Addition of PaymentMode element Removal of Electricity CurrencyUnitName 5.40 Amendment of Type for PrimaryActivePowerImportValue 5.43 Added RMSVoltageSettings to body data items Updated Type value for SinglePhaseVoltageSettings (removed table containing elements no longer relevant) Corrected Type value for PolyPhaseVoltageSettings Amended description for AverageRMSVoltageSettings data items, removed element AverageRMSVoltageMeasurementPeriod 5.45 Amended to clarify separate Gas and Electricity Billing Calendars, removed previous table which no longer applies 5.46 Amendment to the valid values for SupplyTamperState and SupplyDepletionState 5.57 Amended to clarify separate Gas and Electricity status values 5.59 Clarified the Log structure for Event or Security logs Amended the Type value for LogMeaning, OtherInformationLogMeaning elements Added ALCSLog specific data items (Table 149) 5.62 Added Type value for StatusCode, ExistingCertificateHash, NewCertificateHash 5.63 Updated Type and Valid Set list for UpdateSecurityCredentialsResponseCode 5.64 Updated Type and Valid Set list for IssueCredentialsResponseCode 5.72 Added Type value for RemotePartyRole, ExistingCertificateHash Updated Valid set list for StatusCode 5.73 Updated Type and Valid Set list for RetrieveDeviceSecurityCredentialsStatusCode 5.78 Updated Type value for SupplyState and RemainingBatteryCapacity DCC Public Page 23 of 26

24 Consultation on GBCSv0.8.1-aligned documents: DCC User Interface Specification (DUIS) and Message Mapping Catalogue (MMC) MMC Summary of Changes section 5.79 Amended to clarify that the response codes for HCALCS and ALCS are the same 5.81 Added new ALCSHCALCSSpecialDays element in body Added TypeAndIdentifier element in AuxiliaryLoadControlSwitch element group and table detailing elements Amended Status element in AuxiliaryLoadControlSwitch element group to State Removed EventLog element from AuxiliaryLoadControlSwitch element group and supporting element table Removed ALCSScheduler table 5.82 Amended to clarify that the response codes for HCALCS and ALCS are the same 5.88 Updated Type value for RemotePartyRole, StatusCode, ExistingCertificateHash, NewCertificateHash 5.89 Updated Type value for JoinResponseCode 5.90 Updated Type value for JoinResponseCode 5.92 Amended to clarify that Message Code 0x0010 relates to ESME Unjoin from Type 2 Device Amended to clarify that Message Code 0x000F relates to PPMID Unjoin from ESME Updated Type value for UnjoinResponseCode 5.93 Updated Type value for DeviceLogEntries, CHFDeviceLog, DeviceType 5.96 Updated Type value for DeviceLogEntry, joinresponsecode 5.99 Updated Type and Valid Set list for activateimageresponsecode, FirmwareVersion 6.1 Updated Alert Codes Amended string length for AlertDescription from 200 to Updated Alert Code Amended string length for AlertDescription from 200 to Updated and added to list of Alert Codes Updated Valid values for GBCSHexAlertCode Updated Valid Values for AlertDescription 6.4 (now Section removed removed) 6.4 (previously 6.5) Clarification of the structure for Alerts for Future Dated Commands (which will now be issued for each instruction within the Command Clarification that the GBCSHexAlertCode values will be 0x8066 (success) or 0x8067 (failure) Details added for FutureDatedCommandOutcomeDeviceAlert body data items DCC Public Page 24 of 26

25 Service Reference Service Reference Variant Critical On Demand Future Dated Response Pattern DCC Scheduled Non Device Request Eligible User Roles Consultation on GBCSv0.8.1-aligned documents: DCC User Interface Specification (DUIS) and Message Mapping Catalogue (MMC) Appendix C Section Consequential changes to DUIS if change proposed in section Error! Reference source not found. of this consultation is implemented (proposed additions bold and italicised; proposed deletion as strikethrough) In relation to such Requests, DCC shall ensure that either: a) Where the associated Command is capable of being future dated on the relevant Device as defined by GBCS, DCC shall send the corresponding Command to the Device; this follows the Future Dated Response Pattern (Device);or b) Where the associated Command is not capable of being future dated on the Device as defined by GBCS and the associated Command is not a Critical Command, DCC shall provide a similar function within the DCC Systems by storing the Request in the DCC Systems until the future execution date/time as specified in the Request and then sending the corresponding Command to the Device. This follows the Future Dated Response Pattern (DSP). Section 3.1, Table 12 Service Request Matrix (proposed additions bold and italicised; proposed deletion as strikethrough) Service Request Name Modes of Operation Update Device Configuration (Gas Conversion) Update Device Configuration (Gas Flow) Yes Yes DSPNo No No GS Yes Yes DSPNo No No GS Update Device Configuration (Auxiliary Load Control Description) Yes Yes DSPNo No No IS Issue Security Credentials Yes Yes DSPNo No No IS Set Randomised Offset Limit Yes Yes DSPNo No No IS Section 3.8 Can be future dated? table entry for each of the five affected Service Requests within Section 3.8 of the DUIS (Service Request Definitions), to be set to No (i.e. indicating that the Service Request cannot be future dated). DCC Public Page 25 of 26

26 Consultation on GBCSv0.8.1-aligned documents: DCC User Interface Specification (DUIS) and Message Mapping Catalogue (MMC) Amendments to DUIS XML Schema The attribute ExecutionDateTime shall be removed from the following five Types with the DUIS XML Schema UpdateDeviceConfigurationGasConversion UpdateDeviceConfigurationGasFlow UpdateDeviceConfigurationALCDescriptions UpdateSecurityCredentialsKRP SetRandomisedOffsetLimit DCC Public Page 26 of 26