Open SG and SG-Systems Overview for IEC TC57 Working Groups For further information, contact: Greg Robinson Convener of IEC TC57 WG14 Co-Chair of SG-Systems WG (of OpenSG of UCA Users Group) ZigBee & HomePlug SEA – Smart Energy Profile 2.0 Leadership Team

UCAIug Organization Chart

Benefits of OpenSG Participation in SG Standards Development Concentration of utilities engaged in active deployments [not pilots] of Smart Grid systems  Over 35 million US households  Over 14 million smart meters deployed by EOY 2010 and 27 million by 2012  39,000 miles of transmission lines, over 500,000 miles of distribution lines covering over 276,000 sq miles Energy industry operations expertise Active engagement in defining utility requirements for inclusion into national / international standards bodies Proven experience in requirements development and standards development facilitation  OpenHAN  formation [Mar 2007]  spec [SRS 1.04]  technical implementation [Smart Energy profile] in 12 months OpenSG is technology and SDO neutral

OpenSG Subcommittee Organization

Focus Of SG-Systems NIST Conceptual Model [Source: NIST Interim Roadmap]

Business Drivers Interoperability requires many standards in a profile stack Work with relevant SDOs per layer of profile stack (e.g., information standards, security standards, transport standards, media standards, etc.) to ensure complete solutions for in- scope interfaces. Need formal industry standards, but the SDO process is relatively slow & needs more user input Work collaboratively with SDOs to ensure common user requirements are appropriately 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. To ensure consistency of information across all domains, SG-Systems WG is assigned the task of defining requirements and proposing solutions to gaps in existing standards.

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

Key Collaboration Concept for the SG-Systems Working Group Standard building blocks are defined by CIMug and the affiliated IEC working groups along with other relevant industry groups e.g., 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 standard building blocks. Recommended extensions and changes to standard building blocks are provided back to appropriate standards bodies.

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 series of standards Utility’s Projects - Design & Implementations Utility’s Architecture Industry Best Practices Interoperability Testing Industry Best Practices Standards Conformance & Interoperability Testing Industry Standards

The scope of AMI-ENT is the systems and/or applications within and around the utility enterprise and the inter-systems related business functions and stops at the boundaries of applications and the edge of utility enterprise. The focus is on how these systems are to be integrated and composed to support AMI related business processes and functions. Edge applications are those applications that communicate with networks and devices in the field, as well as those that communicate with other businesses or enterprises (generally defined as third parties).

AMI-Ent Summary AMI-ENT DR Use cases v1.0 AMI-ENT SRS v1.0 AMI-ENT Services v1.0 CIM and IEC based Compatible with IEC Specification Complete and implementable integration services Prime example of how an OpenSG task force can leverage existing standards and accelerate its development and adoption. Approach being used by other SG-Systems tasks forces 13

OpenHAN - Home Area Network

OpenHAN Summary OpenHAN SRS 1.04 ratified March 2008 System Requirements Specification(SRS) used by ZigBee and HomePlug technology alliances as basis for SE 2.0 Market Requirements Document (MRD) OpenHAN to update SRS based on SE 2.0 MRD and market developments OpenHAN to review SE 2.0 artifacts as provided to facilitate NIST open review process: Technical Requirements Document Proposed CIM Extensions Proposed Service Definitions 15

OpenADE - Automated Data Exchange 16

OpenADE Summary Permits utilities to share, at the consumer’s request and under the consumer’s direction, a broad set of that consumer’s utility data with specific 3 rd Parties. Immediate Scope (i.e. OpenADE 1.0) includes usage data from utility back end Broader Vision (requirements due post-01/2010) includes pricing, network events, premises configuration, HAN-related data, etc. 17

OpenADR – Automated Demand Response 18

Framework For Integrated DR/DER The key subjects and findings of this document are: DR signals standardization must support all four market conditions, i.e. regions with or without either wholesale or retail open competition. It must also consider key differences that exist and will continue to exist in all four market types. Wholesale market DR and pricing signals have different characteristic than retail market DR and pricing signals, although commonality in format may be developed. Most customers (with a few exception of C&I customers) will not interact directly with wholesale market when it comes to DR and Pricing signals. Retail pricing models is complex due to the large variety of tariff rate structures that exist in both regulated and un-regulated markets. Attempts to standardize DR control and pricing signals must not hinder regulatory changes or market innovations when it comes to future tariff or pricing models. New business entities (Energy Service Providers, Curtailment Service Providers (DR Aggregators), Energy Information Service Providers) will play an increasing role in DR implementation. DER will play an increasingly important role in DR, yet tariff and/or pricing models that support DER’s role in DR are still in its infancy. Customer’s perspective and ability to react to DR control and pricing signals must be a key driver to the development of DR standards.

Closing Remarks In recent NIST discussions, there is general agreement that formal standards are needed. While IEC is viewed as necessary, it suffers from two major criticisms: The IEC process is too slow There is not enough user participation in IEC standards development IEC TC57 helped form the UCAIug. OpenSG is a user-driven organization that functions as part of the UCAIug OpenSG is able to work with the IEC to resolve these two criticisms: OpenSG ballots its work products and make them publically available as an “Industry Best Practice” Please note that these are NOT standards as OpenSG is not a standards development organization (SDO). OpenSG work products are intended to become a common best practice based on applicable industry standards. Extensions to standards that were needed to meet OpenSG’s business requirements will be provided to the appropriate SDO (e.g., IEC TC57 WG14). The OpenSG hopes that the SDOs will accept its recommended extensions (and the extension will become part of the next release of the standard(s) In the meantime, the user community has something to leverage that is far better than custom extensions performed differently at each individual utility.