CIM for Enterprise Integration for the CIM University, CIM Users Group in Charlotte, NC November 10, 2009 For further information, contact: Greg Robinson.

CIM for Enterprise Integration for the CIM University, CIM Users Group in Charlotte, NC November 10, 2009 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

CIM Users Group: CIM for Enterprise Integration
Agenda CIM for enterprise integration (IEC 61968) Overall Scope, Approach Model Evolution 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

Key Premise: The Common Language Should Provide Relevant Information To A User Regardless of Source Materials Management Concerns Construction Concerns Engineering Concerns Operations Concerns Protection Concerns Maintenance Concerns 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! 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’ OMS GIS CIS Integration Infrastructure DMS AMR 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

The IEC Interface Reference Model (IRM) Provides The Framework For Identifying Information Exchange Requirements Among Utility Business Functions All IEC Activity Diagrams and Sequence Diagrams are organized by the IRM CIM Users Group: CIM for Enterprise Integration

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

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

IEC 61968-11: CIM Extension for Distribution
Transitioning from Rational Rose To Enterprise Architect (Depending the state of a Package, some diagrams in this presentation are in Rose and others are in EA) CIM Users Group: CIM for Enterprise Integration

Priorities: WG14 Roadmap priorities by NC
CAN CH DE FR UK US ZA NC Positions Average Priority comment 3 6 3.0 Metering DCIM 2 7 2.9 Operations (DMS/OMS) Asset & record mgmt. 2.8 Reference architecture CDPSM Security 1 5 2.4 2.2 Naming/Design rules 2.1 Work mgmt. 2.0 n/a 1.8 MultiSpeak Glossary Operations Planning Extensions Planning DER 1.7 Integration profile PHEV/PEV 1.6 Customers (mgmt, billing) HAN 1.4 current pending postponed non-modelling [source: Tanja Kostic] CIM Users Group: CIM for Enterprise Integration

Priorities: Current modelling priorities
Driven by interoperability (IOP) tests 2009: Metering (Part 9) + balanced and unbalanced CDPSM (Part 13 Ed.2) 2010: NetworkDataSet (Part 4 Ed.2) for CDPSM needs (GIS-DMS/OMS exchange) Those common classes that support the above Overall CIM modelling principles, naming rules, network model for T&D, coordination with CMM Part 4 maintenance cycle Part 3 maintenance cycle (some useful for Part 5) Metering-related packages (Part 9 Ed. 2) (continuous: clean-up for consistency/correctness, simplification, diagrams, documentation) [source: Tanja Kostic] CIM Users Group: CIM for Enterprise Integration

CIM model and Part 11 evolution: Normative vs. informative
Introduced in January 2009 WG14 package split to normative and informative (unstable, work-in-progress) WG13 also started applying this approach to their obsolete packages  Condition for “normativity” Be used in messages of Part 9 Ed.1 and Part 13 Ed.2 Be used in messages of Ed.2 of Parts 4, 3, 5 (priority by the WG14 roadmap) WG14 uses Informative package as a sandbox, with expiration date for elements Move (potentially refactored) classes to normative packages – these are maintained by WG14 After expiry date, delete informative classes/relationships from the model WG14 SharePoint has the archive of all model releases where deleted elements can be found CIM users can take over and evolve deleted elements and potentially submit through standard CIM issues form the request for inclusion into standard CIM – modelling team decides whether the extension is considered as globally useful and thus provided as standard CIM (and not custom for a product/project/customer/vendor) [source: Tanja Kostic] CIM Users Group: CIM for Enterprise Integration

CIM model and Part 11 evolution Model releases and IOPs
WG14 follows the same timing as WG13 IOPs take place in Q4 of a year WG13 does not have IOP this year, but in April 2010, for CIM14 Given model version (used for IOPs) is frozen 2-3 months before IOPs Base CIM end July (14v12), DCIM mid September (10v27) Modelling team evolves new versions of the model with changes in informative parts only Issues identified in IOPs are addressed and resolutions included in official DCIM release (Q1 of next year) used for Part 11 FDIS WG13 has the same approach for IEC After January meeting, we branch the model Version 14vXX-10vYY (developed during 2009) is for Part 11/301 FDIS IEC61968 package is merged by CMM into the combined 15vYY Copy of it is saved as 15vYY-11v01 and evolved for IOPs in 2010 [source: Tanja Kostic] CIM Users Group: CIM for Enterprise Integration

Schedule until 2010-Q2 Models for 2009 IOPs: CPSM IOP based on CIM14 (14v12) frozen end July 2009 Metering and CDPSM IOPs based on DCIM10 (10v27) frozen mid September 2009 no changes that would impact Part 9 FDIS messages Model usable for all IOPs 2009 Part 11 CDV comments: Arrived end August 2009 We’ll address them in October 20 conference call CIM and DCIM FDIS: FDIS of Ed.4 and FDIS of Ed.1 planned after January 2010 meetings Will include fixes, provided as high priority IOP issues To be submitted not later than end Q1-2010 [source: Tanja Kostic] CIM Users Group: CIM for Enterprise Integration

IEC 61968 Basic Message Structure
CIM Users Group: CIM for Enterprise Integration

Message Header CIM Users Group: CIM for Enterprise Integration

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

(IEC Verbs - continued) CIM Users Group: CIM for Enterprise Integration

Message Payload of “End Device Control” of IEC 61968-9
XSD Tag Names Are From Relevant Data Elements in the CIM CIM Users Group: CIM for Enterprise Integration

“End Device Control” Sample XML
<?xml version="1.0" encoding="UTF-8"?> <!--Sample XML file generated by XMLSpy v2009 sp1 ( <m:EndDeviceControls xsi:schemaLocation=" EndDeviceControls.xsd" xmlns:m=" xmlns:xsi=" <m:EndDeviceControl> <m:mRID> _D0AB</m:mRID> <m:drProgramLevel>3</m:drProgramLevel> <m:drProgramMandatory>true</m:drProgramMandatory> <m:priceSignal>0.2</m:priceSignal> <m:type>PRICE</m:type> <m:DemandResponseProgram> <m:type>RTP</m:type> </m:DemandResponseProgram> <m:scheduledInterval> <m:end> T10:30:47Z</m:end> <m:start> T09:30:47Z</m:start> </m:scheduledInterval> </m:EndDeviceControl> </m:EndDeviceControls>

IEC 61968-4: Records and Asset Management
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 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

The NetworkDataSet is organized by logical
Role (vs. physical asset) and may represent various views, such as as-built, nominal, operational, study, etc. Everything from the IEC Wires Package may be included. Connectivity Is based on IEC Topology CIM Users Group: CIM for Enterprise Integration

From the logical view to the physical asset view of the same object.

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

Graphical Rendering GML has been designed to uphold the principle of separating content from presentation GML provides mechanisms for the encoding of geographic feature data without regard to how the data may be presented to a human reader Since GML is an XML application, it can be readily styled into a variety of presentation formats including vector and raster graphics, text, sound and voice GML is standardized through ISO ISO Geographic information - Geography Markup Language (GML) CIM Users Group: CIM for Enterprise Integration

Presentation of Real World Objects – Key Classes

Case Study: Asset Management System Used to Initialize System Control Center System (source: DistribuTECH2002) Asset Management 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

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

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

Case Study: LIPA Asset Management Concept (source: IEEE 2009)

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

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

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

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

Generic “TypeAssets” are used for Design

IEC 61968-3: Network Operations
Current Message Types: Measurement list; Operational restrictions; Outage records; Safety documents; Switching schedules. More to be added during maintenance cycles CIM Users Group: CIM for Enterprise Integration

An Example: Safety Document Classes

Safety Document Message Type

IEC 61968-8: Customer Support
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

Aspects of Customer Accounts

A Customer Account Message Type for AMI (IEC 61968-9)

IEC Reference Model

IEC 61968-9: Automated Meter Reading and Control
Current Message Types CustomerMeterDataSet MeterAsset MeterAssetReading EndDeviceControls EndDeviceEvents MeterReadings MeterReadSchedule MeterServiceRequest MeterSystemEvents EndDeviceFirmware CIM Users Group: CIM for Enterprise Integration

Metering Inheritance Package

Customer Overview – from a 61968-9 perspective

Pricing structure model
TariffProfile determines the cycle of operation for the tariff, such as hourly, daily, weekly, monthly, etc, at the end of which it resets to start at the beginning of the process again. TimeTariffInterval determines the starting time for a particular interval and several instances of TimeTariffInterval may be used to construct a series of time intervals to realise a time of use tariff for example. ConsumptionTariff Interval determines the starting value of a consumption interval and several instances of ConsumptionTimeInterval may be used to construct a series of consumption intervals to realise a block tariff or a step tariff for example. CIM Users Group: CIM for Enterprise Integration

Auxiliary agreements Receipting payments for ‘other items’ such as debt, rates, taxes, municipal fines, TV licences, garbage collection charges, etc. The collection of such revenue may be integrated with token sales and customer account payments by means of auxiliary agreements and auxiliary accounts. AuxiliaryAccount captures the dynamic information about the charges and payments made against the account. CIM Users Group: CIM for Enterprise Integration

Example of Meter Reading Schedules and Readings

Meter Reading Options Meter Readings may be requested using a variety of parameters: Specific meter, using the MeterAsset mRID Specific meter, using a meter name as known to the Metering System EndDeviceGroups, where a EndDeviceGroup identifies a group address used within the Metering System As specified using a TimeSchedule Reading types can be specified to identify the desired reading types CIM Users Group: CIM for Enterprise Integration

Meter Readings Type Key to the reporting of a value from a meter is the reading type. The ReadingType class allows the capture of the following information: mRID (to uniquely identify a reading type) channel number default quality default value data type dynamic configuration forward chronology interval length (in seconds) measurement type category unit of measure register digits Refer to IEC Annex for details CIM Users Group: CIM for Enterprise Integration

Example type controls: Load control signal Price signal or schedule
Device Control Example type controls: Load control signal Price signal or schedule Remote disconnect Remote reconnect Demand reset Demand reduction signal

End Device Updates CIM Users Group: CIM for Enterprise Integration

Meter System Events (page 1)

Meter System Events (page 2)

Meter Service Requests

Example Meter Relationship from IEC 61968-9
Description of Item Value CIM Location Type This communication module MCM-ID EndDeviceAsset.DeviceFunction.ComFunction.amrAddress name/mRID is servicing this end device End-device ID MeterAsset.name (which is let’s say an electricity meter) End-device type ServiceDeliveryPoint.serviceType Attribute using this connection Port Number EndDeviceAsset.DeviceFunction.ComPort Upstream CommAsset EndDeviceAsset.DeviceFunction. at this location ServiceDeliveryPoint ServiceDeliveryPoint.name for this account Account ID CustomerAccount.name and this customer Customer ID CustomerAccount.Customer.name In this utility Business Unit Commencing at this date Installation date ActivityRecord.statusDateTime Because “In-Service” ActivityRecord.status CIM Users Group: CIM for Enterprise Integration

GWAC Stack – Levels of Interoperability
[Source: GridWise Architectural Council Interoperability Context Setting Framework] CIM Users Group: CIM for Enterprise Integration

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

[Source: NIST Interim Roadmap] CIM Users Group: CIM for Enterprise Integration

Interoperability Layers

(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

Case Study: Consumers Energy and AMI-Ent TF

Case Study: AMI-Ent Use Cases

Case Study: AMI-Ent Service Identification

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

Status/Plans: Verified applicable XSDs are compliant with IEC Submitted to CIM InterOperability Testing; TBD for when it will be included (Margaret) Proposed requirements and extensions being submitted to WG14 for consideration. CIM Users Group: CIM for Enterprise Integration

OpenHAN - Home Area Network – Collaboration between UCA, ZigBee, and IEC SEP 2.0 is being developed by ZigBee/ HomePlug SEA, is intended to be CIM-based which is being coordinated with IEC (and NIST, et al.) OpenHAN SRS given to ZigBee and was used for SEP 1.0 CIM Users Group: CIM for Enterprise Integration

Distributed Energy Resources - Collaboration between NIST, UCA, ZigBee, and IEC Discrete Metering, Incentive Programs, and Demand Response for PEVs © Copyright 2008, Southern California Edison SCE is also committed to advancing Distributed Energy Resource (DER) research and development, in addition to managing its existing portfolio of interconnections. To date, SCE manages over 4,000 DER projects totaling 270 megawatts. As part of SCE’s Circuit of the Future project, internal researchers and scientists developed a “plug-and-play” interface for dispatchable DER as part of a demonstration for future distribution circuit design and functionality. In anticipation of more advanced and widespread deployments of DER by customers and businesses, SCE has completed use cases for facilitating the integration and management of DER using SCE’s Edison SmartConnect advanced metering and communications infrastructure. As discussed in the previous slide, HAN functionality will also give customers the option to purchase, connect, and partially manage systems and devices such as: Distributed Energy Resources (e.g., home energy storage systems, distributed generation such as rooftop photo-voltaic systems, etc.); and Plug-in Electric Vehicles (Source: OIR) Enable Net Metering, Discrete metering and Integrated Energy Management w/Solar Panel Home Energy Storage Creates Opportunities for Increased Renewables [source: Jose A. Salazar, SCE] CIM Users Group: CIM for Enterprise Integration

Future State- PHEV Connection (120VAC) & Communication Scenario B
[source: Jose A. Salazar, SCE] CIM Users Group: CIM for Enterprise Integration

Future State- Battery EV w/ PLC Connection & Communication Scenario A
[source: Jose A. Salazar, SCE] CIM Users Group: CIM for Enterprise Integration

OpenSG’s OpenADE - Automated Data Exchange – Collaboration among NIST, UCA and IEC CIM Users Group: CIM for Enterprise Integration

OpenADE Scope Authorization Publication 1.0 – Interval consumption, after “VEE” 2.0 – (TBD) Near-realtime (from HAN) Pricing / billing information October 19, 2009 OpenSG - OpenADE 81 CIM Users Group: CIM for Enterprise Integration

OpenSG’s OpenADR – Automated Demand Response – Collaboration among NAESB, NIST, UCA, OASIS, ZigBee, and IEC 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 must 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 to! CIM Users Group: CIM for Enterprise Integration

CIM for Enterprise Integration for the CIM University, CIM Users Group in Charlotte, NC November 10, 2009 For further information, contact: Greg Robinson.

Similar presentations

Presentation on theme: "CIM for Enterprise Integration for the CIM University, CIM Users Group in Charlotte, NC November 10, 2009 For further information, contact: Greg Robinson."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

CIM for Enterprise Integration for the CIM University, CIM Users Group in Charlotte, NC November 10, 2009 For further information, contact: Greg Robinson.

Similar presentations

Presentation on theme: "CIM for Enterprise Integration for the CIM University, CIM Users Group in Charlotte, NC November 10, 2009 For further information, contact: Greg Robinson."— Presentation transcript:

Similar presentations

About project

Feedback