1. Open Smart Grid (OpenSG) Technical Committee Plenary October 20, 2009

2. 2 Agenda Agenda this week SG Growth and Governance Discussion Review of PAP 3,4,9,10 Workshop Questions/ Open Discussion

3. Tuesday, Oct 20 Tuesday October 20 Greenbriar/Elkmont866.215.1934, pin 8279 8:30-10 AMOpenSGOpening Plenary Break Greenbriar/Elkmont866.215.1934, pin 8279 10:30AM-12 PMSG Systems: Use Case, SRS, & Service Defintions Status Work Session Cherokee866.246.9203, pin 6022 10:30AM-12 PMSG CommunicationsWork Session Lunch Greenbriar/Elkmont866.215.1934, pin 8279 1 PM-3 PMSG Systems: Use Case, SRS, & Service Defintions Planning Joint Work Session Cherokee866.246.9203, pin 6022 1 PM-3 PMOpenHANWork Session Sequoyah866.255.6835, pin 6290 1 PM-3 PMSG CommunicationsWork Session Break Greenbriar/Elkmont866.215.1934, pin 8279 3:30-5:30 PMSG Systems: OpenADE, OpenADR, & AMI-ENT status Work Session Cherokee866.246.9203, pin 6022 3:30-5:30 PMOpenHANWork Session Sequoyah866.255.6835, pin 6290 3:30-5:30 PMSG CommunicationsWork Session

4. Wednesday, Oct 21 October 21 Greenbriar866.215.1934, pin 8279 8:30 AM-9:30 AMSG-Systems: AMI-ENT, OpenADE, OpenADR, & OpenHAN planning Joint Work Session Sequoyah866.246.9203, pin 6022 8:30 AM-12 PMAMI-NETWork Session Greenbriar866.215.1934, pin 8279 9:30 AM-12 PMAMI-ENTWork Session Elkmont877.255.6835, pin 6290 9:30 AM-12 PMOpenADEWork Session Cherokee877.869.4197, pin 5851545 9:30 AM-12 PMOpenADRWork Session Lunch Greenbriar866.215.1934, pin 8279 1 PM-2 PMOpenADE, SG SecurityJoint Work Session Elkmont877.255.6835, pin 6290 1 PM-5:30 PMOpenADRWork Session Greenbriar866.215.1934, pin 8279 2 PM-4:30 PMSG SecurityWork Session Sequoyah866.246.9203, pin 6022 2 PM-5:30 PMOpenADEWork Session Greenbriar866.215.1934, pin 8279 4:30 PM-5:30PMAMI-NET, SG SecurityJoint Work Session

5. Thursday, Oct 22 Thursday October 22 Greenbriar/Elkmont866.215.1934, pin 8279 8:30 AM-12 PMSG SecurityWork Session Leconte877.255.6835, pin 6290 8:30 AM-12 PMCertification Group 1Work Session Laurel866.246.9203, pin 6022 8:30 AM-12 PMCertification Group 2Work Session Lunch Greenbriar/Elkmont866.215.1934, pin 8279 1 PM-3 PMOpenSGClosing Plenary – Report Outs

6. UCA International Users Group  Influence, select, and/or endorse open and public standards appropriate to the utility market based upon the needs of the membership.  Specify, develop and/or accredit product/system- testing programs that facilitate the field interoperability of products and systems based upon these standards.  Implement educational and promotional activities that increase awareness and deployment of these standards in the utility industry. The mission of the UCA International Users Group is to enable utility integration through the deployment of open standards by providing a forum in which the various stakeholders in the utility industry can work cooperatively together as members of a common organization to: UCAIugCorporate Sponsors

7. UCAIug Membership Stats Corporate accounts are now at 144 Anticipate 150 by year end SharePoint accounts are now at 2,836 Continuing to grow at 4-5/day About half of the accounts are members 1/4 of accounts are utilities Accounts are from 80+ countries Members from 45 countries

8. UCAIug Corporate Supporters

9. UCAIug 2009 User Accounts By Region UCAIug Members Linear Trend Line

10. UCAIug Membership Composition

11. OpenSG Governance Policies and Procedures are ready to release pending Board approval Expected this week Defines voting and membership process Organizational Management: Feedback on registration fees Size of meetings drives this In discussions with Global Inventures to provide greater operational support Allows the members to focus on the work Provides: Meeting organization and logistics Web Page Support WG schedules, document support,

12. NIST PAP 3, 4, 9, 10 Workshop Update 2 day workshop in Washington Sept 28-29 to harmonize work high level results: Common requirements process to bind all technical work to be done within NAESB CIM agreed upon as the root for schematic model Harmonize all inputs into common sets of requirements and a common solution Agree to create a structure to facilitate ease of participation in various groups

13. OpenSG Major Work Areas ASAP-SG NIST PAP 1,2 NIST PAP 3,4,9,10 NIST Phase 3 Coordination

14. Sept 29, 2009Smart Grid Priority Action Plans14 Today’s Agenda (from 9/28) Agenda8:00 AM – 8:10 AM Welcome8:10 AM – 8:40 AM SG Interoperability, PAP Goals8:40 AM – 9:00 AM SG Technology Overview9:00 AM – 10:00 AM Break10:00 AM - 10:30 AM SG Regulatory Background10:30 AM - 11:00 AM Standard Demand Response Signals (PAP 9)11:00 AM - 12:00 PM Lunch12:00 PM - 1:00 PM PAP 9 – Continued1:00 PM - 2:00 PM Common Scheduling (PAP 4)2:00 PM - 3:00 PM Break3:00 PM - 3:30 PM PAP 4 – Continued3:30 PM - 4:30 PM Wrap Up4:30 PM - 5:00 PM

15. Smart Grid Priority Action Plans15 Today’s Agenda (from 9/29) Day 1 Summary8:00 AM – 9:00 AM Common Scheduling – PAP 49:00 AM – 11:00 AM Lunch11:00 PM – 12:00 PM Common Pricing – PAP 312:00 PM – 2:00 PM Break 2:00 PM – 2:30 PM Common Energy Information – PAP 10 2:30 PM – 4:30 PM Wrap Up4:30 PM – 5:00 PM Sept 30, 2009

16. Smart Grid Priority Action Plans16 Development Tracks Silo Utility-led: developing requirements OASIS: schema, web services NAESB Hybrid – We’ll do this one Utility-led: developing requirements OASIS: schema, web services NAESB/UCAIug requirements funnel will bind schema: use cases, requirements, schema Sept 30, 2009

17. PAP 9 Responsibility Breakdown Sept 30, 2009Smart Grid Priority Action Plans17

18. Requirements Capture Process Sept 30, 2009

19. Smart Grid Priority Action Plans19 Consensus IEC 61968 CIM alignment Reuse where appropriate from published DR components with IEC 61968 CIM family for PAP9 work If someone is developing extensions, submit them to IEC (TC57) for approval (loopback) Incorporate where appropriate from OpenADR-OASIS Common semantic model for inter-domain interfaces Scope boundaries fuzzy (need to solve) How deep do the definitions (semantics vs. syntax) go? (need to solve) Utility commitment to IEC 61968 CIM family becomes a boundary requirement Tactical: Need a mechanism for a joint TF to allow parties from each organization to participate in effort and share work products Sept 30, 2009

20. Questions/ Discussion