CIM Misunderstandings PDF

Addressing Misunderstandings of the CIM
Alan McMorran B.Eng Ph.D
OG Open Grid Systems

Misunderstanding 1:
CIM is only for Transmission
2 OG Open Grid Systems

Origins of the CIM
Started as project by the Electric Power Research
Institute (EPRI) as Control Centre API (CCAPI)
This became IEC 61970-301 which is now developed
by Working Group 13
The standard defines the components in a power
system for use in a common Energy Management
System (EMS) Application Programming Interface (API)
as a series of packages and classes
The CIM is now more than just IEC 61970-301, the CIM
is really three IEC standards
O Open Grid Systems

3
CIM for Distribution
IEC 61968-11 is developed by IEC TC57 WG14 as an
extension to IEC 61970-301 for covering the data
requirements of distribution systems
IEC 61968-11 covers a far wider data footprint than IEC
61970-301
As well as extending the functional Wires model to
cover distribution network requirements it extends the
CIM to cover data exchange requirements for:
Metering, Customer Billing, Asset Management,
Work Management, Geographical Data ....
O Open Grid Systems

4
Interface Reference Model
Distribution Management Business Functions External
Business Functions to Distribution Management
NO AM OP MC EMS RET SC
Network Records & Operational Maintenance & Energy Retail Supply Chain
Operations Asset Planning & Construction Management & & Logistics
Management Optimisation Energy Trading
Interface Interface Interface Interface Interface Interface Interface
IEC 61968/61970 Compliant Middleware Services
Interface Interface Interface Interface Interface Interface Interface
NE CS MR ACT FIN PRM HR

Network Customer Meter Reading Customer Financial Premises Human
Extension Support & Control Account Resources
Planning Management
Electric Distribution Network Generation and Transmission Management,

Planning, Construction, Enterprise Resource Planning, Supply Chain
Maintenance and Operations and General Corporate Services
O Open Grid Systems

5
CIM for Markets
CIM for Market Extensions (CME) extend the CIM
packages to define the data exchanges for deregulated
markets
These extensions cover the data required for Market
operations including:
Bidding
Clearing
Settlement
It models the data used in communication between
market participants, not a market itself
O Open Grid Systems

6
Common Model
While the CIM now spans multiple domains common
elements are shared and relationships span packages
SCADA
Dynamics
Diagram Layout
(Graphics)
Planning
Functional Markets
Electrical Model
Asset
Management
Distribution
Work Electrical
Management Extensions Meter Reading
Geographical
Data
Customer Support
O Open Grid Systems

7
Misunderstanding 2:
CIM is too Complex

Is the CIM Complex?
The CIM covers a large number of systems
It models data from multiple domains but must be
consistent
A Substation is the same entity with the same
identifier in a DMS, Asset Management or Meter Data
Management System
To use the CIM you do not need to implement, use or
even look at all 700+ classes and their attributes/
associations
O Open Grid Systems

9
A Complex Model
Work SvVoltage SvTapStep EndDeviceAsset SvPowerFlow Topological
category v continuousPosition amrSystem p Island
EndDeviceAsset SvTapStep SvVoltage SvPowerFlow Work
createdDateTime angle application q name Topological
amrSystem continuousPosition v Location p category
kind category Island
mRID application GeneratingUnit category
angle q PositionPoint
createdDateTime Synchronous
name
corporateCode
name category Location
allocSpinResP corporateCode xPosition
kind Machine
critical
corporateCode
priority category
autoCntrlMarginP direction yPosition
mRID baseQ
GeneratingUnit PositionPoint
demandResponse Synchronous
critical
requestDateTime corporateCode
baseP geoInfoReference zPosition
name condenserP
allocSpinResP xPosition
description Machine
demandResponse
revisionNumber direction
controlDeadband isPolygon priority coolantCondition
autoCntrlMarginP yPosition
disconnect baseQ
description
subject geoInfoReference
controlPulseHigh mRID MeterReading
requestDateTime coolantType
baseP zPosition
dstEnabled condenserP
titledisconnect isPolygon
controlPulseLow name
controlDeadband initialCondition
name
revisionNumber damping
coolantCondition
dstEnabled mRID
description subject inertia
controlPulseHigh MeterReading
initialLossOfLife coolantType
initialCondition
BusbarSection name
dispReserveFlag BaseVoltage Transformer
title localName
installationDate damping
name initialLossOfLife efficiency nominalVoltage Winding mRID
description loadControl inertia
installationDate BaseVoltage
energyMinP b BusbarSection maxQ
dispReserveFlag Transformer
lotNumber localName
loadControl
TopologicalNode nominalVoltage
genControlMode b0name maxU
efficiency
Terminal mRID Winding mRID
name lotNumber initialP connectionType minQ
nameenergyMinP b
metrology TopologicalNode maxQ
mRID longPFTerminal description minU
genControlMode nameb0 name maxU
metrology lowControlLimit
name emergencyS operatingMode
VoltageLevel initialP connectionType
outageReport minQ
name lowerRampRate Asset g pathName
longPF description
purchasePrice minU
outageReport mRID Asset application g0 VoltageLevel phases
lowControlLimit emergencyS
readRequest operatingMode
Line
purchasePrice maxEconomicP category grounded r pathName
application lowerRampRate g
relayCapable
name readRequest maxOperatingP corporateCode insulationU r0 phases
category mRID serialNumber
g0 Line
relayCapable minEconomicP critical localName ratedS
ACLineSegment corporateCode maxEconomicP timeZoneOffset
grounded name r
serialNumber minOperatingP description mRID referencePriority
b0ch critical maxOperatingP utcNumber
insulationU r0
timeZoneOffset minimumOffTime initialCondition name type
bch description minEconomicP localName ratedS
utcNumber name initialLossOfLife normaIlyInService
ACLineSegment x referencePriority
g0ch initialCondition minOperatingP mRID
nominalP installationDate ConformingLoad pathName
b0ch x0type
gch initialLossOfLife minimumOffTime name
normaIlyInService localName customerCount phases
bch
ConformingLoad installationDate name normaIlyInService x
length normalPF lotNumber description r g0ch
customerCount localName nominalP pathName x0
ConnectivityNode
localName ratedGrossMaxP mRID mRID r0gch
description lotNumber normaIlyInService phases
mRID ratedGrossMinP manufacturedDat name ratedS
length
mRID mRID normalPF r
name ratedNetMaxP e pathName ratedU
localName SvCompensator
name manufacturedDat ratedGrossMaxP r0 ConnectivityNode
phases shortPF name pfixed rground
mRID Sections
pathName e ratedGrossMinP ratedS
r startupCost purchasePrice pfixedPct shortTermS
name continuousSections
pfixed name ratedNetMaxP ratedU
r0 startupTime serialNumber phases windingType
phases SvCompensator
pfixedPct purchasePrice shortPF rground
x utcNumber qfixed xr Sections
phases serialNumber startupCost shortTermS
x0 qfixedPct x0r0 continuousSections
qfixed utcNumber startupTime windingType xground
x
qfixedPct x
O
x0
Open Grid Systems
x0
xground
10
Work Management
name
corporateCode
kind Machine
critical
corporateCode
priority category
mRID baseQ
critical
name condenserP
description Machine
demandResponse
disconnect baseQ
description
baseP zPosition
name
coolantCondition
dstEnabled mRID
initialCondition
BusbarSection name
title localName
lotNumber localName
loadControl
efficiency
nameenergyMinP b
outageReport minQ
longPF description
purchasePrice minU
Line
relayCapable
g0 Line
grounded name r
insulationU r0
b0ch x0type
bch
ConnectivityNode
length
mRID Sections
x
qfixedPct x
O
x0
Open Grid Systems
x0
xground
11
Meter Data
name
corporateCode
kind Machine
critical
corporateCode
priority category
mRID baseQ
critical
name condenserP
description Machine
demandResponse
disconnect baseQ
description
baseP zPosition
name
coolantCondition
dstEnabled mRID
initialCondition
BusbarSection name
title localName
lotNumber localName
loadControl
efficiency
nameenergyMinP b
outageReport minQ
longPF description
purchasePrice minU
Line
relayCapable
g0 Line
grounded name r
insulationU r0
b0ch x0type
bch
ConnectivityNode
length
mRID Sections
x
qfixedPct x
O
x0
Open Grid Systems
x0
xground
12
Electrical Network
name
corporateCode
kind Machine
critical
corporateCode
priority category
mRID baseQ
critical
name condenserP
description Machine
demandResponse
disconnect baseQ
description
baseP zPosition
name
coolantCondition
dstEnabled mRID
initialCondition
BusbarSection name
title localName
lotNumber localName
loadControl
efficiency
nameenergyMinP b
outageReport minQ
longPF description
purchasePrice minU
Line
relayCapable
g0 Line
grounded name r
insulationU r0
b0ch x0type
bch
ConnectivityNode
length
mRID Sections
x
qfixedPct x
O
x0
Open Grid Systems
x0
xground
13
Restricted by Profiles
SvVoltage
BusbarSection BaseVoltage Synchronous TopologicalNode
v
name nominalVoltage Machine name
angle
baseQ
Transformer condenserP
VoltageLevel SvPowerFlow
Winding coolantCondition
b p
coolantType q
b0 damping
Line
connectionType inertia
name SvTapStep
description localName
emergencyS continuousPosition
GeneratingUnit mRID
g maxQ
allocSpinResP SvCompensator
g0 maxU
autoCntrlMarginP Sections
grounded minQ
baseP continuousSections
insulationU minU
controlDeadband
localName operatingMode
controlPulseHigh
mRID pathName
controlPulseLow
name phases
description
normaIlyInService r
dispReserveFlag
pathName r0
efficiency
phases ratedS
energyMinP
r referencePriority
genControlMode
r0 type
initialP
ratedS x
longPF
ratedU x0
lowControlLimit
rground
lowerRampRate
shortTermS
mRID ACLineSegment
windingType
maxEconomicP b0ch
x
maxOperatingP bch
x0
minEconomicP g0ch
xground
minOperatingP gch
minimumOffTime Terminal length
name name localName
nominalP mRID
normaIlyInService name
normalPF ConnectivityNode phases
ratedGrossMaxP r
ratedGrossMinP r0
ratedNetMaxP x
x0
O
shortPF
startupCost
startupTime Open Grid Systems
14
SvVoltage
v
angle
baseQ
Transformer maxQ
VoltageLevel SvPowerFlow
Winding maxU p
b minQ q
g minU
Line
name r
name SvTapStep
phases ratedS continuousPosition
GeneratingUnit r referencePriority
baseP ratedS type SvCompensator
initialP ratedU x Sections
maxOperatingP x
continuousSections
minOperatingP ACLineSegment
name Terminal bch
nominalP name gch
length
name
ConnectivityNode phases
r
x
O Open Grid Systems

14
SvVoltage
v
angle
baseQ
VoltageLevel
b
Transformer
Winding
maxQ
maxU Topology p
SvPowerFlow
minQ q
g minU
Line
name r
name SvTapStep
phases ratedS continuousPosition
GeneratingUnit r referencePriority
baseP ratedS type SvCompensator
initialP ratedU x Sections
maxOperatingP x
continuousSections
minOperatingP ACLineSegment
State
name Terminal bch
nominalP name gch
length
name
ConnectivityNode phases
r
x The CIM should be
Equipment viewed in context
Profiles use 20-30
classes with a subset of
attributes not 700+
classes
O Open Grid Systems

14
Misunderstanding 3:
CIM is a Database

It’s only a model...
The CIM is an information model
It can be implemented in any number of ways, but it is
defined as an implementation-agnostic model
You can derive a database schema from the CIM
How you derive that schema can be dependent on a
number of factors
The structure of the schema and thus the structure of
the database will vary from system to system
O Open Grid Systems

16
CIM Database
When someone implements a CIM Database what they
really mean is:
The schema has been derived from the CIM and can
hold data defined by the CIM in a structured way
The database itself is not compliant with an IEC
standard (because there is no IEC standard that
defines what a CIM database is!)
They can import and export data in a CIM structure
from the database
These interfaces however can be compliant with IEC
standards
O Open Grid Systems
17
Applying the CIM
You can derive a number of useful structures from the
CIM:
Database schemas
Object classes for a variety of languages (Java, C++,
C#, Python etc.)
Interface definitions and their data structures (e.g.
Google Protocol Bu!ers)
File formats (including proprietary text and binary
formats or XML)
O Open Grid Systems

18
Misunderstanding 4:
CIM is an XML format

CIM Data
The CIM defines the structure of data, not a format
We can get CIM data from any number of sources
File Import/
File
Export Application
Database Application
Database Interface
Data Network Application

Stream Interface
O Open Grid Systems

20
CIM RDF XML
The IEC standardises the mapping of CIM into RDF XML
in IEC 61970-452
CIM RDF XML (commonly known as CIM XML) is one
way of serialising CIM data and is used primarily for
large network model exchanges
VoltageLevel
name VLA
highVoltageLimit 35.0
lowVoltageLimit 31.0
O Open Grid Systems

21
CIM RDF XML
The IEC standardises the mapping of CIM into RDF XML
in IEC 61970-452
CIM RDF XML (commonly known as CIM XML) is one
way of serialising CIM data and is used primarily for
large network model exchanges VoltageLevel
name VLA
highVoltageLimit 35.0
lowVoltageLimit 31.0
<cim:VoltageLevel rdf:ID=”_xyz987654321”>
<cim:IdentifiedObject.name>VLA</cim:IdentifiedObject.name>
<cim:VoltageLevel.highVoltageLevel
>35.0</cim:VoltageLevel.highVoltageLevel>
<cim:VoltageLevel.lowVoltageLevel
>31.0</cim:VoltageLevel.lowVoltageLevel>
<cim:VoltageLevel.BaseVoltage rdf:resource=”#_jkl567890”/>
</cim:VoltageLevel>
O Open Grid Systems

21
XML Schema
The same data can be serialised as hierarchical XML
Schema Definition (XSD) message
The same data, defined by the same information
model, but serialised in a di!erent format
The IEC is standardising Naming and Design Rules
(NDR) that define how XSDs are derived from the CIM
CIM XML Schema messages are designed for
Enterprise Service Bus environments and systems
integration
O Open Grid Systems

22
<cim:VoltageLevel>
<cim:mRID>_xyz987654321</cim:mRID>
<cim:name>VLA</cim:name>
<cim:highVoltageLevel>35.0</cim:highVoltageLevel>
<cim:lowVoltageLevel>31.0</cim:lowVoltageLevel>
<cim:BaseVoltage>
<cim:nominalVoltage>33.0</cim:nominalVoltage>
</cim:BaseVoltage>
<cim:EnergyConsumer>
<cim:mRID>_abcdef0123456789</cim:mRID>
<cim:name>Load A</cim:name>
<cim:description>Pump motor</cim:description>
<cim:phases>ABCN</cim:phases>
<cim:pFixed>0.03</cim:pFixed>
<cim:qFixed>0.015</cim:qFixed>
<cim:customerCount>39</cim:customerCount>
<cim:Terminal>
<cim:mRID>_pqrs34567890</cim:mRID>
<cim:name>Load A Terminal</cim:name>
</cim:Terminal>
</cim:EnergyConsumer>
</cim:VoltageLevel>
23
CIM XML
CIM RDF XML and XML Schema are serialisation

formats for CIM data
While CIM XML is CIM, the CIM is not CIM XML
In the future other CIM serialisation formats may be
standardised
As we have seen, the CIM is more than just CIM XML!
O Open Grid Systems

24
Misunderstanding 5:
My Software is CIM Compliant

What is Compliance?
There are few terms that will cause more confusion
than claiming software is CIM Compliant
Multiple vendors may claim their software is CIM
compliant but they cannot talk to each other
For something to be compliant with a standard it must
be tested against it and demonstrate it can
interoperate with products from other companies
As we have seen the CIM is an information model, so
how can you test interoperability with a model?
O Open Grid Systems

26
Profile Compliance
A number of standards are derived from the overall CIM
model to form contextual profiles
These profiles use subsets of the CIM model along
with a standard serialisation format (CIM RDF XML or
XSD messages)
Vendors then demonstrate that they can import and/or
export data defined by that profile
A product can be compliant with a CIM-derived
interface standard, not the CIM itself
O Open Grid Systems

27
CIM Profiles
Recent Interoperability tests have tested:
IEC61970-452 & IEC61970-456 for Static
Operational network model exchange using CIM RDF
XML (IEC61970-552)
IEC61968-13 for distribution network model
exchange using CIM RDF XML
IEC61968-9 interfaces for meter reading and control
using XML Schema messages
ENTSO-E CIM RDF XML for transmission model
exchange in Europe
O Open Grid Systems
28
CIM Compliance
Ask your vendor which profiles they have tested in an

EPRI or UCA Interoperability test next time they claim
to be CIM compliant...
O Open Grid Systems

29
Misunderstanding 6:
It’s not a standard if you extend it

Why Extend?
While the CIM is large and extensive information
model, during projects there is often a need to extend
the model
There can be a number of reasons to extend the
standard:
Accommodating legacy data
Introducing new application areas
Refining the level of detail of existing classes
Extending existing classes to cover related but
currently un-modelled components
O Open Grid Systems

31
Legacy Data Example
Supposing we are mapping the data in Equipment
a legacy EMS to CIM

The equipment entries and attributes
are mapping to the CIM class structure
ConductingEquipment
Every piece of equipment, however,

has an attribute fromABCSystem, that
marks whether the entry came from a RegulatingCondEq
previous system migration project
This data must be retained for
compatibility reasons, but there is no
SynchronousMachine
obvious mapping to a CIM class
O Open Grid Systems
32
Legacy Data Example
PowerSystemResource
The separation of extensions

from standards makes it Equipment
ExtEquipment
fromABCSystem
easier to maintain
compatibility with standards-
based interfaces
ConductingEquipment
The exporter can be told to

ignore any attributes that are
inherited from an Extended RegulatingCondEq
class when exporting
SynchronousMachine
O Open Grid Systems

33
Extending the Standard
Another scenario requiring extensions is when a new
application area must be modelled
The IEC 69170-301 classes model the electrical
network
Take a scenario where a company wants to include
some modelling of the gas network along with their
electrical model
They wish the models to be integrated so they can
more closely integrate their gas and electrical status
monitoring equipment
O Open Grid Systems
34
Geographical
Region
IdentifiedObject
mRID
aliasName
SubGeographical localName
Region pathName
name
description
Substation
Equipment PowerSystemResource
ExtSubstation
Container
VoltageLevel
ExtGasPressureLevel ExtEquipment
Pressure Equipment
fromABCSystem
ExtOriginalSource
company
ExtGasPipe ConductingEquipment system
Diamater ExtGasTransferEquipment
PressureRating
GeneratingUnit RegulatingCondEq
ExtGasometer
Capacity
ExtGasSupplyPoint
FlowRate
ThermalGeneratingUnit
SynchronousMachine
ExtGasFiredGenerating
Unit
O
ExtNaturalGas
Open Grid Systems

FossilFuel
CalorificValue
35
Internal vs Global Extensions
When the CIM is extended the resulting extensions can
be considered either Internal or Global
Internal extensions cover extensions to model data
that would not be considered suitable for inclusion in
future revisions of the standard
Global extensions are extensions that would be
considered relevant to the majority of utilities and
thus suitable for inclusion in the standard
In this case the changes would be considered by an IEC
working group and if approved, included in a future
release
O Open Grid Systems
36
Geographical
Region
IdentifiedObject
mRID
aliasName
Region pathName
name
description
Substation
ExtSubstation
Container
Global
VoltageLevel
Extensions
ExtGasPressureLevel ExtEquipment
Pressure Equipment
fromABCSystem
ExtOriginalSource
company
ExtGasPipe ConductingEquipment system
Diamater ExtGasTransferEquipment
PressureRating
Internal
Extensions
ExtGasometer
Capacity
ExtGasSupplyPoint
FlowRate
SynchronousMachine
ExtGasFiredGenerating
Unit
O
ExtNaturalGas
Open Grid Systems

FossilFuel
CalorificValue
37
Geographical
Region
IdentifiedObject
mRID
aliasName
Region pathName
name
description
We now have only a couple

Substation
of classes as internal
extensions, the rest are Container
part of the standard

VoltageLevel
GasPressureLevel ExtEquipment
Pressure Equipment
fromABCSystem
ExtOriginalSource
company
GasPipe ConductingEquipment system
Diamater GasTransferEquipment
PressureRating
Internal
Extensions
Gasometer
Capacity
GasSupplyPoint
FlowRate
SynchronousMachine
GasFiredGenerating
Unit
O
NaturalGas
Open Grid Systems

FossilFuel
CalorificValue
38
Questions?
alan@opengridsystems.com

CIM Misunderstandings PDF

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

CIM Misunderstandings PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

Addressing Misunderstandings of the CIM

Alan McMorran B.Eng Ph.D

OG Open Grid Systems

2 OG Open Grid Systems

O Open Grid Systems

O Open Grid Systems

Interface Interface Interface Interface Interface Interface Interface

IEC 61968/61970 Compliant Middleware Services

Interface Interface Interface Interface Interface Interface Interface

NE CS MR ACT FIN PRM HR

Electric Distribution Network Generation and Transmission Management,

O Open Grid Systems

O Open Grid Systems

O Open Grid Systems

8 OG Open Grid Systems

O Open Grid Systems

O Open Grid Systems

O Open Grid Systems

15 OG Open Grid Systems

O Open Grid Systems

O Open Grid Systems

19 OG Open Grid Systems

Data Network Application

O Open Grid Systems

O Open Grid Systems

O Open Grid Systems

O Open Grid Systems

CIM RDF XML and XML Schema are serialisation

O Open Grid Systems

25 OG Open Grid Systems

O Open Grid Systems

O Open Grid Systems

Ask your vendor which profiles they have tested in an

O Open Grid Systems

30 OG Open Grid Systems

O Open Grid Systems

a legacy EMS to CIM

Every piece of equipment, however,

The separation of extensions

The exporter can be told to

class when exporting

O Open Grid Systems

Open Grid Systems

Open Grid Systems

We now have only a couple

part of the standard

Open Grid Systems

Anda mungkin juga menyukai