Independent Suppliers Day 30 March DCC Public

Size: px

Start display at page:

Download "Independent Suppliers Day 30 March DCC Public"

Garey Wheeler
6 years ago
Views:

1 Independent Suppliers Day 30 March 2017

2 Agenda for Today 1.DCC Business and Programme Update 2.DCC User Interface Specification (DUIS) and Certificates 3.SMKI Keys and SMKI RAPP 4.SREPT and Testing 5.Self Service Interface (SSI) 6.Comms Hub Ordering and Forecasting 7.Comms Hub SM WAN 8.SMETS1 Update 1

3 DCC Update Release 1.2 went live on 25 November 2016 Your obligation is to be live by 25 November 2017 (8 months) Release 1.3 is tracking to plan System Integration Testing (SIT) has completed Report being assessed by the Testing Assurance Group (TAG) this week Will be presented to SEC Panel on 7 April 2017 Release 1.3 Go-live date is 12 May

4 How to engage and get support Come and meet with the Industry Team (point of escalation when required) if you don t know your Industry Partnership Manager (IPM) then use contact@smartdcc.co.uk DCC Service Desk for live services and to log incidents Industry Test Team there to support you through testing Forums running for testing, design, service management & comms hubs Website and SharePoint DCC monthly newsletter 3

5 Independent Suppliers' Day

DCC Solution: Integration Points DCC DCC 1 Smart Meter Key Infrastructure (SMKI) TSP Gamma Network 1 Other devices deices IHD Elec Other devices deices IHD HAN Gas HAN Comms Hub Comms Hub

Self Service Interface Self Service Interface Self Service Management DCC User Gateway Interface Registration Systems Gateway Enterprise Systems Gateway 2 3 4 5 6 DCC User Gateway (Gamma)

6 DCC Solution: Integration Points DCC DCC 1 Smart Meter Key Infrastructure (SMKI) TSP Gamma Network 1 Other devices deices IHD Elec Other devices deices IHD HAN Gas HAN Comms Hub Comms Hub Buddy / Meshed Network CSPs WAN DSP DSP Key Store DCC Service Management System Request Management & Service Audit Audit Trail Smart Meter Inventory DSP Service Request Processing Self Service Interface Self Service Interface Self Service Management DCC User Gateway Interface Registration Systems Gateway Enterprise Systems Gateway DCC User Gateway (Gamma) Suppliers P&C Network Operators P&C Other Parties P&C Registration Agents Elec Gas DCC Enterprise Systems (Billing, BI/MI, Finance, etc) DCC Service Desk 7 Internet OMS (TEF) OMS (ARQ) SharePoint 5

7 Basic Service Request Processing 6

8 Service Requests Service Requests are used to enable communications and issue instructions for action between Users and the DCC Systems. Service Requests are electronic data transfers sent over a web-service interface in XML message format Service Requests are defined as part of SEC 5.5 in Appendix AD - DCC User Interface Specification The DCC Service offers 115 Service Request Variants for Use by Eligible Users 7

9 SERVICE REQUEST EXAMPLE <?xml version="1.0" encoding="utf-8"?> <Request xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <Header> <RequestID>99-00-AA-BB-CC-DD-EE-FF: :50</RequestID> <CommandVariant>1</CommandVariant> <ServiceReference>6.7</ServiceReference> <ServiceReferenceVariant>6.7</ServiceReferenceVariant> </Header> <Body> <UpdateDeviceConfigurationGasConversion> <CalorificValue>40.1</CalorificValue> <ConversionFactor> </ConversionFactor> </UpdateDeviceConfigurationGasConversion </Body> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" </SignedInfo> </Signature> </Request> 8

10 Service Responses A Service Response is sent to every Service Request received by the DCC. Service Responses are electronic data transfers sent over a web-service interface in XML message format Several different Service Response Patterns depending on the Service Request sent to the DCC as defined as part of SEC 5.5 in Appendix AD - DCC User Interface Specification The format of responses form Device is in GBCS format as defined as part of SEC 5.5 in Appendix AF - Message Mapping Catalogue 9

11 Service Responses (2) 10

12 Service Response - Example <?xml version="1.0" encoding="utf-8"?> <Response xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <Header> <RequestID>99-00-AA-BB-CC-DD-EE-FF: :50</RequestID> <ResponseID> :99-00-AA-BB-CC-DD-EE-FF:50</ResponseID> <ResponseCode>I0</ResponseCode> <ResponseDateTime> T18:13:51.00</ResponseDateTime> </Header> <Body> <ResponseMessage> <ServiceReference>3.3</ServiceReference> <ServiceReferenceVariant>3.3</ServiceReferenceVariant> <GBCSPayload>ZGVmYXVsdA==</GBCSPayload> </ResponseMessage> </Body> </Response> 11

13 Security Credentials / Certificates Prior to Installation all Smart Metering Devices must have, A Device GUID assigned SMKI Security certificates populated into each Trust Anchor cell on each Device as defined by GBCS. Device Certificates must be stored in the SMKI Public Key Repository (PKR) operated by the DCC Each Smart Metering Organisation will have one or more public / private cryptographic key pairs for the purposes of securing Smart Metering communications. In accordance with industry good practice, separate key pairs are used for different cryptographic purpose ( key usage ). Specifically, there will be a Key Agreement key pair (generating symmetric keys for encryption and MAC generation) and separately, a key pair for Digital Signing purposes. 12

14 ESME electricity meter GSME gas meter CHF comms hub GPF gas proxy PPMID pre-payment meter HCALC HAN auxiliary load control Devices DCC Keys/Certificates DCC Contingency Symmetric S DCC DCC Root OCA Recovery A A DCC DCC Contingency Private Key Issuing OCA A A Supplier Supplier Digital Signature A DCC Issuing DCA A Supplier Supplier Network Operator Network Operator DCC Supplier Key Agreement Supplier Key Agreement (Pre-Payment) Network Operator Digital Signature Network Operator Key Agreement AccessControlBroker Digital Signature A A A A A DCC Key: Root DCA Key Custodian A DCC DCC DCC AccessControlBroker Key Agreement transitionalcos Digital Signature wanprovider Digital Signature A A A? Device Slot Key type (asymmetric/symmetric) Certificate in Device Slot No Certificate in Device Slot

15 Basic Service Request Processing 14

16 Service Requests Service Requests are used to enable communications and issue instructions for action between Users and the DCC Systems. Service Requests are electronic data transfers sent over a web-service interface in XML message format Service Requests are defined as part of SEC 5.0 in Appendix AD - DCC User Interface Specification The DCC Service offers 115 Service Request Variants for Use by Eligible Users 15

17 SERVICE REQUEST EXAMPLE <?xml version="1.0" encoding="utf-8"?> <Request xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <Header> <RequestID>99-00-AA-BB-CC-DD-EE-FF: :50</RequestID> <CommandVariant>1</CommandVariant> <ServiceReference>6.7</ServiceReference> <ServiceReferenceVariant>6.7</ServiceReferenceVariant> </Header> <Body> <UpdateDeviceConfigurationGasConversion> <CalorificValue>40.1</CalorificValue> <ConversionFactor> </ConversionFactor> </UpdateDeviceConfigurationGasConversion </Body> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" </SignedInfo> </Signature> </Request> 16

18 Service Responses A Service Response is sent to every Service Request received by the DCC. Service Responses are electronic data transfers sent over a web-service interface in XML message format Several different Service Response Patterns depending on the Service Request sent to the DCC as defined as part of SEC 5.0 in Appendix AD - DCC User Interface Specification The format of responses form Device is in GBCS format as defined as part of SEC 5.0 in Appendix AF - Message Mapping Catalogue 17

19 Service Responses (2) 18

20 Service Response - Example <?xml version="1.0" encoding="utf-8"?> <Response xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <Header> <RequestID>99-00-AA-BB-CC-DD-EE-FF: :50</RequestID> <ResponseID> :99-00-AA-BB-CC-DD-EE-FF:50</ResponseID> <ResponseCode>I0</ResponseCode> <ResponseDateTime> T18:13:51.00</ResponseDateTime> </Header> <Body> <ResponseMessage> <ServiceReference>3.3</ServiceReference> <ServiceReferenceVariant>3.3</ServiceReferenceVariant> <GBCSPayload>ZGVmYXVsdA==</GBCSPayload> </ResponseMessage> </Body> </Response> 19

21 Security Credentials / Certificates Prior to Installation all Smart Metering Devices must have, A Device GUID assigned SMKI Security certificates populated into each Trust Anchor cell on each Device as defined by GBCS. Device Certificates must be stored in the SMKI Public Key Repository (PKR) operated by the DCC Each Smart Metering Organisation will have one or more public / private cryptographic key pairs for the purposes of securing Smart Metering communications. In accordance with industry good practice, separate key pairs are used for different cryptographic purpose ( key usage ). Specifically, there will be a Key Agreement key pair (generating symmetric keys for encryption and MAC generation) and separately, a key pair for Digital Signing purposes. 20

22 ESME electricity meter GSME gas meter CHF comms hub GPF gas proxy PPMID pre-payment meter HCALC HAN auxiliary load control Devices DCC Keys/Certificates DCC Contingency Symmetric S DCC DCC Root OCA Recovery A A DCC DCC Contingency Private Key Issuing OCA A A Supplier Supplier Digital Signature A DCC Issuing DCA A Supplier Supplier Network Operator Network Operator DCC Supplier Key Agreement Supplier Key Agreement (Pre-Payment) Network Operator Digital Signature Network Operator Key Agreement AccessControlBroker Digital Signature A A A A A DCC Key: Root DCA Key Custodian A DCC DCC DCC AccessControlBroker Key Agreement transitionalcos Digital Signature wanprovider Digital Signature A A A? Device Slot Key type (asymmetric/symmetric) Certificate in Device Slot No Certificate in Device Slot

23 Obtaining access to SMKI The regulations relating to SMKI registration are set out in full in the SMKI RAPP which is part of the Smart Energy Code

24 Agenda There are three steps to gaining access to SMKI: 1.Registration 2.Checking your ID 3.Issuing Credentials

25 Why? Smart Meter Key Infrastructure (SMKI) is a key foundation of Smart Metering security. The SMKI organisation certificate is only held by the Organisation to whom it relates Individuals are legally acting for their Organisation Individuals are who they say they are Other acronyms: SMKI RAPP SMKI Registration Authority Policies and Procedures SREPT - SMKI and Repository Entry Process Testing IKI - Infrastructure Key Infrastructure DCCKI - DCC Key Infrastructure

26 SMALL SUPPLIERS PROGRESS OBTAINING SMKI Commenced SMKI RAPP Completed SMKI RAPP Completed SREPT

27 1.REGISTRATION The first step in getting access to the SMKI Services for SREPT and to access the SMKI Live Services, is to complete the 5 registration forms below, as set out in the SMKI RAPP. The forms can be obtained from the DCC s Live Operations SharePoint. 1. Organisation Nomination Form to apply for access to the SMKI Services. (Appendix A of the SMKI RAPP). This form must be signed by the SMKI Nominating Officer (NO) of the applicant organisation. 2. Authorised Subscriber / Interface Access Application Form (Appendix B of the SMKI RAPP). This form details which SMKI Interfaces the applicant organisation wishes to access and must be signed by the SMKI Senior Responsible Officer (SRO) (see below) of the applicant organisation. 3. SMKI SRO Nomination Form (Appendix C of the SMKI RAPP). This form nominates an individual to act in the capacity of the SMKI SRO for the applicant organisation and must be signed by the SMKI Nominating Officer. At least one individual must be nominated and each nomination must be on a separate form. They do not have to work for the applicant organisation, they can be from a 3 rd party.

28 REGISTRATION cont. 4. SMKI ARO Nomination Form (Appendix D of the SMKI RAPP). This form nominates an individual to act in the capacity of the SMKI Authorised Responsible Officer (ARO) for the applicant organisation and must be signed by the SMKI SRO. At least one individual must be nominated and more than one SMKI ARO can be nominated per form. They do not have to work for the applicant organisation, they can be from a 3 rd party. NOTE: The SRO and the ARO can be the same person. Applicant organisations must indicate which IKI credentials each SMKI ARO is to be issued with on this form. 5. SMKI Nominee Details Form (Appendix E of the SMKI RAPP). This form lists the personal information for each individual nominated as an NO, SRO or ARO. This information is used to check their identity during the verification meeting. THIS FORM IS DELETED FROM SHAREPOINT IMMEDIATELY AFTER IT HAS BEEN PRINTED Each form requires a physical signature, which can be provided in scanned form. When complete, forms should be scanned and uploaded to the DCC SharePoint site.

29 Organisation Information Form A.1 Full Name of Organisation: This must be the Sec Party name of the Organisation. A.2 Registered Office address A.3 Company Registration No. A.4 Party Signifier or RDP Signifier: This should be the Sec Party Signifier, e.g. PAA 000. A.5 EUI64 Identifier Range: This should be the EUI64 range allocated by SECAS. A.6 Role(s) in respect of the application: An X should be put in each box next to the role requested and an individual EUI64 identifier should be allocated to each different role A.6 Full Name: Name of Nominating Officer A.7 Role: What role the N.O. holds within the company. They must be listed on the Companies House website as an Officer for that organisation. A.8 Phone Numbers A.9 Address A.10 Signature of Nominating Officer

30 Authorised Subscriber/Interface Access Application Form B.1 Full Name of Organisation: This must be the Sec Party name of the Organisation. B.2 Company Registration No. B.3 Name of Authorised Subscriber Application (if any): An X should be put in Organisation Certificate Policy only box and the Device Certificate Policy only box (if required). B.4 Interface access credentials requested: An X should be put in each box to indicate which interfaces you require, either via DCC Gateway OR via the Internet, not both. File signing is only available via the DCC Gateway. B.5 Party Signifier or RDP Signifier: This should be the Sec Party Signifier, e.g. PAA 000. Page 2 of this form is the Nominating Officer Information, which should be the same as that entered on the Organisation Information Form.

31 SMKI SRO Nomination Form C.1 Full name C.2 Role: What role they have within the Company. C.3 Phone numbers C.4 address C.5 Full Name of Organisation: This must be the Sec Party name of the Organisation. C.6 Party Signifier or RDP Signifier: This should be the Sec Party Signifier, e.g. PAA 000. C.7 C.11 Nominating Officer Information: which should be the same as that entered on the Organisation Information Form.

32 SMKI ARO Nomination Form D.1 List of Nominees: This should be the Full Name of one or more people who are being nominated as an ARO. A tick should be put in each box to indicate which credentials they need, as per the list A to H below. C to H are only available via the DCC Gateway and NOT via the Internet. D.2 to D.8: Nominating Officer Information: These are the details of the Nominating Officer, who should be a previously nominated SRO, along with the Full Name and Sec Party ID of your organisation

33 SMKI ARO Nomination Form E.1 Full Name E.2 Gender E.3 Date of Birth E.4 Nationality E.5 Personal Identification: We will go into more detail what documents need to be provided during the ID check. E.6 Residential address: This MUST be the current address and match the one on the document provided, i.e. driving licence E.7 Occupation E.8 Affiliation with Organisation: Employee No. and Evidence Type, e.g. Payslip E.9 Work Phone Number E.10 Address E.11 Signature of Nominee E.12 Date: when the form was signed E.13 to E.18 Nominating Officer Information: Nomination of an individual to become a SMKI SRO should be made by a Director or Company Secretary. Nomination of an individual to become an SMKI ARO should be by a SMKI SRO

34 2. CHECKING YOUR ID Once you have submitted all of your SMKI RAPP forms and they have been checked and verified, the SMKI RA Team will the nominated SRO to arrange to the check the id of everyone who has been nominated, as either NO, SRO or ARO. Normally this will done over a video-link using WebEx and the SMKI RA Team will book the meeting and send out an invite containing a link to connect to WebEx. If this is not possible, then it can be done face-to-face at the DCC office. You Do Not require a Webex licence to join a video conference arranged by DCC The SMKI RA Team use what is called HM Government Good Practice Guide 45 (GPG45) to check an individual s identity to a Level 3. Ideally, we need see a passport (which must be in date), a driving licence (which must have their current address on it) and a company id badge (if you have one). However, there are a number of other options, if either a passport or driving licence are not available (see below).

35 List of acceptable documentation that may be used as evidence of individual identity List of acceptable documentation that may be used as evidence of individual identity The following tables are taken from HMG Good Practice Guide 45, and at Level 3 identity verification requires: Two documents from table 14 (including at least one with a photograph) or One document from table 14 and two documents from table 13 (including at least one with a photograph) If an applicant cannot provide the required documentation the SRO should discuss the position with the SMKI Registration Authority Manager. DCC will revise the list if GP45 is updated (these tables are from v2.3 dated July 2014). The citizen, money and living columns are not of interest to an applicant.

36 List of acceptable documentation that may be used as evidence of individual identity

List of acceptable documentation that may be used as evidence of individual identity The ID check, via WebEx, can be done individually or in a group.

37 List of acceptable documentation that may be used as evidence of individual identity The ID check, via WebEx, can be done individually or in a group. If this is not possible then it can be undertaken at DCC s office. Each person has to show their company id badge (if they have one), passport and driving licence to the camera. The SMKI RA Team will check the details against those that were registered on the SMKI Nominee Details Form. The checks can be done in any order, but must all be successfully completed before you can move onto the next stage.

38 3. ISSUING CREDENTIALS Once all of your nominated NO, SRO and ARO s have been ID checked, the SMKI RA Team will the nominated SRO to arrange for the ARO s to come into DCC to collect their credentials. Therefore, in most cases, it is only the ARO s who have to physically visit DCC, unless the id checks cannot be done over a video-link. When the ARO s come to DCC to collect their credentials, they will need to bring one form of ID with them, so either their passport OR their driving licence. They will be given an etoken, which looks like a USB. This will contain their credentials and they will asked to set a password on it. Once set, this password cannot be changed if the ARO forgets it, the only option being for them to return to DCC to get another etoken. These credentials may allow them to issue Certificate Signing Requests (CSR s) for Organisation, Device and File Signing requests, depending on what has been requested on their Authorised Subscriber / Interface Application Access Form.

39 3. ISSUING CREDENTIALS cont. DEVICE CSR S Only Suppliers and some other organisations that actually own meters, will be given credentials to issue Device CSR requests In addition, if they have requested access to the Adhoc CSR Web Service Interface and Batch CSR Web Service Interface, on their Authorised Subscriber / Interface Application Access Form, they will need to bring in two CSR s for signing. These CSR s can be on a USB and the RA Manager will sign them and copy the certificate back onto the same USB. The user can then take the two certificates back to their organisation and load them onto their servers. REPOSITORY LOGON Each ARO will also be given a login to the SMKI Repository. Their login will be their address and they will be asked to set a password before they leave DCC.

40 DCC Testing

41 Agenda The big picture and Testing Mandatory Testing Managed Service Providers and Placing Reliance Your Testing as a Supplier 40

42 Translation Test Phases The Big picture and testing Test phases are defined in regulatory documents and contracts, i.e. the Smart Energy Code (SEC) and DCC s Service Provider contracts The scope of phases starts narrow and becomes broader Functionality is tested by the DCC before being exposed to Testing Participants DCC Testing: Energy Consumers Data Communications Company (DCC) DCC Service Users Smart DCC Limited Energy Supplier Pre-Integration Testing (PIT) Systems Integration Testing (SIT) The role of DCC is to provide communication services between smart meters and energy suppliers, network operators and other authorised DCC users. User Testing: Smart Metering Key Infrastructure (SMKI) & Repository Entry Process Testing (SREPT) User Entry Process Testing (UEPT) Comms Comms Enterprise Systems Data Key Infrastructure Electricity and gas network operators Other DCC User could be your business End-to-End Testing (E2E) 41

43 Mandatory Testing SREPT SMKI & Repository Entry Process Testing (SREPT) must be conducted by any SEC Party or Registration Data Provider (RDP) that intends to communicate with DCC and to obtain Live SMKI Certificates A Testing Participant (TP), should successfully complete SREPT to receive their Live SMKI Credentials to operate as an Authorised Subscriber or to access the SMKI Repository SREPT should demonstrate that the SEC Party or RDP s systems, and back office processes, are able to successfully use the SMKI and SMKI Repository interfaces UEPT User Entry Process Testing (UEPT) must be conducted by any TP that intends to communicate with meters and access the Self Service Interface (SSI) via DCC and must first become a DCC User UEPT should demonstrate that the testing participants have been able to execute their test scenarios successfully against their identified User roles (i.e. Supplier, Other User etc.) To conduct UEPT the TP must be a SEC Party and have completed SREPT (up to the point of having access to SMKI Certificates) prior to UEPT execution in order to obtain access to the DCC User Gateway A TP should successfully complete UEPT to receive their Test Completion Certificate to then be able to enter in to End to End Testing which is an optional test phase for each User Role that has successfully completed UEPT 42

44 Managed Service Providers and Placing Reliance Testing participants can place reliance on testing conducted by other parties, i.e. their Managed Service Provider (MSP) DCC will work with a Party or their MSP to assess requirements on a case-by-case basis, recognising that individual circumstances are likely to differ Party s would need to direct DCC on the level of communication they wish for us to undertake with their MSP DCC s preference is to copy Party s into all communications with your MSP Party s can be as involved in the process as they wish following the initial notification for intention to undertake testing 43

45 What testing do I need to do if I have a Managed Service Provider? All Parties must follow the process to conduct testing, i.e. provide notification, artefacts etc. The relevant Party or Party s MSP complies with requirements of testing e.g. Requirements Traceability Matrix (RTM) demonstrating coverage of scenarios and evidence that scripts cover requirements of each scenario (as set out in SMKI and Repository Test Scenarios Document (SRTSD) and Common Test Scenarios Document (CTSD)) Architecture diagram from a Party or Party s MSP that demonstrates how testing performed will meet the equivalent for live must be provided Confirmation from the Party that this evidence is correct If architecture is identical, a TP will need to conduct limited testing to be undertaken by TP s to demonstrate their ability to use DCC systems SREPT = minimum of 3 tests to prove organisation credentials UEPT = up to to 4 tests to prove you can exercise each interface If not identical, a case by case assessment of the tests that must be conducted 44

46 R1.3 testing: Options Available Commenced = Submitted test artefacts Q. Had you commenced Release 1.2 UEPT testing prior to Release 1.3 being deployed into UIT? Deployment to start 27/03 & end 05/06 A. Yes A. No You can opt to complete R1.2 UEPT prior to starting R1.3 Testing either via UEPT or E2E You must complete UEPT for R1.2 &1.3 45

47 R1.3 Testing: UEPT v E2E UEPT E2E Laboratory DCC (C&S or N) DCC (C&S or N) OR Remote Test Lab Comms Hubs DCC Testing Comms Hub DCC Testing Comms Hub Devices DCC Enhanced Emulator DCC Enhanced Emulator (in DCC Lab only) OR Own Devices PPMID / HCALC Emulator (where role requires & using a DCC Enhanced Emulator) Progress updates Yes - Test Readiness Reports weekly from 40 working days Yes Test Artefacts submission required 25 working days before start date No Entry Gate Yes No Progress Reporting Yes (Daily Test Execution Report required) Yes (Daily Test Execution Report requested) Evidence of successful SRs Required for all R1.2 & R1.3 SRs in order to be UEPT complete Entry to E2E & use in Production Required to allow use in Production 46

48 Testing Process UIT ENVIRONMENT R1.2 UEPT Not Commenced (when R1.3 deployed in UIT) R1.2 UEPT Commenced (when R1.3 deployed in UIT) R1.2 UEPT Complete (when R1.3 deployed in UIT) Eligibility for E2E Testing in UIT Environment TP Eligible to use R1.2 & R1.3 SRs in E2E Combined R1.2 & R1.3 TP decide their R1.2 Testing Approach UEPT TP decide their R1.3 Testing Approach E2E TP complete UEPT Entry Criteria TP complete UEPT Entry Criteria for R1.3 Split R1.2 & R1.3 TP complete UEPT Entry Criteria for R1.3 TP conduct UEPT on DCC Meters / Enhanced Emulators in DCC Lab TP conduct UEPT of R1.2 SRs on DCC Meters / Enhanced Emulators in DCC Lab TP conduct UEPT of R1.3 SRs on DCC Enhanced Emulators in DCC Lab TP demonstrate R1.3 SRs in E2E on DCC Enhanced Emulators or own devices Eligibility for using SRs in Production Environment TP Eligible to use All R1.2 SRs in Prod All R1.2 & R1.3 SRs Successfully Tested by TP All R1.2 SRs Successfully Tested by TP All R1.3 SRs Successfully Tested by TP All R1.3 SRs Successfully Tested by TP TP Eligible to use All R1.3 SRs in Prod DCC confirms R1.2 UEPT Complete DCC Confirms R1.3 UEPT Complete DCC confirms R1.3 SRs Complete & entry to Production DCC Confirms R1.2 & R1.3 UEPT Complete 47

49 Self Service Interface (SSI)

50 How have I connected today? Before attempting to connect I have ensured that my organisation has fulfilled the pre-requisites*: Configured my gateway connection for Live SSMI Live SMKI Credentials issued Live DCCKI Credentials issued Organisation Admins created User Accounts created And then today I have: 1 Connected to the internet 2. Connected to the DCC Gateway Connection 3. Logged onto SSMI *This is further detailed in the Customer On-boarding Journey 49

51 Lets look at the Self Service Interface 50

52 Extra Material Self Service Interface Design Specification: (Appendix AH) 51

53 Forecasting

54 Objectives Forecasting and its importance Forecast types, and what they are used for Timelines and Benefits Dealing with knowns and unknowns Continual improvement practices Common problems being encountered Questions

55 Forecasting and its importance Mapping the Smart Meter journey for the Industry Insight to allow proactive steps to be taken On target delivery across DCC and all Service Provider teams Ensuring that the growth of DCC is in line with the growth of each Customer Network capable of the timings required to support your customers

Forecast Types and Purpose SEC Quarterly SMKI CSR Forecast Submit by Working Day 15 for March, June, September and December SMKI Repository Downloads Service Requests Forecast SEC L8.

56 Forecast Types and Purpose SEC Quarterly SMKI CSR Forecast Submit by Working Day 15 for March, June, September and December SMKI Repository Downloads Service Requests Forecast SEC L8.7 SMKI CoCo Submit by Working Day 15 for March, June, September and December SEC H3.22 Depending on your Role, you may need to provide monthly and quarterly forecasts for: Communication Hubs SMKI CSRs SMKI Repository Downloads Service Requests Submit by Working Day 15 for January, April, July and October Who needs to submit these forecasts? SMKI CSR Forecasts should be submitted by Authorised Subscribers in respect of device certificates. SMKI Repository Download forecasts should be submitted by DCC Customers who are obliged to forecast the number of Certificate downloads they expect to make each month in the upcoming eight months. Service Request forecasts should be submitted by the Gateway Party detailing the total number of Service Requests submitted by that SEC Party for each month. Forecasts are monitored against actuals and variants and reports are created if data goes outside the tolerances (8 month rolling forecast). Consultation regarding converting transition arrangement to enduring variation requiring Parties who are just about to become Customers to submit information regarding their intended usage of DCC systems in advance of their actually becoming a DCC User.

57 Forecast Types and Purpose SEC Monthly Comms Hubs Forecast SEC F5 Submit 5 full Working Days before month end Comms Hubs Order Submit 5 full Working Days before month end Who needs to submit these forecasts? Anyone planning to install Comms Hubs will need to submit these forecasts and orders DCC Quarterly Comms Hubs & Smart Metering volumes Submit by Working Day 3 for March, June, September and December Not SEC Obligation Service Requests Forecast Submit by Working Day 3 for March, June, September and December (36 Month forecast) Who needs to submit these forecasts? All DCC Customers are encouraged to provide the information for charging statements and budgets.

Timelines / Benefits for Customers Quarterly for 36 months Comms Hubs & Smart Metering volumes Service Requests Forecast Roadmap Helps to create charging statements in line with real demands and up

58 Timelines / Benefits for Customers Quarterly for 36 months Comms Hubs & Smart Metering volumes Service Requests Forecast Roadmap Helps to create charging statements in line with real demands and up to date information. Quarterly for 8 months SMKI CSR Forecast SMKI Repository Downloads Service Requests Forecast Configure Rolling forecasts will provide low effort security certification and close management of message volumes. Proactive interaction when demands or plans create risk for round trip times or network utilisation. Monthly for 24 months (10 month minimum) Comms Hubs Forecast / Order Commit Regular opportunity to fine tune forecasts and orders (either higher or lower) for comms hubs

Comms Hub Forecast & Order - Monthly Timeline JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC Comms Hub Forecast Comms Hub Order Submission due 5 full Working Days before end of the month Worked

hubs in a given month, must submit its first forecast 10 months prior to the required delivery month Key: 10th Month forecast 7th Month Forecast Order Submitted Delivery Month Order Guidelines Order

59 Comms Hub Forecast & Order - Monthly Timeline JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC Comms Hub Forecast Comms Hub Order Submission due 5 full Working Days before end of the month Worked Example of Monthly Comms Hub Forecast & Order Forecast Guidelines 24 month rolling forecast by regions Minimum 896 units, multiples of 224 thereafter (per region) A SEC Party requiring a delivery of hubs in a given month, must submit its first forecast 10 months prior to the required delivery month Key: 10th Month forecast 7th Month Forecast Order Submitted Delivery Month Order Guidelines Order submission 5 months before delivery date Minimum 896 units, multiples of 224 thereafter (per region) Order by Comms Hub variant Order subject to these thresholds: +/-50% of month 10 forecast, and +/-20% of month 7 forecast Orders outside of the thresholds may be subject to amendment in accordance with the Comms Hubs Order Policy Additional information Section F5 SEC 4.5 and Comms Hubs Handover Support Materials Please Note: TEF Mesh Hubs are supplied in palettes of 640 units rather than 896 units and each palette layer is now 160 instead of 224

Dealing with knowns and unknowns Forecasts create a pin in the map, but we must recognise that it will not be able to

Accuracy is important, and this is reflected within SEC by the accuracy obligations on each party.

DCC can help Customers meet those needs.

60 Dealing with knowns and unknowns Forecasts create a pin in the map, but we must recognise that it will not be able to cover every eventuality, as we are dealing with multiple SEC parties who each have their own plan. However. Accuracy is important, and this is reflected within SEC by the accuracy obligations on each party. Customers will know more about their customers and their needs than we will, and by gaining that insight via the forecasts DCC can help Customers meet those needs. Accuracy will improve as we use the network and provide feedback on actual performance to Customers, which can be compared to the forecast. Comparing usage patterns between Customers can provide insight which will inform future forecasts for all.

61 Continual Improvement Practices Forecasts will improve over time, but improvement will be accelerated if it is considered as a whole system. All forecasts will benefit from input from a range of Customer factors which will change: Rollout plans acceleration, slow down or changes to regional split Installation experience, and approach partners, pace and process Sales and Marketing sales, upgrades, regional and seasonal Technical input firmware, security, and functionality Logistics delivery, stock levels, replacements Customer behaviour usage, requirements, feedback, complaints Customer types - pre-pay / credit, dual fuel, in home displays DCC will use the information to ensure the network and services meet the needs of the industry.

How to avoid COMMON Forecast Problems Develop a plan, and establish the key dates.

Keep a close eye on the detail requested, to avoid delays.

Target accuracy is an obligation for Customers and is subject to SEC Panel reporting.

62 How to avoid COMMON Forecast Problems Develop a plan, and establish the key dates. Forecasts should be proportional to each other (i.e. SR, SMKI and CHs). Keep a close eye on the detail requested, to avoid delays. Download the latest forecasting templates, as we keep them up to date. Target accuracy is an obligation for Customers and is subject to SEC Panel reporting. Use of actual results should be used to improve forecast accuracy. Timing of order windows are set, but you can order early to avoid disappointment. Have a backup person to place orders to cover holidays and absence.

How to avoid COMMON OMS Problems Allowed 4 OMS

delivery, or you may be liable for cancellation

Months 8 and 11 are important as they run the risk

Orders need to be submitted to count - don t create

Calculate your orders in pallet layers, unless

63 How to avoid COMMON OMS Problems Allowed 4 OMS logons, nominate your contacts early so you have system access. Contact DCC to discuss preferences, as we may be able to accommodate them. Delivery address details are needed before delivery, or you may be liable for cancellation charges. Months 8 and 11 are important as they run the risk of being deemed as your commitments. Orders need to be submitted to count - don t create and then not submit. Calculate your orders in pallet layers, unless further charges are to apply. Charges may apply if CHs are forecast when they are not required. Order values may need to change to make an aggregated order compliant, but we will tell you if we cant accept your order volume.

64 Comms Hub & SM-WAN Assurance

65 Agenda Smart Metering Wide Area Network (SM WAN) Communications Hubs Aerials Which Comms Hub to Install Where? Installing Comms Hubs Product Supply Chain

66 SMART METERING WIDE AREA NETWORK THE SM WAN

67 Smart Metering Wide Area Network Two Communications Service Providers (CSPs) supply the GB-wide Smart Metering Wide Area Network

68 Smart Metering Wide Area Network Providing GB with Smart Metering connectivity Long-Range Radio communications (LRR), which will be used by Arqiva in Scotland and the North of England. Cellular radio communications, which will be used by Telefónica in the rest of England and Wales. The LRR system uses infrastructure and technology similar to that already used for other important national communications networks, such as those for emergency services and keeping lifeboat stations connected. Communication towers communicate directly with smart meter Communications Hubs in homes. The cellular radio system uses technology already widely used for mobile phone systems. In a cellular system, geographical areas are divided into regular shaped cells. Each cell has at least one transceiver (a device which both transmits and receives radio signals) and when joined together, the cells provide coverage over wide geographical areas. Households in different regions will receive the same quality of service.

69 COMMUNICATIONS HUBS

70 Communications Hubs - Providers Two Communications Service Providers (CSPs) provide Comms Hubs that operate in their SM WAN regions

71 Communications Hubs - Manufacturers Three Communications Hub Manufacturers One for Arqiva Two for Telefonica

72 Communications Hubs What They Do Comms Hubs allow Smart Metering Devices to interact Access Dual Fuel Consumption In Home Display Electric Meter *Illustrative smart metering devices Comms Hub Gas Meter

73 Communications Hubs What They Do Comms Hubs allow Energy Suppliers to communicate with their customers Smart Metering devices Tariff Updates CoS / CoT DCC Customer (DCC User) Meter Readings Device Alerts Customer

74 Comms Hub Variants Different Comms Hubs for each CSP Region Comms Hub Variants A Variant is a Comms Hub model that uses a specific communications technology to connect and communicate across the SM WAN. In the North region, Comms Hubs connect to Arqiva s Long Range Radio network. In the Central & South regions, Comms Hubs connect to Telefonica s Cellular network. Some Central & South region Comms Hub variants allow the use of an aerial to improve connection to the SM WAN in those regions.

75 Communications Hub Variants By CSP Region Arqiva Telefonica Standard 420 Cellular (SKU1) Cellular + Mesh (SKU2) Variant 450 Cellular (SKU1) Special Installation Mesh (SKU3)

76 Arqiva Comms Hubs EDMI Standard 420 WAN Technology - Long Range Radio 420 MHz HAN Technology GHz ZigBee Height from bottom face: 91.76mm Height from ICHIS datum: 80.0mm Depth: 65.61mm Width: mm Points of note For installation in entire CSP North region (except Fylingdales area) in 98% of homes This Comms Hub doesn t require an external aerial

Arqiva Comms Hubs EDMI Variant 450 WAN Technology - Long Range Radio 450 MHz HAN Technology - 2.4 GHz ZigBee Height from bottom face: 91.76mm Height from ICHIS datum: 80.0mm Depth: 65.61mm Width: 130.

77 Arqiva Comms Hubs EDMI Variant 450 WAN Technology - Long Range Radio 450 MHz HAN Technology GHz ZigBee Height from bottom face: 91.76mm Height from ICHIS datum: 80.0mm Depth: 65.61mm Width: mm Points of note For use only in the Fylingdales area Of North Yorkshire Represents approx. 2% of CSP North region This Comms Hub doesn t require an external aerial The Variant 450 device will look like the Standard 420. The visual difference will be in the artwork

78 Telefonica Comms Hubs WNC SKU1 Cellular WAN Technology - Cellular HAN Technology GHz ZigBee Height from bottom face: 77.8mm Height from ICHIS datum: 66.0mm Depth: 64.9mm Width: mm Points of note For installation in entire CSP Central and South regions in 90% of homes This Comms Hub doesn t require an external aerial

79 Telefonica Comms Hubs Toshiba SKU1 Cellular WAN Technology Cellular HAN Technology GHz ZigBee Height from bottom face: 78mm Height from ICHIS datum: 66.11mm Depth: 64mm Width: mm Points of note For installation in entire CSP Central and South regions in 90% of homes This Comms Hub doesn t require an external aerial Same functionality as the WNC SKU1 Cellular

80 Telefonica Comms Hubs Toshiba SKU2 Cellular + Mesh WAN Technology - Cellular + Mesh HAN Technology GHz ZigBee Height from bottom face: 85mm Height from ICHIS datum: 73.11mm Depth: 83.50mm Width: mm Points of note For installation in entire CSP Central and South regions in 9.5% of homes This Comms Hub can mesh to other mesh CHs This Comms Hub can utilise an external cellular aerial

81 Telefonica Comms Hubs Toshiba SKU3 Special Installation Mesh Comms Hub WAN Technology - Cellular + Mesh HAN Technology GHz ZigBee Height from bottom face: 85mm Height from ICHIS datum: 73.11mm Depth: 83.50mm Width: mm Points of note For installation in entire CSP Central and South regions in 0.5% of homes This Comms Hub can mesh to other mesh CHs This Comms Hub can utilise an external cellular aerial & an external mesh aerial

82 The Communications Hubs Breakdown CSP Region WAN Variant Manufacturer Comms Technology External Aerial Port? North (Arqiva) Standard 420 Variant 450 Fylingdales EDMI Long Range Radio No SKU1 Cellular Hub WNC & Toshiba Cellular Central & South (Telefonica) SKU2 Mesh Hub SKU3 SIMCH Toshiba Cellular & Mesh 1 Cellular 1 Cellular, 1 Mesh

83 Comms Hubs & Their Uses In addition to Production models.we have. Test Comms Hub (TCH) A variant used for testing which is not permitted to be used on a Production Environment Dual Band Comms Hub (DBCH) future product A variant which has both 2.4 GHz and 868 MHz HAN provision to additional installation options (i.e. gas meter out of range of standard Comms Hub) Training Simulator Comms Hubs (TSCH) A training device which can be controlled by smart phone to simulate the LED behaviours of a Comms Hub, for training purposes.

84 COMMS HUB AERIALS

85 Comms Hub Aerials Aerials for Specific Comms Hub Variants Aerials are not used in CSP(N) Arqiva region, only CSP (C&S) There are three aerial types: T1, T2 and T3. Aerials are used in some situations in CSP (C&S) Telefonica region, some aerial types are fitted by the Energy Supplier s installers (T1 and T2) Some aerials are provided and fitted by DCC (T3)

86 Aerial Usage Reasons for Use T1 for obstacle avoidance Up to 6% of Comms Hubs million T1 aerials T2 for small range WAN extension Up to 3.5% of Comms Hubs - 682,500 T2 aerials T3 for large range WAN extension Up to 0.5% of Comms Hubs - 97,500 T3 aerials

87 Aerials T1 Panorama Aerial Technology Cellular Type Low Gain Points of note For use in entire CSP Central and South regions with SKU2/3 Comms Hub Used for obstacle avoidance Installed close to Comms Hub

88 Aerials T2 Panorama Aerial Technology Cellular Type High Gain Points of note For use in entire CSP Central and South regions with SKU2/3 Comms Hub Used for small range extension Installed close to Comms Hub

89 Aerials T3 Panorama Aerial Technology Cellular Type High Gain Points of note For use in entire CSP Central and South regions with SKU2/3 Comms Hub Used for large range extension Mounted on external property

90 The Aerials Breakdown

91 WHICH COMMS HUB TO INSTALL WHERE?

92 Planning Installations How an installer knows which Comms Hub to use DCC provides a Coverage Checker Database for Parties to access This allows Parties to check installation postcodes in the DCC Coverage Checker 30 days prior to the Installation Date The response will inform the Supplier of the following: The CSP Region (North, Central, South) The Coverage Availability (Yes/No) The Comms Hub Variant to install (Cellular, Cellular + Mesh, Standard 420, Variant 450) Any Auxiliary Equipment required (aerials) This can be done using DCC Service Requests, the DCC Self Service Interface (SSI) or through the bulk CSV files available from DCC Operational SharePoint

93 Planning Installations DCC Lets You Know Which Comms Hub to Use DCC provides a Coverage Checker Database for Parties to access Installation Postcodes DCC Customer (DCC User) DCC Coverage Checker CSP Coverage Comms Hub Aerials

94 INSTALLING COMMS HUBS

95 Install and Commission Installation Procedure There are three ways to install a Comms Hub Fit a Comms Hub to a SMETS2 Electric Meter Fit a Comms Hub to a Hot Shoe Fit a Comms Hub to a Flying Lead

Install and Commission Installation Procedure SMETS2 Electric Meter Fit a Comms Hub to a SMETS2 Electric Meter Step 1 - Align Comms Hub guide rails with the U- channel of the ICHIS compliant host

96 Install and Commission Installation Procedure SMETS2 Electric Meter Fit a Comms Hub to a SMETS2 Electric Meter Step 1 - Align Comms Hub guide rails with the U- channel of the ICHIS compliant host (SMETS2 electric meters, Hot Shoes* and Flying Leads*) Step 2 - Slide the Coms Hub on to the ICHIS compliant host Step 3 - Press the front faceplate in order to connect the Comms Hub to the interface of the ICHIS compliant host, applying hand pressure only Step 4 - Screw in the M4 retaining screw located on the front faceplate *See next slides for information on Hot Shoes and Flying Leads

97 Install and Commission Installation Procedure Hot Shoe Fit a Comms Hub to a Hot Shoe A Hot Shoe can be used where the Comms Hub is not fit directly onto a SMETS2 electric meter, for gas only installs, for example Electric meter The Hot Shoe is connected via an integrated 230v AC to 12v DC power supply and is sourced/provided by the Energy Supplier/Registered Supplier Agent (DCC do not supply Hot Shoes) Follow Steps 1 through to 4 on slide Installation Procedure SMETS2 Electric Meter to fit the Comms Hub onto the Hot Shoe host Hot Shoe Cut Out Comms Hub

98 Install and Commission Installation Procedure Flying Lead Fit a Comms Hub to a Flying Lead A Flying Lead can be used where the Comms Hub is not able to be positioned on top of a SMETS2 electric meter - where there are space limitations The Flying Lead is connected to the ICHIS connection on the SMETS2 electric meter and provides the ability to move the Comms Hub to a different location at the installation point and is sourced/provided by the Energy Supplier/Registered Supplier Agent (DCC do not supply Flying Leads) Flying Lead SMETS2 electric meter Comms Hub Flying Lead Follow Steps 1 through to 4 on slide Installation Procedure SMETS2 Electric Meter to fit the Comms Hub onto the Flying Lead host Meter Board

99 PRODUCT SUPPLY CHAIN

100 Product Supply Chain CSPs, Comms Hub & Aerial OEMs + Fulfilment Partner CSP North Comms Hub OEM Aerial OEM Fulfilment Partner N/A CSP Central & South Comms Hub OEM Aerial OEM Fulfilment Partner

101 REFERENCES

102 Reference Documents Communications Hub Support Materials These can be found on the Smart Energy Code website: Click on the SEC Subsidiary Documents link and the documents are: Appendix H - CH Handover Support Materials and Appendix I - CH Installation and Maintenance Support DUIS DCC User Interface Specification can be found on the Smart Energy Code website: Click on the SEC Subsidiary Documents link and the document is: Appendix AD - DCC User Interface Specification ICHIS The Intimate Communications Hub Interface specification which defines the CH PIN interface can be found on the DCC website:

103 Reference Documents GBCS The Great Britain Companion Specification can be found on the Smart Energy Code website: Click on the SEC Subsidiary Sections link and the documents is: Schedule 8 - GB Companion Specification SSI The Self-Service Interface documents can be found on the DCC website: DUGIDS The DCC User Gateway Interface Design Specification (DUGIDS) documentation can be found on the DCC website:

104 Reference Documents SMIP Design Notes Design Note document can be found on the Smart Energy Code website: Useful documents are: Install and Commission (Released) Describes how to install and commission smart metering equipment Communications Hub Exchange (Released) Describes the process to be followed in premises and the Service Requests involved in the exchange of a Communications Hub Communications Hub Re-use (Released) Describes the process to be followed in premises and the Service Requests involved in the exchange of a Communications Hub No Wireless Area Network (Draft) Describes how to install and commission smart metering equipment in events where there is temporarily no WAN

105 Reference Documents SM WAN, Comms Hub and Aerial information can be found on the DCC website Smart Meter Wide Area Network - DCC Assurance Strategy Comms Hub Product Range Comms Hub Aerial Range Comms Hub WAN Variant Usage Forecast Guidance _v1.1.pdf Full selection of datasheets and information on Comms Hubs, SM WAN and aerials:

106 SMETS1 Update

107 SMETS1 Update Classification 106

108 Topics Principles and Scope IEPFR and other consultations EOT2 107

109 SMETS1 Programme Principles and Scope 108

110 Switch, stay smart 109

111 Protect investments Classification

112 SMETS1 market in the IEPFR* scope 11+ Million Meters by 2018 (According to Supplier Forecasts) * Initial Enrolment Project Feasibility Report 111

113 The Players Energy Supplier SMSO SMETS1 CSP Meter Manufacturer Energy Suppliers who proposed meters for inclusion in the IEPFR SMSOs providing managed services to those Suppliers SMETS1 CSPs providing connectivity Meter manufacturers Who has invested since? 112

114 Initial Enrolment Project Feasibility Report (IEPFR) and other consultations

115 IEPFR consultation responses Participation in IEPFR workshops Further 2 week period to submit revised/additional consultation responses DCC PUBLIC 114

116 Upcoming consultations Timeline for delivery Consultation launches April 2017 Options into choices (high level design) Summer 2017 Detailed design Through later 2017 and early

117 Enrolment Options Testing (EOT) 116

118 EOT 2 Research Objectives Architecture and Delivery Exploring architectural ideas by developing modular test software in a cloud service environment Exploring continuous integration and release approaches through promoting code through development and test into live Functionality Testing hypotheses for how the Enrolment transaction will be effected Testing hypotheses for delivery of prepayment services Testing hypotheses for securing the estate of integrated SMETS1 meters Commercial Creating small research-based commercial agreements with organisations that may form part of the SMETS1 delivery supply chain 117

119 EOT Overview 118

120 ANY QUESTIONS? 119

Annual Service Report. Performance Year 2016/17

Annual Service Report. Performance Year 2016/17 Performance Year 2016/17 Submitted: 31/08/2017 Contents 1 Context... 4 2 Introduction... 5 3 Performance Year 2016/17 Context... 6 3.1 Key Events... 6 4 DCC Service Delivery Performance... 8 4.1 Operational