CIM for Enterprise Integration for the CIM University, CIM Users Group in San Francisco, CA October 11, 2010 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 NIST SGIP – Smart Grid Architecture Committee Member

Slide 2 CIM Users Group: CIM for Enterprise Integration Agenda CIM for enterprise integration (IEC 61968) –Overall Scope, Approach –Messaging –Highlights for Using CIM AMI, DMS, OMS, GIS, CIS Asset management, work management –Supporting the smart grid

Slide 3 CIM Users Group: CIM for Enterprise Integration This is Not a Good Practice For Wires Integration; It’s Not Good For Data Integration Either! Wires Integration Anarchy!

Slide 4 CIM Users Group: CIM for Enterprise Integration Goal: Interface Standards Should Be Based on Common Semantics (e.g., CIM) to Avoid Adding to ‘Integration Anarchy’ Integration anarchy is a chaos of: (1) duplicated logic, (2) duplicated data, (3) duplicated effort, (4) newly acquired integration difficulties, (5) lack of ability to easily create new application functionality from services, and (6) lack of ability to support business processes with applications Integration anarchy will result in higher costs and an inflexible, brittle Smart Grid System of Systems Integration Infrastructure OMS CIS GIS AMR DMS WMS Without Common Semantics, Point-to-Point Integration Will Continue at the Data Level Data Integration Anarchy!

Slide 5 CIM Users Group: CIM for Enterprise Integration The IEC Interface Reference Model (IRM) Provides The Framework For Identifying Information Exchange Requirements Among Utility Business Functions IEC Sequence Diagrams are organized by the IRM Application Integration Infrastructure Network Operations (NO) – IEC Network Operations Monitoring (NMON) Network Control (CTL) Fault Management (FLT) Operational Feedback Analysis (OFA) Operation Statistics & Reporting (OST) Network Calculations - Real Time (CLC) Records & Asset Management (AM) – IEC Substation & Network Inventory (EINV) Geographical Inventory (GINV) Asset Investment Planning (AIP) Operational Planning & Optimization (OP) – IEC Network Operation Simulation (SIM) Switch Action Scheduling (SSC) Power Import Sched. & Optimization (IMP) Maintenance and Construction (MC) – IEC Maintenance & Inspection (MAI) Construction WMS (CON) Design & Estimate (DGN) Scheduling & Dispatch (SCH) Field Recording (FRD) Network Extension Planning (NE) – IEC Network Calculations (NCLC) Project Definition (PRJ) Construction Supervision (CSP) Compliance Management (CMPL) CustomerSupport (CS) – IEC Customer Service (CSRV) Trouble Call Management (TCM) Meter Reading & Control (MR) – IEC Meter Reading (RMR) External to DMS External to DMS(EXT) Energy Trading (ET) (ET) Retail(RET) Sales(SAL) Customer Account Management (ACT) Financial(FIN) Business Planning & Reporting (BPR) Dispatcher Training (TRN) General inventory management (GIM) Load Control (LDC) Meter Maintenance (MM) Meter Data (MD) Stakeholder Planning & Management (SPM) Supply Chain & Logistics (SC) Premises(PRM) Human Resources (HR) Point Of Sale (POS) Meter Operations (MOP) Advanced Metering Infrastructure (AMI) Meter Data Management IMDM) Metering System (MS) Demand Response (DR)

Slide 6 CIM Users Group: CIM for Enterprise Integration Key Concept: Incremental Integration - in Step With Business Needs Semantically Consistent ESB OMS CIS GIS AMR DMS WMS TT OR IEC IRM Interface CIS OMS DMS TT OR Trouble Ticket Outage Record Information Flow Design

Slide 7 CIM Users Group: CIM for Enterprise Integration Key Concept: Replace Large Monolithic Applications ‘a Chunk at a Time’ WMS Maintenance & Inspection Construction Work Scheduling Design Field Recording Other Apps CIM Message Types

Slide 8 CIM Users Group: CIM for Enterprise Integration Agenda CIM for enterprise integration (IEC 61968) –Overall Scope, Approach –Messaging –Highlights for Using CIM AMI, DMS, OMS, GIS, CIS Asset management, work management –Supporting the smart grid

Slide 9 CIM Users Group: CIM for Enterprise Integration IEC Basic Message Structure A verb to identify the type of action being taken A noun, to identify the type of the payload The payload, which contains the data relevant to the information exchange as defined using a profile [source: IEC ]

Slide 10 CIM Users Group: CIM for Enterprise Integration FieldDescription VerbThis enumerated list of verbs can be used to form message types in compliance with the IEC standard NounThe Noun identifies the main subject of the message type, typically a real world object defined as a profile using the CIM. RevisionRevision level of the message type. ContextIntended context for information usage such as production, testing and etc. TimestampApplication level relevant time and date for when this instance of the message type was produced. This is not intended to be used by middleware for message management. SourceSource person or system that publishes the message AsyncReplyFlagIndicates whether or not reply should be asynchronous ReplyAddressAddress to be used for asynchronous replies AckRequiredIndicates whether or not an acknowledgement is required UserUser information of the sender MessageIDUnique message ID to be used for tracking messages CorrelationIDID to be used by applications for correlating replies CommentOptional comment PropertyMessage properties can be used to identify information needed for extended routing and filtering capabilities. Message Header [source: IEC ]

Slide 11 CIM Users Group: CIM for Enterprise Integration Message Types Are Created By Combining IEC Verbs With Information Exchange Topics, Referred To As Nouns [source: IEC ]

Slide 12 CIM Users Group: CIM for Enterprise Integration (IEC Verbs - continued ) [source: IEC ]

Slide 13 CIM Users Group: CIM for Enterprise Integration Example of a “message type” payload [source: IEC ]

Slide 14 CIM Users Group: CIM for Enterprise Integration Example of how message elements are derived from the CIM [source: IEC ]

Slide 15 CIM Users Group: CIM for Enterprise Integration Navigating associations in CIM (UML notation)

Slide 16 CIM Users Group: CIM for Enterprise Integration Navigating associations in message type schemas

Slide 17 CIM Users Group: CIM for Enterprise Integration Agenda CIM for enterprise integration (IEC 61968) –Overall Scope, Approach –Messaging –Highlights for Using CIM AMI, DMS, OMS, GIS, CIS Asset management, work management –Supporting the smart grid

Slide 18 CIM Users Group: CIM for Enterprise Integration Service Provider Responsibilities: Construction & maintenance project management Materials sourcing & inventory management System engineering & design Bargaining unit negotiations Workforce scheduling & deployment Work practice design & development Asset data input and collection Workforce training Marketing & sales of services Competitor analysis Asset Owner Responsibilities: Asset valuation Investment analysis & strategy Contract negotiation/structuring Regulatory oversight Market & economic analysis Portfolio management Capital allocation Asset financial & operating performance analysis Asset planning Asset acquisition & monetization Asset Manager Asset Optimization Asset yield contribution understanding Financial structuring Business development Asset specifications & standards Full lifecycle asset management Asset data management Workload management Asset financial and operating performance analysis Asset strategy & plan development Asset full lifecycle financial & operational data analysis Regulatory strategy & negotiation Contract management Risk management Asset data requirements definition Asset opportunity development & analysis Industry Best Practices Case Study: LIPA Asset Management and Organization (source: IEEE 2009)

Slide 19 CIM Users Group: CIM for Enterprise Integration Case Study: LIPA Asset Management Concept (source: IEEE 2009)

Slide 20 CIM Users Group: CIM for Enterprise Integration Some Foundational Relationships of the IEC CIM for Asset Management Power System Resource Electrical Network Role Used For Planning, Operations, etc. Asset Physical Plant Filling A Role Such As A Transformer, Pole, etc. Location A Street Address, Coordinates For a Geographic or Schematic reference system, etc. Organisation Entities Performing One or More Roles Such As Customer, Supplier, Manufacturer, Service Provider, etc. Erp Person A Person Performing Roles Such Dispatcher, Field Operator, etc. Document Information Containers Such As Asset Catalogues, Trouble Tickets, Work Orders, etc. Activity Record Used to Record Each State change of CIM objects Type Asset Compatible Unit For Design & Procurement Asset Model Particular Model and Version of a Vendor's Product

Slide 21 CIM Users Group: CIM for Enterprise Integration IEC : Records and Asset Management (Note: Maintenance Update in Process) Network Data Set –Contains data for any part of a distribution network: Typically selected for operational or extension planning studies Used in numerous implementations for GIS to DMS integration Can be part of a feeder, a single feeder or more than one feeder Can be either the ‘As built’ network or a proposed network selected for analysis It is a superset of IEC CDPSM (i.e., Distribution’s CPSM) –Contains references to other static data such as: Elements of a TypeAssetCatalogue Elements of a AssetCatalogue Assets performing the roles of the associated types of PowerSystemResources Other “leaf node” elements such as Organisations, Locations, and Measurements Change Set –Contains updates required in a transaction for an existing NetworkDataSet –Each step in the ChangeSet is described through a separate ChangeItem. A change item identifies the change type (add, delete, modify) Sequence number for a particular change within a set of changes of a ChangeSet. –Only the identifiers of the relevant NetworkDataSet messages are to be included in a ChageSet message. The actual contents are provided in accompanying NetworkDataSets messages.

Slide 22 CIM Users Group: CIM for Enterprise Integration From the logical view to the physical asset view of the same object.

Slide 23 CIM Users Group: CIM for Enterprise Integration IEC : Records and Asset Management (Note: Maintenance Update in Process) Presentation: –Can contain location information for most any element represented in the CIM, particularly elements of the distribution network. –Provides location information of individual assets or power system resources –Provides a set of location information as a companion to the NetworkDataSet. Asset List: –Can contain various amounts of data for any set of utility assets –Contains references to static reference data such as: Elements of an AssetCatalogue Elements of a TypeAssetCatlogue PowerSystemResources that specify the role in which the Asset is being used –If it has been installed rather than sitting in inventory Other “leaf node” elements such as Organisations, Locations, and Measurements

Slide 24 CIM Users Group: CIM for Enterprise Integration Case Study: Asset Management System Used to Initialize System Control Center System (source: DistribuTECH2002) System Control Center Asset Management Adapter Integration Bus Asset data sent in XML Transformation into CIM Objects Publish AMS data in CIM format Subscribe to Asset data [presented at DistribuTECH 2001]

Slide 25 CIM Users Group: CIM for Enterprise Integration Case Study: Operations Model Capabilities (source: DistribuTECH2002) AMS DMS

Slide 26 CIM Users Group: CIM for Enterprise Integration

Slide 27 CIM Users Group: CIM for Enterprise Integration IEC : Records and Asset Management (Note: Maintenance Update in Process) Asset Catalogue: –A collection of information regarding available types of products and materials that are used to build or install an Asset(s), to maintain an Asset(s) or to operate an Asset(s). –Each catagoue item is for a specific product available from a specific supplier. –Contains references to static reference data such as: Elements of a TypeAssetCatalogue Specifications Other “leaf node” elements such as Organisations Type Asset Catalogue –Contains data for a set of utility asset types –It is a collection of information regarding generic types of assets that may be used for design purposes, analysis, and so on –A TypeAsset is not associated with a particular manufacturer –Contains references to other Documents containing static reference data such as: Elements of an AssetCatalogue Other “leaf node” elements such as Organisation

Slide 28 CIM Users Group: CIM for Enterprise Integration IEC : Maintenance & Construction (Note: CD in development – paper being presented at Grid InterOp) Business Functions Performed Maintain and Plan PM Programs Manage Inspection and Maintenance “Triggers” Link Inspection orders to follow-up repair orders Gather “failure” data Initiate and Plan work orders Manage material, equipment, and permit requests Manage and Track Work (Workflow) Close Work and Support Performance Analysis Gather actual costs and support cost reconciliation Monitor work progress support financial closing with accounting systems Work Design and Cost Estimation Compatible Unit based Graphical design Generate Bill of Materials Assign crew based on work type and skills Determine Schedule Date Perform constraint-based “auto-scheduling” Maintenance and Construction (MC) – IEC Maintenance & Inspection (MAI) Construction WMS (CON) Design & Estimate (DGN) Scheduling & Dispatch (SCH) Field Recording (FRD)

Slide 29 CIM Users Group: CIM for Enterprise Integration IEC : Maintenance & Construction Work is created any time a person is required to perform an activity related to company assets. Examples of work include –Construction work (e.g. service installations, line extensions, and system betterment projects) –Service work (e.g meter replacements, Turn-on, Turn- off, etc.) –Maintenance work (e.g. routine oil changes, painting, etc.) –Inspection work (e.g. pole inspections, vault inspections, Substation inspections) –Trouble work (e.g. Power outage, voltage quality problem, etc.)

Slide 30 CIM Users Group: CIM for Enterprise Integration IEC : Construction & Maintenance Current Message Types: –Compatible Units –Construction Work –Crew –Design –Inspect & Test –Labor –One Call Request –Procedure –Service Work –Trouble Work –Work Cost Detail –Work Scheduling –Work Status –Work Task

Slide 31 CIM Users Group: CIM for Enterprise Integration Generic “TypeAssets” are used for Design

Slide 32 CIM Users Group: CIM for Enterprise Integration IEC : Network Operations (Note: Maintenance Update in Process) Current Message Types: –Measurement list; –Operational restrictions; –Outage records; –Safety documents; –Switching schedules. Regarding “Note”, currently being updated through a use case-driven and incremental maintenance cycle, with first iteration being in support of outage management.

Slide 33 CIM Users Group: CIM for Enterprise Integration An Example: Safety Document Classes

Slide 34 CIM Users Group: CIM for Enterprise Integration Safety Document Message Type

Slide 35 CIM Users Group: CIM for Enterprise Integration IEC : Customer Support (Note: Update to second CD in Process) Current Message Types: –Trouble Ticket –Failure Event –Planned Outage Notification –Call Back –Compliance Event –Outage History –Service Extension Request –ServiceRequest –CustomerServiceAgreement –Customer Billing –Construction Billing

Slide 36 CIM Users Group: CIM for Enterprise Integration Aspects of Customer Accounts

Slide 37 CIM Users Group: CIM for Enterprise Integration A Customer Account Message Type for AMI (IEC )

IEC Reference Model Refer to Margaret’s presentation

Slide 39 CIM Users Group: CIM for Enterprise Integration Agenda CIM for enterprise integration (IEC 61968) –Overall Scope, Approach –Messaging –Highlights for Using CIM AMI, DMS, OMS, GIS, CIS Asset management, work management –Supporting the smart grid

Slide 40 CIM Users Group: CIM for Enterprise Integration NIST Conceptual Model [Source: NIST Interim Roadmap]

Slide 41 CIM Users Group: CIM for Enterprise Integration [Source: NIST Interim Roadmap] Note: “Operations” is based on the IEC IRM

Slide 42 CIM Users Group: CIM for Enterprise Integration User groups are a good source of help

Slide 43 CIM Users Group: CIM for Enterprise Integration

Slide 44 CIM Users Group: CIM for Enterprise Integration Key Collaboration Concept for the SG-Systems Working Group Standard building blocks are defined by standards development organizations (SDOs) 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.

OpenSG 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, NAESB, IEEE, et al. Utility’s Projects - Design & Implementations Utility’s Architecture Industry Best Practices Interoperability Testing Industry Best Practices Standards Conformance & Interoperability Testing Industry Standards

Slide 46 CIM Users Group: CIM for Enterprise Integration 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). (of UCAIug/OpenSG/SG-Systems WG)

Slide 47 CIM Users Group: CIM for Enterprise Integration Case Study: Consumers Energy and AMI-Ent TF

Slide 48 CIM Users Group: CIM for Enterprise Integration Case Study: AMI-Ent Service Identification

Slide 49 CIM Users Group: CIM for Enterprise Integration Case Study: AMI-Ent Inventory of CIM-Based Services Supporting Use Cases for AMI-Enterprise

Slide 50 CIM Users Group: CIM for Enterprise Integration Application View

Slide 51 CIM Users Group: CIM for Enterprise Integration Technical View (Patterns)

Slide 52 CIM Users Group: CIM for Enterprise Integration Common Concerns About The CIM for Integration –Concern 1: the CIM is too large For the common systems language, the CIM can be thought of as the unabridged dictionary. It is important to note that projects only use the portion of the dictionary relevant to their implementation But as the dictionary is is much richer, there will be consistency and congruity for other areas that the implementation must interface with. –Concern 2: the CIM inhibits innovation Because people don’t have to waste time re-inventing things that have been well vetted in the community, they can leverage the existing dictionary while focusing more energy on their innovative concept. Not only is this more efficient for the innovator, but it is also much more efficient for the people the innovators wants to share his ideas with. The community is already educated on how to use the well vetted language. –Concern 3: the CIM is too slow This is like saying the English language is slow; it is based on the speakers command of the language and the choice of media used. When a person communicates with someone, they must: 1.Articulate the information for the receiver to comprehend it 2.As a person may then provide this information through the US Postal Service, through , through phone calls, etc., the system may provide this information over many types of middleware (messaging, file transfers, data base, etc.) [source: IEEE T&D Optimization Panel 2010]

Slide 53 CIM Users Group: CIM for Enterprise Integration Common Concerns About The CIM for Integration (continued) –Concern 4: The CIM is too abstract This quality enables the CIM to continue to be relevant and valid even as technology continuously changes. The ability to properly convey unambiguous information primarily boils down to one’s skills in applying the common systems language. –Concern 5: The CIM is not a best practice data model For any individual purpose, one can always invent a model that is superior to any other existing model. The CIM has not been developed for only one functional area, but rather by a wide range of domain experts for integrating disparate applications. So for inter-application integration purposes, a superior model does not exist and would be difficult to achieve. –Concern 6: The CIM is too hard to implement Specialized models are often biased for a particular implementation and used with the a specific implementation technology. If the implementation never had to interface with other systems, this would be easier. As the CIM is an information model that is technology neutral, using the CIM does require following a process that restricts the general information model for particular contexts and then generates the appropriate design artifacts. The CIM Community has been doing this for some time and many tools are available for automating the process. [source: IEEE T&D Optimization Panel 2010]

Slide 54 CIM Users Group: CIM for Enterprise Integration Thank you for your time! Good news: The CIM is being used extensively – so learning about it is time well spent. Bad news: The CIM continues to need a lot of work and therefore users must be prepared for revision management Fun news: The CIM is a key NIST standard – so we have many exciting adventures (HAN, DER, PEV, ADE, DR, etc.) to look forward too!