Académique Documents
Professionnel Documents
Culture Documents
CIM University
Introduction to CIM
And Its Role in the Utility Enterprise
Data Preparation, Exchange, Integration,
and Enterprise Information Management
Presentation Contents
Background
What is the CIM
How the CIM is used in the Utility Enterprise
As a semantic model for information exchange
CIM History
1992 Unified Information turned over a data model based on the EPRI OTS to
the CCAPI Task Force with the understanding it would be turned into an industry
standard model
1993 to 1996 - The CCAPI task force expanded the data model with a primary goal
of enabling use of plug compatible applications to help protect utility investment in
applications
1996 The CIM was turned over to IEC Technical Committee 57, Working Group
13&14, where it is advancing through the standards process. It covers both electric
utility transmission and distribution business operations
Converted to UML and initially maintained in Rational Rose
Role of CIM
Load Area
Belongs
To
Member
Of
Operates
Owns
Operates
Connects
To
Connects
To
Generator
AC Line
Connects
To
Load
Substation
Model Mapping
Model Mapping
Application 1
Application 2
SISCO SYSTEMS
VENDOR
HELP!
AM/FM/GIS
Asset
Planning
Protection
SCADA
Risk
Analysis
Work Mgmt
Historian
The CIM
Outage
Management
Property
Mgmt
Customer
Information
Compliance
HR
Network
Management
Network
Planning
Maintenance
& Inspection
Financial
Contract
Management
Engineering
Concerns
Operations
Concerns
Materials
Management
Concerns
Protection
Concerns
Construction
Concerns
Maintenance
Concerns
10
Field Name
Spatial Location
Version
Physical Connectivity
Load Projections
Capacity Requirements
Compatible Unit
Equipment Ratings
Asset Identifier
Compatible Unit
Equipment Manufacturer/Model
Serial Number
Location
Manufacturer Specifications
Construction Concerns
Lifecycle information regarding when
and how to install equipment:
Field Name
Location
Equipment Manufacturer/Model
Compatible Unit
Equipment Ratings
Work Order
Work Design
Permits
Manufacturer Specifications
Safety Requirements
11
Operations Concerns
Real-time condition of equipment and
electrical network necessary to
maintain reliable network operation:
Field Name
Electrical Connectivity
Equipment Status
Clearances
Equipment Faults
Weather Measurements
Operational Restrictions
Protection Concerns
Setting and configuring relays based
on equipment and network protection
requirements:
Field Name
Schematics
Electrical Connectivity
Maximum Capacity
Zones Of Protection
Equipment Status
Clearances
Network Measurements
(voltage, current, frequency,
transients)
Equipment Faults
Maintenance Concerns
Lifecycle information regarding when
and how equipment is maintained:
Field Name
Location
Equipment Manufacturer/Model
Equipment Ratings
Routine Maintenance
Equipment Condition
Inspection Schedule
Maintenance Budget
Safety Requirements
12
Service Connection
Request
Blah, Blah, Blah,
Organization,
Blah, Blah, Blah
Work
Blah, Blah, Blah,
Organization,
Blah, Blah, Blah
Asset Catalog
Planned Outage
Crew
Blah, Blah, Blah,
Organization,
Blah, Blah, Blah
Maintenance
Blah, Blah, Blah,
Organization,
Blah, Blah, Blah
Switching Schedule
Blah, Blah, Blah,
Organization,
Blah, Blah, Blah
Meter Reading
Load Control
Blah, Blah, Blah,
Organization,
Blah, Blah, Blah
For example, in each of the message exchanges depicted above, the same Organization is referenced
for different reasons. There should be NO inconsistencies about this Organization in them!
13
Risk
Management
Program Mgmt.
Load Forecast
Budget
Asset
Portfolios
Work Mgmt.
Reliability
Analysis
SRCM
Executive
Dashboard
Network
Analysis
Portal
Facility I&M
Financial
Management
GIS
CRM
IVR
Customer Management
Asset Owner
OMS
Metering
eBusiness
Supply Chain
Management
Contract
Management
Asset Repository
CIS
Equip./Fleet
Management
Contract Mgmt.
Revenue
Regulatory
Reporting
Resource
Scheduling &
Planning
EMS
SCADA
DMS
SA/DA
Asset Operations
Asset Manager
[source: DistribuTECH 2003 paper by Zhou & Robinson]
Mobile
Workforce
Mgmt.
Work
Collaboration
& Reporting
Work
Design
Service Provider
14
15
How is it used?
Before making mappings, a model (or an ontology) of a given business
domain is defined.
The model is expressed in a knowledge representation language and it
contains business concepts, relationships between them and a set of
rules.
By organizing knowledge in a discrete layer for use by information
systems, semantic models enable communication between computer
systems in a way that is independent of the individual system
technologies, information architectures and applications.
Compared to one-to-one mappings, mapping data sources to a common
semantic model offer a much more scaleable and maintainable way to
manage and integrate enterprise data.
16
Web Services
Business Intelligence
Integration Bus
ETL
DW
Common
Language
Generic
Services
Semantic
Model
Metadata
Apps.
17
Decoupled Information
Exchange
CIM
X.1
X.2
X.3
X.4
X.5
CIM
X.1
X.2
X.3
X.4
X.5
App
B.1
B.2
Subscriber
Subscribers:
Several Application Adapters Receive The Same Message
Each Adapter:
Parses Message, Pulling Out Data Needed By Application
Transforms Data (if necessary) to Local Application Format
Passes Data To Local Application And/Or Database
Through Most Appropriate Means
App
A.1
A.4
A.5
Subscriber
Outage
Reporting
Grid
Wires
Model
DAC
Dist
Wires
Model
EMS
OMS
CIM
X.1
X.2
X.3
X.4
X.5
App
C.1
Subscriber
C.3
C.4
VRU
Distribution
Automation
CIS
Event History
CIM
X.1
X.2
X.3
X.4
X.5
AM/FM/GIS
Subscriber
Human
Resources
App
Y.1
Y.2
Y.3
Y.4
Y.5
CIM
X.1
X.2
X.3
X.4
X.5
Publisher
Work
Management
Substation
Automation
...
Data
Warehouse
Publishers:
One Application Connector:
Obtains Data From Application And/Or Database
Transforms Data (if necessary) to the Common
Language (a Canonical Data Model)
Puts Data Into Message Template
Publishes The Message (Fires & Forgets)
18
18
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
B u s in e s s F u n c tio n s
E x te rn a l T o D is trib u tio n
M anagem ent
D is tr ib u tio n M a n a g e m e n t
B u s in e s s F u n c tio n s
(N O )
N e tw o rk
O p e r a tio n
In te r f a c e
S ta n d a rd : P a rt 3
(A M )
R e c o rd s &
A sset
M anagem ent
(O P )
O p e r a tio n a l
P la n n in g &
O p tim iz a tio n
(M C )
M a in t e n a n c e
&
C o n s tr u c tio n
In te r f a c e
S ta n d a rd : P a rt 4
In t e r f a c e
S ta n d a rd : P a rt 5
In t e r f a c e
S ta n d a rd : P a rt 6
(E M S )
E n e rg y
M anagem ent &
E n e r g y T r a d in g
In t e r f a c e
S ta n d a rd : P a rt 1 0
(R E T )
R e ta il
In te rf a c e
S ta n d a rd : P a rt 1 0
(S C )
S u p p ly
C h a in a n d
L o g is tic s
In te rf a c e
S ta n d a rd : P a rt 1 0
I E C 6 1 9 6 8 C o m p li a n t M i d d l e w a r e S e r v i c e s
In te r f a c e
S ta n d a rd : P a rt 7
In te r f a c e
S ta n d a rd : P a rt 8
In t e r f a c e
S ta n d a rd : P a rt 9
(N E )
N e tw o rk
E x te n s io n
P la n n in g
(C S )
C u s to m e r
S u p p o rt
(M R )
M e te r
R e a d in g &
C o n tro l
E le c t r ic D is tr ib u t io n N e tw o r k
P la n n in g , C o n s t r u c tin g ,
M a in ta in in g , a n d O p e ra tin g
In t e r f a c e
S ta n d a rd : P a rt 1 0
(A C T )
C u s to m e r
Account
M anagem ent
In t e r f a c e
S ta n d a rd : P a rt 1 0
In t e r f a c e
S ta n d a rd : P a rt 1 0
In te rf a c e
S ta n d a rd : P a rt 1 0
(F IN )
F in a n c ia l
(P R M )
P r e m is e s
(H R )
Hum an
R e s o u rc es
G e n e r a tio n a n d T r a n s m is s io n M a n a g e m e n t,
E n te r p ris e R e s o u rc e P la n n in g , S u p p ly C h a in , a n d
G e n e ra l C o rp o ra te S e rv ic e s
19
20
CIM UML
Information Model
Application independent
Context
Profile
Message Syntax
Message
XML Schema
22
CIM UML
Context
61968
Rules
Profile
Message Assembly
CIM/XML
Rules
Project
Rules
Message Syntax
Message
XML Schema
CIM/XML
RDF Schema
Relational
Database
23
To Summarize
The CIM is an abstract information model
standard expressed in UML.
Profiles specifying a subset of the CIM classes
and attributes for specific business context
Implementation technologies, such as use of
XML to create serialized files and messages
Standards for power system models
Standards for information message payloads
CIM UML
Information Model
Context
Profiles
Restrictions
Message Syntax
XML/RDF
Schema
File syntax
PowerSystemResource
Organisation
Asset
Contact
Location
Customer
Document
Information Containers Such As
Trouble Ticket, Work Orders, etc.
26
CIM Packages
class M ain
WG13
CombinedVersion
IEC61970
{root}
+
+
WG14
IEC61968
WG16
M arketOperations
Reservation
Financial
EnergyScheduling
27
Outage
Protection
ControlArea
Generation
Production
(fr om Generat ion)
Wires
SCADA
GenerationDynamics
Equivalents
WorkInProgress
Contingency
OperationalLimits
WorkInProgress
StateVariables
T opology
Meas
Core
Global
Domain
28
Locations
Domain2
AssetsLinear
AssetsPointOriented
Metering
LoadControl
PaymentMetering
ERPSupport
GMLSupport
Operations
Assets
AssetModels
T ypeAsset
Planning
Work
Customers
29
Bid
FTR
RTO
Security
Constraints
Resource
Clearing
Results
30
(from AssetBasics)
code : String
utc : String
number : String
serialNumber : SerialNumber
assetType : String
maufacturedDate : AbsoluteDate
installationDate : AbsoluteDate
inServiceDate : AbsoluteDate
outOfServiceDate : AbsoluteDate
removalDate : AbsoluteDate
warrantyDate : AbsoluteDate
financialValue : Money
status : String
statusDate : AbsoluteDate
critical : Boolean
corpStandard : String
removalReason : String
condition : String
plantTransferDate : AbsoluteDate
usage : String
purchaseDate : AbsoluteDate
purchasePrice : Money
purchaseOrderNumber : String
height : ShortLength
weedAbate : Boolean
weedRemDate : AbsoluteDate
fumigant : String
fumigantApplyDate : AbsoluteDate
jpaRefNum : String
classification : String
species : String
treatment : String
base : String
preservative : String
treatedDate : AbsoluteDate
breastBlock : Boolean
+AttachedTo_Pole
0..1
+Support_Streetlights
0..n
Streetlight
rating : String
armLength : ShortLength
32
Concepts: Generalization/Inheritance
Breaker: Specialization of
ProtectedSwitch
ProtectedSwitch:
Specialization of Switch
Switch: Specialization of
Conducting Equipment
ConductingEquipment:
Specialization of
Equipment
Equipment: Specialization
of PowerSystem
Resource
33
Equipment Inheritance
Hierarchy
class InheritanceHierarchy
Core::
Identifi edObject
Core::
PowerSystemResource
T apChanger
VoltageControlZone
Core::
ConnectivityNodeContainer
Core::
Equipment
Core::
EquipmentContainer
CompositeSwitch
Core::
Substation
Core::
VoltageLevel
HeatExchanger
Core::Bay
PowerT ransf ormer
Plant
Core::
ConductingEquipment
Line
Conductor
SeriesCompensator
T ransf ormerWinding
DCLineSegment
ACLineSegment
EnergySource
EnergyConsumer
Rectifi erInverter
BusbarSection
Ground
Connector
J unction
ShuntCompensator
RegulatingCondEq
FrequencyConverter
Switch
SynchronousMachine
ProtectedSwitch
StaticVarCompensator
LoadBreakSwitch
Breaker
J umper
Fuse
Disconnector
GroundDisconnector
34
Naming
Hierarchy 1
35
Naming
Hierarchy 2
36
class M ain
Connectivity
and
Topology
Model
Core::
Identifi edObject
Core::
PowerSystemResource
M eas::
M easurement
Core::
Equipment
Core::
ConductingEquipment
+Measurements
0..*
+Terminal
0..1
+Terminals
+Terminals
Core::
T erminal
1
0..*
+ConductingEquipment
+Terminal
+Connectiv ityNodes
0..* ConnectivityNode
0..*
0..1
+Connectiv ityNode
0..*
0..*
+Connectivity Nodes
0..*
+Connectiv ityNode
+MemberOf_EquipmentContainer
1
Core::
+Connectiv ityNodeContainer
ConnectivityNodeContainer
+TopologicalNode 0..1
+TopologicalNode
0..1
0..1
+BusNameMarker 0..1
+TopologicalNode
0..* T opologicalNode
Core::
EquipmentContainer
+TopologicalNodes0..*1..*
BusNameM arker
0..1
+BusNameMarker
+AngleRef_TopologicalNode
0..*
+TopologicalNode
+TopologicalIsland
1
0..1 +AngleRef_TopologicalIsland
T opologicalIsland
+ControlArea
0..1
ControlArea::ControlArea
+
+
+
+ControlArea
0..1
37
Taken from McMorran, An Introduction to IEC 61970-301 & 61968-11: The Common Information
Model, University of Strathclyde, Glasgow, UK
38
ACLineSegment
Breaker
Breaker
BusbarSection
Breaker
GeneratingUnit
SynchronousMachine
Current measurement
represented by
Measurement
connected to Terminal
39
Part of
TransformerWinding, not
separate piece of
equipment
Physically connected to
network and conducts
electricity, so inherits
from
ConductingEquipment
41
42
Equipment
(from Core)
PowerTransformer
+PowerTransformer 1
+HeatExchanger
TapChanger
0..n
+TapChangers
0..n
+TapChangers
+MemberOf_PowerTransformer
0..1
HeatExchanger
+Contains_TransformerWindings
1..n
ConductingEquipment
(from Core)
TransformerWinding
0..n
+To_TransformeWindings
+To_WindingTest
+RegulationSchedule
0..1
RegulationSchedule
+TransformerWinding
1
+From_TransformerWinding
+From_WindingTests
0..n
WindingTest
43
44
Maps to
17 CIM classes
45 CIM objects
Could be
extended further
with addition of
objects for
control areas
equipment
owners
measurement
units
generation and
load curves
asset data
45
0..n
+Assets
1
+Asset
+PowerSystemResource
0..1
0..n
+Location
1..n
Location
PowerSystem
Resource
(from Core)
+PowerSystemResources
0..n
+Location
coordinate : CoordinatePair
coordinateList : PointSequence
polygonFlag : Boolean
type : String
code : String
46
0..n
0..n
Document
0..n
(f rom DocumentationPackage)
...)
0..n
PowerSystem
Resource
(from Core)
QualificationRequirement
qualificationID : String
MaintenanceProcedure
type : String
AssetProperty
propertyType : String
propertyValue : String
units : String
AssetRating
ratingType : String
property : String
ratingValue : Float
units : String
InspectionRoutine
(f rom AssetsInspection)
47
Activity Records
ErpContact
(f rom ERP_Support)
0..n
History
Custom er
(f rom ConsumerPackage)
0..1
0..n
0..n
0..n
0..n
ActivityRecord
createdOn : AbsoluteDateTime
status : String
statusReason : String
remarks : String
0..n
0..n
0..n
Organisation
(f rom TopLev elPackage)
0..n
0..n
1..n
0..n
Work
(f rom WorkInitiationPackage)
...)
0..n
0..1
1
Asset
WorkTask
(f rom WorkDesignPackage)
(f rom AssetBasics)
0..n
PowerSystem
Resource
0..n
Location
(f rom LocationPackage)
(from Core)
48
Go to UML model in EA
49
Questions?
50
CIM UML
Information Model
Context
Profiles
Restrictions
Message Syntax
XML/RDF
Schema
File syntax
Profile Documents
IEC 61970-4xx series of Component Interface
Standards (CIS)
Specifies the functional requirements for interfaces that
a component (or application) implements to exchange
information with other components (or applications)
and/or to access publicly available data in a standard
way
Component interfaces describe the specific message
contents and services that can be used by applications
for this purpose
Implementation of these messages in a particular
technology is described in Part 5 of the standard
52
IEC 61970-452 specifies the specific profile (or subset) of the CIM for
exchange of static power system data between utilities, security
coordinators and other entities participating in a interconnected power
system
All parties have access to the modeling of their neighbors systems
that is necessary to execute state estimation or power flow
applications
A companion standard, IEC 61970-552, defines the CIM XML Model
Exchange Format based on the Resource Description Framework
(RDF) Schema specification language which can be used to transfer
power system model data for a particular profile
Interoperability tests have validated several vendors products for
exchanging complete power system models, partial models, and
incremental updates
53
61970-452
CPSM
Profile
TOC
Snippet
54
CIM UML
Information Model
Context
Profiles
Restrictions
Message Syntax
XML/RDF
Schema
File syntax
RDF Schema
Used for exchange of power system models
56
What is XML?
eXtensible Markup Language
A text-based tag language, similar in style to HTML but
with user-definable tags
Similar in use of ASCII text and tags
Self-describing
Open industry standard - W3C Recommendation
(spec)
Broad usage across industries (many XML tools available)
Basic Syntax
Starts with XML declaration
<?xml version="1.0"?>
58
An XML element is everything from (including) the element's start tag to (including) the
element's end tag.
An element can contain other elements, simple text or a mixture of both. Elements can
also have attributes.
<bookstore>
<book category="CHILDREN">
<title>Harry Potter</title>
<author>J K. Rowling</author>
<year>2005</year>
<price>29.99</price>
</book>
<book category="WEB">
<title>Learning XML</title>
<author>Erik T. Ray</author>
<year>2003</year>
<price>39.95</price>
</book>
</bookstore>
In the example above, <bookstore> and <book> have element contents, because they
contain other elements. <author> has text content because it contains text.
In the example above only <book> has an attribute (category="CHILDREN").
59
60
61
62
Aggregation changed
from 0..n to 2
Multiplicity
changed from
0..1 to 1
Multiplicity
changed from
0..1 to 1
63
Note:
Associations changed to aggregations
Parent classes removed
Not required in actual message content
Parent classes already known by both sender and receiver
Corollary: Only those parts of the CIM used in message exchange
need to be supported by interface applications
End result modified class structure
Example of application of business context to information model
64
Database Schema
Defines the table names and columns, describes the relationships
between tables (via keys), and acts as a repository for triggers and
stored procedures.
XML Schema
Describes the ordering and inter-relationship of
XML elements (i.e., sequence and nesting of tags) and
Attributes (i.e., values, types, defaults) in the class of XML documents
to which the schema applies.
(source: Professional XML Meta Data, by Kal Ahmed, et al.)
65
66
Equipment
(from Core)
PowerTransformer
+PowerTransformer 1
+HeatExchanger
TapChanger
0..n
+TapChangers
0..n
+TapChangers
+MemberOf_PowerTransformer
0..1
HeatExchanger
+Contains_TransformerWindings
1..n
ConductingEquipment
(from Core)
TransformerWinding
0..n
+To_TransformeWindings
+To_WindingTest
+RegulationSchedule
0..1
RegulationSchedule
+TransformerWinding
1
+From_TransformerWinding
+From_WindingTests
0..n
WindingTest
67
68
69
RDF Schema
Used for exchange of power system models
70
Big Issue
Although we can swap our documents with
each other through XML, we still havent a
clue what they mean.
(Professional XML Meta Data, by Kal Ahmed, et al.)
71
RDF Schema
RDF Schema mechanism is a
set of RDF resources (including
properties) and constraints on
their relationships
Defines application-specific
RDF vocabularies, for example
CIM vocabulary
RDF Schema URI
unambiguously identifies a
single version of a schema
72
Technical Approach
RDF (Resource Description Framework)
- Defines mechanism for describing resources that makes no assumptions
about a particular application domain, nor defines the semantics of any
application domain. The definition of the mechanism is domain neutral, yet
the mechanism is suitable for describing information about any domain:
For more information: http://www.w3.org/RDF
Status: W3C Recommendation 22 February 1999
http://www.w3.org/TR/REC-rdf-syntax/
RDF Schema
- Defines a schema specification language. Provides a basic type system
for use in RDF models. It defines resources and properties such as Class
and subClassOf that are used in specifying application-specific schemas:
Status: W3C Proposed Recommendation 03 March 1999
http://www.w3.org/TR/PR-rdf-schema/
73
74
XML Namespaces
Distinguish between duplicate element type and attribute
names
Collection of element type and attribute names. The
namespace is identified by a URI.
Declared with an xmlns attribute, which can associate a
prefix with the namespace.
If XML namespace declaration contains a prefix, refer to
element type and attribute names in that namespace with
the prefix. E.g. cim:Substation, UCTE:Substation
If XML namespace declaration does not contain a prefix,
the namespace is the default XML namespace, refer to
element type names in that namespace without a prefix.
75
76
77
T2
BDD-RSK2
78
79
ACLineSegment in RDF
Siemens 100 bus model - RDF schema
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xml:base="siemens" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:cim="http://iec.ch/TC57/2001/CIM-schema-cim10#">
<cim:ACLineSegment rdf:ID="_6B1DD5C2CB934E86AC53FFD886E2D1B3">
<cim:Naming.name>BBD-RSK2</cim:Naming.name>
<cim:Conductor.bch>2.79</cim:Conductor.bch>
<cim:Conductor.x>4.3378</cim:Conductor.x>
<cim:Conductor.r>0.4761</cim:Conductor.r>
</cim:ACLineSegment>
<cim:Terminal rdf:ID="_EB6085D9DF364DA78A884D4D0A571371">
<cim:Naming.name>T2</cim:Naming.name>
<cim:Terminal.ConnectivityNode rdf:resource="#_CC312D30C85C4236948A4129AEE3B5F7"/>
<cim:Terminal.ConductingEquipment rdf:resource="#_6B1DD5C2CB934E86AC53FFD886E2D1B3"/>
</cim:Terminal>
<cim:Terminal rdf:ID="_7C8354E0DA247DBB3611E2E8BF8A86D">
<cim:Naming.name>T1</cim:Naming.name>
<cim:Terminal.ConnectivityNode rdf:resource="#_D16FD63501444AECBF8157D1E4764E38"/>
<cim:Terminal.ConductingEquipment rdf:resource="#_6B1DD5C2CB934E86AC53FFD886E2D1B3"/>
</cim:Terminal>
80
ACLineSegment in RDF
Siemens 100 bus model - RDF schema
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xml:base="siemens" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:cim="http://iec.ch/TC57/2001/CIM-schema-cim10#">
<cim:ACLineSegment rdf:ID="_6B1DD5C2CB934E86AC53FFD886E2D1B3">
<cim:Naming.name>BBD-RSK2</cim:Naming.name>
<cim:Conductor.bch>2.79</cim:Conductor.bch>
<cim:Conductor.x>4.3378</cim:Conductor.x>
<cim:Conductor.r>0.4761</cim:Conductor.r>
</cim:ACLineSegment>
<cim:Terminal rdf:ID="_EB6085D9DF364DA78A884D4D0A571371">
<cim:Naming.name>T2</cim:Naming.name>
<cim:Terminal.ConnectivityNode rdf:resource="#_CC312D30C85C4236948A4129AEE3B5F7"/>
<cim:Terminal.ConductingEquipment rdf:resource="#_6B1DD5C2CB934E86AC53FFD886E2D1B3"/>
</cim:Terminal>
<cim:Terminal rdf:ID="_7C8354E0DA247DBB3611E2E8BF8A86D">
<cim:Naming.name>T1</cim:Naming.name>
<cim:Terminal.ConnectivityNode rdf:resource="#_D16FD63501444AECBF8157D1E4764E38"/>
<cim:Terminal.ConductingEquipment rdf:resource="#_6B1DD5C2CB934E86AC53FFD886E2D1B3"/>
</cim:Terminal>
81
Containment in RDF
Substation VOL
with
230 230
KV voltage
level and
Bay 240W79
with 240W79
Breaker CB
Substation
VOL
with
KV voltage
level
and Bay
with Breaker CB
<cim:Substation rdf:ID="_277B2933524E43E19DAAF1D138DC62C4">
<cim:Naming.name>VOL</cim:Naming.name>
<cim:Substation.LoadArea rdf:resource="#_BA2173878B0645A7AC8EA57B6249D537"/>
</cim:Substation>
<cim:VoltageLevel rdf:ID="_C20AF84C15E047218D75C47870C34C87">
<cim:Naming.name>230K</cim:Naming.name>
<cim:VoltageLevel.MemberOf_Substation rdf:resource="#_277B2933524E43E19DAAF1D138DC62C4"/>
<cim:VoltageLevel.BaseVoltage rdf:resource="#_CF8BD1450E264399891F7FE5653D0760"/>
</cim:VoltageLevel>
<cim:BusbarSection rdf:ID="_5E0DBC09FE4D4A0DB902FEFF18AA4C30">
<cim:Naming.name>VOL 2304</cim:Naming.name>
<cim:Equipment.MemberOf_EquipmentContainer rdf:resource="#_C20AF84C15E047218D75C47870C34C87"/>
</cim:BusbarSection>
82
Measurement in RDF
<cim:Measurement rdf:ID="_5B22599688AC4DE6B99FD8B13C1BA36F">
<cim:Naming.name>LN
1 MVAr</cim:Naming.name>
<cim:Measurement.MeasurementType rdf:resource="#_83D7B035901D4D2E80C040609D5ED7EC"/>
<cim:Measurement.Unit rdf:resource="#_61784D3DA1954750A4E09444BE5206CB"/>
</cim:Measurement>
<cim:MeasurementValue rdf:ID="_FF332A9A82FF43719AAF4E5DAFCFB9CD">
<cim:Naming.aliasName>ICCP ID
24</cim:Naming.aliasName>
<cim:Naming.name>MVAr</cim:Naming.name>
<cim:MeasurementValue.MeasurementValueSource
rdf:resource="#_F0F5BA1CDE23483A8C80D20A4907A272"/>
<cim:MeasurementValue.MemberOf_Measurement rdf:resource="#_
5B22599688AC4DE6B99FD8B13C1BA36F"/></cim:MeasurementValue>
83
This standard relies upon the CIM RDF Schema of IEC 61970501
84
CIM
(in UML)
ref
e
UML
to RDF
Transformers
ren
ce
Exporter
Enterprise
Architect
CIM as
XML/RDF specifies
Schema
Power
System Data
as
XML/RDF
85
Key Standards
and Related Organizations UCA : User groups
MultiSpeak
TC57
Open
Application
Group
Coordination
WG19
(NRECA)
CIM/61850
WG14
DMS
OLE
Process
Control
(OPC)
EPRI
CCAPI
Project
WG9
Distribution
Feeders
WG7
Control
WG17 Centers
WG18 WGs 10
Substations
WG13
EMS WG16
W3C
EPRI
UCA2
Project
CIM
Object
Mgmt.
Group
ebXML
OASIS
86
Lists of the CIMug working groups and works in progress as well as minutes of
meetings and conference calls
CIM issues lists and status of resolution
Help desk
Discussion forums
Links to other CIM-related sites
87
Questions?
Contact tsaxton@xtensible.net
Thank you
88
90
Conforms to
IEC 61970-301 CIM
CIM UML
Information Model
Reused parts
New extensions
Context
Conforms to
IEC 61970-452, 453,
456, others
Model Exchange
Profile
Power System
Model Profile
Group
Restrictions
Message Syntax
Conforms to
IEC 61970-501 and -552
CIM XML Model Exchange Format
CIM/RDF
Schema
File syntax
CIM UML
Information Model
Concrete
Message
Conforms to
IEC 61970-452
Model Exchange
Profile
Conforms to
IEC 61970-552-4
CIM XML Model Exchange Format
Profile
CIM/XML
RDFSchema
Reused parts
New extensions
Restrictions
File syntax
92
93
94
Role of CIM
95
CIM UML
Merge resolve
semantic
differences
Other
Information
Models
Context
Profile
Message Syntax
Schemas
XSD, RDFS,
DDL
96
Semantic Consistency
Existing Terminology
and Metadata
3) Generate Canonicals
1) Establish Vocabulary
2) Develop ESM
Control Content
Collaborate
Identify and refine semantics
Context Refinement
Compliments Xtensible MD3i
97
Application
Information
Process
Integration
Business
Intelligence
Business
Definitions
BPM/Workflow
Enterprise
Enterprise
Semantic
Semantic
Model
Model
Applications
Metadata
98
CIM UML
Bridge
Other
Information
Models
Profile 2
Profile 3
CIM/RDF
Schema
DDL
Context
System Interface
Design
Document
Profile 1
Profile 1
Profile 1
Interface Syntax
Message
XML Schema
99
ESM
Concrete
Message
Conforms to
Profiles defined
for each
system interaction
Conforms to
WSDLs and Message
XML Schemas
Reused parts
New extensions for project
Profile
Restrictions
XML
Schema
File syntax
100
Project Integration
Architecture
101
Data Architecture
Model
REFEFENCE
MODELS
CIM
SCHEMAS
OTHER
Semantic Model
SEMPRA
MODEL
MESSAGES
CIS
Business
Entity
Business
Entity
DB Schema
XML Schema
Business
Entity
102
103
Interface Examples:
Interface Type
Example
Implemented
by
Utilized by
Description
Information
Creation
submitBid(XML)
Vendor
Enterprise
Information
Transfer
publishCleanBidSet(XML)
CAISO
Vendor
Information
Interest
receiveCleanBidSet(XML)
Vendor
EAI
Information
Sharing
getResourceInfo(XML)
XML
Vendor
Enterprise
104
Integration Layer
System A
WS
receiveMarketMeterData
WS
broadcastMarketMeterData
WS
retrieveMarketMeterData
WS
receiveMarketMeterData
WS
broadcastMarketMeterData
retrieveMarketInterchange
broadcastInvoiceData
WS
broadcastGeneralLedgerData
WS
WS
receiveInvoiceData
WS
PI
BITS
WS
broadcastStatusInvoiceData
receiveGeneralLedgerData
WS
MC
105
106
107
Bidding
Market Results
Settlement
Outage Scheduling
Dispatch Signals
System
EMS
OASIS
Interchange Scheduling
System
Congestion Revenue Rights
Intermittent Resources
Compliance
RMR Validation
Generation Outage Scheduling
Transmission Outage
Scheduling
Market Quality System
(ATF updates)
Application/
Project
Message(s)
CIM
Pct of
message
that is
CIM
Power
Delivery
Substation
Measurements
IntervalRead, SubstationEquipment.Measurement
MeasurementList
90%
Outage Center
Call Handing
OutageManagement
80%
Retail Access
Project
CustomerMeterDataSet,
CustomerServiceAgreement,
MeasurmentList,
Document, ActivityRecord,
CustomerBilling,
BillingDeterminant
80%
Pole Attachment
System
AssetList
70%
Transmission
Planned
Outages
PlannedOutage.Change
PlannedOutageNotification
50%
Transmission
Wholesale
Billing System
70%
EMS SCADA
WeatherData
MeasurementList
100%
Transmission
110
Application/
Project
Message(s)
CIM
Pct of
message
that is CIM
Power
Supply/
Generation
Availability
Information
System
GeoThermalPlantGeneration
MeasurementList
60%
Hydro
Information
Website
FlowDisplay
MeasurementList
100%
Generation
Equipment
Performance
Work
Management
Work
WorkHistory
90%
CRS
MarkToMarketData
80%
California ISO
interface
EDI810
Settlement
50%
Giving
Campaign
EmployeeDetails, ContributionPayrollDetails
Employee (erpPerson)
70%
Sarbanes Oxley
Audit
ChangeAuditReport
90%
Commercial
& Trading
Corporate
111
CIM is to complex too learn and contains many parts I do not need
Fact: The CIM UML model is evolving as new applications are identified
Fact: Only small part of CIM information model is used for a given interface, so change of information model
unlikely to affect specific interface.
Solution: Version control - tie interface designs to project specifications, not directly to standard
Fact: Only instantiated concrete class/attributes are actually sent in a message instance
Reality: Message payload is no larger than any XML formatted message
I dont want to add in an extra step of converting to CIM for system integration
I cant expect my vendors to adopt the CIM model for their interface
Fact: Only a few parts of the CIM need to be Known by the vendor
Reality: Approach is to specify the mappings to a common language (CIM) as part of the interface contract
CIM does not contain everything I need or in the form I need for my interfaces
112
CIM Usage
Many EMS vendors support power system model exchange using CIM/RDF/XML,
some with CIM-based databases behind the scenes
EPRI has sponsored 12 interoperability tests for transmission model exchange and
service validation and more recently for planning and distribution
Utilities have implemented CIM-based integration using EAI technologies
Asset and work management vendors as well as GIS application vendors are
supporting CIM/XSD standards
AMI (Smart Meter) projects use IEC 61968 Part 9 for meter related information
exchange
CIM has been extended into the power market, planning, and dynamic model exchange
CIM provides a foundation for Service-Oriented Architecture (SOA) and Web service
implementations
Vendors have developed tools to build CIM-based information exchange messaging,
ESB and OPC interfaces, and repository applications that can process CIM-aware data
MultiSpeak is converting to CIM-based UML models and XML
ENTSO_E is converting power model exchanges and day-ahead forecasts for
planning/operational applications to CIM based format
Utilities have used the CIM as the basis for developing common messages for integration
Second IOP conducted in July 2010 (first was UCTE IOP in March 2009)
CIM Acceptance
114
Concluding Remarks
Bottom line: CIM standards are different and
much more powerful
Can be applied in many ways
Support many types of functions/applications through
combination of reuse and extension
Architecture supports future, unknown applications
115
Questions?
Contact tsaxton@xtensible.net
Thank you
116
Profiles Defined
Equipment
Identifies equipment,
describes basic
characteristics, and electrical
connectivity that would be
input to topology processing
Schedules
Measurement Specs
Describes how SCADA will
obtain measurements and
what equipment objects are
measured
Measurement Set
Topology
The result of topology processing.
State Variables
This is the set of state variables
Schematic Layouts
Describes how equipment objects
Dynamics
121
T1
S1
S2
T1.1
Time
E1.1
S3
S4
T1.2
S5
T1.3
S6
Profile
Full model
S7
DifferentialModel
Predecessor
S8
DependsOnModel
122