1. OpenSG Closing Plenary Oct 22 nd, 2009

2. Agenda SG Conformity SG Communications SG Systems SG Security Feedback Next Meeting

3. SG Conformity Key accomplishments – Defined scope and charter with unanimous agreement – Established guiding principles – Agreed on formation and prioritization of 3 TFs: Edge Conformity (ADE/ADR/HAN) SG Security Conformity AMI ENT Conformity (Not currently prioritized) Next steps – kick off task forces and establish weekly calls and Next encounter data/time (tele./webinar/f2f) – To be announced via the general listserve

4. SG Communications Key accomplishments – OpenSG PAP #1 and #2 requirements Identified 21 top level SG applications and 15 potential actors for each Worked through 4 of the applications end to end and created over 100 high level functional requirements – Organization Scope/Charter discussion

5. SG Communications Next steps – OpenSG PAP #1 and #2 Complete walkthrough of top level actions Align requirements by actor interfaces Distill communications requirements Face to face at Grid-Interop in Denver (mid November) – Organization Task Groups per Knoxville session discussion Weekly conference calls Next encounter data/time (tele./webinar/f2f)

6. SG Communications Next encounter data/time (tele./webinar/f2f) – Plan for next week to continue PAP #1 and #2 requirements generation

7. SG Systems Key accomplishments – Updated SharePoint – Electronic Balloting Process – Task Forces (next slides) Next steps – (Next Slides)

9. SG-Systems Task Forces & Service Teams Planning Underway With NAESB Collaboration With SE 2.0 Collaboration With SE 2.0 & OASIS Planning Underway With NAESB Underway Collaboration With SE 2.0 & OASIS Collaboration With SE 2.0 & OASIS Collaboration With SE 2.0 Collaboration With SE 2.0

10. SG Systems – AMI-Enterprise Key accomplishments – Industry Best Practice Approved: Use Cases System Requirements Specification (SRS) Methodology Services Ready to submit to SDO (IEC TC57 WG14) Next steps Participate in IEC61968-9 interoperability testing Analyze and incorporate security requirements Update and ballot next release

11. Service Definition Team Key accomplishments – Approval of the Service Definition Artifacts Next steps – Build the roadmap Open a model for access/collaboration Baseline the artifacts Plan new work, e.g. OpenADE, sharing with WG14 Next encounter data/time (tele./webinar/f2f) – Service Definition con call: 10/28 2PM

12. SG Systems - OpenADE Key accomplishments – Agreement on 1.0 version of Use Case document Next steps – Work on SRS, service definitions – Reference / prototype implementations Next encounter data/time (tele./webinar/f2f) – Weekly meetings, every Thursday @noon Mtn.

13. SG-Systems - OpenHAN Leadership – Chair and co-chair – lead teleconferences Chair – Mary Zientara (Reliant) Co-chair – Steve Van Ausdall (Xtensible) Co-chair – Charles (Google) Co-chair – Charlie (GE) Define scope and charter Use cases – common team – Focused on format and capture but still need content and selection for our purposes in OpenHAN Business level requirements – in OpenHAN? Provide input to SEP 2.0 (and others as requested) Analysis – update SRS requirements table Conformance tasks Security tasks

14. Suggest DR Use Case Matrix SG-Systems - OpenADR

15. Use Case Development Accomplishments Use Case #Use case descriptionNote 4.2Notify DR EventSD and Interaction - Completed 4.2.1Advanced Notification for DRSD and Interaction - Completed 4.2.2Update a DR EventSD and Interaction - Completed 4.2.3Cancel a DR EventSD and Interaction - Completed 4.2.4DR Resource ConfirmationSD and Interaction - Completed 4.7Direct Load ControlSD and Interaction - Completed 4.7.1Monitor DR EventSD and Interaction - Completed

16. DR Use Case Discussion Topics 4.4 Broadcast “Pricing” (Retail) for DR Purpose – The term pricing will change to more generic Reference Architecture DR acknowledgement and confirmation Advanced Notification for DR Adding testing use case DR Resource Confirmation (DR Resource, Asset, PHEV) Direct Load Control – randomization, monitor protocol

17. Next steps and next encounter date/time Next steps – Refine use cases developed – Provide draft use cases to sub-group leader (Joe) by Friday, October 21 st – Refine combined retail and wholesale use cases in the next two weeks – Finalized use case and framework document by first week of November – Continue to work with NAESB, NIST and OASIS on SRS and Service Definition Next encounter date/time – Every Thursday joint conference call with NAESB (12-2:00 central time) – NAESB SGTF sub-group F2F meeting in New England

18. If you have comments and/or wish to join and contribute to the OpenADR Task Force effort, please contact Albert Chiu or Ed Koch at akc6@pge.com or ed@akuacom.comakc6@pge.com

19. Attendee Feedback Names, specific group and meeting Consistent dashboards across WGs for reporting More detailed agenda, better, earlier planning for F2F Realtime schedule time change mechanism at F2F Capture on phone attendance Real full- duplex polycomm type phones for conf calls New people better comms, glossary, terms, promote don’t be shy attitude. Online library ref Boot camps were a positive WGs need to tighten up scopes, ie. OpenHAN and Net, more groups means need for tighter coordination More formal joint sessions Web based agenda with links to open meeting etc.

20. Next Meeting Host is Florida Power & Light Juno Beach, FL January 18-21, 2010 – Boot camps on January 18 – Parallel sessions January 19-21

21. Hosting Opportunity April 2010 Meeting…somewhere warmer? – Looking at DC or Raleigh July 2010 Meeting…somewhere cooler? – Looking at San Francisco Area Send email to Chris Knudsen: cxkq@pge.com

22. Thank you! Safe return!