CIM For Enterprise Integration (IEC) 61968

CIM for Enterprise Integration
for the
CIM University, CIM Users Group
in San Francisco, CA
October 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
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 2
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 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: Without
(1) duplicated logic, Common
(2) duplicated data, Semantics,
Point-to-Point
(3) duplicated effort, Integration Will
(4) newly acquired integration difficulties, Continue at the
(5) lack of ability to easily create new application functionality from Data Level
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
Slide 4
The IEC 61968-1 Interface Reference Model (IRM) Provides The Framework For
Identifying Information Exchange Requirements Among Utility Business Functions
Maintenance and
IEC 61968 Sequence Diagrams are organized by the IRM Construction
(MC) – IEC 61968-6
Network Operations Records & Asset
(NO) – IEC 61968-3 Management Maintenance &
(AM) – IEC 61968-4 Operational Planning Inspection (MAI)
& Optimization
Network Operations Operation Statistics Construction WMS
Monitoring (NMON) & Reporting (OST)
Substation & Network (OP) – IEC 61968-5 (CON)
Inventory (EINV)
Network Control Network Calculations Geographical Network Operation Design &
(CTL) - Real Time (CLC) Inventory (GINV) Simulation (SIM) Estimate (DGN)
Fault Management Dispatcher Training General inventory Scheduling

Switch Action
(FLT) (TRN) management (GIM) & Dispatch (SCH)
Scheduling (SSC)
Operational Feedback Asset Investment Power Import Sched. Field

Analysis (OFA) Planning (AIP) & Optimization (IMP) Recording (FRD)
Application Integration Infrastructure
Network Extension Customer Meter Reading & Control External to DMS

Planning Support (MR) – IEC 61968-9 (EXT)
(NE) – IEC 61968-7 (CS) – IEC 61968-8 Meter Reading Meter Data Energy Trading Customer Account
(RMR) Management IMDM) (ET) Management (ACT)
Network Customer Service
Calculations (NCLC) (CSRV) Advanced Metering Metering System Retail Financial
Infrastructure (AMI) (MS) (RET) (FIN)
Project Definition Trouble Call
(PRJ) Management (TCM) Demand Response Meter Maintenance Sales Business Planning &
(DR) (MM) (SAL) Reporting (BPR)
Construction Point Of Sale
Supervision (CSP) (POS) Load Control Stakeholder Planning & Premises
Meter Data (MD) Management (SPM) (PRM)
(LDC)
Compliance
Management (CMPL) Meter Operations Supply Chain & Human Resources
(MOP) Logistics (SC) (HR)
Slide 5
Key Concept: Incremental Integration
- in Step With Business Needs
GIS
OMS
OR CIS
TT
IEC 61968
IRM Interface
Semantically Consistent ESB
WMS AMR
DMS Information Flow Design

CIS OMS DMS
Trouble Ticket TT
OR
Outage Record
Slide 6
Key Concept:
Replace Large Monolithic Applications ‘a Chunk at a Time’
Other Apps
CIM Message Types Other Apps
Other Apps
Maintenance &
Construction
Scheduling
Recording
Inspection
Design
Work
Field
WMS
Slide 7
Agenda

– Messaging
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]
Slide 9
Message Header
Field Description
Verb This enumerated list of verbs can be used to form message types in compliance
with the IEC 61968 standard
Noun The Noun identifies the main subject of the message type, typically a real world
object defined as a profile using the CIM.
Revision Revision level of the message type.
Context Intended context for information usage such as production, testing and etc.
Timestamp 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 Source person or system that publishes the message
AsyncReplyFlag Indicates whether or not reply should be asynchronous
ReplyAddress Address to be used for asynchronous replies
AckRequired Indicates whether or not an acknowledgement is required
User User information of the sender
MessageID Unique message ID to be used for tracking messages
CorrelationID ID to be used by applications for correlating replies
Comment Optional comment
Property Message properties can be used to identify information needed for extended
routing and filtering capabilities.
Slide 10
Message Types Are Created By Combining IEC 61968 Verbs With
Information Exchange Topics, Referred To As Nouns
Verbs Meaning Message Body

CREATE The CREATE verb is used to publish a request to All sections (data
the master system to create a new document. required to create the
document)
CHANGE The CHANGE verb is used to publish a request to All sections (key(s) +
the master system to make a change in the data to be changed)
document based on the information in the
message.
CANCEL The CANCEL verb is used to publish a request to Header information +
the master system to cancel the document. The message content key(s)
CANCEL verb is used when the business content
of the document is no longer valid due to error(s).
CLOSE The CLOSE verb is used to publish a request to Header information +
the master system to close the document. The message content key(s)
CLOSE verb is used when the business document
reaches the end of its life cycle due to successful
completion of a business process.
DELETE The DELETE verb is used to publish a request to Header information +
the master system to delete the document. The message content key(s)
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.
GET The GET verb is used to publish a request to the One or more document
master system to get the current data for a given reference codes +
document reference code or a set of documents. Key(s)
Slide 11
Verbs Meaning Message Body
CREATED The CREATED verb is used to publish the All sections
creation of a document as a result of either an
external request or an internal action within the
master system of that document.
CHANGED The CHANGED verb is used to publish the All sections (key(s) +
change of a document as a result of either an changed content)
CLOSED The CLOSED verb is used to publish the normal Header information +
closure of a document as a result of either an message content key(s)
CANCELED The CANCELED verb is used to publish the
cancellation of a document as a result of either an
Header information +
message content key(s)
(IEC 61968
Verbs - continued)
SHOW The SHOW verb is used to publish the most All sections
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.
REPLY The REPLY verb is used to publish the processing Header information +
result of an external request to the master system message content key(s)
to create, change, delete, cancel, or close a + confirmation
document. The REPLY message type could information +
contain specific confirmation information as to alternatives (optional)
whether the request is processed successfully or
not and provide alternatives if applicable.
SUBSCRIBE The SUBSCRIBE verb is used to publish the Header information +
request to ask the master system of a document message content key(s)
to publish a CHANGED document whenever there
is a change to the document.
UNSUBSCRIB The UNSUBSCRIBE verb is used to publish the Header information +
E request to ask the master system of a document message content key(s)
to stop publishing a CHANGED document [source: IEC 61968-1]
whenever there is a change to the document.
Slide 12
Example of a “message type” payload
Slide 13
Example of how message elements are derived from the CIM
class part9: MeterReadings message type
I dent ifiedObject
+ ServiceDeliveryPoint
Metering::
0..1 ServiceDeliveryPoint
Agreement
+ CustomerAgreement
Customers::
0..1 CustomerAgreement
+ MeterReadings
I dent ifiedObject Act ivit y Record
+ EndDeviceEvents
Metering:: 0..* Metering::
MeterReading + MeterReadings 0..* EndDeviceEvent
0..*
+ MeterReading
EndDeviceAsset
0..1 Metering::
+ MeterReadings + MeterAsset MeterAsset
0..* 0..1
+ MeterReading + IntervalBlocks
Metering::
0..1 0..*
IntervalBlock
+ MeterReadings
0..*
+ Readings
Measurement Value
0..*
Metering::Reading
Slide 14
Navigating associations in CIM (UML notation)
class part9: MeterReadings message type
I dent ifiedObject
Metering::
MeterReading
+ IntervalReadings Measurement Value + IntervalReading

Metering::
0..* IntervalReading 1
+ MeterReading + IntervalBlocks + IntervalBlocks
0..1 0..* Metering:: 0..*

IntervalBlock + Pending + ReadingQualities
Metering::
Pending 0..*
0..* 0..1
+ IntervalBlocks 0..* + IntervalBlocks
Metering::
+ Pending 0..1 ReadingQuality
+ ReadingType
I dent ifiedObject
Metering:: 1
ReadingType + ReadingType
Slide 15
Navigating associations in message type schemas
Slide 16
Agenda

– Messaging
Slide 17
Case Study: LIPA Asset Management and Organization (source: IEEE 2009)
Asset Owner Asset Manager

Responsibilities: • Asset Optimization
• Asset valuation • Asset yield contribution
• Investment analysis & strategy understanding
• Contract negotiation/structuring • Financial structuring
• Regulatory oversight • Business development
• Market & economic analysis • Asset specifications &
• Portfolio management standards
• Capital allocation • Full lifecycle asset
• Asset financial & operating management
performance analysis • Asset data management
• Asset planning • Workload management
• Asset acquisition & • Asset financial and
monetization operating performance
analysis
• Asset strategy & plan
Service Provider
development
Responsibilities: • Asset full lifecycle
• Construction & maintenance financial & operational
project management data analysis
• Materials sourcing & inventory • Regulatory strategy &
management negotiation
• System engineering & design • Contract management
• Bargaining unit negotiations • Risk management
• Workforce scheduling & • Asset data requirements
deployment definition
• Work practice design & • Asset opportunity
development development & analysis
• Asset data input and collection • Industry Best Practices
• Workforce training
• Marketing & sales of services
• Competitor analysis
Slide 18
Case Study: LIPA Asset Management Concept (source: IEEE 2009)
MSA
Asset
AssetManagement
Management
Management
Asset Service
Owner Asset Manager Provider
LIPA
LIPA Risk
Management Impl Exe
Goals Strategy Plan
Assess Effectiveness
Goals ement cute
Customer
Satisfaction Data and Process Integration – CIM/IB/SOA
Financial Risk
RiskAssessment
Assessment
Technical Risk Risk Risk
Performance Status Drivers Tolerance
Regulatory
Assets & Processes (O&M&Planning) aspects
KRIs/Risk
KPIs Visualization Dynamic Criticality
FMEA Indicators
Slide 19
Some Foundational Relationships
of the IEC CIM for Asset Management
Document Organisation
Information Containers Such As Entities Performing One or More
Asset Catalogues, Trouble Tickets, Roles Such As Customer, Supplier,
Work Orders, etc. Manufacturer, Service Provider, etc.
Location
A Street Address, Coordinates Erp Person
For a Geographic or Schematic A Person Performing Roles Such
reference system, etc. Dispatcher, Field Operator, etc.
Power System Resource Activity Record

Electrical Network Role Used For
Used to Record Each State
Planning, Operations, etc.
change of CIM objects
Type Asset Asset Model Asset

Compatible Unit For Particular Model and Version Physical Plant Filling A Role
Design & Procurement of a Vendor's Product Such As A Transformer, Pole, etc.
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., 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 21
From the logical view to the physical asset view of the same object.
PowerSystemResource 0..n
Organisation
(from Core) (from TopLevel)
0..n
OrgPsrRole
0..n 0..n (from AssetBasics)
1..n
DocPsrRole OrgAssetRole
(from AssetBasics) (from AssetBasics)
AssetPsrRole
(f rom AssetBasics)
ErpInventory
(from ERP_Support)
0..1
+Documents DocAssetRole 0..n 0..n

0..n (from AssetBasics) 0..1
0..n
Document 0..n Asset
(from DocumentInheritance) (from AssetBasics)
0..1
0..1
AssetModel 0..n 0..1 TypeAsset FinancialProperties
(from AssetBasics) (from TypeAsset) (from AssetBasics)
Slide 22
• 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 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]
Slide 24
Case Study: Operations Model Capabilities (source: DistribuTECH2002)
AMS
DMS
Slide 25
PowerSystemResource
(from Core)
0..n
DocPsrRole
(from AssetBasics)
DocAssetRole
(from AssetBasics)
0..n
AssetListRole
Document 0..n 0..n Asset (from AssetBasics)
(from DocumentInheritance) (from AssetBasics)
0..n 0..n
Collecti on 0..n AssetList

Specification
(f rom AssetBasics) 0..n (from Collections) (f rom AssetBasics)
TypeAssetCatalogue AssetCatalogue
(from AssetBasics) (from AssetBasics)
0..1 1
0..n
AssetModel 0..n 0..1 TypeAsset

(from AssetBasics) (from TypeAsset)
0..n
0..1
AssetCatalogueItem
0..n (f rom AssetBasics)
Slide 26
• 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 27
IEC 61968-6: Maintenance & Construction
(Note: CD in development – paper being presented at Grid InterOp)
Maintenance and
Construction Business Functions Performed
(MC) – IEC 61968-6
• Maintain and Plan PM Programs
• Manage Inspection and Maintenance “Triggers”
Maintenance &
• Link Inspection orders to follow-up repair orders
Inspection (MAI)
• Gather “failure” data
• Initiate and Plan work orders

Construction • Manage material, equipment, and permit requests
WMS (CON) • Manage and Track Work (Workflow)
• Close Work and Support Performance Analysis
• Work Design and Cost Estimation

Design & • Compatible Unit based Graphical design
Estimate (DGN) • Generate Bill of Materials
• Assign crew based on work type and skills

Scheduling • Determine Schedule Date
& Dispatch (SCH) • Perform constraint-based “auto-scheduling”
• Gather actual costs and support cost

Field reconciliation
Recording (FRD) • Monitor work progress
• support financial closing with accounting systems
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, 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 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
Slide 30
Generic “TypeAssets” are used for Design
CostType 0..1
CUGroup
(f rom WorkClosing)
(f rom WorkStandards)
0..1 0..n
0..n 0..1
0..n
0..n
CompatibleUnit 0..n CUContractorItem
(from WorkDesign) (f rom WorkStandards)
0..n
0..n
0..n 0..n 0..n
0..n 0..n
Procedure
(f rom WorkInspectionMaintenance)
0..n 0..n
0..n 0..n
CUMaterialItem CULaborItem
(f rom WorkStandards)
CUAsset CUEquipmentItem (f rom WorkStandards)
(from WorkStandards) (from WorkStandards)
0..n
0..1
0..1
0..1
0..1
0..1
TypeMaterial
(f rom WorkStandards) TypeAsset
(from TypeAsset)
Slide 31
IEC 61968-3: Network Operations

– 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 32
An Example: Safety Document Classes
Organisation
(from TopLevel) OrgErpPersonRole
DocOrgRole
(from TopLevel)
(from TopLevel)
0..n
0..n
0..n
0..n
SafetyDocument Document ErpPerson
(from DocumentInheritance) (from ERP_Support)
(from Operational)
0..n
0..n 0..n
0..n
ActivityRecord
OperationalRestriction 0..n (from ActivityRecords)
(from Operational)
0..n
PowerSystemResource
(from Core)
0..n
0..1
ClearanceTag 1 ConductingEquipment Equipment PSRType
(from Outage)
(from Core) (from Core) (from Core)
0..n
Slide 33
Safety Document Message Type
Slide 34
IEC 61968-8: Customer Support
(Note: Update to second CD in Process)

– Trouble Ticket
– Failure Event
– Planned Outage Notification
– Call Back
– Compliance Event
– Outage History
– Service Extension Request
– ServiceRequest
– CustomerServiceAgreement
– Customer Billing
– Construction Billing
Slide 35
Aspects of Customer Accounts
Agreement
CustomerAccount (from TopLevel) Equipment ConductingEquipment
(from Consumers) (f rom Core) (f rom Core)
1..n 1 0..n
1 0..n 0..n
CustomerData CustomerAgreement 0..n ServiceLocation EnergyConsumer

(from Consumers) (f rom Wires)
(from Consumers) (from Locations)
0..n
1
0..1 0..1 0..n 0..n 0..1
1 0..n 0..n
0..1 0..n
Organisation ErpPerson ServiceKind SDPLocation 0..n ServiceDeliveryPoint
0..n (f rom Consumers) (from Locations)
(f rom TopLev el) (f rom ERP_Support) (from Metering)
0..n 0..n
1 0..n
0..n 0..n
0..n
Tariff PricingStructure 1 PowerQualityPricing
(from Consumers) (f rom Consumers) (f rom Consumers)
0..n 0..n 0..n
Slide 36
A Customer Account Message Type for AMI (IEC 61968-9)
Slide 37
IEC 61968-9
Reference
Model
Refer to
Margaret’s presentation
Agenda

– Messaging
Slide 39
NIST Conceptual Model

[Source: NIST InterimSlide
Roadmap]
40
User groups are a good source of help
Advisors
Operating
Board of Directors Officers
Audit
Committee
Executive Technical Oversight Technical

Help Desk
Committee Committee Publications
Marketing CIM Testing
Liaison 61850 Harmonization
Membership OpenSG
http://www.ucaiug.org/
Slide 42
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.
Slide 44
OpenSG Focus: Finding/Developing Best Practices &
Making Them into Vetted “Industry Best Practices”
Utility’s
Projects
- Design & • Local Utility Projects
Implementations
--------------- • Consortiums & User
Utility’s Groups like OpenSG
(business requirements) &
Architecture CIMug (optimization &
----------------------- implementation support)
Industry Best Practices
Interoperability Testing • Standards Development
--------------------------------- Organizations (SDOs) like
IEC TC57 Working Group
Industry Best Practices 14 for the IEC 61968 series
------------------------------------------ of standards, NAESB, IEEE,
Standards Conformance & et al.
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 enterprises (generally defined as third parties).
Case Study: Consumers Energy and AMI-Ent TF
Customer Distribution
Info. & Billing Management
HAN
Management
Outage
Revenue AMI Service
Management
Protection Manager
Enterprise Bus + Common Model & Service
AMI-
AMI-ENT
Demand
Customer
Response
Portal AMI Network
Management
Asset
Management
Third Party Meter
Meter Asset
Portal Data
Management
Management
Representative of AMI-ENT components, not all inclusive.
Slide 47
Case Study: AMI-Ent Service Identification
Slide 48
Case Study: AMI-Ent Inventory of CIM-Based Services
Supporting Use Cases for AMI-Enterprise
Use Case & Integration Functional Description of Operation Service Name Service Operation Service Service Provider Information Object
Scenario Requirement the Service Pattern Consumer (Inbound - WS) (normalized)
(Outbound)
B1-S1 REQ-B1004 MDUS receives the meter Created MeterReading CreatedMeterReading Head End MDUS MeterReading
reading results on
B1-S12 REQ-B1011 scheduled basis.meter
MDUS receives Created MeterReading CreatedMeterReading Field Tool MDUS MeterReading
reads
B1-S15 REQ-B1012 MDUS notifies meters with Created MeterSystemEvent CreatedMeterSystemEvent MDUS? MDUS MeterSystemEvent
reading problems
B1-S15 REQ-B1013 AMI Head End operator Created MeterServiceOrder CreatedMeterServiceOrder MDUS Head End MeterServiceOrder
receives meter service
orders
B1-S17 REQ-B1014 Request billing determinant Create BillingDeterminantRequest CreateBillingDeterminant CIS MDUS BillingDeterminant
B1-S17 REQ-B1014 Request billing determinant Created BillingDeterminant CreatedBillingDeterminant MDUS CIS BillingDeterminant
B1-S2 REQ-B1001 Head End receives the Create MeterReading CreateMeterReading TBD Head End MeterReading
request for a meter reading
B1-S2 REQ-B1002 on demand
MDUS receives a meter Created MeterReading CreatedMeterReading Head End MDUS MeterReading
reading on demand
B1-S2 REQ-B1003 A user or system receives Created MeterReading CreatedMeterReading MDUS TBD MeterReading
a meter reading on
demand
B1-S3 REQ-B1006 CIS receives meter event Created MeterSystemEvent CreatedMeterSystemEvent Head CIS MeterSystemEvent
End/MDUS
B1-S7 REQ-B1009 MDUS receives the request Create MeterReading CreateMeterReading Third Party MDUS MeterReading
for meter readings Portal
B1-S7 REQ-B1010 Third party receives the Created MeterReading CreatedMeterReading MDUS Third Party Portal MeterReading
meter readings
B1-S8 REQ-B1009 MDUS receives the request Create MeterReading CreateMeterReading Third Party MDUS MeterReading
for meter readings Portal
B1-S8 REQ-B1010 Third party receives the Created MeterReading CreatedMeterReading MDUS Third Party Portal MeterReading
meter readings
B2-S1 REQ-B2001 Send scheduled shut off Created ScheduledEvent CreatedScheduledEvent CIS Head End ScheduledEvent
notification
B2-S1 REQ-B2002 Send scheduled shut off Created ConnectDisconnect CreatedConnectDisconnect CIS Head End ConnectDisconnect
command
B2-S1 REQ-B2003 Send scheduled shut off Created CommonConfirmation CreatedCommonConfirmation Head End CIS CommonConfirmation
command confirmation
B2-S1 REQ-B2004 Send meter read (final) Created MeterReading CreatedMeterReading Head End MDUS MeterReading
B2-S2 REQ-B2005 Request AMI Meter status Create MeterStatusRequest CreateMeterStatus CIS Head End MeterStatus
Slide 49
Application View
Services Provided/Consumed by “Customer Information Management”
Service Operation Service Operation
CommonConfirmation CommonConfirmation ScheduledEvent Created ScheduledEvent

Created
MeterStatus MeterStatus ConnectDisconnect Create ConnectDisconnect
Created
HanAsset Created HANAsset MeterStatusRequest Create MeterStatusRequest
AMI Head End

AMI Head End LoadControlCommandRequest Create LoadControlCommandRequest
HANAsset Create HANAsset

BillingDeterminant BillingDeterminant
Created
ServiceToken Created ServiceToken
MeterStatus MeterStatus
Created
Changed
AMI Head End
MeterSystemEvent MeterSystemEvent AMI Head End
Created
Meter Data Management

Meter Data Management Create
BillingDeterminant BillingDeterminant
Change
MeterAssetRequest MeterAssetRequest
Create
MeterServiceOrderRequest MeterServiceOrderRequest

Customer Information Management

Customer Information Management
Service Consumers Service Providers / Consumers Service Providers

Slide 50
Technical View (Patterns)
Service SendMeterReading ReceiveMeterReading
CreatedMeterReading CreatedMeterReading
Operations
ChangedMeterReading ChangedMeterReading
CanceledMeterReading CanceledMeterReading
Native Native
A API or T S/C S/P Orchestration S/C S/P T API or B
Service Service
Application A Transparent ESB Application B
Guaranteed delivery within ESB,

Other interested parties……
plus internal routing……
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 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 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]
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 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 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!
Slide 54

CIM For Enterprise Integration (IEC) 61968

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

CIM For Enterprise Integration (IEC) 61968

Încărcat de

Drepturi de autor:

Formate disponibile

CIM for Enterprise Integration

For further information, contact:

• CIM for enterprise integration (IEC 61968)

Wires Integration Anarchy!

OMS GIS CIS

WMS DMS AMR

Fault Management Dispatcher Training General inventory Scheduling

Operational Feedback Asset Investment Power Import Sched. Field

Application Integration Infrastructure

Network Extension Customer Meter Reading & Control External to DMS

Semantically Consistent ESB

DMS Information Flow Design

• CIM for enterprise integration (IEC 61968)

• A verb to identify the

[source: IEC 61968-1]

Verbs Meaning Message Body

[source: IEC 61968-1]

class part9: MeterReadings message type

[source: IEC 61968-1]

class part9: MeterReadings message type

+ IntervalReadings Measurement Value + IntervalReading

+ MeterReading + IntervalBlocks + IntervalBlocks

0..1 0..* Metering:: 0..*

• CIM for enterprise integration (IEC 61968)

Asset Owner Asset Manager

Power System Resource Activity Record

Type Asset Asset Model Asset

• Network Data Set

+Documents DocAssetRole 0..n 0..n

Asset data sent in XML

Adapter Subscribe to Asset data

Collecti on 0..n AssetList

AssetModel 0..n 0..1 TypeAsset

• Initiate and Plan work orders

• Work Design and Cost Estimation

• Assign crew based on work type and skills

• Gather actual costs and support cost

• Work is created any time a person is required to

• Current Message Types:

• Current Message Types:

• Current Message Types:

CustomerData CustomerAgreement 0..n ServiceLocation EnergyConsumer

• CIM for enterprise integration (IEC 61968)

CIM Users Group: CIM for Enterprise Integration

Executive Technical Oversight Technical

Marketing CIM Testing

Liaison 61850 Harmonization

• Standard building blocks are defined by standards

Enterprise Bus + Common Model & Service

Representative of AMI-ENT components, not all inclusive.

Service Operation Service Operation

CommonConfirmation CommonConfirmation ScheduledEvent Created ScheduledEvent

AMI Head End

HANAsset Create HANAsset

Meter Data Management

Meter Data Management

Customer Information Management

Service Consumers Service Providers / Consumers Service Providers

Service SendMeterReading ReceiveMeterReading

Application A Transparent ESB Application B

Guaranteed delivery within ESB,

– Concern 1: the CIM is too large

– Concern 4: The CIM is too abstract