1 / 53

CIM for Enterprise Integration: Improving Integration Anarchy in the Smart Grid

Learn about the benefits of using the Common Information Model (CIM) for enterprise integration in the smart grid, including improved messaging, asset management, and support for AMI, DMS, OMS, GIS, and CIS. Avoid the chaos of integration anarchy.

tommiej
Download Presentation

CIM for Enterprise Integration: Improving Integration Anarchy in the Smart Grid

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CIM for Enterprise Integration for the CIM University, CIM Users Groupin San Francisco, CAOctober 11, 2010 For further information, contact: Greg Robinson (grobinson@xtensible.net), 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

  2. 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 CIM Users Group: CIM for Enterprise Integration

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

  4. Goal: Interface Standards Should Be Based on Common Semantics(e.g., CIM) to Avoid Adding to ‘Integration Anarchy’ GIS OMS CIS Integration Infrastructure AMR DMS WMS Data Integration Anarchy! Without Common Semantics, Point-to-Point Integration Will Continue at the Data Level • 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 CIM Users Group: CIM for Enterprise Integration

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

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

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

  8. 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 CIM Users Group: CIM for Enterprise Integration

  9. IEC 61968 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 61968-1] CIM Users Group: CIM for Enterprise Integration

  10. Message Header [source: IEC 61968-1] CIM Users Group: CIM for Enterprise Integration

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

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

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

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

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

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

  17. 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 CIM Users Group: CIM for Enterprise Integration

  18. Case Study: LIPA Asset Management and Organization (source: IEEE 2009) • 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 • 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 CIM Users Group: CIM for Enterprise Integration

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

  20. Some Foundational Relationships of the IEC CIM for Asset Management Document Information Containers Such As Asset Catalogues, Trouble Tickets, Work Orders, etc. Organisation Entities Performing One or More Roles Such As Customer, Supplier, Manufacturer, Service Provider, etc. Location A Street Address, Coordinates For a Geographic or Schematic reference system, etc. Erp Person A Person Performing Roles Such Dispatcher, Field Operator, etc. Power System Resource Electrical Network Role Used For Planning, Operations, 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 Asset Physical Plant Filling A Role Such As A Transformer, Pole, etc. CIM Users Group: CIM for Enterprise Integration

  21. IEC 61968-4: 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 61968-13 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. CIM Users Group: CIM for Enterprise Integration

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

  23. IEC 61968-4: 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 CIM Users Group: CIM for Enterprise Integration

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

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

  26. CIM Users Group: CIM for Enterprise Integration

  27. IEC 61968-4: 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 CIM Users Group: CIM for Enterprise Integration

  28. Maintenance & Inspection (MAI) Business Functions Performed Construction WMS (CON) • Maintain and Plan PM Programs • Manage Inspection and Maintenance “Triggers” • Link Inspection orders to follow-up repair orders • Gather “failure” data Design & Estimate (DGN) Scheduling & Dispatch (SCH) Field Recording (FRD) • Initiate and Plan work orders • Manage material, equipment, and permit requests • Manage and Track Work (Workflow) • Close Work and Support Performance Analysis • 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 61968-6 • Gather actual costs and support cost reconciliation • Monitor work progress • support financial closing with accounting systems IEC 61968-6: Maintenance & Construction(Note: CD in development – paper being presented at Grid InterOp) CIM Users Group: CIM for Enterprise Integration

  29. IEC 61968-6: 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.) CIM Users Group: CIM for Enterprise Integration

  30. IEC 61968-6: 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 CIM Users Group: CIM for Enterprise Integration

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

  32. IEC 61968-3: 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. CIM Users Group: CIM for Enterprise Integration

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

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

  35. IEC 61968-8: 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 CIM Users Group: CIM for Enterprise Integration

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

  37. A Customer Account Message Type for AMI (IEC 61968-9) CIM Users Group: CIM for Enterprise Integration

  38. IEC 61968-9ReferenceModel Refer to Margaret’s presentation

  39. 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 CIM Users Group: CIM for Enterprise Integration

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

  41. User groups are a good source of help http://www.ucaiug.org/ CIM Users Group: CIM for Enterprise Integration

  42. CIM Users Group: CIM for Enterprise Integration

  43. 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. CIM Users Group: CIM for Enterprise Integration

  44. 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 61968 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

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

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

  47. Case Study: AMI-Ent Service Identification CIM Users Group: CIM for Enterprise Integration

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

  49. Application View CIM Users Group: CIM for Enterprise Integration

  50. Technical View (Patterns) CIM Users Group: CIM for Enterprise Integration

More Related