Zig Bee Home Plug Joint Working Group

Zig. Bee® + Home. Plug® Joint Working Group - The Smart. Energy Profile AMI-Ent Task Force Meeting January 6, 2009 For further information, contact: Jeremy Mc. Donald (Jeremy. [email protected] com) Zig. Bee Smart Energy TWG Chair Zahra Makoui (zxm [email protected] com) Member of Zig. Bee & Home. Plug TWG Greg Robinson ([email protected] net), Vice-Chair of Zig. Bee & Home. Plug TWG – Applications TF Copyright © 2008 Accenture All Rights Reserved. Accenture, its logo, and High Performance Delivered are trademarks of Accenture.

The Approach § To build on what we already have § To work through a process open to stakeholders to define the solutions § To define a standard and certification process that scales a mainstream retail market distribution channel 2

Utility Goals Robust System Solution Sta nda mon Com re u itect Arch Standards defined with a comprehensive certification process rds Stra tegy Mainstream Market Adoption s es oc on Pr i r Ce t at fic i Plug N Play Interoperability By aligning behind a common architecture, standards strategy and a comprehensive certification process, we can ensure a robust system solution, Plug N Play Interoperability and a target of zero customer support calls. 3

Current State of the Industry Current State Utility Requirements Fragmented Standards Efforts Many Moving Pieces Minimal collaboration between industry resulting in proprietary processes to each utility Joint Utility Leadership propr ietary l ra cation he Certifi rip Ar Sys ch te ite m ctu re HAN Standards and Certifications pe ve g® Plu Home SO Z-Wa ee IP ® g. B Zi HAN standard definitions and clear path to certification Common Comprehensive Solution There is an opportunity to align around a common comprehensive solution § Fragmented standards § Timing is good § No common end-to-end system definition § Standards bodies are open to utility engagement § No comprehensive certification process § Pick the best minimum solution 4

Utility Requirements Current State HAN standard definitions and clear path to certification Fragmented Standards Efforts SO IP ® e Be Zig Home. Pl ug ® HAN Standards and Certifications SO IP Arc Sys hit tem ec tu re Certifi cation Industry Collaboration Z-Wave Common Comprehensive Solution Many Moving Pieces Align to define a common comprehensive solution by focusing on: § Aligning the standards § Common and scalable end-to-end system definition with a robust registration process. (e. g. , activation, commissioning, provisioning) § Ensuring a plug-n-play solution targeting zero customer support calls § Define a comprehensive industry certification process that satisfies these requirements 5

Mainstream Market & Scalability Requires a Comprehensive Solution Mainstream Market Adoption Align Standards Common System Definition Plug-N-Play Interoperability Comprehensive Certification Process Technology Independent Requirements (Open. HAN) 6

Overview of HAN standards Requirements Technology HAN Standards Any standards activity that touches the HAN in any way. Zig. Bee® MSC Marketing Steering Committee MWG Oversee Zig. Bee certification Acts as the technical oversight committee and authority Goal of integrating to a common application layer independent of the underlying physical platform Zig. Bee Labs 1. NTS 2. TUV Comprehensive Certification Labs ZB + HP Joint Working Group Zig. Bee Security WG Recently reestablished to review Zig. Bee security issues Utility communications architecture international users group ZB Qualification Group ZARC Zig. Bee Architecture Review committee Marketing Working Group UCAIUG Certification Joint SC Joint steering committee Smart Energy Profile WG TBD chaired by PG&E Utility HAN public profile Open DR IP Connectivity TG Open AMI Vendor implementation models of the utility requirements Marketing WG Market requirements and alignment Technical WG Answer the technical questions Defining Zig. Bee’s IP gateway functionality Chaired by SCE Chaired by Reliant Compliance WG Define certification process Utility AMI Utility driven requirements Home. Plug 1. 0 Home. Plug CC High bandwidth PLC communications std Lower bandwidth PLC communication std Home. Plug Labs No specified labs exist at the moment Home. Plug® AMI enterprise AMI SEC Open HAN Back office integrations requirements Security requirements for the AMI system Technology agnostic HAN requirements HAN standard getting traction in Europe IEC 802. 15. 4 HAN 2. 4 GHz Low power wireless mesh technology Wireless M-Bus SAE J 2836 ROLL 6 l. WPAN Electric Vehicle communications Routing over low power and lossy networks Skinny IP (UDP) over 802. 15. 4 Bluetooth 802. 15 Labs 802. 15 NAN SG 900 MHz No specified labs. NTS and TUV execute their own conformance testing 802. 11 IETF Other Standards SAE IPSO IEEE 7

Working Groups Charters Develop a common system architecture and application profile interfaces for home energy devices, supported by a comprehensive certification process that delivers secure, robust, reliable, plug and play interoperability with AMI and Smart Grid applications Joint SC Joint steering committee chaired by PG&E Marketing WG Market requirements and alignment Chaired by Reliant Sub WGs Technical WG Answer the technical questions Chaired by SCE Sub WGs Certification WG Define certification process Sub WGs • • • Create Market Requirements Document Create Marketing Plan Create and Manage Roadmap Prepare Collateral and Press Releases Create Branding for in premise devices compliance program Manage cross industry and SDO liaisons • Develop the End to End System Specification based on MWG documents • Leverage of industry standards where available • Align Zig. Bee and Home. Plug technical requirements to maximize the efficiency of the implementation • Develop a common Smart Energy Profile using the Zig. Bee Smart Energy Profile as the forward starting point • Develop a comprehensive Certification Program • Develop certification flow and process • Manage the development of the certification standards and document (PICS, TC, Test Harness, Test Report • Define common test tool interface standard • Select and approve and manage test house(s) 8

Zig. Bee + Home. Plug Steering Committee Steering Team Utility Members Zig. Bee BOD Members Chris Knudsen, PG&E – Chair Home. Plug BOD Members Matt Spaur, Itron Wayne Longcore, Consumers Ruben Salazar, Landis+Gyr Gary Stuebing, Duke Michael Bourton, Texas Instruments Brent Hodges, Reliant Kerry Evans, GE Energy Jeremy Mc. Donald, SCE Carl Mansfield, Sharp George Bjelovuk, AEP Skip Ashton, Ember TBD, Oncor TBD, Center. Point Other Utility Contributors Working Groups Must be a member of Zig. Bee and Home. Plug Marketing Technical Certification Brent Hodges, Chair Jeremy Mc. Donald, Chair TBD, Chair Must be a member of Zig. Bee and Home. Plug or Zig. Bee or Home. Plug and sign an IP License agreement * Hydro. One SDG&E FPL Xcel DTE * Waived for this first meeting 9

TWG Objectives § § § § Build upon successful Zig. Bee Application Definition (SE 1. 0) Support MRD Define Common Application Layer – Allow for Platform Optimization (802. 15. 4 and HP) – Develop Common Translation (if necessary) – Reuse SE Profile and IEC CIM Work – Add Advanced Service/Interface Discovery (e. g. , Self Describing Interfaces) – Add Advanced Application Support (PEV, DG, SG Sensor Services) – Force Application Decoupling (Layered Approach) Develop Platform Recommendations – IP Connectivity – Network Interoperability Develop Comprehensive Security Specification – Develop System Level Security Architecture – Define Commissioning/Provisioning and System Registration – Support Multiple Security Suites (If Necessary) – Define Trust Models (e. g. , Root/Chains, Certificate Authorities) – Support Portability – Support Firmware Upgrades with source authentication Develop/Support Test Specifications Support Certification WG Source: Jeremy Mc. Donald Zig. Bee Smart Energy TWG Chair 10

Organization Source: Jeremy Mc. Donald Zig. Bee Smart Energy TWG Chair 11

System Architecture 12

Smart Energy 2. 0 High-level Timeline and Milestones Platform feasibility report Nov 2008 Technical Requirements Document May 2009 Certification Lab Requirements Document July 2009 Master Test and certification strategy December 2008 NOV DEC JAN FEB MAR Smart Energy 2. 0 profile release November 2009 APR 2008 MAY JUN JUL AUG SEP OCT 2. 0 Commercial Availability May 2010 NOV DEC JAN FEB 2009 Comprehensive certification process reference manual April 2009 Draft 0. 1 Market requirements document January 2009 MAR APR MAY 2010 SE 2. 0 Test Plan Final January 2010 Smart Energy 2. 0 Test Plan Draft October 2009 13

Device Types § ESP (Energy Services Portal) – can be integrated into meter or standalone § In-Home Display § PCT (Programmable Communicating Thermostat) § Load Control Devices (Pool Pumps, Water Heaters, Appliances, Lighting, etc. ) § Some support for Plug-In Vehicles § “Dumb” devices (Refrigerator Magnet, Glowing Orb, etc. ) Source: Robby Simpson, Ph. D Zig. Bee Smart Energy WG Chair 14

Price § § § § § Multiple commodities (Electric, Gas, Water, Thermal, Pressure, etc. ) Multiple units of measure for international support (lbs vs. kg) Multiple currencies for international support (ISO 4217) Scheduling and canceling Multiple providers (de-regulated) and rates Price ratios and price tiers (and labels) Tie to meter register tier Net metering Alternative cost (greenhouse gas emissions) Inter-PAN communication Source: Robby Simpson, Ph. D Zig. Bee Smart Energy WG Chair 15

Demand Response and Load Control § § Scheduling and canceling Digital signature for non-repudiation of event participation – Completed, Opt-Out, Opt-In, etc. and “what” happened Can simultaneously or individually target groups of devices § Enrollment groups § Criticality levels, temperature offsets, temperature set points, average load adjustment percentage, duty cycle § Randomization of start and stop times to avoid spiking § Source: Robby Simpson, Ph. D Zig. Bee Smart Energy WG Chair 16

Utility. AMI Open. HAN TF Platform Independent Requirements UCAIUG Utility communications architecture international users group Value Proposition Open DR Guiding Principles Open AMI Vendor implementation models of the utility requirements Utility AMI Utility driven requirements Use Cases AMI enterprise System Criteria AMI SEC Open HAN Back office integrations requirements Security requirements for the AMI system Technology agnostic HAN requirements Platform Independent Requirements Platform Requirements (Technology Specific) 17

Open. HAN Principles § Inferred Architectural principles – Utilities support two logical interfaces § § public interface private interface § § utility network any third party network § this function can be a part of any HAN device – There are two logical networks within the premise – The utility private network is formed through registration – Translation (i. e. , a gateway) is required in order to move data between networks – Certain elements are not architecturally relevant: Device ownership - requirements are universally applicable Third party gateways – does not impact Open. HAN architecture § Physical transport - both networks (public and private) can share the same physical transport § § – separation is logical and separates the applications 18

Utility. AMI Open. HAN TF’s Scenario 6: Mature System 19

HAN Requirements Organization and System Criteria by the Utility. AMI Open. HAN TF There is a good bit to investigate and build on in the CIM 20

IEC 61968 CIM Asset Containers 21

IEC 61968 CIM End Device Functions 22

Call to Action § We have a unique opportunity to align behind a common standard and avoid fragmentation to achieve mainstream market adoption – Regulatory accelerates 100% market adoption – The market size is multi billions – Big tech industry is finally realizing this and will build businesses § If we fragment we will only penetrate a small fraction of the potential market 23