CIM Standards Overview CIM U Oslo - Part2
CIM Standards Overview CIM U Oslo - Part2
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
3
How the CIM is Applied to Specific
Information Exchanges
• The CIM Information Model is partitioned into sub-
domains by IEC WGs
– These groups work hard to maintain a unified semantic model over the whole
domain
• 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
4
Presentation Contents
5
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
6
61970 Profiles Currently Defined
• Equipment • Topology
– Identifies equipment, describes – The result of topology
basic characteristics, and processing. i.e. Description of
electrical connectivity that how equipment connects into
would be input to topology buses and how buses makeup
processing connected systems
• Schedules • State Variables
– Describes input to functions – Result of a state estimator or
that derive parameters for a power flow, or the starting
specific point in time conditions of state variables
• Measurement Specs • Dynamics
– Adds dynamics to static
– Describes how SCADA will network model for running
obtain measurements and system simulations
what equipment objects are
measured • Schematic Layouts
– Describes how equipment
• Measurement Set objects are placed on
– The set of SCADA values for schematic diagrams
measurements for a particular
point in time
7
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
Measurement
Specifications
61970-452 Equipment
Profiles Model
Connectivity Schedules
8
Plus 61970-451 Measurement and Control
and -456 Solved System State Profiles
61970-451 61970-456 Profiles
Profile
State
Variables Adds SCADA
Measurement
and Control
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
9
Plus 61970-451 Measurement and Control
and -456 Solved System State Profiles
61970-451 61970-456 Profiles
Profile
State
Variables
Measurement
and Control
Topology
10
Plus 61970-453 Diagram Layout
Profile
61970-456 Profiles Future 61970-
457 Profile Adds diagram
State 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
11
Typical Workflow for Model
Exchange
Equipment State
Topology
Variables
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
12
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
13
Presentation Contents
14
Abstract
Information/ Model
From Semantic
Information Model
Model to
Syntactic Model
Context/
Profiles
Message
UML World
Assembly
Message <xsd:element
name=« EnergyTransaction"/>
<xsd:sequence> Syntactic
Syntax <xsd:element name=« Name"/>
<xsd:element name=« Type"/>
</xsd:sequence> Model
</xsd:element>
15
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
16
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
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)
19
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)
20
IEC 61968-9: Interface Standard for Meter
Reading and Control
23
Scope/Purpose
24
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
Mappings, translations
and/orforwardiing as Messages defined
needed Mapping, translations by PAN/HAN
and/or forwarding as specifications
needed
25
Reference Model
26
Part 9 Reference Model
Power reliability and quality events Planning
Outage
and
Management
Scheduling
Special read
Readings
and status Meter Meter Meter
Meter Data Collection readings Data history
Management
Metering System
Tokens
Control and
Controls and signals Reconfiguration
Customer
Data
Set
Configuration,
Readings
installation, etc. On request read Customer
and status
Information
Transaction records
and
Meter health and
Billing
tamper detection Disconnect/reconnect,
Meter Maintenance demand reset
Demand response signals
(e.g. load control, price signals)
27
Part 9 Message Types
28
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
30
Implementation Syntax – XML
Schema
• XML Syntax
• Example of use of XML Schema
• Mapping Proprietary EMS Interfaces to the CIM
– Provide enterprise system access to transformer data
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)
33
Mapping EMS Interfaces to the CIM –
User access to transformer data
34
Transformer Class Diagram in CIM
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
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
(MW)
BR3
Cable3
P2
(MW) CN6
TW 1
CN8
T1
TW 2
SS 4
CN7
BDD-RSK2
110KV
46
Siemens 100 Bus Network Model in RDF
47
ACLineSegment in RDF
<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
<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 VOL with
with 230 230 KV voltage
KV voltage level
level and and Bay
Bay 240W79 with 240W79 with Breaker CB
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
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: 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
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
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
56
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
57
Enterprise Semantic Models
– CIM + Other Industry Standards
Context
Contextual layer restricts information model
Constrain or modify data types
Profile Cardinality (may make mandatory)
Cannot add to information model
58
Building and Using an ESM for Generating
Canonicals (XSDs, DDLs, others)
Existing Terminology
and Metadata
ClassA
ClassB
ClassC
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
Enterprise
Semantic Enterprise Integration Platforms
Model
Applications
Metadata
60
Let’s Apply to a Utility Project
- Interface Architecture
Other
CIM UML
CIM UML Bridge Information
Extensions Models
Context
Profile 1
System Interface Profile 1
Profile 1 Profile 2 Profile 3
Design
Document
Interface Syntax
Message CIM/RDF
DDL
XML Schema Schema
61
Ex: Project Interaction Test
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
62
Project Integration
Architecture
63
Data Architecture
– Model
MESSAGES
Business Business Business
Entity Entity Entity
SCHEMAS
DB Schema XML Schema
64
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
65
Interface Examples:
66
Typical Web Services
retrieveMarketMeterData WS PI
WS receiveMarketMeterData WS broadcastMarketMeterData
BITS
retrieveMarketInterchange WS
broadcastInvoiceData WS receiveInvoiceData WS
WS broadcastStatusInvoiceData
broadcastGeneralLedgerData WS receiveGeneralLedgerData WS
MC
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
– Outage Scheduling Market Quality System
• Bid Interface and – Dispatch Signals
Validation (ATF updates)
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
70
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 Second Edition CIM Primer
71
Where to Get More Information About
the CIM and Related Standards
• Visit CIM User Group (CIMug) Web Site
– cimug.ucaiug.org or www.cimug.org
• Single site for gaining access to information about the CIM and related
standards
– Includes all standards being developed by IEC TC57 Working Groups 13, 14, 16,
and 19
• Now provide access to:
– Announcements of CIM-related activities and events
– Calendar of activities
– Past meeting presentations
– 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
72
Concluding Remarks
Questions
73