OpenHAN Boot Camp

1. OpenHAN Boot Camp July 19, 2010

2. OpenHAN TF Overview Chair Erich W. Gunther, EnerNex – erich@enernex.com Co-chair Mary Zientara, Reliant Energy - mzientara@reliant.com Task Groups: OpenHAN 2.0 Mary Zientara, Reliant Energy, chair Charlie Smith, GE, co-chair Charles Spirakis, Google, co-chair Zahra Makoui, PG&E, co-chair

3. OpenHAN TF Information Email reflector: OPENSG-SGSYS-OPENHAN@SMARTGRIDLISTSERV.ORG Web meeting information: Provided via email to all members of OpenHAN reflector Announced on the OpenSG sharepoint in the OpenHAN calendar Web meeting times: Meeting minutes and documents: http://osgug.ucaiug.org/sgsystems/openhan/default.aspx

4. OpenHAN Detroit F2F Agenda Monday, July 19th SG Systems Boot Camp – OpenHAN @ 4:35 PM – Mary Zientar Note: Session is an overview for newcomers Tuesday, July 20th 1:00 – 3:00 – OpenHAN 2.0 Work Session - Woodward C – 2 - Mary Zientara 3:30 – 5:30 - OpenHAN 2.0 Work Session - Woodward C – 2 - Mary Zientara Wednesday, July 21st 1:00 – 3:00 - Joint session with SG Security - Woodward D – 2 - Mary Zientara 3:30 – 5:30 - OpenHAN 2.0 Work Session - Founders A – 3 - Mary Zientara Thursday, July 22nd 10:30 – 12:00 - Work Session - Woodward D – 2 - Mary Zientara 12:00 – 1:00 pm - Closing Plenary – Report Outs

5. 2008 2007 2009 2010 August 2008 UtilityAMI 2008 HAN SRS v1.04 released OpenHAN TF is formed to develop system requirements for the HAN June 2009 Utility AMI 2008 HAN SRS v1.04 selected as a customer domain standard in the NIST Smart Grid Interoperability Standards Roadmap October 2009 OpenHAN 2.0 formed to develop the next version of the HAN SRS July 2010 UCAIug HAN SRS v1.98 released August 2010 UCAIug HAN SRS v2.0 ratified OpenHAN History

6. UCAIug HAN SRS v1.98 Purpose Define the system requirements for an open standard Home Area Network system Promote open standards-based HANs that are interoperable Provide the vendor community with a common set of principles and requirements around which to build products Ensure reliable and sustainable HAN platforms Support various energy policies in a variety of states, provinces, and countries Empower consumers to manage their electricity consumption by giving them the information and control they need to make decisions on their energy use 6

7. Scope of OpenHAN in the NIST conceptual model 7

8. HAN SRS v1.98 The audiences for the HAN SRS are: Utilities considering deploying AMI systems that interact with HANs Vendors that make AMI systems for Utilities that interact with HANs Vendors that make consumer products (e.g. programmable communicating thermostats, energy management systems, load control switches, in-home displays, smart appliances, Plug-in Electric Vehicles (PEV), distributed energy resources, etc.) Service Providers developing smart grid enabled programs for consumers (e.g. demand response, energy management, pre-pay, PEV programs, distributed energy resources, etc.) Policy makers looking to understand how Utility AMI deployments that interact with HANs benefit and impact consumers Industry alliances and standards organizations NIST Smart Grid Interoperability Panel (SGIP) activities (e.g. Smart Grid Architectural Committee (SGAC), Cyber Security Working Group (CSWG), Smart Grid Testing and Certification Committee (SGTCC), etc.) 8

9. HAN SRS v1.98 Guiding Principles Capabilities Support Two-way Communication Between HAN Devices and Service Providers Supports load control integration The AMI meter provides the HAN with direct access to Consumer-specific usage data Provides a growth platform for future products which leverage the HAN and meter data Supports three types of messaging: Public Information, Consumer-Specific Information, and Control Signals Supports end-use metering and other utility meters Supports distributed energy resources Assumptions Consumer owns the HAN HAN devices present additional security considerations The HAN is enabled by open and interoperable standards 9

10. HAN SRS v1.98 Architectural Considerations OpenHAN applies from the edge of the AMI System, where the Energy Services Interface (ESI) resides, to all relevant HAN Devices in the home Energy Services Interface (ESI) An interface which enables communication between authorized parties and HAN devices that are registered to it There may be more than one ESI in the premise (e.g. Utility ESI, 3rd party ESI) Utility ESI – provides interface between the Utility AMI network and HAN devices Other ESI – provides interface between other communication media (e.g. internet, cell phone, EMS, etc.) and HAN devices registered to it 10

11. HAN SRS v1.98 Architectural Considerations, continued Commissioning, Registration, Enrollment Commissioning is the process by which a HAN device obtains access to a specific physical network and allows the device to be discovered on that network Registration is the process by which a Commissioned HAN device is authorized to communicate on a logical network by exchanging security credentials with an ESI Enrollment is the process by which a Consumer enrolls a HAN device in a Service Provider program (e.g. demand response, energy management, PEV program, etc.) 11

12. HAN SRS v1.98

13. HAN SRS v1.98 Architectural Considerations, continued OpenHAN SRS is agnostic to device ownership Some HAN devices may reside on more than one ESI OpenHAN SRS is agnostic to electric market structure and may be used in integrated utility markets as well as consumer choice electric markets There may be multiple communication paths into the HAN (e.g. Utility AMI, internet, cell phone network, EMS, etc.) OpenHAN SRS addresses the following special applications Plug-in-Electric Vehicle (PEV) Energy Management System (EMS) Distributed Energy Resources (DER) 13

14. HAN SRS v1.98 HAN System Requirements Application Requirements Control applications respond to control signals Measurement and Monitor applications provide internal data and status Processing applications consume, process, and act on external and internal data Human Machine Interface (HMI) provides Consumers a means to provide input into an application or to view information from an application Communication Requirements Commissioning is the network process of adding a HAN device on the HAN to allow the device to communicate with other devices and involves network scanning, selection, admission, and configuration Control of a node involving self-organization, path selection, mitigation 14

15. HAN SRS v1.98 HAN System Requirements, continued Security Requirements Access Controls and Confidentiality address data protection for data-at-rest and data-in-transit Registration is the network process to authenticate and authorize HAN device participation with an ESI and includes initialization, authentication, correlation, authorization, and de-register Enrollment is the process by which a Consumer enrolls a HAN device in a Service Provider’s program (e.g. demand response, energy management, pre-pay, PEV programs, distributed generation, pricing, messaging, etc.) and gives certain rights to the Service Provider to communicate with their HAN device Integrity preserves the HAN operating environment through resistance and recovery Accountability will allow for monitoring malicious activities through audit and non-repudiation 15

16. HAN SRS v1.98 HAN System Requirements, continued Performance Requirements Ensure applications or other factors do not limit the performance of the system, which is dependent upon availability, reliability, maintainability, scalability, upgradeability, quality and latency Operations, Maintenance, and Logistics Requirements Manufacturing and Distribution - Vendor’s pre-installation activities including pre-Commissioning settings, application configuration, labeling, support for multiple distribution channels Installation – Documentation for the physical placement of the device and support systems Manage, Maintain – ensure HAN device diagnostic, management and trouble shooting capabilities including alarming, logging, testing, device reset, and monitoring 16

17. HAN SRS v1.98 Requirements Mapping to Logical Devices • Provides guidance to Service Providers and vendors • For reference only and should not limit the needs of Service Providers or vender innovation • Mapping Categories • CP or CommissioningProcess– Minimum requirement for the Commissioning process. These requirements are mandatory and must be included to support the process of Commissioning a HAN device on the HAN. • RP or Registration Process - Minimum requirement for the Registration process. These requirements are mandatory and must be included to support the process of Registering a HAN device on the ESI. • BF or Basic Functionality – Minimum requirement that the OpenHAN TF recommends is needed to support the basic functionality of the logical HAN device. • S or Security – Minimum requirement for HAN security. These requirements are mandatory and must be included to protect the HAN against compromises to the confidentiality, integrity, and availability of the HAN • O or Optional – An optional requirement that may be included to support a Service Provider program or allow a vendor to differentiate their product. • NA or Not Applicable - This requirement is not applicable to this logical HAN Device.

18. HAN SRS v1.98 Requirements Mapping to Logical Devices, continued Mapping table located after each requirement section 18