“SG-Systems” (Smart Grid – Operational Applications Integration) “Boot Camp” Overview

1. “SG-Systems”(Smart Grid – Operational Applications Integration)“Boot Camp” Overview Brent Hodges, Chair, SG-Systems Greg Robinson, Co-Chair, SG-Systems

2. Agenda • 3:00 Introductions and Brief Overview of SG-Systems (Greg) • 3:15 Use Case Process with TOGAF AMI-Ent example (Kay) • 3:30 System Requirements Overview with AMI-Ent example (Shawn) • 3:45 Service Definitions Process with AMI-Ent example (Jerry) • 4:00 OpenADE (Steve) • 4:15 OpenADR (Albert) • 4:30 OpenHAN (Erich) • 4:45 General discussion, questions & answers • 5:00 Adjourn

3. New EIM Task Force

4. NIST Conceptual Model [Source: NIST Interim Roadmap]

5. Business Drivers • Interoperability requires many standards in a profile stack • The SDO process is relatively slow & needs more user input • Work collaboratively with SDOs to ensure common user requirements are addressed • Facilitate standards development by proposing potential solutions for addressing gaps in existing standards. • The SDO ultimately determines when and how its standards are updated based on input. • For Information Standards, resolve (don’t add to) semantic chaos • Avoid having the same information defined with different names, varying definitions, etc. • Ensure same information standards can be used across different communication profiles • While mapping to other standards will be unavoidable, strive to use, correct and extend one information model standard: • The IEC TC57 Common Information Model (CIM) is the default information model for this purpose. • There is substantial information overlap among AMI, ADE, HAN and ADR • While requirements and services vary significantly, they can be built using the same information model.

6. The CIM is the Basis for a Common Systems Language for Utilities The same dictionary is used for multiple forms of human communication: Letters Phone calls Conversations Emails Etc. In similar manner, the same CIM is used for multiple forms of computer communication: XML RDF OWL DDL Etc. One Dictionary Supports Many Forms of Communication 7 Proprietary and Confidential

7. SG-Systems WG: The SG-Systems Working Group defines requirements, policies, and services, based on utility industry standards such as the Common Information Model (CIM), required for information exchange from and to utility enterprise back office systems and between these back office systems and data acquisition and control servers (e.g., MDMS, AMI Head Ends, SCADA, etc.). Task forces are established on an as needed basis to accomplish these goals for specific functional areas. In addition to work performed by their ‘vertical team,’ Task Force Chairs act as matrix managers to ensure their functional requirements are met through the ‘horizontal teams’ supporting them. ‘Horizontal Teams’ are ongoing, providing consistent artifacts for each increment of functionality that is requested of them by the functional (vertical) teams. SG-Systems WG Scope

8. NIST EPRI, MultiSpeak SG-Systems WG Process Overview HomePlug & ZigBee SE 2.0 IEC TC57 WG14, OASIS, IEEE Other SDOs Use Cases From SCE and others Task Forces Business-Oriented, Common Format Use Cases Based on SRS Reference Model System Requirements (SRS) Team Use Case Team SG-Security WG Service Definitions Team • Integration Requirements • Patterns • Sequence Diagram • Services • WSDL • Recommendations to IEC TC57 WG14: • Proposed CIM Extensions • Message Schemas Updates • Requirements Updates • Recommendations to other SDOs SG-Conformity Working Group

9. Key Collaboration Concept for the SG-Systems Working Group Standard building blocks are defined by IEC, other Standards Development Organizations, and industry groups: e.g., OAISIS, Open Applications Group (OAG), MultiSpeak, OGC Requirements (use cases) are gathered from helpful sources Utilities Industry initiatives The SG-Systems WG articulates Industry Best Practices(see next slide) that satisfy requirements through the use of industry standard building blocks. Ideas for recommended extensions and changes to standard building blocks are provided back to appropriate standards bodies. SG-Systems WG February 2010

10. Utility’s Projects - Design & Implementations --------------- Utility’s Architecture ----------------------- Industry Best Practices Interoperability Testing --------------------------------- Industry Best Practices ------------------------------------------ Standards Conformance & Interoperability Testing ----------------------------------------------------- Industry Standards Our Focus: Finding/Developing Best Practices & Making Them into Vetted “Industry Best Practices” • Local Utility Projects • Consortiums & User Groups like OpenSG (business requirements) & CIMug (optimization & implementation support) • Standards Development Organizations (SDOs) like IEC TC57 Working Group 14 for the IEC 61968 series of standards SG-Systems WG

11. Defining EIM (Gartner) Enterprise Information Management (EIM) is: • An organizational commitment to structure, secure and improve the accuracy and integrity of information assets, • to solve semantic inconsistencies across all boundaries, • and support the technical, operational and business objectives within the organization's enterprise architecture strategy. • A commitment to EIM is recognition that information in the enterprise is as important as process (application development) and infrastructure (technology) • Task Force “kick-off” during SG-Systems Meeting at 3:30 on Tuesday