Вы находитесь на странице: 1из 53

CIM for Enterprise Integration

CIM University, CIM Users Group


in San Francisco, CA October 11, 2010

for the

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

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

Slide 2

This is Not a Good Practice For Wires Integration; Its Not Good For Data Integration Either!

Wires Integration Anarchy!

CIM Users Group: CIM for Enterprise Integration

Slide 3

Goal: Interface Standards Should Be Based on Common Semantics (e.g., CIM) to Avoid Adding to Integration Anarchy

OMS

GIS

CIS

Integration Infrastructure

WMS

DMS

AMR
Data Integration Anarchy!

Integration anarchy is a chaos of:


(1) (2) (3) (4) (5)

Without duplicated logic, Common Semantics, duplicated data, Point-to-Point duplicated effort, Integration Will newly acquired integration difficulties, Continue at the Data Level 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 Slide 4 System of Systems CIM Users Group: CIM for Enterprise Integration

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
Network Operations (NO) IEC 61968-3
Network Operations Monitoring (NMON) Operation Statistics & Reporting (OST)

Records & Asset Management (AM) IEC 61968-4


Substation & Network Inventory (EINV) Geographical Inventory (GINV) General inventory management (GIM) Asset Investment Planning (AIP)

Maintenance and Construction (MC) IEC 61968-6


Maintenance & Inspection (MAI) Construction WMS (CON) Design & Estimate (DGN) Scheduling & Dispatch (SCH) Field Recording (FRD)

Operational Planning & Optimization (OP) IEC 61968-5


Network Operation Simulation (SIM) Switch Action Scheduling (SSC) Power Import Sched. & Optimization (IMP)

Network Control (CTL)


Fault Management (FLT) Operational Feedback Analysis (OFA)

Network Calculations - Real Time (CLC)


Dispatcher Training (TRN)

Application Integration Infrastructure


Network Extension Planning (NE) IEC 61968-7
Network Calculations (NCLC) Project Definition (PRJ) Construction Supervision (CSP) Compliance Management (CMPL)

Customer Support (CS) IEC 61968-8


Customer Service (CSRV)
Trouble Call Management (TCM) Point Of Sale (POS)

Meter Reading & Control (MR) IEC 61968-9


Meter Reading (RMR) Advanced Metering Infrastructure (AMI) Demand Response (DR) Load Control (LDC) Meter Operations (MOP) Meter Data Management IMDM) Metering System (MS) Meter Maintenance (MM) Meter Data (MD)

External to DMS (EXT)


Energy Trading (ET) Retail (RET) Sales (SAL) Stakeholder Planning & Management (SPM) Supply Chain & Logistics (SC) Customer Account Management (ACT) Financial (FIN) Business Planning & Reporting (BPR) Premises (PRM) Human Resources (HR)

CIM Users Group: CIM for Enterprise Integration

Slide 5

Key Concept: Incremental Integration

- in Step With Business Needs

GIS OMS
OR

CIS
TT

IEC 61968 IRM Interface

Semantically Consistent ESB

WMS DMS

AMR
Information Flow Design
CIS OMS TT OR
Slide 6

DMS

Trouble Ticket Outage Record


CIM Users Group: CIM for Enterprise Integration

Key Concept: Replace Large Monolithic Applications a Chunk at a Time

CIM Message Types

Other Apps Other Apps Other Apps

Maintenance & Inspection

Construction

Work Scheduling

WMS

Field Recording

Design

CIM Users Group: CIM for Enterprise Integration

Slide 7

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

Slide 8

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 Slide 9

Message Header
Field Verb Noun Description This enumerated list of verbs can be used to form message types in compliance with the IEC 61968 standard The Noun identifies the main subject of the message type, typically a real world object defined as a profile using the CIM.

Revision
Context Timestamp

Revision level of the message type.


Intended context for information usage such as production, testing and etc. Application 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. Source person or system that publishes the message Indicates whether or not reply should be asynchronous Address to be used for asynchronous replies Indicates whether or not an acknowledgement is required User information of the sender

Source AsyncReplyFlag ReplyAddress AckRequired User

MessageID
CorrelationID Comment Property

Unique message ID to be used for tracking messages


ID to be used by applications for correlating replies Optional comment Message properties can be used to identify information needed for extended routing and filtering capabilities.
[source: IEC 61968-1] CIM Users Group: CIM for Enterprise Integration Slide 10

Message Types Are Created By Combining IEC 61968 Verbs With Information Exchange Topics, Referred To As Nouns
Verbs
CREATE

Meaning
The CREATE verb is used to publish a request to the master system to create a new document. The CHANGE verb is used to publish a request to the master system to make a change in the document based on the information in the message. The CANCEL verb is used to publish a request to the master system to cancel the document. The CANCEL verb is used when the business content of the document is no longer valid due to error(s). The CLOSE verb is used to publish a request to the master system to close the document. The CLOSE verb is used when the business document reaches the end of its life cycle due to successful completion of a business process. The DELETE verb is used to publish a request to the master system to delete the document. The DELETE verb is used when the business document should no longer be kept in the integrated systems either due to error(s) or due to archiving needs. The GET verb is used to publish a request to the master system to get the current data for a given document reference code or a set of documents.
CIM Users Group: CIM for Enterprise Integration

Message Body
All sections (data required to create the document) All sections (key(s) + data to be changed)

CHANGE

CANCEL

Header information + message content key(s)

CLOSE

Header information + message content key(s)

DELETE

Header information + message content key(s)

GET

One or more document reference codes + Key(s)


[source: IEC 61968-1]
Slide 11

Verbs
CREATED

Meaning
The CREATED verb is used to publish the creation of a document as a result of either an external request or an internal action within the master system of that document. The CHANGED verb is used to publish the change of a document as a result of either an external request or an internal action within the master system of that document. The CLOSED verb is used to publish the normal closure of a document as a result of either an external request or an internal action within the master system of that document. The CANCELED verb is used to publish the cancellation of a document as a result of either an external request or an internal action within the master system of that document. The SHOW verb is used to publish the most current content of a document as a result of either an external GET request or an internal action within the master system of that document. The REPLY verb is used to publish the processing result of an external request to the master system to create, change, delete, cancel, or close a document. The REPLY message type could contain specific confirmation information as to whether the request is processed successfully or not and provide alternatives if applicable. The SUBSCRIBE verb is used to publish the request to ask the master system of a document to publish a CHANGED document whenever there is a change to the document. The UNSUBSCRIBE verb is used to publish the request to ask the master system of a document to stop publishing a CHANGED document whenever there is a change to the document.

Message Body
All sections

CHANGED

All sections (key(s) + changed content)

CLOSED

Header information + message content key(s)

CANCELED

Header information + message content key(s)

(IEC 61968 Verbs - continued)

SHOW

All sections

REPLY

Header information + message content key(s) + confirmation information + alternatives (optional)

SUBSCRIBE

Header information + message content key(s)

UNSUBSCRIB E

Header information + message content key(s)


[source: IEC 61968-1]

CIM Users Group: CIM for Enterprise Integration

Slide 12

Example of a message type payload

[source: IEC 61968-1]

CIM Users Group: CIM for Enterprise Integration

Slide 13

Example of how message elements are derived from the CIM

class par t9 : Meter Readings m essage type I dent if iedObject Meter ing:: Ser viceDeliver yPoint

+ ServiceDeliveryPoint 0..1

+ Cust omerAgreement

Agr eement

Custom er s:: 0..1 Custom er Agr eem ent

+ Met erReadings I dent if iedObject Meter ing:: Meter Reading 0..* + Met erReadings 0..* + Met erReading 0..1 + Met erReadings 0..* + Met erReading 0..1 + Met erReadings 0..* + Readings + Met erAsset 0..1 + Int ervalBlocks 0..* + EndDeviceEvent s

Act ivit y Recor d

Meter ing:: 0..* EndDeviceEvent

EndDeviceAsset Meter ing:: Meter Asset

Meter ing:: Inter valBlock

0..* Measur ement Value Meter ing::Reading

[source: IEC 61968-1] CIM Users Group: CIM for Enterprise Integration Slide 14

Navigating associations in CIM (UML notation)

class par t9 : Meter Readings m essage type I dent if iedObject Meter ing:: Meter Reading + Int ervalReadings Measur ement Value 0..* Meter ing:: Inter valReading + Int ervalReading 1

+ Met erReading 0..1

+ Int ervalBlocks 0..* Meter ing:: Inter valBlock 0..*

+ Int ervalBlocks 0..* 0..* + Int ervalBlocks + Pending 0..1 + ReadingQualit ies 0..* Meter ing:: ReadingQuality

Meter ing:: Pending 0..1

+ Int ervalBlocks

+ Pending

I dent if iedObject Meter ing:: ReadingType

+ ReadingType 1 + ReadingType 1

CIM Users Group: CIM for Enterprise Integration

Slide 15

Navigating associations in message type schemas

CIM Users Group: CIM for Enterprise Integration

Slide 16

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

Slide 17

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

Slide 18

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

MSA Asset Management AssetManagement Management


Asset Owner Asset Manager Service Provider

LIPA LIPA Goals Goals


Customer Satisfaction Financial Technical Performance Regulatory

Risk
Management

Strategy Plan

Impl ement

Exe cute

Assess Effectiveness

Data and Process Integration CIM/IB/SOA

Risk Assessment Risk Assessment


Risk Status Risk Drivers Risk Tolerance

Assets & Processes (O&M&Planning) aspects

KPIs

Visualization Dynamic Criticality


FMEA

KRIs/Risk Indicators

CIM Users Group: CIM for Enterprise Integration

Slide 19

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

Slide 20

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., Distributions CPSM) 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

Contains references to other static data such as:

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

Slide 21

From the logical view to the physical asset view of the same object.
PowerSystemResource
(from Core)
0..n 0..n 0..n 0..n OrgPsrRole
(from AssetBasics)

Organisation
(from TopLevel)

1..n

DocPsrRole
(from AssetBasics)

OrgAssetRole
(from AssetBasics)

AssetPsrRole
(f rom AssetBasics)

ErpInventory
(from ERP_Support)
0..1 +Documents 0..n DocAssetRole
(from AssetBasics)

0..n 0..n

0..n 0..1

Document
(from DocumentInheritance)

0..n

Asset
(from AssetBasics)
0..1 0..1

AssetModel
(from AssetBasics)

0..n

0..1

TypeAsset
(from TypeAsset)

FinancialProperties
(from AssetBasics)

CIM Users Group: CIM for Enterprise Integration

Slide 22

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

Slide 23

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 Slide 24

Case Study: Operations Model Capabilities (source: DistribuTECH2002)

AMS

DMS

CIM Users Group: CIM for Enterprise Integration

Slide 25

PowerSystemResource
(from Core)

0..n DocPsrRole
(from AssetBasics)

DocAssetRole
(from AssetBasics)

0..n Document
(from DocumentInheritance)

0..n

0..n

Asset
(from AssetBasics)
0..n

AssetListRole
(from AssetBasics)

0..n

Specification
(f rom AssetBasics)

Collecti on 0..n
(from Collections)

0..n

AssetList
(f rom AssetBasics)

TypeAssetCatalogue
(from AssetBasics)
0..1

AssetCatalogue
(from AssetBasics)
1

0..n

AssetModel
(from AssetBasics)

0..n

0..1

TypeAsset
(from TypeAsset)
0..n

0..1

AssetCatalogueItem
0..n
(f rom AssetBasics)

CIM Users Group: CIM for Enterprise Integration

Slide 26

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

Slide 27

IEC 61968-6: Maintenance & Construction

(Note: CD in development paper being presented at Grid InterOp)


Maintenance and Construction (MC) IEC 61968-6

Business Functions Performed Maintain and Plan PM Programs Manage Inspection and Maintenance Triggers Link Inspection orders to follow-up repair orders Gather failure data

Maintenance & Inspection (MAI)

Construction WMS (CON)

Initiate and Plan work orders Manage material, equipment, and permit requests Manage and Track Work (Workflow) Close Work and Support Performance Analysis

Design & Estimate (DGN)

Work Design and Cost Estimation Compatible Unit based Graphical design Generate Bill of Materials

Scheduling & Dispatch (SCH)

Assign crew based on work type and skills Determine Schedule Date Perform constraint-based auto-scheduling Gather actual costs and support cost reconciliation Monitor work progress support financial closing with accounting systems

Field Recording (FRD)

CIM Users Group: CIM for Enterprise Integration

Slide 28

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, Turnoff, 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

Slide 29

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 Slide 30

Generic TypeAssets are used for Design

CUGroup
(f rom WorkStandards)

CostType
(f rom WorkClosing)

0..1

0..1 0..n

0..n

0..n 0..1

0..n

CompatibleUnit
(from WorkDesign)
0..n 0..n 0..n 0..n 0..n 0..n

0..n

CUContractorItem
(f rom WorkStandards)

0..n

Procedure
(f rom WorkInspectionMaintenance)

0..n

0..n

0..n

0..n

CUMaterialItem
(f rom WorkStandards)

CUAsset
(from WorkStandards)
0..1

CUEquipmentItem
(from WorkStandards)
0..1 0..1 0..1

CULaborItem
(f rom WorkStandards)

0..n

0..1

TypeMaterial
(f rom WorkStandards)

TypeAsset
(from TypeAsset)

CIM Users Group: CIM for Enterprise Integration

Slide 31

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 Slide 32

An Example: Safety Document Classes

Organisation DocOrgRole
(from TopLevel) (from TopLevel)

OrgErpPersonRole
(from TopLevel)

0..n 0..n 0..n 0..n

SafetyDocument
(from Operational)

Document
(from DocumentInheritance)

ErpPerson
(from ERP_Support)

0..n 0..n OperationalRestriction


(from Operational)

0..n

0..n 0..n ActivityRecord


(from ActivityRecords)

0..n PowerSystemResource
(from Core)

0..n 0..1
ClearanceTag
(from Outage)

1 0..n

ConductingEquipment
(from Core)

Equipment
(from Core)

PSRType
(from Core)

CIM Users Group: CIM for Enterprise Integration

Slide 33

Safety Document Message Type

CIM Users Group: CIM for Enterprise Integration

Slide 34

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

Slide 35

Aspects of Customer Accounts

CustomerAccount
(from Consumers)
1..n 1 1 0..n

Agreement
(from TopLevel)

Equipment
(f rom Core)

ConductingEquipment
(f rom Core)

0..n 0..n

CustomerData
(from Consumers)
0..1 0..1

CustomerAgreement
(from Consumers)
0..n 0..n

0..n 0..n

ServiceLocation
(from Locations)
0..1 0..n

EnergyConsumer
(f rom Wires)

0..1

0..n 0..n

0..n 0..n 0..n

Organisation
(f rom TopLev el)

ErpPerson
(f rom ERP_Support)

ServiceKind
(f rom Consumers)

SDPLocation
(from Locations)

ServiceDeliveryPoint
(from Metering)
0..n

0..n

0..n 0..n Tariff


(from Consumers)

0..n 1 0..n

PricingStructure
0..n
(f rom Consumers)

PowerQualityPricing
(f rom Consumers)

0..n

CIM Users Group: CIM for Enterprise Integration

Slide 36

A Customer Account Message Type for AMI

(IEC 61968-9)

CIM Users Group: CIM for Enterprise Integration

Slide 37

IEC 61968-9 Reference Model


Refer to Margarets presentation

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

Slide 39

NIST Conceptual Model

CIM Users Group: CIM for Enterprise Integration

[Source: NIST InterimSlide 40 Roadmap]

User groups are a good source of help


Advisors

Board of Directors
Audit Committee

Operating Officers

Executive Committee

Help Desk

Technical Oversight Committee

Technical Publications

Marketing

CIM

Testing

Liaison

61850

Harmonization

Membership

OpenSG

http://www.ucaiug.org/
CIM Users Group: CIM for Enterprise Integration Slide 42

CIM Users Group: CIM for Enterprise Integration

Slide 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

Slide 44

OpenSG Focus: Finding/Developing Best Practices & Making Them into Vetted Industry Best Practices

Utilitys Projects - Design &


Implementations

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.

---------------

Utilitys Architecture
----------------------Industry Best Practices Interoperability Testing ---------------------------------

Industry Best Practices


-----------------------------------------Standards Conformance & Interoperability Testing

(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 Slide 46 communicate with other businesses or CIM Users Group: CIM fordefined as Integration enterprises (generally Enterprise third parties).

Case Study: Consumers Energy and AMI-Ent TF


Customer Info. & Billing Distribution Management HAN Management

Outage Management

Revenue Protection

AMI Service Manager

Enterprise Bus + Common Model & Service

AMI-ENT AMI-

Customer Portal

Demand Response Management

AMI Network Asset Management

Third Party Portal

Meter Data Management

Meter Asset Management

Representative of AMI-ENT components, not all inclusive.

CIM Users Group: CIM for Enterprise Integration

Slide 47

Case Study: AMI-Ent Service Identification

CIM Users Group: CIM for Enterprise Integration

Slide 48

Case Study: AMI-Ent Inventory of CIM-Based Services Supporting Use Cases for AMI-Enterprise
Use Case & Integration Scenario Requirement B1-S1 B1-S12 B1-S15 B1-S15 REQ-B1004 REQ-B1011 REQ-B1012 REQ-B1013 Functional Description of Operation the Service Pattern MDUS receives the meter Created reading results on scheduled basis. MDUS receives meter Created reads MDUS notifies meters with Created reading problems AMI Head End operator Created receives meter service orders Request billing determinant Create Request billing determinant Created Head End receives the Create request for a meter reading on demand MDUS receives a meter Created reading on demand A user or system receives a meter reading on demand CIS receives meter event Created Service Name Service Operation Service Consumer (Outbound) Head End Field Tool MDUS? MDUS Service Provider Information Object (Inbound - WS) (normalized) MDUS MDUS MDUS Head End MeterReading MeterReading MeterSystemEvent MeterServiceOrder

MeterReading MeterReading MeterSystemEvent MeterServiceOrder

CreatedMeterReading CreatedMeterReading CreatedMeterSystemEvent CreatedMeterServiceOrder

B1-S17 B1-S17 B1-S2 B1-S2

REQ-B1014 REQ-B1014 REQ-B1001 REQ-B1002

BillingDeterminantRequest BillingDeterminant MeterReading MeterReading

CreateBillingDeterminant CreatedBillingDeterminant CreateMeterReading CreatedMeterReading

CIS MDUS TBD Head End

MDUS CIS Head End MDUS

BillingDeterminant BillingDeterminant MeterReading MeterReading

B1-S2

REQ-B1003

MeterReading

CreatedMeterReading

MDUS

TBD

MeterReading

B1-S3 B1-S7 B1-S7 B1-S8 B1-S8 B2-S1 B2-S1 B2-S1 B2-S1 B2-S2

REQ-B1006 REQ-B1009 REQ-B1010 REQ-B1009 REQ-B1010 REQ-B2001 REQ-B2002 REQ-B2003 REQ-B2004 REQ-B2005

Created

MeterSystemEvent MeterReading MeterReading MeterReading MeterReading ScheduledEvent ConnectDisconnect CommonConfirmation MeterReading MeterStatusRequest

CreatedMeterSystemEvent CreateMeterReading CreatedMeterReading CreateMeterReading CreatedMeterReading CreatedScheduledEvent CreatedConnectDisconnect CreatedCommonConfirmation CreatedMeterReading CreateMeterStatus

MDUS receives the request Create for meter readings Third party receives the meter readings Created

Head End/MDUS Third Party Portal MDUS Third Party Portal MDUS CIS CIS Head End Head End CIS

CIS MDUS

MeterSystemEvent MeterReading

Third Party Portal MeterReading MDUS MeterReading

MDUS receives the request Create for meter readings Third party receives the meter readings Send scheduled shut off notification Send scheduled shut off command Send scheduled shut off command confirmation Send meter read (final) Request AMI Meter status Created Created Created Created Created Create

Third Party Portal MeterReading Head End Head End CIS MDUS Head End ScheduledEvent ConnectDisconnect CommonConfirmation MeterReading MeterStatus

CIM Users Group: CIM for Enterprise Integration

Slide 49

Application View
Services Provided/Consumed by Customer Information Management

Service Operation

Service Operation

CommonConfirmation MeterStatus HanAsset

Created Created Created

CommonConfirmation MeterStatus HANAsset

ScheduledEvent ConnectDisconnect MeterStatusRequest

Created Create Create Create Create Created Changed

ScheduledEvent ConnectDisconnect MeterStatusRequest LoadControlCommandRequest HANAsset

AMI Head End AMI Head End

LoadControlCommandRequest HANAsset

BillingDeterminant MeterStatus MeterSystemEvent

Created Created Created

BillingDeterminant MeterStatus MeterSystemEvent ServiceToken ServiceToken

AMI Head End AMI Head End

Meter Data Management Meter Data Management

BillingDeterminant MeterAssetRequest MeterServiceOrderRequest

Create Change Create

BillingDeterminant MeterAssetRequest MeterServiceOrderRequest

Meter Data Management Meter Data Management

Customer Information Management Customer Information Management

Service Consumers

Service Providers / Consumers


CIM Users Group: CIM for Enterprise Integration

Service Providers
Slide 50

Technical View (Patterns)

Service

SendMeterReading CreatedMeterReading

ReceiveMeterReading CreatedMeterReading ChangedMeterReading CanceledMeterReading

Operations

ChangedMeterReading CanceledMeterReading

Native API or Service

S/C

S/P

Orchestration

S/C

S/P

Native API or Service

Application A

Transparent ESB

Application B

Guaranteed delivery within ESB, plus internal routing


CIM Users Group: CIM for Enterprise Integration

Other interested parties


Slide 51

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 dont 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 email, 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] CIM Users Group: CIM for Enterprise Integration Slide 52

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 ones 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] CIM Users Group: CIM for Enterprise Integration Slide 53

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!
CIM Users Group: CIM for Enterprise Integration Slide 54