Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
CIM University
Windsor, England
15 May 2012
1
CIM Standards Overview
And Its Role in the Utility Enterprise – Part 1
2
Presentation Contents
• Background
• What is the CIM
• How the CIM is used in the Utility Enterprise
• Three Layer Architecture for Using the CIM Standards
• CIM UML model
• Profiles for business context
• Implementation syntax
• IEC CIM Working Groups and Standards
• CIM as Basis for Enterprise Semantic Model (ESM)
• Case studies
• Where to get CIM information
3
The IEC Common Information Model
(CIM) - What Is It?
• A set of standards in enable system integration and information exchange
based on a common information model
– Provides a general information model and message/file schemas for
messages/files exchanged between systems
• A key differentiator: The CIM standards are based on a Unified Modeling
Language (UML) based information model representing real-world objects
and information entities exchanged within the value chain of the electric
power industry
– Provides common semantics for all information exchanges
Referred to as Model-Driven Integration (MDI)
– Not tied to a particular application’s view of the world
• But permits same model to be used by all applications to facilitate information sharing
between applications
– Maintained by IEC in Sparx Enterprise Architect modeling tools
– Many tools available generating design artifacts and documentation
– Enable data access to enterprise data warehouse in a standard way
4
GWAC Stack and the CIM
Standards
Interoperability Categories
Political and Economic Objectives as
8: Economic/Regulatory Policy Embodied in Policy and Regulation
PpenADR
IEC 61970 CIM IEC 61970 CIM IEC 61968 CIM
MultiSpeak
NAESB ESPI (Green Button)
IEC 62325 CIM
SAE J2847
IEEE 1547
ZigBee SEP
IEC 61850
IEC 61334
Slide 7
Role of CIM in Smart Grid
Architecture
• CIM standards aim to simplify integration of
components and expand options for supply of
components by standardizing information
exchanges
– Reduce complexity with clear consistent semantic
modeling across the enterprise
– Data sources: achieve a clear picture of data
mastership in the enterprise
– Data consumers: make ‘data of record’ available on
demand to qualified users
• CIM employs a canonical data model (CDM)
strategy for standardizing interfaces in the
power system operations and planning domain.
Application of Information Model
Application 1 Application 2
Common model creates
understanding
SISCO SYSTEMS
9
What is a Canonical Data Model?
Materials
Management Construction
Engineering Concerns
Concerns Concerns
11
The Needs of Various Users –
Some Same, Some Different
12
The Needs of Various Users –
Some Same, Some Different (continued)
13
Exchanging Common Language Messages Among Systems
Should Provide Relevant Information To Each System That
Is Harmonious With All Other Systems’ Information
Maintenance
Blah, Blah, Blah,
Organization,
Switching Schedule Meter Reading Load Data Set Load Control
Blah, Blah, Blah
Blah, Blah, Blah, Blah, Blah, Blah,
Blah, Blah, Blah, Blah, Blah, Blah,
Organization, Organization,
Organization, Organization,
Blah, Blah, Blah Blah, Blah, Blah
Blah, Blah, Blah 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!
14
Smart Data is Key to Enabling Adaptive Smart
Grid Systems
For example, a common language-based logical
infrastructure facilitates collaboration among the many
applications involved in Asset Management
SCADA Work
CRM Mobile & Dispatching Collaboration
Financial & Reporting
Management
IVR eBusiness EMS DMS SA/DA
Work
Design
Customer Management Asset Operations
Asset Owner Asset Manager Service Provider
16
Application To Common Language Mapping –
The Typical Field to Field Process Is Cumbersome
17
Using A Semantic Model To
Simplify & Scale Up The Mapping Process
• What is a Semantic Model?
– The key ingredients that make up a semantic model are a vocabulary of
basic terms, a precise specification of what those terms mean and how
they relate to each other.
• 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.
Generic Semantic
Model
Services Metadata
Apps.
19
Subscribers:
Decoupled Information CIM App
Several Application Adapters Receive The Same Message
Each Adapter:
Exchange X.1
X.2
B.1
B.2 •Parses Message, Pulling Out Data Needed By Application
X.3 Subscriber •Transforms Data (if necessary) to Local Application Format
X.4
X.5
•Passes Data To Local Application And/Or Database
Through Most Appropriate Means
Outage Distribution
Reporting EMS OMS Automation CIS
CIM Publishers:
X.1 App CIM
X.2 Y.1 X.1
One Application Connector:
X.3 Subscriber Y.2 X.2 •Obtains Data From Application And/Or Database
X.4 Y.3 X.3 Publisher •Transforms Data (if necessary) to the “Common
X.5 Y.4 X.4
Y.5 X.5 Language” (a Canonical Data Model)
•Puts Data Into Message Template
•Publishes The Message (Fires & Forgets)
20
© 2003-2004 Xtensible Solutions, Inc. 20
The CIM and Related Standards
• The CIM standards are more than just an abstract
information model (or CDM) expressed in UML
• Profiles for specifying a subset of the CIM classes and
attributes for a specific business context at a specific
system interface or system interaction
• Implementation models
– Use of XML to create serialized files and messages
• RDF Schema-based standards for power system model exchange
• XML Schema-based standards for information message payloads
– ETL based on CIM for data base access
• DDLs for data tables
21
We Need An Organizing Framework
• Layered Reference Architecture for TC57
– See 62357-1: Reference Architecture for Power System
Information Exchange, Second Edition
• Based on UN/CEFACT
– Information Model
– Contextual Model
– Message Syntax
• Rules for Message Assembly
GWAC Stack – Not an IT Architecture for
the CIM Standards
Interoperability Categories
Political and Economic Objectives as
8: Economic/Regulatory Policy Embodied in Policy and Regulation
Information Model
• Generalized model of all utility objects and their
CIM UML relationships
• Application independent, but defines all concepts
needed for any application
Context
Contextual layer restricts information
model
Profiles •
•
Specifies which part of CIM is used for given profile
Mandatory and optional
• Restrictions
• But cannot add to information model
•Message • <xsd:element
name=« EnergyTransaction"/> •Syntactic
• <xsd:sequence>
Syntax •
•
<xsd:element name=« Name"/>
<xsd:element name=« Type"/> •Model
• </xsd:sequence>
• </xsd:element>
Layered Architecture for CIM Standards
Information
CIM Ext CIM/UML Bridging
CIM Bridge Foreign
Context
CPSM WG 14 Other UML
Profile Profiles Profiles Modelling
Message Rules
WG 13 WG 14
Logical
Assembly File Message Messages
Schemas
Structure Structure
CIM
RDF
XML
Exchange
NDR
Schema
Other
Rules
XML DataBase
CIM RDF OWL
Schema Schema
26
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
• Also, the CIM UML can be extended
– Standard extensions for new functional areas
– Private extensions for specific utility requirements
27
TC 57 Organization and Formal Liaisons
UCA International
WG19 User groups
Architecture
WG13 WG 10
EMS-API Substation
Automation
CIM/61850 CIGRE
Harmonization SC D2-24
WG14 WG17 SC B5-38
SIDMS DER
TC57
WG16
WG18
Energy
Hydro IEEE
Markets Conveners
Advisory Group PES PSCC
CAG Security
WG3 WG20 SubComm
Telecontrol Power Line
Protocols Carrier
WG21
WG15
Grid System Legend
Security
Interfaces
CIM-based
61850-based
28
IEC TC57 - Reference Architecture for Power System Information Exchange
Energy Utility
Other
Market Utility Customers Service
Businesses
Participants Providers Application To Application (A2A)
and Business To Business
(B2B) Communications
CIM Extensions 61970 / 61968 Common Information Model (CIM) Bridges to Other Domains Application/System
End-to-End Security Standards and Recommendations (62351-6)
Interfaces
61970 Component Interface Specification (CIS) / 61968 SIDMS Technology Mappings
Network, System, and Data Management (62351-7)
Communications
Media and Services
61850 IED
60870-5 61850 Field Devices
Devices
TC13 RTUs or and Systems 60870-6
Field Substation Beyond the External Systems
WG14 Substation using TASE.2
Devices Devices Substation (Symmetric client/server
Systems Web Services
protocols)
Customer DERs Other
IEDs, Relays, Meters, Switchgear, CTs, VTs
Meters and Meters Control Centers
Information Model
• Generalized model of all utility objects and their
CIM UML relationships
• Application independent, but defines all concepts
needed for any application
Context
Contextual layer restricts information
model
Profiles •
•
Specifies which part of CIM is used for given profile
Mandatory and optional
• Restrictions
• But cannot add to information model
PowerSystemResource Organisation
Electrical Network Role Used For Entities Performing Roles Such
Planning, Operations, etc. As Operations, Tax Authority
Asset Person
Physical Plant Filling A Role People Performing Roles Such
Such As A Transformer, Pole, etc. Dispatcher, Field Operator, etc.
Location
Where To Find Something By
Customer
Industrial, Commercial, & Residential
GPS, Address, Electronically, etc.
Which Can Have Multiple Accounts
Document
Information Containers Such As
Trouble Ticket, Work Orders, etc.
31
IEC TC57 CIM Packages
WG13
Transmission
EMS/Planning
Interfaces
WG14
DMS
Interfaces
WG16
Deregulated
Market
Communications
32
WG13 CIM Packages - 61970
33
WG14 CIM Packages - 61968
pkg M ain
Operations
Part 4
Planning
Work
Part 6
Customers
Part 8
Part 9
34
WG16 CIM Market Extensions
35
The CIM Is Expressed In Unified Modeling
Language (UML) Notation* Asset
(from AssetBasics)
code : String
utc : String
number : String
serialNumber : SerialNumber
Class Name usually describes things in the real world assetType : String
maufacturedDate : AbsoluteDate
installationDate : AbsoluteDate
Structure inServiceDate : AbsoluteDate
height : ShortLength outOfServiceDate : AbsoluteDate
weedAbate : Boolean removalDate : AbsoluteDate
weedRemDate : AbsoluteDate warrantyDate : AbsoluteDate
fumigant : String financialValue : Money
Class Attributes describe fumigantApplyDate : AbsoluteDate status : String
significant aspects about the thing jpaRefNum : String statusDate : AbsoluteDate
critical : Boolean
corpStandard : String
removalReason : String
This Specialization indicates that a “Pole” is a type of condition : String
“Structure.” Since a “Structure” is a type of “Asset,” the Pole plantTransferDate : AbsoluteDate
usage : String
inherits all of the attributes from both Structure and Asset purchaseDate : AbsoluteDate
purchasePrice : Money
Pole purchaseOrderNumber : String
classification : String
species : String
treatment : String
base : String
preservative : String
* For more information on UML notation treatedDate : AbsoluteDate +AttachedTo_Pole
(a standard), refer to Martin Fowler’s book breastBlock : Boolean 0..1
+Support_Streetlights
“UML Distilled,” Addison-Wesley 0..n
Streetlight
36
Concepts: Generalization/Inheritance
class DocumentationExampleInheritance
• Breaker: Specialization of
IdentifiedObject
Core::
ProtectedSwitch
PowerSystemResource
• ProtectedSwitch:
Core:: Specialization of Switch
Equipment
Release 14 • Switch: Specialization of
PowerTransformer
Conducting Equipment
Core::
ConductingEquipment
Release 15
• ConductingEquipment:
Specialization of
Switch
Equipment
ProtectedSwitch
• Equipment: Specialization
of PowerSystem
Breaker
Resource
37
cl a ss I nher i t a nceHi er a r chy
Hierarchy C or e::
P ow er Sy st emResour ce
Ta pC ha nger
V ol t a geC ont r ol Zone
C or e::
C onnect i v i t y NodeC ont a i ner
C or e::
C or e:: Equi pment C ont a i ner C or e::Subst a t i on
Equi pment C omposi t eSw i t ch
C or e::V ol t a geLev el
C or e::B a y
P l a nt
Li ne
A C Li neSegment
Ser i esC ompensa t or
Ener gy Sour ce
Ener gy C onsumer
Rect i f i er I nv er t er
C onnect or Junct i on
Shunt C ompensa t or
Naming +
C or e::I dent i f i edO bject
Hierarchy 1 +
+
mRID: String [0..1]
name: String [0..1]
C or e:: C or e::
C or e::
C onnect i v i t y NodeC ont a i ner P ow er Sy st emResour ce
Geogr a phi ca l Regi on
+Region 0..1
+Regions 0..*
C or e:: C or e::
SubGeogr a phi ca l Regi on Equi pment C ont a i ner +EquipmentContainer
0..1
+Region
+Region 0..1 +Equipments
0..1 C or e::
0..*
Equi pment
+Lines 0..*
P l a nt
Li ne
+Substations 0..*
+Substation C or e::
Subst a t i on
0..1
+Substation 1
+VoltageLevels 0..*
C or e::
V ol t a geLev el
+VoltageLevel
0..1
0..* +Bays
C or e::
+Bays 0..* Bay
39
cl a ss Na mi ngHi er a r chy P a r t 2
+
+
aliasName: String [0..1]
mRID: String [0..1]
+ name: String [0..1]
Hierarchy 2
M ea s:: +Measurements
C or e::
M ea sur ement P ow er Sy st emResour ce Ta pC ha nger
0..* 0..1
+PowerSystemResource
0..1 +CompositeSwitch
+GeneratingUnit 0..1
+SynchronousMachines 1..*
+Switches 0..*
C or e::
Sw i t ch
C onduct i ngEqui pment
Fuse
DC Li neSegment
Di sconnect or
C onnect or
P r ot ect edSw i t ch
Fr equency C onv er t er
B usba r Sect i on
Loa dB r ea k Sw i t ch Shunt C ompensa t or
Ener gy C onsumer
Junct i on
B r ea k er
Rect i f i er I nv er t er
Gr ound
Ener gy Sour ce
40
Connectivity
and
Topology
Model
41
Converting a Circuit to CIM Objects
• Example to show how voltage levels, current
transformers, power transformers and generators
are modelled
• Circuit contains a single generating source, load,
line and busbar. The circuit also contains two
power transformers resulting in three voltage
levels of 17kV, 33kV and 132kV
Taken from Alan McMorran, Common Information Model Primer: First Edition., EPRI,
Palo Alto, CA: 2011, 1024449
42
Example Circuit as a Single Line
Diagram
EnergyConsumer ACLineSegment
Breaker
Breaker
BusbarSection
Breaker
GeneratingUnit
Current measurement
SynchronousMachine represented by
Measurement connected
to Terminal
43
Representing a Power Transformer as
CIM Objects
• A power transformer is not mapped to a single
CIM class
– Represented by a number of classes
– Two-winding power transformer becomes two
TransformerWinding objects within a
PowerTransformer container
• If a tap changer is present to control one of the
windings
– An instance of the TapChanger class is associated
with that particular winding
– Also contained within the PowerTransformer instance
44
Transformer Class Diagram
- pre CIM Release 15
Shell of transformer,
containing windings,
insulation, magnetic core,
etc.
Part of
TransformerWinding, not
separate piece of
equipment
Terminal
Physically connected to
network and conducts
electricity, so inherits from
ConductingEquipment
45
Transformer Instance for Transformer 17-33
- pre Release 15
• Transformer 17-33 is
Terminal represented as four CIM
objects
• Connections from the
transformer to the network
are made from the
windings via Terminal
Terminal
46
Transformer Class Diagram
CIM Release 15
ConductingEquipment with
associations to types of
TransformerEnds for
electrical connectivity
Previously included in
Winding class
47
Balanced Transformer Model
48
Balanced Transformer Instance for
Transformer 17-33 - Release 15
• Transformer 17-33 is
represented as four
CIM objects plus
optional objects
• Connections from the
transformer to the
network are made
directly from the
PowerTransformer via
association to
PowerTransformerEnd
49
Unbalanced Distribution Transformer with
Multiple Tanks Instance Example
50
Example Circuit with Full CIM Mappings
• 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
51
How The CIM Handles Location For Logical Devices
And/Or The Physical Asset Performing The Device’s Role
52
Types Of Document Relationship
Inherited By All Assets
53
Activity Records
54
CIM UML Release Cycles
• 61970 CIM UML has annual release cycle
• Current official annual release is IEC61970CIM15v33
• Basis for IEC 61970-301 CIM Base Fifth Edition
• Word document auto-generated from the UML electronic model
• Information system and Profile documents are synchronized with
UML model release
• 61968 CIM UML different update cycles
• Basis for IEC 61968-11 CIM Distribution Information Exchange
Model
• 62325 CIM UML on another update cycle
• Basis for IEC 62325-301 CIM for Deregulated Markets
• Complete CIM UML available as a combined model on CIMug
Sharepoint site: iec61970cim14v13_iec61968cim10v28_combined
55
CIM UML in Enterprise Architect
• The CIM UML model is maintained in Sparx
Enterprise Architect (EA)
• Current Official CIM Release 15 UML Model
– iec61970cim15v33_iec61968cim11v13_iec62325cim0
1v07
• Go to UML model in EA
57