CIM Standards Overview

And Its Role in the Utility Enterprise - Part 2

CIM Users Group

Austin, Texas
15 November 2011
Terry Saxton

1
Presentation Contents
• 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

2
 Next - Context Layer
Information and Semantic Models

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 Syntax Message syntax describes format for

Message/File instance data
Format • Can re-label elements
(XSD, RDF • Change associations to define single structure for
Schema, OWL) message payloads
• Mappings to various technologies can be defined
 From •Information/
•Abstract
•Model
Information Semantic
Model
Model to
Syntactic
•Context/
Model Profiles

•Message
UML World Assembly

XML Syntactic World •<?xml version="1.0" encoding="UTF-8"?>

•<xsd:element
name=« MT_EnergyTransaction">
•<xsd:sequence>

•Message • <xsd:element
name=« EnergyTransaction"/> •Syntactic
• <xsd:sequence>
Syntax •
•
<xsd:element name=« Name"/>
<xsd:element name=« Type"/> •Model
• </xsd:sequence>
• </xsd:element>
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

5
61970 Profiles Currently Defined
• Equipment • Topology
– Identifies equipment, describes – The result of topology
basic characteristics, and processing. i.e. Description of
electrical connectivity that how equipment connects into
would be input to topology buses and how buses
processing makeup connected systems
• Schedules • State Variables
– Describes input to functions – Result of a state estimator or
that derive parameters for a power flow, or the starting
specific point in time conditions of state variables
• Measurement Specs • Dynamics
– Describes how SCADA will – Adds dynamics to static
obtain measurements and what network model for running
equipment objects are system simulations
measured
• Schematic Layouts
• Measurement Set – Describes how equipment
– The set of SCADA values for objects are placed on
measurements for a particular schematic diagrams
point in time
61970-452 Static Transmission
Network Model Profiles
• Also known as Common Power System Model (CPSM)
• Many Interoperability (IOP) tests since year 2000
• In use in many countries
• 61968-13 distribution model (CDPSM) based on these profiles as well
Plus 61970-451 Measurement and Control
and -456 Solved System State Profiles
61970-451 61970-456 Profiles
Profile
State
Variables Adds SCADA
Measurement
and Control Adds steady state
Topology
solution of power
system case
produced by
Measurement power flow
Specifications applications

61970-452 Equipment
Profiles Model Dependencies via
references to
CPSM Part 452
Connectivity Schedules
Plus 61970-451 Measurement and Control
and -456 Solved System State Profiles
61970-451 61970-456 Profiles
Profile
State
Variables
Measurement
and Control
Topology

Measurement Adds dynamic

Specifications models used in
system simulation
61970-452 Equipment
Profiles Model
Dependencies via
references to
Connectivity Schedules CPSM Part 452
Plus 61970-451 Measurement and Control
and -456 Solved System State Profiles
61970-451 61970-456 Profiles
Profile
State
Variables
Measurement Adds
and Control diagram
Topology
layout info
for
schematic
Measurement
data
Specifications
Dependen
61970-452 Equipment - cies via
Profiles Model
reference
to CPSM
Connectivity Schedules Part 452
Plus 61970-453 Diagram Layout
Profile
61970-456 Profiles Future 61970-
457 Profile Adds
State diagram
Variables Dynamic layout info
Models
for
Measurement
Topology schematic
Set
data

61970-453 Dependen
Measurement Profile
Specifications
- cies via
reference
61970-452 Equipment Diagram
to CPSM
Profiles Model Layout Part 452
Boundary
Objects
Common Schedules
Objects
Typical Workflow for Model
Exchange

•E1 •T1 •S1

•S2

•T1.1 •S3

•Time
•E1.1 •S4

•T1.2

•S5

•T1.3
•S6

•Profile
•S7
•Full model
•DifferentialModel
•Predecessor
•S8
•DependsOnModel
 TC57 CIM Standards
for Power System Model Exchange
•Information and Semantic Models

• Information Model
•Conforms to • Generalized model of all utility objects and their
IEC 61970-301 CIM •CIM UML relationships
• Application independent, but defines all concepts
needed for any application

•Context
•Conforms to •Contextual layer restricts information
collection of model
Standard
4xx Profiles
•Profiles •
•
Specifies which part of CIM is used for given profile
Mandatory and optional
• Restrictions
• But cannot add to information model

•Message Syntax •Message syntax describes format for

•Conforms to
•Message/File instance data
IEC 61970-552-4 Format • Can re-label elements
CIM XML Model Exchange Format (XSD, RDF • Change associations to define single structure for
Schema, OWL) message payloads
• Mappings to various technologies can be defined
Example of Use of CIM to Define Standard
Interfaces
Working Group 14:
Establishing A Common Language For Enterprise Application
Integration In the IEC 61968 Series of Standards

Utility Control
Center

Network Utility
Customer Business
Expansion
Inquiry
Planning Systems
(ERP, Billing,
Energy trading,
Meter other systems)
Reading &
Network IEC 61968 Control
Distribution
Distribution Automation
Automation Operation Compliant Corporate
Interface LAN
Architecture

Records Operational
& Asset Planning &
Management Maintenance Optimization
Substation
Substation Protection,
Protection, &
Monitoring
Monitoring and
and Control
Control
Construction

RTU
RTU Communications
Communications
•Information:
•http://www.ucainternational.org/
•http://www.iec.ch
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
 The Business Sub-Function Level of the IRM for IEC 61968 Scope

•Network Operations •Records & Asset

•Management
•Network Operations •Operation Statistics •Substation & Network •Operational •Maintenance and
•Monitoring (NMON) •& Reporting (OST) •Inventory (EINV) Planning •Construction
•Network Control •Network Calculations •Geographical
•&•Network
Optimization
Operation
•(CTL) •- Real Time (CLC) •Maintenance & •Scheduling
•Inventory (GINV) •Simulation (SIM) •Inspection (MAI) •& Dispatch (SCH)
•Fault Management •Dispatcher Training •General inventory •Switch Action •Construction WMS •Field
•(FLT) (TRN) management (GIM) •Scheduling (SSC) (CON) •Recording (FRD)
•Operational Feedback •Asset Investment •Power Import Sched. •Design &
•Analysis (OFA) •Planning (AIP) •& Optimization (IMP) •Estimate (DGN)

•Application Integration Infrastructure

•Network Extension •Customer •Meter Reading & Control • External Systems

•Planning •Support •Meter Reading •Meter Data
•(RMR) Management IMDM)
•Network •Customer Service
•Calculations (NCLC) •(CSRV) •Advanced Metering •Metering System
Infrastructure (AMI) •(MS)
•Project Definition •Trouble Call
•(PRJ) •Management (TCM)
•Demand Response •Meter Maintenance
•(DR) (MM)
•Construction •Point Of Sale
•Supervision (CSP) •(POS)
•Load Control
•Meter Data (MD)
•(LDC)
•Compliance
•Management (CMPL) •Meter Operations
•(MOP)
The IEC 61968 Basic Message Structure
Message Header
 •WG14 Status
Work Overview

Publication No. Description Status Responsible To IEC Next Step

WG14 Lead

61968-01 Interface Architecture IS Shawn Hu July 2010 MCR

and General
Requirements
61968-01-1 ESB Implementation Working Scott Neumann July 2010 NWIP & CD
Profile Draft

61968-01-2 Web Services Working Mark Ortiz July 2010 NWIP & CD
Draft

61968-02 Glossary Technical David Haynes June 2009 MCR

Report

61968-03 Network Operations IS Bruce Scovill July 2011 MCR

61968-04 Records & Asset IS Jon Fairchild July 2011 MCR

Management

22
 •WG14 Status
Work Overview

Publication Description Status Responsible To IEC Next Step

No. WG14 Lead

61968-05 Operational Working Draft Jim Waight TBD Postponed until experts from 5
countries are provided. Also,
Planning and part 5 should be based on the
Optimization revised parts 3.
61968-06 Maintenance and Working Draft Nada July 2011 NWIP & CD
Construction Reinprecht

61968-07 Network Extension Working Draft Jim Waight TBD Postponed until experts from 5
countries are provided. Also,
Planning part 7 should be based on the
revised parts 3 & 4 and
coordinated with part 6 and
WG13.
61968-08 Customer Support NWIP & CD Larry Clark and Sept 2010 Work to recast document to new
format& issue CD. Get experts
Mark Ortiz from 5 countries to develop CDV,
which is due Dec 2011..

61968-09 Meter Reading and IS Scott Neumann July 2011 MCR

Control

23
 •WG14 Status
Work Overview

Publication No. Description Status Responsible To IEC Next Step

WG14 Lead

61968-11 Common Information FDIS Tanja Kostic March 2011 MCR

Model for DMS

61968-12 Compliance and Working Margaret As tests are NWIP & Technical
Interoperability Draft Goodrich performed Report
Testing
61968-13 Common Distribution IS Eric Lambert January 2011 MCR
Power System Model

61968-14-1 Mapping between Working Gary In planning and

MultiSpeak 4.0 and IEC Draft McNaughton recruitment stage
61968, parts 3 through
10
61968-14-2 A CIM profile for Working Gary In planning and
MultiSpeak 4.0, one Draft McNaughton recruitment stage
profile for IEC 61968
parts 3 through10

24
 Next – Message Syntax
Information and Semantic Models

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 Syntax Message syntax describes format for

Message/File instance data
Format • Can re-label elements
(XSD, RDF • Change associations to define single structure for
Schema, OWL) message payloads
• Mappings to various technologies can be defined
Implementation Syntax – XML Schema

• Example of use of XML Schema

• Mapping Proprietary EMS Interfaces to the CIM
– Provide enterprise system access to transformer data

26
Mapping EMS Interfaces to the CIM –
User access to transformer data

• EMS Native Interface attributes:

– TRANS_NAME – The Transformer’s name
– WINDINGA_R – The Transformer’s primary winding resistance
– WINDINGA_X – The Transformer’s primary winding reactance
– WINDINGB_R – The Transformer’s secondary winding resistance
– WINDINGB_X – The Transformer’s secondary winding reactance
– WINDINGA_V – The Transformer’s primary winding voltage
– WINDINGB_V – The Transformer’s secondary winding voltage

27
Transformer Class Diagram in CIM

28
CIM Interface Mapping
- Beginnings of Profile/Message Payload Definition
Two different interface Aggregation changed
attributes (WINDINGA_R and from 0..n to 2
WINDINGB_R) map to same
CIM attribute Multiplicity
changed from
0..1 to 1

Multiplicity
changed from
0..1 to 1

29
Message Payload in UML

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

30
XML Schema of CIM
• An XML Schema of the CIM can be
autogenerated from UML models with third party
tools
– A list and description of available tools is on the
• The CIM classes and attributes are used to
define tags
• Then the CIM can be shown in XML as well as
UML
• Example is PowerTransformer

31
Transformer Model Diagram from
61970-301CIM Base
PowerSystemResource
(from Core)

Equipment
PowerTransformer TapChanger
(from Core)

+PowerTransformer 1 1 0..n 0..n

+TapChangers +TapChangers
+HeatExchanger +MemberOf_PowerTransformer
0..1
HeatExchanger

+Contains_TransformerWindings +RegulationSchedule
1..n 0..1
1
ConductingEquipment TransformerWinding RegulationSchedule
(from Core)
+TransformerWinding
0..n 1
+To_TransformeWindings +From_TransformerWinding

+From_WindingTests
+To_WindingTest
1 0..n
WindingTest

32
XML Schema for
Transformer
Message

33
Sample Transformer Interface
Message Payload in XML
<cim:PowerTransformer>
<cim:Naming.name>Transformer SGT1</cim:Naming.name>
<cim:PowerTransformer.Contains_TransformerWindings>
<cim:TransformerWinding.r>0.23</cim:TransformerWinding.r>
<cim:TransformerWinding.x>0.78</cim:TransformerWinding.x>
<cim:TransformerWinding.windingType>WindingType.primary
</cim:TransformerWinding.windingType>
<cim:Equipment.MemberOf_EquipmentContainer>
<cim:VoltageLevel.BaseVoltage>
<cim:BaseVoltage.nominaVoltage>400
</cim:BaseVoltage.nominalVoltage>
</cim:VoltageLevel.BaseVoltage>
</cim:Equipment.MemberOf_EquipmenContainer>
</cim:PowerTransformer.Contains_TransformerWindings>
<cim:PowerTransformer.Contains_TransformerWindings>
<cim:TransformerWinding.r>0.46</cim:TransformerWinding.r>
<cim:TransformerWinding.x>0.87</cim:TransformerWinding.x>
<cim:TransformerWinding.windingType>WindingType.secondary
</cim:TransformerWinding.windingType>
<cim:Equipment.MemberOf_EquipmentContainer>
<cim:VoltageLevel.BaseVoltage>
<cim:BaseVoltage.nominaVoltage>275
</cim:BaseVoltage.nominalVoltage>
</cim:VoltageLevel.BaseVoltage>
</cim:Equipment.MemberOf_EquipmenContainer>
</cim:PowerTransformer.Contains_TransformerWindings>
</cim:PowerTransformer>

34
XML Implementation Technologies
• XML Schema
– Used for generation of message payloads for system
interfaces in system integration use cases
• RDF Schema
– Used for exchange of power system models

35
Big Issue

• “Although we can swap our documents with

each other through XML, we still haven’t a
clue what they mean.”
» (“Professional XML Meta Data,” by Kal Ahmed, et al.)

• Resource Description Framework (RDF) Is

W3C’s Means To Resolve This.

36
 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

[Courtesy Of Leila Schneburger]

37
 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/

38
Technical Approach (Cont.)
• Namespaces
- provide a simple method for qualifying element and attribute names
used in XML documents by associating them with namespaces
identified by URI references:
– Status: WC3 Recommendation 14-January-1999
• http://www.w3.org/TR/REC-xml-names/

• URI (Uniform Resource Identifiers)

- provide a simple and extensible means for identifying a resource:
– Status: Internet RFC August 1998
• ftp://ftp.isi.edu/in-notes/rfc2396.txt

39
CIM UML=>RDF Schema=>RDBMS

UML. RDF Relational

Model
Object Resource Tuple (i.e. row)
Attribute or Property Attribute (i.e.
association column) or
foreign key
Class Class Relation (i.e.
table)
Resource Tuple value
Description
URI Key value
Value Field value
[Courtesy Of Leila Schneburger]

40
Simple Network Example

SS2

400KV
SS1-SS2
SS1
Cable1 Cable2
12345 MW

Cable3
12345 KV
BB1
12345 MW

SS4
T1

110KV

41
Simple Network Connectivity Modeled with
CIM Topology
T1 T2
SS 2
400KV
BB1
Volts SS1-SS2
(KV) P1 SS 1
(M W)

CN5 DC2 CN4 CN3 Cable1 CN2 Cable2 CN1

BR1

BR3

Cable3
P2
(M W) CN6

TW 1

CN8
T1

TW 2
SS 4

CN7
BDD-RSK2
110KV

42
 Siemens 100 Bus Network Model
in RDF
Top of RDF Schema version of Siemens 100 bus model

<?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><cim:ACLineSegment rdf:ID="_E83B07FE54A945539A95FD2DB2CDD4FC">
<cim:Naming.name>BKR-TUR</cim:Naming.name><cim:Conductor.bch>0.39</cim:Conductor.bch><cim:Conductor.x>4.1262
</cim:Conductor.x><cim:Conductor.r>1.0051</cim:Conductor.r></cim:ACLineSegment><cim:Terminal
rdf:ID="_E273D9258F9D42FCA018B274BE6F5FA6"><cim:Naming.name>T2</cim:Naming.name><cim:Terminal.ConnectivityNode
rdf:resource="#_576B6D171B174B8BACB7AFF7289D0434"/><cim:Terminal.ConductingEquipment
rdf:resource="#_E83B07FE54A945539A95FD2DB2CDD4FC"/></cim:Terminal><cim:Terminal
rdf:ID="_B23175B9692441AFBD2C581E86300550"><cim:Naming.name>T1</cim:Naming.name><cim:Terminal.ConnectivityNode
rdf:resource="#_A69ED82F4EB4B65A8840CDD1E064887"/><cim:Terminal.ConductingEquipment
rdf:resource="#_E83B07FE54A945539A95FD2DB2CDD4FC"/></cim:Terminal><cim:Unit rdf:ID="_
5EAAD38A446E429E9905FAC32070D6FC"><cim:Naming.name>Amperes</cim:Naming.name></cim:Unit><cim:ACLineSegment
rdf:ID="_329884C01F6B4DC08492F711088538D6"><cim:Naming.name>CRS-ANY1</cim:Naming.name><cim:Conductor.bch>5.03
</cim:Conductor.bch><cim:Conductor.x>12.90761</cim:Conductor.x><cim:Conductor.r>1.2696</cim:Conductor.r></

43
 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>

44
 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>

45
 Containment in RDF
Substation VOL
Substation with
VOL 230 230
with KV voltage level and
KV voltage Bay 240W79
level with 240W79
and Bay Breaker CB
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>
Further down in document
<cim:Bay rdf:ID="_7DBBA5E32C834B6AB08BB6FB07155D46">
<cim:Naming.name>240W79</cim:Naming.name>
<cim:Bay.MemberOf_VoltageLevel rdf:resource="#_C20AF84C15E047218D75C47870C34C87"/>
</cim:Bay>

<cim:Breaker rdf:ID="_4A74B55420834E40B85F0304B6F9ADF8">
<cim:Naming.name>CB</cim:Naming.name>
<cim:Switch.normalOpen>false</cim:Switch.normalOpen>
<cim:Equipment.MemberOf_EquipmentContainer rdf:resource="#_7DBBA5E32C834B6AB08BB6FB07155D46"/>
</cim:Breaker>

46
 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>

47
Implementation Syntax – WG13 61970

• Part 501 specifies the translation of the CIM in UML form

into a machine readable format as expressed in the
Extensible Markup Language (XML) representation of
that schema using the Resource Description Framework
(RDF) Schema specification language
– The resulting CIM RDF schema supports CIM Model Exchange
specifications, as presented in IEC 61970-452 and others
• Part 552 describes the CIM XML format at a level for
implementation to support the model exchange
requirements in IEC 61970-452
– This standard relies upon the CIM RDF Schema of IEC 61970-
501

48
Basics: Schema from CIM

CIM Power
(in UML) System Data

CIM as

Exporter
Enterprise XML/RDF specifies
Architect Schema

UML Power
to RDF System Data
Transformers as
XML/RDF

49
How Are CIM Standards Used?
• Unlike most standards we use
– Ex: ICCP/TASE.2 Communication Protocol standard
– Fixed functionality, very stable, easy to test compliance, but inflexible
• CIM standards can be strictly applied and tested for compliance
– Ex: CIM/XML Power system model exchange
– Product interfaces can be developed and tested for compliance
– Subject of several EPRI-sponsored interoperability tests for specific
interface definition

50
 Example: Power Flow Network Model Exchange

Information and Semantic Models

Information Model
• Defines all concepts needed for
Conforms to exchange of operational load flow
IEC 61970-301 CIM CIM UML models
– Reused parts
– New extensions

Context
Contextual layer restricts information model
Conforms to • Specifies which part of CIM is used for
IEC 61970-452, 453, Power System
static/dynamic model exchange
456, others Model Profile • Mandatory and optional
Model Exchange Group • Restrictions
Profile • But cannot add to information model

Message Syntax File syntax

Conforms to • Can re-label elements
IEC 61970-501 and -552 CIM/RDF • Change associations to define single
CIM XML Model Exchange Format Schema structure for message payloads
• Mappings to various technologies can
be defined

51
Ex: Power Flow Network Model Exchange
Information Model
• Defines all concepts needed for
Conforms to CIM UML exchange of operational load flow
IEC 61970-301 CIM models
– Reused parts
– New extensions

Contextual layer restricts information model

Conforms to • Specifies which part of CIM is used for
Concrete IEC 61970-452
Profile static model exchange
Message Model Exchange • Mandatory and optional
Profile • Restrictions
• But cannot add to information model

File syntax
Conforms to • Can re-label elements
IEC 61970-552 CIM/XML
RDFSchema • Change associations to define single
CIM XML Model Exchange Format structure for message payloads
• Mappings to various technologies can
be defined

52
How Are CIM Standards Used?
• Unlike most standards that we are used to
– Ex: IDDP/TASE.2 Communication Protocol standard
– Fixed functionality, very stable, easy to test compliance, but inflexible
• CIM standards can be strictly applied and tested for compliance
– Ex: CIM/XML Power system model exchange
– Product interfaces can be developed and tested for compliance
– Subject of several EPRI-sponsored interoperability tests for specific
interface definition
• CIM can also be used as a starter kit
– Basis for an Enterprise Semantic Model (ESM) which includes other
models/semantics from other sources
– Ex: Sempra Information Model (SIM)
– Interfaces are usually project-defined, so no standard tests
– System interfaces are managed and tested for each project

53
GridWise Interoperability Framework

Role of CIM

54
 Enterprise Semantic Models
– CIM + Other Industry Standards

Merge – resolve Other

Private UML
CIM UML semantic Information
Extensions differences Models

Context
Contextual layer restricts information model
• Constrain or modify data types
Profile • Cardinality (may make mandatory)
• Cannot add to information model

Message Syntax
Message/data syntax describes format for instance
Schemas data
XSD, RDFS, • Can re-label elements
DDL • Change associations to define single structure for
message payloads
• Mappings to various technologies can be defined

55
Building and Using an ESM for Generating
Canonicals (XSDs, DDLs, others)

Semantic Formalization Semantic Consistency

Existing Terminology
and Metadata

3) Generate Canonicals
1) Establish Vocabulary 2) Develop ESM •Syntactically and semantically
•Control Content •Model using vocabulary terms consistent canonical models
•Collaborate •Refine context
•Identify and refine semantics
Context Refinement

Compliments Xtensible MD3i

56
 Role of Enterprise Semantic Model
Application Process Business
Open Information Integration Intelligence
Standards
BPM/Workflow
Definitions
Business

Enterprise
Semantic Enterprise Integration Platforms
Model

Applications
Metadata

57
 Let’s Apply to a Utility Project
- Interface Architecture

Other
CIM UML
CIM UML Bridge Information
Extensions Models

Context
Profile 1
System Interface Profile 1
Profile 1 Profile 2 Profile 3
Design
Document

Interface Syntax
Message CIM/RDF
DDL
XML Schema Schema

58
Ex: Project Interaction Test

Conforms to Enterprise Semantic Model

Utility ESM ESM • Defines all concepts needed for
Enterprise
– Reused parts
– New extensions for project

Contextual layer restricts ESM

Conforms to • Specifies which part of ESM is used for
Concrete Profiles defined specific system interaction
Message for each
Profile • Mandatory and optional
system interaction • Restrictions
• But cannot add to information model

File syntax
Conforms to • Can re-label elements
WSDLs and Message XML • Change associations to define single
Schema structure for message payloads
XML Schemas • Mappings to various technologies can
be defined

59
Project Integration
Architecture

60
Data Architecture
– Model

CIM CIS OTHER

REFEFENCE
MODELS

SEMPRA Semantic Model

MODEL

MESSAGES
Business Business Business
Entity Entity Entity

SCHEMAS
DB Schema XML Schema

61
Use of ESM to Implement a Service Oriented
Architecture (SOA)

• CAISO designed a new power market system

– Multi-year program that involved many vendors, new systems, as
well as numerous legacy systems
• Includes EMS, Full Network Model, Outage Management, PI
Historian, Market Systems, many others
• External interfaces to Market Participants included
• Integration Competency Center decided on a Service
Oriented Architecture (SOA) for the integration framework
– Require all new applications and systems to be “Integration
Ready” with service-enabled interfaces
– Use only standard CAISO-defined services
– Payloads based on the CIM
– Based on Web services
– CIM and Model Driven Integration (MDI) methodology used to
define information exchange

62
Interface Examples:
Interface Type Example Implemented Utilized by Description
by
Information submitBid(XML) Vendor Enterprise These interfaces are for creating
Creation or modifying information within a
system of record.

Information publishCleanBidSet(XML) CAISO Vendor These interfaces are for

Transfer transferring information and
releasing custody.

Information receiveCleanBidSet(XML) Vendor EAI These interfaces are implemented

Interest by vendors to allow systems to
receive information as it becomes
available. This indicates a
subscription type interest in data.

Information getResourceInfo(XML) Vendor Enterprise These interfaces are implemented

Sharing XML by the vendors to surface
information currently within
custody to the enterprise.

(Slide from Stipe Fustar, KEMA)

63
System A Integration Layer
WS receiveMarketMeterData WS broadcastMarketMeterData

retrieveMarketMeterData WS PI

WS receiveMarketMeterData WS broadcastMarketMeterData

BITS
retrieveMarketInterchange WS

broadcastInvoiceData WS receiveInvoiceData WS

WS broadcastStatusInvoiceData

broadcastGeneralLedgerData WS receiveGeneralLedgerData WS
MC

(Slide from Stipe Fustar, KEMA)

64
(Slide from Stipe Fustar, KEMA)
65
(Slide from Stipe Fustar, KEMA)
66
CAISO Project Statistics
22 Systems
• Dispatch System • Default Energy Bids • OASIS
• MP Report Interface • Real Time Metering • Interchange Scheduling
• Load Forecast System
• Transmission Capacity • Adjusted Metering
• Congestion Revenue Rights
Calculator • Market Participants
• Real Time Nodal System – Bidding
• Intermittent Resources
• Settlement and Market – Market Results • Compliance
Clearing – Settlement • RMR Validation
• Bid Interface and Validation – Outage Scheduling • Generation Outage Scheduling
– Dispatch Signals • Transmission Outage
7 Vendors • Forward Market Nodal Scheduling
• Siemens - Market Systems System • Market Quality System
• ABB - EMS system (ATF updates)
• Areva - Settlement System • EMS
• Legacy - CAISO system
• Nexant - Congestion
Revenue Rights System
• MCG - Interchange Appr 130 integrations between the 22 systems
Scheduling System Appr 75 message schemas
• Potomac - Default Energy Appr 175 service definitions
Bids
Appr 450 publisher/consumer testable data transfers
between systems

67
Pacificorp Use of CIM
• PacifiCorp is successfully using CIM to design both interfaces and
databases
– CIM was adopted in 1999 as PacifiCorp’s application integration standard
– Used for both messaging and database design for new projects
– Existing interfaces are reworked when the need arises
• Model Driven Integration based on the CIM viewed internally as “Best
Practice”
– Having a common vocabulary reduces semantic misinterpretation
– Reusing messages minimizes integration costs
– Minimal knowledge of internal application designs required
– Xtensible MDI Workbench used for message creation, management, and
maintenance
• CIM is here to stay
– CIM is standard design practice
– PacifiCorp vendors are getting used to the idea
– PacifiCorp’s data warehouse is based on the CIM
– EMS/SCADA system (Ranger) uses a CIM-based data maintenance tool

68
CIM Scorecard – Examples of CIM use
Business Application/ Message(s) CIM Pct of
Units Project message
that is CIM

Power Substation IntervalRead, SubstationEquipment.Measurement MeasurementList 90%

Delivery Measurements

Outage Center TroubleCalls, TroubleReportAlerts, TroubleReportDetails, OutageManagement 80%

Call Handing TroubleReportSummary, Customer Info, Customer Balance,
Customer Account Balance

Retail Access RegisterReadRequest, BillDeterminant, CustDrop, CustomerMeterDataSet, 80%

Project Enroll.DACust, EnrollmentChange, NonDACust, CustomerServiceAgreement,
Reg.ESSRegister, Register.ESS, ESStatusChange, MeasurmentList,
SESSESSRelationshipChange, RegisterReadResponse, Document, ActivityRecord,
CnIConsumption, DAEnrollConsumption, CustomerBilling,
EnrollmentChange, NonDAEnrollConsumption, BillingDeterminant
ESSStatusChange

Pole Attachment FacilityPoint, JointUse.Agreement, JointUse.Attachment, AssetList 70%

System JointUse.Notice, JointNoticeRequest, FacilityPoint

Transmission Transmission PlannedOutage.Change PlannedOutageNotification 50%

Planned
Outages

Transmission TransmissionData, STLossData, LTLossData, Settlement and MarketClearing 70%

Wholesale Billing Scheduling.LoadData,
System ConsumptionData, InvoiceData

EMS SCADA WeatherData MeasurementList 100%

69
CIM Scorecard Cont’d
Business Application/ Message(s) CIM Pct of
Units Project message
that is CIM

Power Availability GeoThermalPlantGeneration MeasurementList 60%

Supply/ Information
Generation System

Hydro FlowDisplay MeasurementList 100%

Information
Website
Generation SolutionNotification, Performance, SolutionProject, Work 90%
Equipment EquipmentGroupRepetitiveTasks, WorkHistory
Performance Inventory.StockingPlan,
Work WorkHistoryDocument
Management

Commercial CRS MarkToMarketData MarkToMarket (Not in CIM) 80%

& Trading

California ISO EDI810 Settlement 50%

interface

Corporate Giving EmployeeDetails, ContributionPayrollDetails Employee (erpPerson) 70%

Campaign

Sarbanes Oxley ChangeAuditReport ChangeAudit (Not in CIM) 90%

Audit

70
Addressing Objections to the Use of
the CIM Standards
• Claim: CIM is not stable
– 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
• CIM is to complex too learn and contains many parts I do not need
– Fact: The overall CIM UML model is large and complex
– Reality: A typical interface requires only very small subset of information model
• CIM creates too much overhead in message content
– 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 don’t want to add in an extra step of converting to CIM for system integration
– Fact: There is an extra step of mapping to CIM for one connection
– Reality: Consequence of not mapping to a common language is solution that does not scale:
• n(n-1) instead of 2n connection mappings
• I can’t 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
• I don’t want to convert all my metadata to the CIM
– Fact: CIM is a starter kit
– Reality: Use CIM as appropriate for building your own ESM – far better than starting from scratch
• CIM does not contain everything I need or in the form I need for my interfaces
– Fact: CIM UML is extensible
– Reality: Many utilities still use the CIM as a starting point, using namespaces to maintain traceability

71
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
– Utilities have used the CIM as the basis for developing common messages for integration
• 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
– Third IOP conducted in July 2011 (first was UCTE IOP in March 2009)
• Many Smart Grid-related activities based on CIM
– Separate presentations during week

72
CIM Acceptance
• In use at dozens of utilities throughout world
– In North America, used at TSOs, RTO/ISOs, IOUs, and Distribution
Utilities
– In Europe now being adopted by ENTSO-E and TOs
• 80+ applications support CIM standards
• 60+ suppliers sell application/products based on CIM
– Based on 2007 CIM Reference List published by EPRI
• Endorsed and used by other standards organizations
– Multispeak, Zigbee, HAN, ENTSO-E, NASBE, OASIS, etc.
• Foundation for information exchange between utilities and/or other
external organizations
• Foundation for Model-Driven Integration (MDI) architecture based on
Enterprise Information Model (EIM) within an enterprise
• Key building block in Smart Grid to achieve interoperability
– 61968/70 are top 2 of 5 priority standards recognized by FERC in North America
• CIM User Group to deal with questions and issues arising from
increased use

73
Where to Get More Information About
the CIM and Related Standards
• Visit CIM User Group (CIMug) Web Site
– cimug.ucaiug.org or www.cimug.org
• Single site for gaining access to information about the CIM and related
standards
– Includes all standards being developed by IEC TC57 Working Groups 13, 14, 16,
and 19
• Now provide access to:
– Announcements of CIM-related activities and events
– Calendar of activities
– CIM electronic model in various formats
– Lists of CIM-related tools and access to open source tools
– Documents that are publicly available
• Draft IEC TC57 CIM standards for CIMug members
– 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

74
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

75