Transcript CIM for Enterprise Integration (IEC 61968 Series)

CIM for Enterprise Integration
for the
CIM University, CIM Users Group
in Charlotte, NC
November 10, 2009
For further information, contact:
Greg Robinson ([email protected]),
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
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
Slide 2
Key Premise: The Common Language Should Provide
Relevant Information To A User Regardless of Source
Engineering
Concerns
Operations
Concerns
Materials
Management
Concerns
Protection
Concerns
CIM Users Group: CIM for Enterprise Integration
Construction
Concerns
Maintenance
Concerns
Slide 3
This is Not a Good Practice For Wires Integration;
It’s Not Good For Data Integration Either!
Wires Integration Anarchy!
CIM Users Group: CIM for Enterprise Integration
Slide 4
Goal: Interface Standards Should Be Based on Common Semantics
(e.g., CIM) to Avoid Adding to ‘Integration Anarchy’
OMS
GIS
CIS
DMS
AMR
Integration Infrastructure
WMS
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 5
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
All IEC 61968 Activity Diagrams and Sequence Diagrams are organized by the IRM
Business Functions
External To Distribution
Management
Distribution Management
Business Functions
(NO)
Network
Operation
Interface
Standard: Part 3
(AM)
Records &
Asset
Management
(OP)
Operational
Planning &
Optimization
(MC)
Maintenance
&
Construction
Interface
Standard: Part 4
Interface
Standard: Part 5
Interface
Standard: Part 6
(EMS)
Energy
Management &
Energy Trading
Interface
Standard: Part 10
(RET)
Retail
Interface
Standard: Part 10
(SC)
Supply
Chain and
Logistics
Interface
Standard: Part 10
IEC 61968 Compliant Middleware Services
Interface
Standard: Part 7
Interface
Standard: Part 8
(NE)
Network
Extension
Planning
(CS)
Customer
Support
Interface
Standard: Part 9
(MR)
Meter
Reading &
Control
Electric Distribution Network
Planning, Constructing,
Maintaining, and Operating
Interface
Standard: Part 10
(ACT)
Customer
Account
Management
Interface
Standard: Part 10
Interface
Standard: Part 10
Interface
Standard: Part 10
(FIN)
Financial
(PRM)
Premises
(HR)
Human
Resources
Generation and Transmission Management,
Enterprise Resource Planning, Supply Chain, and
General Corporate Services
CIM Users Group: CIM for Enterprise Integration
Slide 6
Key Concept: Incremental Integration
- in Step With Business Needs
GIS
OMS
CIS
OR
TT
IEC 61968
IRM Interface
Semantically Consistent ESB
AMR
WMS
DMS
Information Flow Design
Trouble Ticket
Outage Record
CIM Users Group: CIM for Enterprise Integration
DMS
OMS
CIS
TT
OR
Slide 7
Key Concept:
Replace Large Monolithic Applications ‘a Chunk at a Time’
Other Apps
Other Apps
Other Apps
Field
Recording
Maintenance &
Inspection
Construction
Work
Scheduling
Design
MDI/CIM Messages
WMS
CIM Users Group: CIM for Enterprise Integration
Slide 8
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
Slide 9
IEC 61968-11: CIM Extension for Distribution
IEC61968CIMVersion
+
+
date: AbsoluteDateTime [0..1] = 2009- 04- 01
version: String [0..1] = IEC61968CIM10v23
Common
Assets
AssetModels
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)
Part 4
Work
Part 6
Customers
Part 8
Metering
LoadControl
PaymentMetering
Part 9
CIM Users Group: CIM for Enterprise Integration
Slide 10
Priorities:
WG14 Roadmap priorities by NC
CAN
CH
DE
FR
UK
US
61968-9
61968-11
61968-3
61968-4
61968-1
61968-13
Security
61968-1-2
61968-6
61968-10
61968-14-1
3
3
2
2
3
3
1
3
2
2
3
3
3
3
3
3
3
3
1
1
3
3
3
3
3
3
3
3
1
3
3
3
3
3
3
2
2
2
3
3
3
3
3
2
1
3
3
3
3
3
2
3
3
3
3
1
1
1
2
3
61968-14-2
61968-2
61968-5
61968-7
DER
61968-1-1
PHEV/PEV
3
3
2
2
1
3
1
1
2
2
2
2
1
2
1
2
2
2
1
1
2
1
1
2
2
2
2
1
2
1
1
1
3
1
3
2
2
61968-8
2
1
1
1
1
2
HAN
1
1
1
1
current
pending
postponed
3
ZA
3
3
3
3
NC
Positio
ns
6
6
7
7
6
6
5
6
7
1
6
Averag
e
Priority
3.0
3.0
2.9
2.9
2.8
2.8
2.4
2.2
2.1
2.0
1.8
6
5
5
5
5
6
5
1.8
1.8
1.8
1.8
1.8
1.7
1.6
7
1.6
5
1.4
comment
Metering
DCIM
Operations (DMS/OMS)
Asset & record mgmt.
Reference architecture
CDPSM
Naming/Design rules
Work mgmt.
n/a
MultiSpeak
MultiSpeak
Glossary
Operations Planning
Extensions Planning
Integration profile
Customers (mgmt,
billing)
non-modelling
[source: Tanja Kostic]
CIM Users Group: CIM for Enterprise Integration
Slide 11
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 (GISDMS/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
Slide 12
CIM model and Part 11 evolution:
Normative vs. informative
•
•
Introduced in January 2009
WG14 package split to normative and informative (unstable, work-inprogress)
– 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
Slide 13
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 IEC61970-301
• 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
Slide 14
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 61970-301 Ed.4 and FDIS of 61968-11 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
Slide 15
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
Slide 16
IEC 61968 Basic Message Structure
CIM Users Group: CIM for Enterprise Integration
Slide 17
Message Header
CIM Users Group: CIM for Enterprise Integration
Slide 18
Message Types Are Created By Combining IEC 61968 Verbs With
Information Exchange Topics, Referred To As Nouns
Verbs
Meaning
CREATE
The CREATE verb is used to publish a request to
the master system to create a new document.
CHANGE
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.
CANCEL
CLOSE
DELETE
GET
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)
Header information +
message content key(s)
Header information +
message content key(s)
Header information +
message content key(s)
One or more document
reference codes +
Key(s)
Slide 19
Verbs
CREATED
CHANGED
CLOSED
CANCELED
SHOW
REPLY
SUBSCRIBE
UNSUBSCRIB
E
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
All sections (key(s) +
changed content)
Header information +
message content key(s)
Header information +
message content key(s)
(IEC 61968
Verbs - continued)
All sections
Header information +
message content key(s)
+ confirmation
information +
alternatives (optional)
Header information +
message content key(s)
Header information +
message content key(s)
CIM Users Group: CIM for Enterprise Integration
Slide 20
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
Slide 21
“End Device Control” Sample XML
<?xml version="1.0" encoding="UTF-8"?>
<!--Sample XML file generated by XMLSpy v2009 sp1 (http://www.altova.com)-->
<m:EndDeviceControls xsi:schemaLocation="http://iec.ch/TC57/2009/EndDeviceControls#
EndDeviceControls.xsd" xmlns:m="http://iec.ch/TC57/2009/EndDeviceControls#"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<m:EndDeviceControl>
<m:mRID>53185955_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>2001-12-17T10:30:47Z</m:end>
<m:start>2001-12-17T09:30:47Z</m:start>
</m:scheduledInterval>
</m:EndDeviceControl>
</m:EndDeviceControls>
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
Slide 23
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
Slide 24
ChangeSet
(from DataSets)
0..n
...
The NetworkDataSet is organized by logical
Role (vs. physical asset) and may represent
various views, such as as-built, nominal,
operational, study, etc.
NetworkDataSet
(from DataSets)
ChangeItem
(from DataSets)
0..n
0..1
0..1
0..n
0..n
0..1
0..n
PowerSystemResource
0..n
0..n
0..n
(f rom Core)
LoadDataSet
LandBase
(f rom DataSets)
(f rom DataSets)
0..1
1..n
0..n
Asset
0..n
0..n
(f rom AssetBasics)
0..n
0..n
Circuit
CircuitSection
0..n
(f rom DataSets)
(f rom DataSets)
1..n
0..n
Everything from the IEC 61970 Wires
Package may be included. Connectivity
Is based on IEC 61970 Topology
CIM Users Group: CIM for Enterprise Integration
Slide 25
From the logical view to the physical asset view of the same object.
PowerSystemResource
(from Core)
Organisation
0..n
(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
0..n
DocAssetRole
0..n
0..n
0..1
(from AssetBasics)
0..n
Document
Asset
0..n
(from DocumentInheritance)
(from AssetBasics)
0..1
0..1
AssetModel
(from AssetBasics)
0..n
0..1
TypeAsset
FinancialProperties
(from TypeAsset)
(from AssetBasics)
CIM Users Group: CIM for Enterprise Integration
Slide 26
IEC 61968-4: Records and Asset Management
• 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 27
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 19136 - Geographic information - Geography Markup
Language (GML)
CIM Users Group: CIM for Enterprise Integration
Slide 28
Presentation of Real World Objects – Key Classes
Location
GmlDiagramObject
(from Locations)
(from GML_Support)
1
0..1
0..n
0..n
GmlPointGeometry
(f rom GML_Support)
GmlLineGeometry
0..10..1
0..1
(f rom GML_Support)
0..1
Diagram
GmlPosition
GmlPolygonGeometry
(from Presentation)
(from GML_Support)
(f rom GML_Support)
0..n
Map
(f rom Presentation)
0..n
1
0..1
0..n
1..n
GmlTextSymbol
GmlCoordinateSystem
(f rom GML_Support)
(from GML_Support)
0..n
0..n
0..n
0..n
GmlRasterSymbol
GmlPointSymbol
GmlLineSymbol
GmlPolygonSymbol
(f rom GML_Support)
(f rom GML_Support)
(f rom GML_Support)
(f rom GML_Support)
CIM Users Group: CIM for Enterprise Integration
Slide 29
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 30
Case Study: Operations Model Capabilities (source: DistribuTECH2002)
AMS
DMS
CIM Users Group: CIM for Enterprise Integration
Slide 31
Case Study: LIPA Asset Management and Organization
Asset Owner
Responsibilities:
(source: IEEE 2009)
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
•
•
•
•
•
•
•
•
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
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 32
Case Study: LIPA Asset Management Concept (source: IEEE 2009)
MSA
Asset
Management
AssetManagement
Management
Asset
Owner
Customer
Satisfaction
Risk
Management
Strategy Plan
Exe
cute
Data and Process Integration – CIM/IB/SOA
Financial
Technical
Performance
Impl
ement
Service
Provider
Risk
RiskAssessment
Assessment
Risk
Status
Risk
Drivers
Risk
Tolerance
Assess Effectiveness
LIPA
LIPA
Goals
Goals
Asset Manager
Regulatory
Assets & Processes (O&M&Planning) aspects
KPIs
Visualization Dynamic Criticality
FMEA
CIM Users Group: CIM for Enterprise Integration
KRIs/Risk
Indicators
Slide 33
Some Foundational Relationships
of the IEC CIM for Asset Management
Document
Organisation
Information Containers Such As
Asset Catalogues, Trouble Tickets,
Work Orders, etc.
Entities Performing One or More
Roles Such As Customer, Supplier,
Manufacturer, Service Provider, etc.
Location
Erp Person
A Street Address, Coordinates
For a Geographic or Schematic
reference system, etc.
A Person Performing Roles Such
Dispatcher, Field Operator, etc.
Power System Resource
Activity Record
Electrical Network Role Used For
Planning, Operations, etc.
Used to Record Each State
change of CIM objects
Type Asset
Asset Model
Asset
Compatible Unit For
Design & Procurement
Particular Model and Version
of a Vendor's Product
Physical Plant Filling A Role
Such As A Transformer, Pole, etc.
CIM Users Group: CIM for Enterprise Integration
Slide 34
PowerSystemResource
(from Core)
0..n
DocPsrRole
(from AssetBasics)
DocAssetRole
(from AssetBasics)
0..n
Document
AssetListRole
Asset
0..n
0..n
(from AssetBasics)
(from AssetBasics)
(from DocumentInheritance)
0..n
0..n
Collecti on
Specification
0..n
(f rom AssetBasics)
(from Collections)
0..n
AssetList
(f rom AssetBasics)
TypeAssetCatalogue
AssetCatalogue
(from AssetBasics)
(from AssetBasics)
1
0..1
0..n
AssetModel
0..n
(from AssetBasics)
0..1
TypeAsset
(from TypeAsset)
0..n
0..1
AssetCatalogueItem
0..n
CIM Users Group: CIM for Enterprise Integration
(f rom AssetBasics)
Slide 35
IEC 61968-4: Records and Asset Management
• 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 36
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 37
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 38
Generic “TypeAssets” are used for Design
CostType
CUGroup
(f rom WorkStandards)
0..1
0..n
0..1
(f rom WorkClosing)
0..n
0..1
0..n
0..n
CompatibleUnit
CUContractorItem
0..n
(from WorkDesign)
0..n
0..n
0..n
(f rom WorkStandards)
0..n
0..n
0..n
0..n
Procedure
(f rom WorkInspectionMaintenance)
0..n
CUMaterialItem
(f rom WorkStandards)
0..n
0..n
0..n
CUAsset
CUEquipmentItem
(from WorkStandards)
(from WorkStandards)
CULaborItem
(f rom WorkStandards)
0..n
0..1
0..1
TypeMaterial
(f rom WorkStandards)
0..1
0..1
0..1
TypeAsset
(from TypeAsset)
CIM Users Group: CIM for Enterprise Integration
Slide 39
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
Slide 40
An Example: Safety Document Classes
Organisation
OrgErpPersonRole
(from TopLevel)
DocOrgRole
(from TopLevel)
(from TopLevel)
0..n
0..n
0..n
0..n
SafetyDocument
Document
ErpPerson
(from Operational)
(from DocumentInheritance)
(from ERP_Support)
0..n
0..n
0..n
0..n
OperationalRestriction
0..n
(from Operational)
ActivityRecord
(from ActivityRecords)
0..n
PowerSystemResource
(from Core)
0..n
0..1
ClearanceTag
1
(from Outage)
0..n
ConductingEquipment
Equipment
PSRType
(from Core)
(from Core)
(from Core)
CIM Users Group: CIM for Enterprise Integration
Slide 41
Safety Document Message Type
CIM Users Group: CIM for Enterprise Integration
Slide 42
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
Slide 43
Aspects of Customer Accounts
Agreement
CustomerAccount
(from TopLevel)
Equipment
ConductingEquipment
(f rom Core)
(f rom Core)
(from Consumers)
1..n
1
0..n
0..n
0..n
1
CustomerData
CustomerAgreement
(from Consumers)
(from Consumers)
0..n
0..n
ServiceLocation
EnergyConsumer
(from Locations)
(f rom Wires)
1
0..1
0..n
(f rom TopLev el)
0..n
0..1
0..n
0..n
1
0..n
0..1
Organisation
0..n
0..1
ErpPerson
(f rom ERP_Support)
ServiceKind
SDPLocation
(f rom Consumers)
(from Locations)
0..n
0..n
ServiceDeliveryPoint
(from Metering)
0..n
1
0..n
0..n 0..n
PricingStructure
Tariff
(from Consumers)
0..n
0..n
PowerQualityPricing
1
(f rom Consumers)
0..n
CIM Users Group: CIM for Enterprise Integration
(f rom Consumers)
0..n
Slide 44
A Customer Account Message Type for AMI (IEC 61968-9)
CIM Users Group: CIM for Enterprise Integration
Slide 45
IEC 61968-9
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
Slide 47
Metering Inheritance Package
CIM Users Group: CIM for Enterprise Integration
Slide 48
Customer Overview – from a 61968-9 perspective
CIM Users Group: CIM for Enterprise Integration
Slide 49
Document
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.
Customers::
PricingStructure
+ PricingStructures
0..*
+ Tariffs
0..*
Document
Customers::
Tariff
+ Tariffs
0..*
+ TariffProfiles
0..*
Document
+ TariffProfiles
0..*
TariffProfile
+
+ TariffProfiles
tariffCycle: String [0..1] 0..*
+ TimeTariffIntervals
+ ConsumptionTariffIntervals
0..*
0..*
TimeTariffInterval
+
+
ConsumptionTariffInterval
sequenceNumber: Integer [0..1]
startDateTime: AbsoluteDateTime [0..1]
0..*
+ TimeTariffIntervals
+
+
sequenceNumber: Integer [0..1]
startValue: RealEnergy [0..1]
0..*
+ ConsumptionTariffIntervals
I dent ifiedObject
Charge
+ Charges
0..* +
+
+
+ Charges
kind: ChargeKind [0..1]
0..*
fixedPortion: AccountingUnit [0..1]
variablePortion: PerCent [0..1]
+ ParentCharge
0..1
CIM Users Group: CIM for Enterprise Integration
+ ChildCharges
0..*
Slide 50
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
Slide 51
CIM Users Group: CIM for Enterprise Integration
Slide 52
CIM Users Group: CIM for Enterprise Integration
Slide 53
Example of Meter Reading Schedules and Readings
CIM Users Group: CIM for Enterprise Integration
Slide 54
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
Slide 55
CIM Users Group: CIM for Enterprise Integration
Slide 57
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 61968-9 Annex for details
CIM Users Group: CIM for Enterprise Integration
Slide 58
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
Slide 60
Meter System Events (page 1)
CIM Users Group: CIM for Enterprise Integration
Slide 61
Meter System Events (page 2)
CIM Users Group: CIM for Enterprise Integration
Slide 62
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
name/mRID
(which is let’s say an
electricity
meter)
End-device type
ServiceDeliveryPoint.serviceType
Attribute
using this connection
Port Number
EndDeviceAsset.DeviceFunction.ComPort
Attribute
Upstream CommAsset
EndDeviceAsset.DeviceFunction.
name/mRID
at this location
ServiceDeliveryPoint
ServiceDeliveryPoint.name
name/mRID
for this account
Account ID
CustomerAccount.name
name/mRID
and this customer
Customer ID
CustomerAccount.Customer.name
name/mRID
In this utility
Business Unit
Commencing at this
date
Installation date
ActivityRecord.statusDateTime
Attribute
Because
“In-Service”
ActivityRecord.status
Attribute
CIM Users Group: CIM for Enterprise Integration
Slide 64
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
Slide 65
GWAC Stack – Levels of Interoperability
[Source: GridWise Architectural Council Interoperability Context Setting Framework]
CIM Users Group: CIM for Enterprise Integration
Slide 66
NIST Conceptual Model
CIM Users Group: CIM for Enterprise Integration
67
[Source: NIST InterimSlide
Roadmap]
Interoperability Layers
CIM Users Group: CIM for Enterprise Integration
Slide 69
(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 70
CIM
Users
Group:
CIM
for
Enterprise
Integration
communicate with other businesses or enterprises (generally defined as third parties).
Case Study: Consumers Energy and AMI-Ent TF
Customer
Info. & Billing
Outage
Management
Distribution
Management
Revenue
Protection
HAN
Management
AMI Service
Manager
Enterprise Bus + Common Model & Service
AMIAMI-ENT
Demand
Response
Management
Customer
Portal
Third Party
Portal
Meter
Data
Management
AMI Network
Asset
Management
Meter Asset
Management
Representative of AMI-ENT components, not all inclusive.
CIM Users Group: CIM for Enterprise Integration
Slide 71
Case Study: AMI-Ent Use Cases
CIM Users Group: CIM for Enterprise Integration
Slide 72
Case Study: AMI-Ent Service Identification
CIM Users Group: CIM for Enterprise Integration
Slide 73
Case Study: AMI-Ent Inventory of 142 CIM-Based Services
Supporting Use Cases for AMI-Enterprise
Use Case & Integration
Scenario
Requirement
Functional Description of Operation
the Service
Pattern
Service Name
Service Operation
Service Provider Information Object
(Inbound - WS) (normalized)
CreatedMeterReading
Service
Consumer
(Outbound)
Head End
B1-S1
REQ-B1004
MeterReading
B1-S12
REQ-B1011
B1-S15
REQ-B1012
MDUS receives the meter Created
reading results on
scheduled
basis.meter
MDUS
receives
Created
reads
MDUS notifies meters with Created
reading problems
MDUS
MeterReading
MeterReading
CreatedMeterReading
Field Tool
MDUS
MeterReading
MeterSystemEvent
CreatedMeterSystemEvent
MDUS?
MDUS
MeterSystemEvent
B1-S15
REQ-B1013
MeterServiceOrder
CreatedMeterServiceOrder
MDUS
Head End
MeterServiceOrder
REQ-B1014
AMI Head End operator
Created
receives meter service
orders
Request billing determinant Create
B1-S17
BillingDeterminantRequest
CreateBillingDeterminant
CIS
MDUS
BillingDeterminant
B1-S17
REQ-B1014
Request billing determinant Created
BillingDeterminant
CreatedBillingDeterminant
MDUS
CIS
BillingDeterminant
B1-S2
REQ-B1001
MeterReading
CreateMeterReading
TBD
Head End
MeterReading
B1-S2
REQ-B1002
Head End receives the
Create
request for a meter reading
on
demand
MDUS
receives a meter
Created
reading on demand
MeterReading
CreatedMeterReading
Head End
MDUS
MeterReading
B1-S2
REQ-B1003
Created
MeterReading
CreatedMeterReading
MDUS
TBD
MeterReading
B1-S3
REQ-B1006
A user or system receives
a meter reading on
demand
CIS receives meter event
Created
MeterSystemEvent
CreatedMeterSystemEvent
CIS
MeterSystemEvent
B1-S7
REQ-B1009
MDUS receives the request Create
for meter readings
MeterReading
CreateMeterReading
Head
End/MDUS
Third Party
Portal
MDUS
MeterReading
B1-S7
REQ-B1010
Third party receives the
meter readings
MeterReading
CreatedMeterReading
MDUS
Third Party Portal MeterReading
B1-S8
REQ-B1009
MDUS receives the request Create
for meter readings
MeterReading
CreateMeterReading
Third Party
Portal
MDUS
B1-S8
REQ-B1010
Third party receives the
meter readings
Created
MeterReading
CreatedMeterReading
MDUS
Third Party Portal MeterReading
B2-S1
REQ-B2001
Created
ScheduledEvent
CreatedScheduledEvent
CIS
Head End
ScheduledEvent
B2-S1
REQ-B2002
Created
ConnectDisconnect
CreatedConnectDisconnect
CIS
Head End
ConnectDisconnect
B2-S1
REQ-B2003
Send scheduled shut off
notification
Send scheduled shut off
command
Send scheduled shut off
command confirmation
Created
CommonConfirmation
CreatedCommonConfirmation
Head End
CIS
CommonConfirmation
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
Created
CIM Users Group: CIM for Enterprise Integration
MeterReading
Slide 74
Status/Plans:
1) Verified applicable XSDs are
compliant with IEC 61968-9
2) Submitted to CIM
InterOperability Testing; TBD
for when it will be included
(Margaret)
3) Proposed requirements and
extensions being submitted
to WG14 for consideration.
http://osgug.ucaiug.org/sgsystems/Pages/Voting%20Ballots.aspx
CIM Users Group: CIM for Enterprise Integration
Slide 75
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
s
tion
lica
p
Ap
Ot
h
Ga er Pr
(In tewa emis
ter
e
ne y
t)
Ce
rtif
ied
DG
Ce
tive
rtif
ied
rac
e
t
n
Hy Plu
I
y
bri g-In
lit
i
t
d
Ad
rU
e
v
m
an
u
ce
ns
dI
Co
HD
Lo
ad
Co
ntr
ol
PC
T
n
atio
nic
u
m
om
d C nel
e
r
cu han
C
Se
lity
i
t
U R
No eve
n-e nu
lec e G
tric ra
Me de
Re
ter
ve
Ele nu
e
ctr
ic M Gra
ete de
r
Uti
lity AM
Ow I G
ne atew
da
nd ay
Op
era
ted
AM
IB
ac
kh
au
lN
etw
ork
ns
atio
c
i
l
p
Ap
lity
Uti
P Ce
Uti rem rtifie
lity ise
d
A
E
Ga pplic MS
tew ati
ay on
(e. HA
g.,
Se Cont
t T rol
op ler
Bo
x)
Sm
art
Ap
plia
nc
e
Lig
htin
gC
on
tro
l
Ho
me
Ca Healt
h
re
Ho
me
Se
cu
rity
r
me
nsu
Co
s
tion
lica
p
Ap
t
as
dc gnal)
a
o
i
Br e s
blic ric
Pu .g,., p
y
e
lit
Uti nel (
an
h
C
CIM Users Group: CIM for Enterprise Integration
Slide 76
Distributed Energy Resources - Collaboration between NIST,
UCA, ZigBee, and IEC
Discrete Metering,
Incentive Programs, and
Demand Response for
PEVs
© Copyright 2008, Southern California
Edison
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
Slide 77
Future State- PHEV Connection (120VAC) &
Communication Scenario B
[source: Jose A. Salazar, SCE]
CIM Users Group: CIM for Enterprise Integration
Slide 78
Future State- Battery EV w/ PLC Connection & Communication
Scenario A
[source: Jose A. Salazar, SCE]
CIM Users Group: CIM for Enterprise Integration
Slide 79
OpenSG’s OpenADE - Automated Data Exchange –
Collaboration among NIST, UCA and IEC
Third Parties
Energy
Usage
Energy
Management
AMI
AMI&&
Internet
Internet
Utilities
Consumers
Energy
Delivery and Management
The Changing Dynamics of Energy Services
CIM Users Group: CIM for Enterprise Integration
Slide 80
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
CIM Users Group: CIM for Enterprise Integration
81
Slide 81
OpenSG’s OpenADR – Automated Demand Response –
Collaboration among NAESB, NIST, UCA, OASIS, ZigBee, and IEC
OpenADR
Message
OpenADR
Message
LOAD
Utility/ISO
EMCS
Utility/ISO
Facility
Facility
Direct Load Control,
(not OpenADR
Messages)
Facility
Proprietary
Communications
OpenADR
Message
LOADS
OpenADR
Message
Facility
Utility/ISO
Utility/ISO
Intermediary
Third Party
Service Provider
Facility
CIM Users Group: CIM for Enterprise Integration
Slide 82
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
Slide 83