1. OpenHAN TF Meeting Where do we go next? Erich W. Gunther

2. Agenda OpenHAN Overview Work Plan Discussion Next Steps

3. Promotes open standards-based HANs that are interoperable Provides the vendor community with a common set of principles and requirements around which to build products Ensures reliable and sustainable HAN platforms Supports various energy policies in a variety of states, provinces, and countries Empowers end users with the information they need to make decisions on their energy use by enabling the vision of a home energy ecosystem UtilityAMI 2008 HAN SRS

4. HAN SRS Ratification Vote Unanimous Mar 7, 2008 AEP SCE SDG&E PG&E Detroit Edison FPL BC Hydro Entergy Consumers Energy CenterPoint Energy Oncor EDF Endorsing Utilities: Duke Energy Reliant Energy

5. HAN Standards Overview

6. Dec 20076 HAN Guiding Principles Value Proposition Guiding Principles Use Cases Platform Independent Requirements Platform Requirements (Technology Specific) System Criteria

7. Dec 20077 HAN Guiding Principles Capabilities  Supports a secure two way communication with the meter  Supports load control integration  Provides direct access to usage data  Provides a growth platform for future products which leverage HAN and meter data  Supports three types of communications: public price signaling, consumer specific signaling and control signaling  Supports distributed generation and sub-metering Assumptions  Consumer owns the HAN*  Meter to HAN interface is based on open standards  Implementation is appropriate given the value and the cost  Technology obsolescence does not materially impact the overall value

8. Dec 20078 HAN Use Cases Value Proposition Guiding Principles Use Cases Platform Independent Requirements and Architecture Considerations Platform Requirements (Technology Specific) System Criteria

9. Dec 20079 Use Case Scope  Abstracted to highest level for rapid adoption (i.e., more details to follow) note: previous work has been more detailed  Concentrates on Utility to HAN interactions  Device ownership independent (e.g., registration is the same whether or not the utility supplies the device)  Interactions are based on Utility relevant activities only (Ignores other HAN activities within the premise – e.g., Home Automation)  Required device functionality will be specified in subsequent phases (i.e., platform independent requirements)

10. Dec 200710 Organization  System Management and Configuration  Depot Configuration  Installation and Provisioning  Utility Registration  Remote Diagnostics  Maintenance and Troubleshooting  Load Control and Energy Management  Voluntary  Mandatory  Opt-out  Energy Management System  Energy Storage and Distribution  User Information  HAN Metering

11. Dec 200711 Platform Independent Requirements Value Proposition Guiding Principles Use Cases Platform Independent Requirements and Architecture Considerations Platform Requirements (Technology Specific) System Criteria

12. Dec 200712 Requirements Overview  Requirements are platform independent  Requirement are to products applied via device mappings (Appendix)  Special class of requirements for an AMI gateway (See Mappings)  Two types of compliance  Technology/alliance – application and communication compliance (e.g., message structures)  Vendor/product – compliant with device mapping requirements

13. Work Plan Discussion No consensus yet on next steps Needs to be driven by industry need This is the only way to get the volunteers needed to do the work Stated need to update the SRS New use cases Lessons learned from SEP 2.0 and utility projects Conformance General discussion What do we need to support deployments – what are the hot buttons?

14. Use Cases Proposed in 2008 Installation - ZBHP Deregistration Reconstituting Security after failure/replacement Medical appliances inside the home Discovery for various utility program use PEV - ZBHP Fallback modes in degraded condition - ZBHP Failure mode cases missing in general Pre-pay - ZBHP Energy messages (pricing and usage) - ZBHP Duty cycle control Energy storage Multiple dwelling units and high rises (Toronto has some) Dynamic T&D integration

15. Use Case Development Prioritize, select, develop narrative

16. Questions? For any additional information, please do not hesitate to contact us Note: Full participation requires UCAIug membership – join at http://www.ucaiug.org/ UCAIug Board Members: Erich W. Gunther EnerNex Corporation erich@enernex.com Wayne R. Longcore Consumers Energy wrlongcore@cmsenergy.com