Upload
dinhduong
View
225
Download
1
Embed Size (px)
Citation preview
1
Welcome to the CIM University
ČEPSPrague, Czech Republic
10 May 2011
2
CIM Standards Overview And Its Role in the Utility Enterprise
CIM Users GroupPrague, Czeck Republic
10 May 2011Terry Saxton
3
Presentation Contents
• Background• What is the CIM• How the CIM is used in the Utility Enterprise• Three Layer Architecture for Using the CIM Standards• CIM UML model• Profiles for business context• Implementation syntax• IEC CIM Working Groups and Standards• CIM as Basis for Enterprise Semantic Model (ESM)• Case studies• Where to get CIM information
4
The IEC Common Information Model (CIM) - What Is It?• A set of standards in enable system integration and information exchange
based on a common information model– Provides a general information model and message/file schemas for
messages/files exchanged between systems• A key differentiator: The CIM standards are based on a Unified Modeling
Language (UML) based information model representing real-world objects and information entities exchanged within the value chain of the electric power industry
– Provides common semantics for all information exchangesReferred to as Model-Driven Integration (MDI)
– Not tied to a particular application’s view of the world• But permits same model to be used by all applications to facilitate information sharing
between applications– Maintained by IEC in Sparx Enterprise Architect modeling tools– Many tools available generating design artifacts and documentation– Enable data access to enterprise data warehouse in a standard way
5
CIM History• 1992 – Unified Information turned over a data model based on the EPRI OTS
to the CCAPI Task Force with the understanding it would be turned into an industry standard model
• 1993 to 1996 - The CCAPI task force expanded the data model with a primary goal of enabling use of plug compatible applications to help protect utility investment in applications
– Entity Relationship Visio Diagram with MS Access database• 1996 – The CIM was turned over to IEC Technical Committee 57, Working
Group 13&14, where it is advancing through the standards process. It covers both electric utility transmission and distribution business operations
– Converted to UML and initially maintained in Rational Rose • 2000 – NERC mandates CIM and first IOP test• 2003 – ISO/RTO Council and EPRI sponsored an initiative to expand CIM
into Market Operations, a.k.a. CME, followed by extensions for Planning and Dynamics
• 2005 – First edition of IEC 61970-301 CIM Base• 2005 – CIM Users Group established under UCA Users Group• 2008 – CIM adopted by UCTE• 2009 – NIST identifies CIM as key standard for Smart Grid interoperability• 2010 – ENTSO-E migrates to CIM and holds first IOP test
Smart Grid Conceptual Model
Slide 7
8
Information is Needed From Many Individual Systems
AM/FM/GIS
Mobile
SCADA
Work Mgmt
CustomerInformation
NetworkManagement
Maintenance& Inspection
HRFinancial
ContractManagement
ProtectionAsset
Planning
RiskAnalysis
NetworkPlanning
Historian OutageManagement
PropertyMgmt Compliance
The CIM
VENDORHELP!
GWAC Stack and the CIM Standards
Organizational
Technical
Informational
8: Economic/Regulatory Policy
7: Business Objectives
6: Business Procedures
3: Syntactic Interoperability
5: Business Context
2: Network Interoperability
4: Semantic Understanding
1: Basic Connectivity
Interoperability Categories
Political and Economic Objectives as Embodied in Policy and Regulation
Strategic and Tactical Objectives Shared between Businesses
Alignment between Operational Business Processes and Procedures
Awareness of the Business Knowledge Related to a Specific Interaction
Understanding of the Concepts Contained in the Message Data Structures
Understanding of Data Structure in Messages Exchanged between Systems
Mechanism to Exchange Messages between Multiple Systems across a Variety of Networks
Mechanism to Establish Physical and Logical Connections between Systems
CIM
10
Sample Power System Model
Generator AC Line Substation
Company
Load
Operates
Operates
Belongs To
Member Of
Owns
Load Area
Connects To
Connects To
Connects To
11
Application of Information Model
SISCO SYSTEMS
Common model creates understanding
Application 1 Application 2
12
The Common Language Should Provide Relevant Information To A User Regardless of Source
EngineeringConcerns
MaterialsManagement
ConcernsConstruction
Concerns
OperationsConcerns
ProtectionConcerns
MaintenanceConcerns
13
The Needs of Various Users –Some Same, Some Different
14
The Needs of Various Users –Some Same, Some Different (continued)
15
Exchanging Common Language Messages Among Systems Should Provide Relevant Information To Each System That Is Harmonious With All Other Systems’ Information
WorkBlah, Blah, Blah,
Organization,Blah, Blah, Blah
MaintenanceBlah, Blah, Blah,
Organization,Blah, Blah, Blah Switching Schedule
Blah, Blah, Blah, Organization,
Blah, Blah, Blah
Load Data SetBlah, Blah, Blah,
Organization,Blah, Blah, Blah
Meter ReadingBlah, Blah, Blah,
Organization,Blah, Blah, Blah
Load ControlBlah, Blah, Blah,
Organization,Blah, Blah, Blah
Asset CatalogBlah, Blah, Blah,
Organization,Blah, Blah, Blah
CrewBlah, Blah, Blah,
Organization,Blah, Blah, Blah
Service ConnectionRequest
Blah, Blah, Blah, Organization,
Blah, Blah, Blah
Planned OutageBlah, Blah, Blah,
Organization,Blah, Blah, Blah
For example, in each of the message exchanges depicted above, the same Organization is referenced for different reasons. There should be NO inconsistencies about this Organization in them!
16
For example, a common language-based logical infrastructure facilitates collaboration among the many applications involved in Asset Management
Asset Strategy
Asset Portfolios
Risk Management
RegulatoryReporting
Financial Management
ResourceScheduling &
Planning
Equip./FleetManagement
Supply Chain Management
ContractManagement
Mobile Workforce
Mgmt.
Work Collaboration & Reporting
Work Design
Asset Owner Asset Manager Service Provider
Asset Investment Planning Asset Program Management
Customer Management Asset Operations
CIS
CRM
IVR eBusiness EMS DMS
SCADA
OMS
Asset Planning Tool
Budget Load Forecast
ReliabilityAnalysis
NetworkAnalysis
Asset Repository
ExecutiveDashboard
Program Mgmt.
Work Mgmt.
Mobile & Dispatching
Contract Mgmt.
GISRevenue
Facility I&M
Portal
SA/DA
Metering
SRCM
17
Application To Common Language Mapping –The Typical Field to Field Process Is Cumbersome
• Individual fields of data models from data sources are mapped to each other
• Approach does not scale well as the number of maps grows exponentially with each new data source
• Mapping is a challenge as ‘mappers’ must have an in depth understanding of all relevant data sources – a tall order!
18
Using A Semantic Model ToSimplify & Scale Up The Mapping Process
• What is a Semantic Model?– The key ingredients that make up a semantic model are a vocabulary of
basic terms, a precise specification of what those terms mean and how they relate to each other.
• How is it used?– Before making mappings, a model (or an ontology) of a given business
domain is defined. – The model is expressed in a knowledge representation language and it
contains business concepts, relationships between them and a set of rules.
– By organizing knowledge in a discrete layer for use by information systems, semantic models enable communication between computer systems in a way that is independent of the individual system technologies, information architectures and applications.
– Compared to one-to-one mappings, mapping data sources to a common semantic model offer a much more scaleable and maintainable way to manage and integrate enterprise data.
[source: TopQuadrant Technology Briefing, July 2003]
The CIM is a Canonical Data Model (CDM)
Provided by Jay Britton
A CDM is a semantic model chosen as a unifying model to govern a collection of interface specifications
20
ETLIntegration BusWeb Services
Apps.
GenericServices
Composite Applications
DW
Business Intelligence
CommonLanguage
SemanticModel
Metadata
The CIM Provides a Semantic Layer in an Enterprise Architecture
21
App CIMY.1 X.1Y.2 X.2Y.3 X.3Y.4 X.4Y.5 X.5
Publisher
Publishers:One Application Connector:•Obtains Data From Application And/Or Database•Transforms Data (if necessary) to the “CommonLanguage” (a Canonical Data Model)
•Puts Data Into Message Template•Publishes The Message (Fires & Forgets)
DataWarehouse
SubstationAutomation
OMS
DistWiresModel
GridWiresModel
DAC
CIS
VRU
AM/FM/GIS
DistributionAutomation
HumanResources
OutageReporting
Event History WorkManagement
EMS
...
CIMX.1 X.2 X.3 X.4 X.5
Subscriber
CIM AppX.1 B.1X.2 B.2X.3 X.4 X.5
Subscriber
CIM AppX.1 A.1X.2 X.3 X.4 A.4X.5 A.5
Subscriber
CIM AppX.1 C.1X.2 X.3 C.3X.4 C.4X.5
Subscriber
Subscribers:Several Application Adapters Receive The Same MessageEach Adapter:•Parses Message, Pulling Out Data Needed By Application•Transforms Data (if necessary) to Local Application Format•Passes Data To Local Application And/Or Database Through Most Appropriate Means
Message Type Instance: ChangedNetworkDataSet (Expressed In Common Language)
Decoupled InformationExchange
© 2003-2004 Xtensible Solutions, Inc. 21
22
The CIM and Related Standards
• The CIM standards are more than just an abstract information model (or CDM) expressed in UML
• Profiles for specifying a subset of the CIM classes and attributes for a specific business context at a specific system interface or system interaction
• Implementation models– Use of XML to create serialized files and messages
• RDF Schema-based standards for power system model exchange• XML Schema-based standards for information message payloads
– ETL based on CIM for data base access• DDLs for data tables
We Need An Organizing Framework
• Layered Reference Architecture for TC57• Based on UN/CEFACT
– Information Model– Contextual Model– Message Syntax
• Rules for Message Assembly
GWAC Stack
Organizational
Technical
Informational
8: Economic/Regulatory Policy
7: Business Objectives
6: Business Procedures
3: Syntactic Interoperability
5: Business Context
2: Network Interoperability
4: Semantic Understanding
1: Basic Connectivity
Interoperability Categories
Political and Economic Objectives as Embodied in Policy and Regulation
Strategic and Tactical Objectives Shared between Businesses
Alignment between Operational Business Processes and Procedures
Awareness of the Business Knowledge Related to a Specific Interaction
Understanding of the Concepts Contained in the Message Data Structures
Understanding of Data Structure in Messages Exchanged between Systems
Mechanism to Exchange Messages between Multiple Systems across a Variety of Networks
Mechanism to Establish Physical and Logical Connections between Systems
CIM
– Not an IT Architecture for the CIM Standards
TC57 Layered Reference Architecture
CIM UML
Information and Semantic Models
Context
Message Syntax
Profiles
Message/FileFormat
(XSD, RDFSchema, OWL)
Contextual layer restricts information model• Specifies which part of CIM is used for given profile• Mandatory and optional• Restrictions• But cannot add to information model
Message syntax describes format for instance data• Can re-label elements• Change associations to define single structure for
message payloads• Mappings to various technologies can be defined
Information Model• Generalized model of all utility objects and their
relationships• Application independent, but defines all concepts
needed for any application
From Information
Model to Syntactic
Model
•Abstract•Model
•Syntactic •Model
•<?xml version="1.0" encoding="UTF-8"?>•<xsd:elementname=« MT_EnergyTransaction">•<xsd:sequence>• <xsd:elementname=« EnergyTransaction"/>• <xsd:sequence>• <xsd:element name=« Name"/>• <xsd:element name=« Type"/>• </xsd:sequence>• </xsd:element>
UML World
XML Syntactic World
•Information/SemanticModel
•Context/Profiles
•MessageAssembly
•MessageSyntax
27
Semantic Models and Profiles
CIM UML
Information and Semantic Models
Context
Message Syntax
Profile
MessageXML Schema
CIM/XMLRDF Schema
RelationalDatabase
61968Rules
CIM/XMLRules
ProjectRules
Message Assembly
28
To Summarize
• The CIM is an abstract information modelstandard expressed in UML.
• Profiles specifying a subset of the CIM classes and attributes for specific business context
• Implementation technologies, such as use of XML to create serialized files and messages– Standards for power system models– Standards for information message payloads
• Also, the CIM UML can be extended– Standard extensions for new functional areas– Private extensions for specific utility requirements
29
Market Operation Apps
60870-6-503App Services
SCADA Apps EMS Apps DMS Apps Engineering & Maintenance Apps
ExternalIT Apps
Data Acquisition and Control Front-End / Gateway / Proxy Server / Mapping Services / Role-based Access Control
61850-8-1Mapping to MMS
TC13 WG14 Meter
Standards
61334
60870-5101&
104
61970 Component Interface Specification (CIS) and 61968 SIDMS for Enterprise Application Integration (EAI, EII, and ETL)
61970 / 61968 Common Information Model (CIM)
Inter-Application Messaging Middleware (specified in XML; mapped to appropriate protocols)
61850 Substation Devices
61850 IED Field Devices &
Distribution Feeders
60870-6TASE.2
Other Control Centers
60870-5RTUs or
SubstationSystems
IEDs, Relays, Meters, Switchgear, CTs, VTs
End
-to-E
nd S
ecur
ity S
tand
ards
and
Rec
omm
enda
tions
(wor
k in
pro
gres
s)
IEC TC57 Reference Architecture
External Systems(Symmetric client/server
protocols)
Specific Communication Services Mappings
Specific Object Mappings
ApplicationInterfaces
Equipment AndSystem Interfaces
Communication Industry Standard Protocol Stacks(ISO/TCP/IP/Ethernet)
XMLMessaging
(work inprogress)
Protocol Profiles
XML Messaging
External Systems (e.g., Substations)
Communications Media and Services
FieldDevices
Utility CustomersEnergyMarket Participants Other BusinessesUtility
Service Providers
Net
wor
k, S
yste
m, a
nd D
ata
Man
agem
ent
(futu
re)
TC13 WG14
*Notes: 1) Solid colors correlate different parts of protocols within the architecture.2) Non-solid patterns represent areas that are future work, or work in progress, or related work provided by another IEC TC.
61850-7-2 ACSI
61850-7-3, 7-4 Object Models
CustomerMeters
Peer-to-Peer 61850 overSubstation bus and Process bus
60870-6-802Object Models
60870-6-703Protocols
Field Object Models
Application To Application (A2A)and Business To Business
(B2B) Communications
Let’s look at each layer of the CIM
CIM UML
Information and Semantic Models
Context
Message Syntax
Profiles
Message/FileFormat
(XSD, RDFSchema, OWL)
Contextual layer restricts information model• Specifies which part of CIM is used for given profile• Mandatory and optional• Restrictions• But cannot add to information model
Message syntax describes format for instance data• Can re-label elements• Change associations to define single structure for
message payloads• Mappings to various technologies can be defined
Information Model• Generalized model of all utility objects and their
relationships• Application independent, but defines all concepts
needed for any application
32
Foundational Relationships Of The CIM
PowerSystemResourceElectrical Network Role Used For
Planning, Operations, etc.
AssetPhysical Plant Filling A Role
Such As A Transformer, Pole, etc.
LocationWhere To Find Something By
GPS, Address, Electronically, etc.
OrganisationEntities Performing Roles Such
As Operations, Tax Authority
PersonPeople Performing Roles SuchDispatcher, Field Operator, etc.
DocumentInformation Containers Such AsTrouble Ticket, Work Orders, etc.
CustomerIndustrial, Commercial, & Residential
Which Can Have Multiple Accounts
33
IEC TC57 CIM Packages
WG13TransmissionEMS/Planning Interfaces
WG14DMSInterfaces
WG16DeregulatedMarketCommunications
34
WG13 CIM Packages - 61970
35
WG14 CIM Packages - 61968pkg M ain
AssetsPointOriented
Customers
Common
Operations
ERPSupport
Work
Assets
M etering PaymentM etering
Domain2Locations
TypeAssetAssetM odelsAssetsLinear
Planning
LoadControl
GM LSupport
Parts 3, 4 (and 5?)
Part 4
Parts (5 and 7)?
Part 6
Part 8
Part 9
Part 10?
36
WG16 CIM Market Extensions
37
CIM UML Release Cycles
• 61970 CIM UML has annual release cycle– Current official annual release is IEC61970CIM14v13– Basis for IEC 61970-301 CIM Base Fourth Edition
• Word document auto-generated from the UML electronic model– Information system and Profile documents are synchronized with
UML model release
• 61968 CIM UML different update cycles– Basis for IEC 61968-11 CIM Distribution Information Exchange
Model
• 62325 CIM UML on another update cycle– Basis for IEC 62325-301 CIM for Deregulated Markets
• Complete CIM UML available as a combined model on CIMug Sharepoint site: iec61970cim14v13_iec61968cim10v28_combined
39
Structureheight : ShortLengthweedAbate : BooleanweedRemDate : AbsoluteDatefumigant : StringfumigantApplyDate : AbsoluteDatejpaRefNum : String
Asset
code : Stringutc : Stringnumber : StringserialNumber : SerialNumberassetType : StringmaufacturedDate : AbsoluteDateinstallationDate : AbsoluteDateinServiceDate : AbsoluteDateoutOfServiceDate : AbsoluteDateremovalDate : AbsoluteDatewarrantyDate : AbsoluteDatefinancialValue : Moneystatus : StringstatusDate : AbsoluteDatecritical : BooleancorpStandard : StringremovalReason : Stringcondition : StringplantTransferDate : AbsoluteDateusage : StringpurchaseDate : AbsoluteDatepurchasePrice : MoneypurchaseOrderNumber : String
(from AssetBasics)
Pole
classification : Stringspecies : Stringtreatment : Stringbase : Stringpreservative : StringtreatedDate : AbsoluteDatebreastBlock : Boolean
Streetlight
rating : StringarmLength : ShortLength
0..1
0..n
+AttachedTo_Pole
0..1 +Support_Streetlights0..n
The CIM Is Expressed In Unified Modeling Language (UML) Notation*
Class Name usually describes things in the real world
Associations connect classes and areassigned a role that describes the relationship
Class Attributes describesignificant aspects about the thing
This Specialization indicates that a “Pole” is a type of“Structure.” Since a “Structure” is a type of “Asset,” the Poleinherits all of the attributes from both Structure and Asset
* For more information on UML notation (a standard), refer to Martin Fowler’s book“UML Distilled,” Addison-Wesley
40
Concepts: Generalization/Inheritance
• Breaker: Specialization of ProtectedSwitch
• ProtectedSwitch: Specialization of Switch
• Switch: Specialization of Conducting Equipment
• ConductingEquipment: Specialization of Equipment
• Equipment: Specialization of PowerSystem Resource
41
Equipment InheritanceHierarchy
class InheritanceHierarchy
Transf ormerWinding
Core: :PowerSystemResource
HeatExchanger
BusbarSection
VoltageControlZone
ShuntCompensator
ACLineSegment
DCLineSegment
LoadBreakSwitch
Core: :VoltageLevel
TapChanger
PowerTransf ormer
Fuse
StaticVarCompensator
RegulatingCondEq
Rectif ierInverter
Junction
Jumper
Ground
Conductor
Disconnector
EnergySource
SeriesCompensator
ProtectedSwitch
Core: :Identif iedObject
PlantLine
FrequencyConverter
Connector
Core: : Bay
Switch
Core: :ConnectivityNodeContainer
Core: :Substation
EnergyConsumer
GroundDisconnector
Core: :ConductingEquipment
Breaker
SynchronousM achine
Core: :Equipment
Core: :EquipmentContainer
CompositeSwitch
42
NamingHierarchy 1
class NamingHierarchyPart1
Core: :Substation
Core: : Bay
Core: :VoltageLevel
Core: :SubGeographicalRegion
Line
Core: :GeographicalRegion
Core: : Identif iedObject
+ aliasName: String [0..1]+ description: String [0..1]+ localName: String [0..1]+ mRID: String [0..1]+ name: String [0..1]+ pathName: String [0..1]
Core: :Equipment
Core: :EquipmentContainer
Core: :PowerSystemResource
Plant
Core: :ConnectivityNodeContainer
+EquipmentContainer0..1
+Equipments0..*
+Region 0..1
+Regions 0..*
+Region 0..1
+Substations 0..*
+Region
0..1
+Lines 0..*
+VoltageLev el0..1
+Bay s0..*
+Bay s 0..*
+Substation
0..1
+Substation 1
+VoltageLev els 0..*
43
NamingHierarchy 2
class NamingHierarchyPart2
Fuse
EnergyConsumer
ShuntCompensator
Connector
BusbarSection
Breaker
ACLineSegment
Disconnector
Jumper
FrequencyConverter
EnergySource
StaticVarCompensator
Rectif ierInverter
Conductor
Core: :ConductingEquipment
Core: :Equipment
DCLineSegment
SynchronousM achine
CompositeSwitch
Switch
M eas: :M easurement
Core: :PowerSystemResource
Transf ormerWinding
TapChanger
PowerTransf ormer
Ground
RegulatingCondEq
GroundDisconnector
Production: :GeneratingUnit
Core: : Identif iedObject
+ aliasName: String [0..1]+ description: String [0..1]+ localName: String [0..1]+ mRID: String [0..1]+ name: String [0..1]+ pathName: String [0..1]
SeriesCompensator
ProtectedSwitch
LoadBreakSwitch
Junction
HeatExchanger
+PowerSy stemResource
0..1
+Measurements
0..*
+TransformerWindings 1..*
+PowerTransformer 1
+GeneratingUnit 0..1+Sy nchronousMachines 1..*
+HeatExchanger 0..1
+PowerTransformer 1
+CompositeSwitch 0..1
+Switches 0..*
44
ConnectivityandTopology Model
cla ss Ma in
Cor e::EquipmentConta iner
Switch/Node static Model
Cor e::Connect iv i ty Node
Cor e::Connect iv i ty NodeConta iner
Cor e::Ter mina l
Bus/Branch calculated Model
Topologica lNode
Meas::Measur ement
Cor e::Conduct ingEquipment
Sta teVa r iables::Topologica l Island
Cor e::Power Sy stemResour ce
Cor e::Ident i f iedObject
BusNameMar ker
Cor e::Equipment
Bus/Branch bus naming specificaiton static model.
Contr olAr ea ::Contr olAr ea
+ netInterchange: ActivePower [0..1]+ pTolerance: ActivePower [0..1]+ type: ControlAreaTypeKind [0..1]
+Terminals
0..*
+ConductingEquipment 1
+TopologicalNodes 1..*
+TopologicalIsland 1
+Terminal0..*
+TopologicalNode0..1
+ConnectivityNodes 0..*
+TopologicalNode 0..1
+AngleRef_TopologicalIsland0..1
+AngleRef_TopologicalNode0..1
+Measurements 0..*
+Terminal0..1
+BusNameMarker
0..1
+Terminal1..*
+TopologicalNode
0..*
+ConnectivityNodeContainer 0..1
+ConnectivityNodes 0..*
+ConnectivityNodeContainer
1
+Terminals0..*
+ConnectivityNode 0..1
45
Converting a Circuit to CIM Objects
• Example to show how voltage levels, current transformers, power transformers and generators are modelled
• Circuit contains a single generating source, load, line and busbar. The circuit also contains two power transformers resulting in three voltage levels of 17kV, 33kV and 132kV
Taken from McMorran, “An Introduction to IEC 61970-301 & 61968-11: The Common Information Model”, University of Strathclyde, Glasgow, UK
46
Example Circuit as a Single Line Diagram
EnergyConsumer
Breaker
SynchronousMachine
GeneratingUnit
Breaker
BusbarSection
Breaker
ACLineSegment
Current measurement represented by
Measurement connected to Terminal
47
Representing a Power Transformer as CIM Objects• A power transformer is not mapped to a single
CIM class– Represented by a number of components with a single
PowerTransformer container class– Two-winding power transformer becomes two
TransformerWinding objects within a PowerTransformer container
• If a tap changer is present to control one of the windings– An instance of the TapChanger class is associated
with that particular winding– Also contained within the PowerTransformer instance
48
Transformer Class Diagram
Inherits from Equipment, since does not conduct
electricity
Physically connected to network and conducts
electricity, so inherits from ConductingEquipment
Part of TransformerWinding, not
separate piece of equipment
Shell of transformer, containing windings,
insulation, magnetic core, etc.
49
CIM Mapping for Transformer 17-33
• Transformer 17-33 is represented as four CIM objects
50
Transformer Model Diagram from 61970-301CIM Base
ConductingEquipment(from Core)
Equipment(from Core)
PowerSystemResource(from Core)
RegulationSchedule
TapChanger
0..1
0..n
+RegulationSchedule0..1
+TapChangers0..n
WindingTest
HeatExchanger
TransformerWinding
0..n+TapChangers
0..n
+TransformerWinding
1
1
0..n
+From_TransformerWinding1
+From_WindingTests1
0..n
+To_WindingTest
+To_TransformeWindings0..n
PowerTransformer
0..1
1
+HeatExchanger0..1
+PowerTransformer 1
1..n
1
+Contains_TransformerWindings
+MemberOf_PowerTransformer
1
51
Transformer Winding Attributes
Transformer Windingb: SusceptanceinsulationKV: VoltageconnectionType: WindingConnectionemergencyMVA : ApparentPowerg: Conductancegrounded: Booleanr: Resistancer0: ResistanceratedKV: Voltagerated MVA: ApparentPowerrground: ResistanceshortTermMVA: ApparentPowerwindingType: WindingTypex: Reactancex0: Reactancexground: Reactance
52
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
53
How The CIM Handles Location For Logical Devices And/Or The Physical Asset Performing The Device’s Role
54
Types Of Document Relationship Inherited By All Assets
55
Activity Records
56
CIM UML in Enterprise Architect
• The CIM UML model is maintained in Sparx Enterprise Architect (EA)
• Current ENTSO-E CIM UML Model for IOP– iec61970cim15v15_iec61968cim10v16_combined.eap
• Go to UML model in EA
Next - Context Layer
CIM UML
Information and Semantic Models
Context
Message Syntax
Profiles
Message/FileFormat
(XSD, RDFSchema, OWL)
Contextual layer restricts information model• Specifies which part of CIM is used for given profile• Mandatory and optional• Restrictions• But cannot add to information model
Message syntax describes format for instance data• Can re-label elements• Change associations to define single structure for
message payloads• Mappings to various technologies can be defined
Information Model• Generalized model of all utility objects and their
relationships• Application independent, but defines all concepts
needed for any application
From Information
Model to Syntactic
Model
•Abstract•Model
•Syntactic •Model
•<?xml version="1.0" encoding="UTF-8"?>•<xsd:elementname=« MT_EnergyTransaction">•<xsd:sequence>• <xsd:elementname=« EnergyTransaction"/>• <xsd:sequence>• <xsd:element name=« Name"/>• <xsd:element name=« Type"/>• </xsd:sequence>• </xsd:element>
UML World
XML Syntactic World
•Information/SemanticModel
•Context/Profiles
•MessageAssembly
•MessageSyntax
59
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
61970 Profiles Currently Defined
• Equipment – Identifies equipment, describes
basic characteristics, and electrical connectivity that would be input to topology processing
• Schedules – Describes input to functions
that derive parameters for a specific point in time
• Measurement Specs– Describes how SCADA will
obtain measurements and what equipment objects are measured
• Measurement Set– The set of SCADA values for
measurements for a particular point in time
• Topology– The result of topology
processing. i.e. Description of how equipment connects into buses and how buses makeup connected systems
• State Variables – Result of a state estimator or
power flow, or the starting conditions of state variables
• Dynamics– Adds dynamics to static
network model for running system simulations
• Schematic Layouts– Describes how equipment
objects are placed on schematic diagrams
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-456 Solved System State Profiles
61970-452Profiles
Equipment Model
61970-456 Profiles
Common Objects
Topology
State Variables
Schedules
Measurement Set
Measurement Specifications
Boundary Objects
Adds steady state solution of power system case produced by power flow applications
Dependencies via references to CPSM Part 452
Plus 61970-457 Dynamic Models Profile
61970-452Profiles
Equipment Model
61970-456 Profiles
Common Objects
Topology
State Variables
Schedules
Measurement Set
Measurement Specifications
Boundary Objects
Future 61970-457 Profile
DynamicModels
Adds dynamic models used in system simulation
Dependencies via references to CPSM Part 452
Plus 61970-453 Diagram Layout Profile
61970-452Profiles
Equipment Model
61970-456 Profiles
Common Objects
Topology
State Variables
61970-453 Profile
Schedules
Diagram Layout
Measurement Set
Measurement Specifications
Boundary Objects
Future 61970-457 Profile
DynamicModels
Adds diagram layout info for schematic data
Dependen- cies via reference to CPSM Part 452
Typical Workflow for Model Exchange
•S1
•S2
•S3
•S4
•S5
•S6
•S7
•S8
•E1
•E1.1•Time
•T1
•Profile
•Full model
•DifferentialModel
•Predecessor
•DependsOnModel
•T1.1
•T1.3
•T1.2
TC57 Reference Architecturefor Model Exchange
•CIM UML
•Information and Semantic Models
•Context
•Message Syntax
•Profiles
•Message/FileFormat
(XSD, RDFSchema, OWL)
•Contextual layer restricts information model• Specifies which part of CIM is used for given profile• Mandatory and optional• Restrictions• But cannot add to information model
•Message syntax describes format for instance data• Can re-label elements• Change associations to define single structure for
message payloads• Mappings to various technologies can be defined
• Information Model• Generalized model of all utility objects and their
relationships• Application independent, but defines all concepts
needed for any application
•Conforms to IEC 61970-301 CIM
•Conforms to collection of
Standard4xx Profiles
•Conforms to IEC 61970-552-4
CIM XML Model Exchange Format
Example of Use of CIM to Define Standard Interfaces
MeterReading &
Control
MeterReading &
Control
Utility ControlCenter
Utility ControlCenter
NetworkExpansionPlanning
NetworkExpansionPlanning
CustomerInquiry
CustomerInquiry
NetworkOperationNetwork
Operation
Records& Asset
Management
Records& Asset
Management
OperationalPlanning &
Optimization
OperationalPlanning &
Optimization
IEC 61968CompliantInterface
Architecture
IEC 61968CompliantInterface
Architecture
Maintenance&
Construction
Maintenance&
Construction
UtilityBusinessSystems
(ERP, Billing,Energy trading,other systems)
UtilityBusinessSystems
(ERP, Billing,Energy trading,other systems)
Corporate LAN
Corporate LAN
Distribution AutomationDistribution Automation
Substation Protection,Monitoring and Control
Substation Protection,Monitoring and Control
RTU Communications RTU Communications
Working Group 14:Establishing A Common Language For Enterprise Application Integration In the IEC 61968 Series of Standards
•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
•Application Integration Infrastructure
•Network Operations•Network Operations•Monitoring (NMON)
•Network Control•(CTL)
•Fault Management•(FLT)
•Operational Feedback•Analysis (OFA)
•Operation Statistics•& Reporting (OST)
•Network Calculations•- Real Time (CLC)
•Records & Asset•Management
•Substation & Network•Inventory (EINV)
•Geographical•Inventory (GINV)
•Asset Investment•Planning (AIP)
•Operational Planning•& Optimization •Network Operation
•Simulation (SIM)
•Switch Action•Scheduling (SSC)
•Power Import Sched.•& Optimization (IMP)
•Maintenance and•Construction
•Maintenance &•Inspection (MAI)
•Construction WMS (CON)
•Design &•Estimate (DGN)
•Scheduling•& Dispatch (SCH)
•Field•Recording (FRD)
•Network Extension•Planning
•Network•Calculations (NCLC)
•Project Definition•(PRJ)
•Construction•Supervision (CSP)
•Compliance•Management (CMPL)
•Customer•Support
•Customer Service•(CSRV)
•Trouble Call•Management (TCM)
•Meter Reading & Control•Meter Reading•(RMR)
• External Systems
•Dispatcher Training (TRN) •General inventory
management (GIM)
•Load Control•(LDC)
•Meter Maintenance (MM)
•Meter Data (MD)
•Point Of Sale•(POS)
•Meter Operations•(MOP)
•Advanced Metering Infrastructure (AMI)
•Meter Data Management IMDM)
•Metering System•(MS)
•Demand Response•(DR)
The IEC 61968 Basic Message Structure
Message Header
Message Types Are Created By Combining IEC 61968 Verbs With Information Exchange Topics, Referred To As Nouns
(IEC 61968 Verbs - continued)
78
Work Overview
Publication No. Description Status Responsible WG14 Lead
To IEC Next Step
61968-01 Interface Architecture and General Requirements
IS Shawn Hu July 2010 MCR
61968-01-1 ESB Implementation Profile
Working Draft
Scott Neumann July 2010 NWIP & CD
61968-01-2 Web Services Working Draft
Mark Ortiz July 2010 NWIP & CD
61968-02 Glossary Technical Report
David Haynes June 2009 MCR
61968-03 Network Operations IS Bruce Scovill July 2011 MCR
61968-04 Records & Asset Management
IS Jon Fairchild July 2011 MCR
•WG14 Status
79
Work Overview
Publication No.
Description Status Responsible WG14 Lead
To IEC Next Step
61968-05 Operational Planning and Optimization
Working Draft Jim Waight TBD Postponed until experts from 5 countries are provided. Also, part 5 should be based on the revised parts 3.
61968-06 Maintenance and Construction
Working Draft Nada Reinprecht
July 2011 NWIP & CD
61968-07 Network Extension Planning
Working Draft Jim Waight TBD Postponed until experts from 5 countries are provided. Also, 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 Mark Ortiz
Sept 2010 Work to recast document to new format& issue CD. Get experts from 5 countries to develop CDV, which is due Dec 2011..
61968-09 Meter Reading and Control
IS Scott Neumann July 2011 MCR
•WG14 Status
80
Work Overview
Publication No. Description Status Responsible WG14 Lead
To IEC Next Step
61968-11 Common Information Model for DMS
FDIS Tanja Kostic March 2011 MCR
61968-12 Compliance and Interoperability Testing
Working Draft
Margaret Goodrich
As tests are performed
NWIP & Technical Report
61968-13 Common Distribution Power System Model
IS Eric Lambert January 2011 MCR
61968-14-1 Mapping between MultiSpeak 4.0 and IEC 61968, parts 3 through 10
Working Draft
Gary McNaughton
In planning and recruitment stage
61968-14-2 A CIM profile for MultiSpeak 4.0, one profile for IEC 61968 parts 3 through10
Working Draft
Gary McNaughton
In planning and recruitment stage
•WG14 Status
Next - Context Layer
CIM UML
Information and Semantic Models
Context
Message Syntax
Profiles
Message/FileFormat
(XSD, RDFSchema, OWL)
Contextual layer restricts information model• Specifies which part of CIM is used for given profile• Mandatory and optional• Restrictions• But cannot add to information model
Message syntax describes format for instance data• Can re-label elements• Change associations to define single structure for
message payloads• Mappings to various technologies can be defined
Information Model• Generalized model of all utility objects and their
relationships• Application independent, but defines all concepts
needed for any application
82
Implementation Syntax – XML Schema
• Example of use of XML Schema• Mapping Proprietary EMS Interfaces to the CIM
– Provide enterprise system access to transformer data
83
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
84
Transformer Class Diagram in CIM
85
CIM Interface Mapping- Beginnings of Profile/Message Payload Definition
Two different interface attributes (WINDINGA_R and WINDINGB_R) map to same
CIM attribute
Aggregation changed from 0..n to 2
Multiplicity changed from
0..1 to 1
Multiplicity changed from
0..1 to 1
86
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
87
XML Schema of CIM
• An XML Schema of the CIM can be generated with XML tools
• 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
88
Transformer Model Diagram from 61970-301CIM Base
ConductingEquipment(from Core)
Equipment(from Core)
PowerSystemResource(from Core)
RegulationSchedule
TapChanger
0..1
0..n
+RegulationSchedule0..1
+TapChangers0..n
WindingTest
HeatExchanger
TransformerWinding
0..n+TapChangers
0..n
+TransformerWinding
1
1
0..n
+From_TransformerWinding1
+From_WindingTests1
0..n
+To_WindingTest
+To_TransformeWindings0..n
PowerTransformer
0..1
1
+HeatExchanger0..1
+PowerTransformer 1
1..n
1
+Contains_TransformerWindings
+MemberOf_PowerTransformer
1
89
XML Schema for Transformer Message
90
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>
91
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
92
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.
93
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]
94
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/
95
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
96
CIM UML=>RDF Schema=>RDBMS
UML. RDF Relational Model
Object Resource Tuple (i.e. row)Attribute or association
Property Attribute (i.e. column) or foreign key
Class Class Relation (i.e. table)
Resource Description
Tuple value
URI Key value Value Field value
[Courtesy Of Leila Schneburger]
97
Simple Network Example
SS1
SS2
400KV
110KV
12345 MW
12345 KV
12345 MW
Cable1 Cable2
SS1-SS2
T1
BB1
SS4
Cable3
98
Simple Network Connectivity Modeled with CIM Topology
SS 1
Cable2
SS 2
110KV
400KV
Cable1 CN2CN3BR1DC2 CN4
P1(MW)
CN5
BB1
T 1
TW 1
TW 2
CN7
CN6
Volts(KV)
BR3
P2(MW)
CN1
SS1-SS2
Cable3
SS 4
CN8
BDD-RSK2
T1 T2
99
Siemens 100 Bus Network Model in RDF
<?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></
Top of RDF Schema version of Siemens 100 bus model
100
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>
101
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>
102
Containment in RDFSubstation VOL with 230 KV voltage level and Bay 240W79 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
Substation VOL with 230 KV voltage level and Bay 240W79 with Breaker CB
<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>
103
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>
104
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
105
Basics: Schema from CIM
EnterpriseArchitect
CIM (in UML)
UMLto RDF
Transformers
CIM asXML/RDFSchema
specifies
PowerSystem Data
Exporter
PowerSystem Data
as XML/RDF
106
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
107
Example: Power Flow Network Model Exchange
CIM UML
Information and Semantic Models
Context
Message Syntax
Power SystemModel Profile
Group
CIM/RDFSchema
Information Model• Defines all concepts needed for
exchange of operational load flow models
– Reused parts– New extensions
Contextual layer restricts information model• Specifies which part of CIM is used for
static/dynamic model exchange• Mandatory and optional• Restrictions• But cannot add to information model
File syntax• Can re-label elements• Change associations to define single
structure for message payloads• Mappings to various technologies can
be defined
Conforms to IEC 61970-301 CIM
Conforms to IEC 61970-452, 453,
456, othersModel Exchange
Profile
Conforms to IEC 61970-501 and -552
CIM XML Model Exchange Format
108
Ex: Power Flow Network Model Exchange
Information Model• Defines all concepts needed for
exchange of operational load flow models
– Reused parts– New extensions
Contextual layer restricts information model• Specifies which part of CIM is used for
static model exchange• Mandatory and optional• Restrictions• But cannot add to information model
File syntax• Can re-label elements• Change associations to define single
structure for message payloads• Mappings to various technologies can
be defined
CIM UML
Profile
CIM/XML RDFSchema
ConcreteMessage
Conforms to IEC 61970-301 CIM
Conforms to IEC 61970-452
Model ExchangeProfile
Conforms to IEC 61970-552
CIM XML Model Exchange Format
109
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
110
GridWise Interoperability Framework
Role of CIM
111
Enterprise Semantic Models– CIM + Other Industry Standards
CIM UMLPrivate UMLExtensions
Merge – resolvesemantic
differences
Other Information
Models
Context
Message Syntax
Profile
SchemasXSD, RDFS,
DDL
Contextual layer restricts information model• Constrain or modify data types• Cardinality (may make mandatory)• Cannot add to information model
Message/data syntax describes format for instance data• Can re-label elements• Change associations to define single structure for message payloads• Mappings to various technologies can be defined
112
3) Generate Canonicals•Syntactically and semantically consistent canonical models
Semantic Consistency
1) Establish Vocabulary•Control Content•Collaborate•Identify and refine semantics
Semantic Formalization
Context Refinement
2) Develop ESM•Model using vocabulary terms•Refine context
Existing Terminologyand Metadata
Building and Using an ESM for GeneratingCanonicals (XSDs, DDLs, others)
Compliments Xtensible MD3i
113
Role of Enterprise Semantic Model
Enterprise Integration Platforms
Application Information
Process Integration
Business Intelligence
BPM/Workflow
EnterpriseSemantic
Model
Open Standards
ApplicationsMetadata
Bus
ines
sD
efin
ition
s
114
Let’s Apply to a Utility Project- Interface Architecture
CIM UMLCIM UMLExtensions
Context
Interface Syntax
Profile 1
MessageXML Schema
Profile 2
CIM/RDFSchema
Profile 3
DDL
BridgeOther
Information Models
System Interface Design
Document
Profile 1Profile 1
115
Ex: Project Interaction Test
Enterprise Semantic Model• Defines all concepts needed for
Enterprise– Reused parts– New extensions for project
ESM
Profile
XML Schema
ConcreteMessage
Conforms to Utility ESM
Conforms to Profiles defined
for each system interaction
Conforms to WSDLs and Message
XML Schemas
Contextual layer restricts ESM• Specifies which part of ESM is used for
specific system interaction• Mandatory and optional• Restrictions• But cannot add to information model
File syntax• Can re-label elements• Change associations to define single
structure for message payloads• Mappings to various technologies can
be defined
116
Project Integration Architecture
117
Data Architecture– Model
CIM
Semantic Model
XML SchemaDB Schema
CIS OTHERREFEFENCE MODELS
SEMPRA MODEL
MESSAGES
SCHEMAS
Business Entity
Business Entity
Business Entity
118
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
119
Interface Examples:Interface Type Example Implemented
byUtilized by Description
Information Creation
submitBid(XML) Vendor Enterprise These interfaces are for creating or modifying information within a system of record.
Information Transfer
publishCleanBidSet(XML) CAISO Vendor These interfaces are for transferring information and releasing custody.
Information Interest
receiveCleanBidSet(XML) Vendor EAI These interfaces are implemented by vendors to allow systems to receive information as it becomes available. This indicates a subscription type interest in data.
Information Sharing
getResourceInfo(XML) XML
Vendor Enterprise These interfaces are implemented by the vendors to surface information currently within custody to the enterprise.
(Slide from Stipe Fustar, KEMA)
120
System A Integration Layer
PI
BITS
MC
broadcastMarketMeterDataWS
retrieveMarketMeterData WS
broadcastMarketMeterData
WSretrieveMarketInterchange
WS
receiveMarketMeterDataWS
receiveMarketMeterDataWS
broadcastInvoiceData WS
broadcastGeneralLedgerData WS
receiveInvoiceData WS
receiveGeneralLedgerData WS
broadcastStatusInvoiceDataWS
(Slide from Stipe Fustar, KEMA)
121(Slide from Stipe Fustar, KEMA)
122(Slide from Stipe Fustar, KEMA)
123
CAISO Project Statistics22 Systems• Dispatch System• MP Report Interface• Load Forecast• Transmission Capacity
Calculator• Real Time Nodal System• Settlement and Market
Clearing• Bid Interface and Validation
7 Vendors• Siemens - Market Systems• ABB - EMS system• Areva - Settlement System• Legacy - CAISO system• Nexant - Congestion
Revenue Rights System• MCG - Interchange
Scheduling System• Potomac - Default Energy
Bids
• Default Energy Bids• Real Time Metering• Adjusted Metering• Market Participants
– Bidding– Market Results– Settlement– Outage Scheduling– Dispatch Signals
• Forward Market NodalSystem
• EMS
• OASIS• Interchange Scheduling
System• Congestion Revenue Rights• Intermittent Resources• Compliance• RMR Validation• Generation Outage Scheduling• Transmission Outage
Scheduling• Market Quality System
(ATF updates)
Appr 130 integrations between the 22 systemsAppr 75 message schemasAppr 175 service definitionsAppr 450 publisher/consumer testable data transfers
between systems
124
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
125
CIM Scorecard – Examples of CIM useBusiness Units
Application/Project
Message(s) CIM Pct of message that is CIM
Power Delivery
Substation Measurements
IntervalRead, SubstationEquipment.Measurement MeasurementList 90%
Outage Center Call Handing
TroubleCalls, TroubleReportAlerts, TroubleReportDetails, TroubleReportSummary, Customer Info, Customer Balance, Customer Account Balance
OutageManagement 80%
Retail Access Project
RegisterReadRequest, BillDeterminant, CustDrop, Enroll.DACust, EnrollmentChange, NonDACust, Reg.ESSRegister, Register.ESS, ESStatusChange, SESSESSRelationshipChange, RegisterReadResponse, CnIConsumption, DAEnrollConsumption, EnrollmentChange, NonDAEnrollConsumption, ESSStatusChange
CustomerMeterDataSet,CustomerServiceAgreement,MeasurmentList,Document, ActivityRecord, CustomerBilling, BillingDeterminant
80%
Pole Attachment System
FacilityPoint, JointUse.Agreement, JointUse.Attachment, JointUse.Notice, JointNoticeRequest, FacilityPoint
AssetList 70%
Transmission Transmission Planned Outages
PlannedOutage.Change PlannedOutageNotification 50%
Transmission Wholesale Billing System
TransmissionData, STLossData, LTLossData, Scheduling.LoadData,ConsumptionData, InvoiceData
Settlement and MarketClearing 70%
EMS SCADA WeatherData MeasurementList 100%
126
CIM Scorecard Cont’dBusiness Units
Application/Project
Message(s) CIM Pct of message that is CIM
Power Supply/Generation
Availability Information System
GeoThermalPlantGeneration MeasurementList 60%
Hydro Information Website
FlowDisplay MeasurementList 100%
Generation Equipment Performance Work Management
SolutionNotification, Performance, SolutionProject, EquipmentGroupRepetitiveTasks, Inventory.StockingPlan, WorkHistoryDocument
WorkWorkHistory
90%
Commercial & Trading
CRS MarkToMarketData MarkToMarket (Not in CIM) 80%
California ISO interface
EDI810 Settlement 50%
Corporate Giving Campaign
EmployeeDetails, ContributionPayrollDetails Employee (erpPerson) 70%
Sarbanes Oxley Audit
ChangeAuditReport ChangeAudit (Not in CIM) 90%
127
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
128
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– Second IOP conducted in July 2010 (first was UCTE IOP in March 2009)
• Many Smart Grid-related activities based on CIM– Separate presentations during week
129
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
– See CIM Reference List for Details• 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
130
Where to Get More Information About the CIM and Related Standards• Visit CIM User Group (CIMug) Web Site
– http://cimug.ucaiug.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
131
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