CIM Standards Overview

And Its Role in the Utility

Enterprise - Part 2

CIM Users Group

Amsterdam, Netherlands
Terry Saxton
Presentation Contents – Part 2
• Layer 2 - Profiles for defining system interfaces
– IEC 61970 network model exchange
– IEC 61968 message payloads for system integration
• Layer 3 - Implementation syntax of instance data
– CIM expressed in XML and RDF Schema
• Value of an Enterprise Semantic Model (ESM)
based on the CIM
• Case studies
• Where to get more 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

3
How the CIM is Applied to Specific
Information Exchanges
• The interfaces defined under CIM are defined by Profiles
– A profile specifies the information structure of exchanged
information by creating contextual semantic models
• Contextual semantic models are a subset of the overall CIM
information model (i.e., they inherit their structure from the CIM UML
model)
– There is typically a family of related interfaces defined within a
profile
– Products implement support for profiles in the form of CIM/XML
import/export software or ESB run-time adapters
– Testing occurs against profiles
– “CIM compliance” is defined against profiles – otherwise the term
is meaningless

• Note: We saw that the CIM Information Model is partitioned into sub-domains by IEC
WGs
– But these groups work hard to ensure there is a single, unified semantic model over the whole
utility domain
– That means any part of the whole UML model can be used to define a system interface
–

4
Presentation Contents

• Profiles for business context

– WG13 61970 Profiles for Power System Network Model Exchange
– WG14 61968 Message Payloads for System Integration

5
WG13 Reference Diagram for Power Flow Cases

6
6
61970 Profiles Currently Defined

Part 452 Static Transmission Part 456 - Solved Power

Network Model Profiles System State Profiles
• Equipment (EQ) • Steady State Hypothesis
– Identifies equipment, basic (SSH)
characteristics, and electrical – Measurements
connectivity of steady state
network model – Status
– Also known as Common – Controls
Power System Model (CPSM) – Limits
• Many Interoperability (IOP) – Energy distribution
tests since year 2000
• In use in many countries • Topology (TP)
– The result of topology
• 61968-13 distribution model processing. i.e. description of
(CDPSM) based on EQ with how equipment is connected
some extensions at a particular point in time
• State Variables (SV)
– Result of a state estimator or
power flow, or the starting
conditions of state variables

7
61970 Profiles
• Part 457 - Dynamics (DY)
– Adds dynamics to static network model for running system simulations
• Part 453 - Diagram Layout (DL)
– Describes how equipment objects are placed on schematic diagrams for
display purposes

8
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

9
Plus 61970-451 Measurement and Control
and -456 Solved System State Profiles
61970-451 61970-456 Profiles
Profile
State SSH
Variables Adds SCADA
Measurement
and Control
Topology
Adds steady state
solution of power
system case
produced by
Measurement power flow
Specifications
applications
61970-452 Equipment
Profiles Model Dependencies via
references to
Connectivity Schedules CPSM Part 452

10
Plus 61970-451 Measurement and Control
and -456 Solved System State Profiles
61970-451 61970-456 Profiles
Profile
State SSH
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

11
Plus 61970-453 Diagram Layout
Profile
61970-456 Profiles Future 61970-
457 Profile Adds diagram
State SSH layout info for
Variables Dynamic
Models schematic
Measurement
data
Topology
Set
Dependencies
via reference
61970-453
Measurement Profile
to CPSM Part
Specifications 452
61970-452 Equipment Diagram
Profiles Model Layout
Boundary
Objects
Common Schedules
Objects

12
Typical Workflow for Model
Exchange

E1 T1 S1

S2

T1.1 S3

Time E1.1 S4

T1.2

S5

T1.3
S6

Profile
Full model S7
DifferentialModel
Predecessor
DependsOnModel S8

13
 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 Profiles •
•
Specifies which part of CIM is used for given profile
Mandatory and optional
4xx Profiles • Restrictions
• But cannot add to information model

Message Syntax Message syntax describes format for

Message/File
Conforms to instance data
Format • Can re-label elements
IEC 61970-552 and -501
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

14
Presentation Contents

• Profiles for business context

– WG13 61970 Profiles for Power System Network Model Exchange
– WG14 61968 Message Payloads for System Integration

15
 Abstract
Information/ Model
From Semantic
Information Model
Model to
Syntactic Model
Context/
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"/>
<xsd:sequence> Syntactic
Syntax <xsd:element name=« Name"/>
<xsd:element name=« Type"/>
</xsd:sequence> Model
</xsd:element>
16
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 Information:
http://www.ucainternational.org/
http://www.iec.ch

RTU
RTU Communications
Communications

17
Smart Grid Interoperability

• Ability of systems to operate in coordination

– Ability to exchange and use information appropriately
• Requires standard interface definitions
– Governed by open industry working groups
• Provides Benefits
– Promotes loosely-coupled integration
• Allows incremental functional enhancements
• Creates market for reusable, compatible components
– Only one integration instead of many
• To an open, public, standard interface
– Instead of each proprietary vendor or utility interface

18
Smart Grid Challenges

• Requires Integration – LOTS of integration

– Onslaught of new applications and technologies
• AMI, MDMS, HAN, DR, ADE, etc.
• In a complex IT environment
– Many custom systems, legacy technologies
– Typically departmentally controlled – within “silos”
• Need ability to govern, manage, and share resources
– at the Enterprise level and beyond (external services)
– Aging / outsourced systems and IT workforce
– Historically, extremely low R&D expenditures
• Must ramp up capabilities quickly

19
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

External Systems:
Energy Trading (ET)
Records & Operational Maintenance
Network Retail (RET)
Asset Planning & & Sales (SAL)
Operation
Management Optimization Construction Stakeholder Planning & Management (SPM)
(NO)
(AM) (OP) (MC) Supply chain and logistics (SC)
Human Resources (HR)

IEC 61968-3 IEC 61968-4 IEC 61968-5 IEC 61968- 6 Applicable parts of
IEC 61968 Series

Enterprise Application Integration and Enterprise Service Bus Middleware

IEC 61970 & Applicable parts of

IEC 62325 & IEC 61968 Series
IEC 61968-7 IEC 61968-8 IEC 61968-9 Applicable parts of Applicable parts of
IEC 61968 Series IEC 61968 Series

External Systems:
Network Meter Customer Account
Customer Bulk Energy Management (ACT)
Extension Reading & Market
Inquiry Management Financial (FIN)
Planning Control Operations
(CS) (EMS) Business Planning and
(NE) (MR) Reporting (BPR)
Premises (PRM)

Utility Electric Network Planning, Constructing, Enterprise Resource Planning, Supply

Maintaining, and Operating Chain, and General Corporate Services

20
The Business Sub-Function Level of the
IRM for IEC 61968 Scope
Network Operations Records & Asset
Management
Network Operations Operation Statistics Substation & Network Operational Planning Maintenance and
Monitoring (NMON) & Reporting (OST) Inventory (EINV)
& Optimization Construction
Network Control Network Calculations Geographical Network Operation Maintenance & Scheduling
(CTL) - Real Time (CLC) 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
Point Of Sale (DR) (MM)
Construction
Supervision (CSP) (POS)
Load Control
Meter Data (MD)
(LDC)
Compliance
Management (CMPL) Meter Operations
(MOP)

21
The IEC 61968 Basic Message Structure

22
Message Header

23
IEC 61968-9: Interface Standard for Meter
Reading and Control

24
Scope/Purpose

• To Define the exchange of information between a

Metering System and other systems within the Utility
enterprise
• Specifies the information content of a set of message
types that can be used to support many of the
business functions related to Merter Reading and
Control.
• Typical uses of the message types include:
– Meter Reading and Meter Control
– Meter Events
– Customer Data Synchronization and Customer Switching

25
Scope of Part 9

Area Causally/Indirectly
Area of Direct Impact
Impacted by or impacting
using IEC 61968-9
IEC 61968-9

Customer

Electric Utility
Standard or Proprietary Meter
Communication
Enterprise Integration Infrastructures
Infrastructure
(e.g. ESB, SOA, …)
Customer
PAN
Device

Enterprise Head End Meter or

PAN
IEC 61968-9 Messages Gateway
Applications Systems PAN
Device

Messages defined by IEC

61968-9 and based upon Customer
PAN
IEC CIM, conveyed using a Device
variety of integration
technologies Messages defined by Meter or
relevant standards or PAN
Gateway
vendors. May use a wide PAN
variety of communication Device
technologies PAN
Device

Mappings, translations
and/orforwardiing as Messages defined
needed Mapping, translations by PAN/HAN
and/or forwarding as specifications
needed

26
Reference Model

• The Reference Model provides examples of the logical

components and data flows related to this standard.
• The Meter is treated as an “end device”
• An End Device:
– Has a unique identity
– Is managed as a physical asset
– May issue events
– May receive control requests
– May collect and report measured values
– May participate in utility business processes
• The Reference Model describes the flows between the
components.

27
Part 9 Reference Model

28
Part 9 Message Types

29
Typical Message Payload Definition -
EndDeviceEvent Message

EndDeviceEvent
Messages Convey
events related to:
• Sustained Outage
Detection
• Momentary Outage
Detection
• Low Voltage
Threshold Detection
• High Voltage
Threshold Detection
• Distortion Meter
Health
• Tamper Detection
• Revenue Event

30
 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

31
Xtensible Markup Language (XML)
• Universal format for structured documents and data
• Provides a syntax for exchange of information
• CIM uses for exchange of message payloads between systems, such
as an Outage message from an Outage Management System (OMS) to
a Customer Information System (CIS), which are actually XML
documents
• Can be transported over multiple, different types of communication
infrastructure, such as an Enterprise Service Bus (ESB) or the Internet
• XML uses “tags” that are based on the CIM UML class attributes to
denote elements within documents

32
Mapping CIM Class Structure to XML using
XML Schema (XSD)

• 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 CIMug
SharePoint site
• The CIM classes and attributes are used to define tags
• Then the CIM can be shown in XML as well as UML

Example of use of XML Schema

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

33
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

34
Transformer Class Diagram in CIM
Simplified (Pre-Release 15 model)

35
CIM Interface Mapping
- Beginnings of Profile/Message Payload Definition
“name” from
IdentifiedObject
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

36
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

37
XML Schema
for Transformer
Message

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

39
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

40
Resource Description Framework
(RDF)
• RDF provides a framework for data in an XML format by allowing
relationships to be expressed between objects
• RDF Syntax
– With a basic XML document there is no way to denote a relationship
between two elements that are not a parent or a child
• Ex: an association or aggregation/containment, as between
Substation and VoltageLevel)
– Within an RDF document each element can be assigned a unique ID
attribute (RDFID) under the RDF namespace
– Adding a resource attribute to an element allows references to be made
between elements by having its value refer to another element’s ID

41
RDF Schema
• While RDF provides a means of expressing simple statements about
the relationship between resources, it does not define the vocabulary
of these statements
• The RDF Vocabulary Description Language, known as RDF Schema
(RDFS) provides the user with a means of describing specific kinds
of resources or classes
• RDFS does not provide a vocabulary for a specific application's
classes, but instead allows the user to describe these classes and
properties themselves and indicate when they should be used
together
– Semantics contained in the CIM UML model provide the vocabulary
• RDF combined with RDF Schema
– Provides a mechanism for expressing a basic class hierarchy as an XML schema by
specifying the basic relationship between classes and properties
– This allows a set of objects to be expressed as XML using a defined schema that
retain their relationships and class hierarchy

42
References

• RDF (Resource Description Framework)

– For more information: http://www.w3.org/RDF
– Status: W3C Recommendation 2004-02-10
– List of documents at: http://www.w3.org/standards/techs/rdf
• RDF Schema
– Status: W3C Recommendation 2004-02-10
• http://www.w3.org/TR/PR-rdf-schema
• Namespaces
– Provides 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 2009-12-08
• http://www.w3.org/TR/REC-xml-names
• URI (Uniform Resource Identifiers)
– Provides a simple and extensible means for identifying a resource
– Status: Internet RFC August 1998
• http://www.w3.org/Addressing/

43
Mapping CIM Class Structure to XML
using RDF Schema
• Commonly referred to as “CIM/XML” but correct reference is CIM
RDF XML
• 61970-501 specifies the mapping between CIM UML model defined in
61970-301 into a machine readable format as expressed in the XML
representation of that schema using the RDF Schema specification
language
– The resulting CIM RDF schema supports CIM Model Exchange profiles,
as presented in IEC 61970-452 and others
– Allows CIM data objects to be mapped, one-to-one, into RDF instance
data.
• Part 501 specifies the subset of RDF used for CIM RDF XML
– Any RDF parser can be used to read CIM RDF XML
– CIM community developed tools to auto-generate the CIM RDF XML
from the CIM UML model

44
Simple Network Example

SS2

400KV
SS1-SS2
SS1
Cable1 Cable2
12345 MW

Cable3
12345 KV
BB1
12345 MW

SS4
T1

110KV

45
Simple Network Connectivity Modelled
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

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

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

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

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

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

51
Implementation Syntax – WG13 61970

• 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
– Includes Difference model
– Includes file header specification with file dependencies to for
importer to ensure all prerequisite models exist prior to
importing

52
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

53
How Are CIM Standards Used?
• Unlike most standards we use
– Ex: IEC 60870-6 ICCP/TASE.2 Communication Protocol standard
– Fixed functionality, very stable, easy to test compliance, but inflexible
• CIM standards can also be strictly applied and tested for compliance
– Ex: CIM/XML Power system network model exchange
– Product interfaces are developed and tested for compliance
– Subject of several EPRI-sponsored interoperability tests (IOPs) for
specific interface definition
– ENTSO-E is best example of the need for strict compliance testing of
power system network models and related information exchanges (such
as congestion forcasts) via IOPs

54
Example: Power Flow Network Model
Exchange
Information and Semantic Models

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

Context Contextual layer restricts information model

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

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

55
Example: 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

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

Conforms to File syntax

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

56
ENTSO-E is THE European TSO platform
• Founded 19 December 2008 and
fully operational since 1 July 2009
• Represents TSOs from 44 countries
• 532 million citizens served
• 880 GW net generation
• 305,000 Km of transition lines
managed by the TSOs
• 3,200 TWh/year demand
• 380 TWh/year exchanges
• Replaced former TSO organisations:
ATSOI, BALTSO, RTSO, NORDEL,
UCTE, UKTSOA

• Migrated to CIM-based network

protocols after close liaison with
WG13/16 and extensive IOPs with
multiple vendors and TSOs

57
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

58
 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

59
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

Complements Xtensible MD3i

60
 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

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

Other
CIM UML
CIM UML Bridge Information
Extensions Models

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

Interface Syntax
Message CIM/RDF
DDL
XML Schema Schema

62
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

63
Project Integration
Architecture

64
Data Architecture
– Model

CIM CIS OTHER

REFEFENCE
MODELS

SEMPRA Semantic Model

MODEL

MESSAGES
Business Business Business
Entity Entity Entity

SCHEMAS
DB Schema XML Schema

65
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

66
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, PowerGrid 360)

67
Typical Web Services

System A Integration Layer

WS receiveMarketMeterData WS broadcastMarketMeterData

retrieveMarketMeterData WS PI

WS receiveMarketMeterData WS broadcastMarketMeterData

BITS
retrieveMarketInterchange WS

Bid Interchange Transaction Scheduling system

broadcastInvoiceData WS receiveInvoiceData WS

WS broadcastStatusInvoiceData

broadcastGeneralLedgerData WS receiveGeneralLedgerData WS
MC

(Slide from Stipe Fustar, PowerGrid 360)

68
(Slide from Stipe Fustar, PowerGrid 360)
69
(Slide from Stipe Fustar, PowerGrid 360)
70
CAISO Project Statistics

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

71
Other Case Stories*
• The Green Button Standard
– Green Button leverages CIM standards in the creation of a
common way to share and view energy consumption data
• Consumers Energy
– Consumers Energy leverages IEC CIM for Enterprise Integration
and an enterprise semantic model
• Long Island Power Authority
– Long Island Power Authority (LIPA) leverages IEC CIM for
Enterprise Information Management and semantic integration
initiatives
• Sempra Energy
– Sempra Energy uses CIM to support their OpEx 20/20 and Smart
Metering programs, reducing the cost of systems integration,
maintenance, and support

*These are described in some detail in the Third Edition CIM Primer
72
OpenFMB Distributed Intelligence Vision

• Visit OpenFMB Demo at Duke Energy booth at DistribuTech 2016

• Initial focus of demo is MicroGrid optimization and islanding transitions

73
Open Field Message Bus – SGIP PAP
• Framework for distributed intelligent nodes interacting with each other
• IoT (Internet of Things) technologies applied to Smart Grid
• Distributed resources communicating via common semantic definitions
derived from the CIM extended as needed
– enables grid devices to speak to each other, e.g. meters, relays, inverters, cap bank
controllers, etc.
• Grid-edge OpenFMBnodes processing data locally for control and
reporting
• OpenFMB supports field-based applications that enable:
– Scalable peer-to-peer publish/subscribe architecture
– Data-centric rather than device-centric communication including
support for harmonized system and device data
– Distributed logic as well as centralized logic
– Legacy equipment to be retrofitted for new capabilities, features, and
extended life
• Led by utilities (largest IOU, Muni, and Co-op) based on their
priorities and interoperability demonstration experience

74
Overall OpenFMB Design Process

75
CIM Acceptance
• In use at hundreds of utilities throughout world
– Used at TSOs, RTO/ISOs, IOUs, and Distribution Utilities
– In Europe now being adopted by ENTSO-E and TOs
• Many applications support CIM standards
• Many suppliers sell application/products based on CIM
• 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 an Enterprise InformatiSemantic Model (ESM) within an
enterprise
• Key building block in Smart Grid to achieve interoperability
– 61968/70 are top 2 of 5 priority standards recognized by NIST & FERC in North
America
• CIM User Group to deal with questions and issues arising from
increased use

76
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 draft standards being developed by IEC TC57 Working Groups
13, 14, 16, and 19 for CIMug members
• Published IEC CIM standards available from online store at www.iec.ch
– Now provide access to:
• EPRI CIM Primers and Webinars streamed via YouTube
• Announcements of CIM-related activities and events
• Past meeting presentations
• CIM electronic UML model in various formats
• Lists of CIM-related tools and access to open source tools
• Membership in various Groups, Projects, and Focus Communities
• CIM issues lists and status of resolution
• Help desk
• Links to other CIM-related sites
• IEEE PES Power and Energy CIM Special Edition Jan-Feb 2016 – available
now

77
Gartner/EPRI CIM Survey Results
2013
• 218 respondents completed an online survey in
August/September 2013 about their organizations use of
CIM standards
• To qualify, respondents had to be knowledgeable about
their organizations use and planned use of CIM standards
• Had to be in either an electric utilities company, a
university/R&D organization or a technology provider,
systems integrator, or consultant to electric utilities clients
• Report available from either EPRI or Gartner

78
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

79
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

Questions

• For more info, contact:

– Terry Saxton, Xtensible Solutions
– [email protected] : +1 612 396 7099

80