1. OpenADE November 17, 2011 PM2 David Mollerstuen, OpenADE TF Chair Steve Van Ausdall, OpenADE TF Vice-Chair

2. Roadmap November 2011 (Austin, TX) OpenADE – NAESB ESPI 1.0 ratified Oct. 17 OpenADE – Discussions around ITCA, ability to certify, test plan and profiles OpenADE - Focus on reducing barriers to adoption, facilitate early simple implementations (“Green Button”)

3. Roadmap March 2012 (Bay Area) OpenADE – Full ESPI test plan complete OpenADE – ITCA operational OpenADE – OpenADE 1.1 requirements complete / submit to NAESB (PEV sub-meter)

4. Roadmap June 2012 (Chicago) Ability to certify implementations November 2012 (Hawaii)

5. SSO ITCA Stakeholder Community Test LabImpl. OpenADE Requirements Marketing Develop Test Plan Follow ISO 17025 Verify products against Test Plan UCAIug Manage Certification Program Ensure ISO 65 compliance NAESB Develop Standard Specification (ESPI) Protect copyrights Develop product Engage Test House to perform test ESPI Certification Roles Certification Body Issue Certificate Follow ISO 65

6. Certification Actions Funding Opportunity guidance by mid-December – testing and certification services (James) Test Plan - Complete ESPI Green Button profile and test plan by mid-January (Steve & team) Certification Plan – resources, funding, budget, options, requirements, labs, CBs, schedule by mid- December (collaboration – address IPRM items)

7. Certification Actions Funding Opportunity guidance by mid- December – testing and certification services Test Plan - Complete ESPI Green Button profile and test plan by mid-January

8. Future Requirements Extensibility Compression PEV sub-metering Price / DRLC Text Message

9. Extensibility Current specification contains – Allows additions without schema change New use cases – Advertise capabilities (resources available) – Negotiate desired extensions – Allow for extensions to use schema If using EXI, allows minimal encoding for extensions

10. Compression (and Encoding) Current specification does not limit – Beyond media type “ application/atom+xml ” – HTTP defines compression mechanics Accept-Encoding, Content-Encoding New use cases – Specify recommended encoding / compression compress, gzip, deflate, EXI

11. PEV sub-metering Delivery from DMA to Utility via ESPI in scope. – Comms between sub-meter and DMA (Data Management Agent / Third Party) out of scope. Sub-meter to premises meter association – Is currently possible by allowing selection during authorization, or association afterward – However, OAuth may not always be an option

12. PEV sub-meter Use Case 1, Scenario 1

13. PEV sub-meter Use Case 1, Scenario 3

14. PEV sub-meter CPUC protocol by September 2012 Contact Glenn.Pincus@sce.com to get inviteGlenn.Pincus@sce.com

15. Price, DRLC Defined in IEC CIM, refined in SEP 2.0 Capabilities include the following – Communication of upcoming price intervals – Block thresholds, relative price levels (TOU) and actual commodity price – DRLC events specify cooling and heating offsets or set points, duty cycle and target reductions, etc.

16. Text Messages Defined in IEC CIM, refined in SEP 2.0 Supports simple text notices Could be enhanced to support other formats

17. Other Suggestions White paper on differences and similarities – OpenADR – OpenADE / ESPI / green button – OpenHAN / SEP 2.0 – ASHRAE 201