International Standards Common Information Model (CIM) CIM for Market Extensions (CME) and Oasis

1
International Standards Common Information Model
(CIM) CIM for Market Extensions (CME)and Oasis

• David Becker, EPRI
• Presented at the NERC/NAESB
• Future of Oasis Conference
• Washington DC 3/29/2005

2
Outline for CIM/Oasis II

• What is CIM?
• Why are Standards important? For Oasis?
• CIM Extensions for Market Operations (CME)

3
History of the Common Information Model (CIM)

• Late 1980s-Early 90s- Informal meetings of
  Industry focused on How to achieve open system
  design
• 1993-Formation of EPRI led CCAPI Task Force
  One vendor did not have all solutions for a
  customer. Need for integration
• Initial Goals of CCAPI
• Provide common information model to facilitate
  information exchange
• Enable use of plug in applications
• Protect application investment
• Framework for integration of legacy systems

4
The Common Information Model Defines Power System
Resources, Attributes and Relationships
Company
Generator
Control Area
Operates
Controls
Supplies Energy for
Connects to
Busbar
Provides Transmission for
Load
Connects to
AC Line
Connects to
Company
Owns
5
Changing Design of CCAPI in 90s

• Design focus changed from EMS control computer
  systems to Enterprise data exchange
• Expand to use new applications with plug and
  play
• USA technical team expanded with all world
  experts
• Standards Org (IEC) WGs of control centers,
  substations, distribution ALL adopt CIM as base

6
Important Milestones

• 9/1996 CIM initially submitted to IEC CIM 10
  final version accepted for standard in 2001.
  First major CIM Installation 1998
• Component technology emerged in late 1990s .
  CCAPI calls them Component Interface Specs (CIS).
  Key to facilitating integration in a distributed
  environment
• Generic Interface Design (GID) initial design
  submitted to IEC 12/2001 after 2 yrs technical
  debate and design
• SW developers create components w/o concern for
  underlying infrastructure
• GID guides standard API for an application to
  exchange/access data

7
CIM Packages
8
Concepts Generalization/Inheritance
Naming
Naming
( from Core)
( from Core)

• Breaker Specialization of Switch
• Switch Specialization of Conducting Equipment
• ConductingEquipment Specialization of
  PowerSystem Resource

PowerSystemResource
PowerSystemResource
(from Core)
(from Core)
ConductingEquipment
ConductingEquipment
PowerTransformer
PowerTransformer
(from Core)
(from Core)
Switch
Switch
Breaker
9
Equipment Inheritance Hierarchy
10
CIM Class Model
11
ENTERPRISE CAPABILITYStandards Position A
Utility To Capitalize On Best Fitting
Off-The-Shelf Products
Customer Information
PI Historian Load Forecaster Dynamic
CircuitRatings
EMS Control Center
GID
GID
GID
Middleware(Integration Bus)CIM 10
Distribution Automation
Engineering
GID
GID
GID
GID
GID
Transmission Grid
Facilities Management
Planning
Standard Interface Specifications
12
Control Center Application Program
Interface(CCAPI ) as an Integration Framework
(start out)
Legacy
System
Legacy
SCADA
SCADA
Network
System
Programs OASIS?
CIM Server
Public
Public
Legacy
Data
Data
Wrapper
Integration Bus
User
PCs
Public
ICCP
Data
Network
Programs
ICCP
13
Control Center Application Program Interface
(CCAPI ) as an Integration Framework

Legacy
System
Generation
Network
Alarm
Accounting/
Topology
PI-Historian
Control
Applications
Processor
Settlement
Processor
Legacy
SCADA
SCADA
Network
Programs
Programs
Programs
CIM Server
System
Programs
Programs
Public
Public
Public
Public
Public
Public
Legacy
Data
Data
Data
Data
Data
Data
Wrapper
This buscan be spread across multiple entities
Component Execution System
and Component Adapters (e.g., Integration Bus)
User
Distribution
PCs
Management
Public
Public
ICCP
Data
Systems
Data
Network
Component
Programs
Programs
Interface
ICCP
14
CIM today

• CIM 10 is ready for use. Has Widespread
  acceptance
• CIM for Asset Mgmt also robust and ready for your
  use
• Deployment of CIM Projects now ongoing worldwide
• Integration of CCAPI into Substations
• Integration of CIM for Market Extensions

15
Why International Standards

• Global world. Many vendors international
• Vendors willing to build products to STANDARDS
• Allows multiple designs to compete
• New applications can be installed
• Migration path more robust flexible
• Lower vendor costs to produce and sell

16
TC 57 Slide Organization
Important Standardization Activities
Component Container
TC57
Technology
Standards
_________________
Technology
CORBA (OMG)
WG3
___________
WG18
RTUs
Enterprise Java Beans

ISO ODP
WG9
DCOM (Microsoft)

ISO Security
WG17
Distribution
Feeders
Metadata
WG16
Repository
Stds
Market
WG7
SPAG
Ops

IEEE
Control
Centers

ebXML
WG15

IETF Internet
Security
WGs 3 10
Services
WG14
Substations
EPRI
W3C Web

DMS
UCA2
Services
EPRI
WG13
Project
EMS

CIRED
CCAPI
Open GIS
Project

Object

DistribuTECH
OPC

GITA
Mgmt.
Foundation

TD
Group
OAG
17
Initiative of CIM for Market Extensions (CME)
Project

• FERC requested EPRI to extend the CIM
  architecture to support the SMD and facilitate
  markets
• EPRI initiated CIM for Market Extensions (CME)
  project with ISOs/RTOs ,vendors
• Made up of utility and industry organizations to
  support this initiative
• Managed by Xtensible Solutions for EPRI
• Focus on the Day-Ahead and Real-Time Market
  Processes to define extensions needed for the CIM
  data model to support these processes
• Goal of CME
• Standardize information format and application
  interfaces to make the North American wholesale
  electricity market run efficiently, reduce seams
  issues and save substantial costs in the
  development of applications for each RTO
• Will allow RTOs to buy best-of-breed applications
  and communicate with Independent Transmission
  Organizations (ITOs) or other ISOs and RTOs in a
  standard information format
• Will allow marketers, Load Serving Entities
  (LSE), and Generator Serving Entities (GSE) to
  access information and bid into the RTOs
  preferred format

18
Scope of CME Project
Inter-ISO/RTO Messaging
Intra-ISO/RTO Messaging
Generators
RTO A
RTO A
ISO B
MIS
Settlement
Marketers
ISO D
RTO C
SCUC
SCED
Loads
CIM extensions in scope for CME
XML information exchange model and terms database
message standards to be developed as part of
RTO/ISO Data Initiative
Market, Load, Generation Participants CIM
extension and information exchange model Other
Initiatives and/or Future Phase(s)
19
CME Phase 1 Deliverables

• EPRI Technical Report CIM Extensions to Support
  Market Operations Phase 1 Day Ahead and Real
  Time Scheduling Applications (TR 1009455)
• CIM representation of data requirements in table
  format with mapping to existing applications
• Extended CIM UML model to support the SCUC/ED/LMP
  data requirements
• New Market Operations package
• Updates to existing CIM Packages
• Reuse of existing IEC 61970 and 61968 Packages
• Created XML Schema for the Input/Output data
• Basis for the message standards defined for the
  SCUC application by the ITC Standards
  Collaborative

20
Phase 1 CIM UML Extensions

• New CIM Package created for Market Operations
• Bid
• Resource
• RTO
• Security Constraints
• Clearing Results
• Updates to existing CIM Packages
• Energy Scheduling
• Financial
• Reuse of existing IEC 61970 and 61968 Packages
• 61970 Core, Generation/Production,
  Measurements, others
• 61968 - Core2/Top Level and Activity Record

21
CME Phase 2 Deliverables

• EPRI Technical Report CIM Extensions to Support
  Market Operations Phase 2
• Day Ahead and Real Time Scheduling Applications
  (TR 1011431)
• Extended CIM UML model to support the SCUC/ED/LMP
  data requirements
• Network Analysis applications (e.g., State
  Estimator, Security Analysis, OPF, etc.)
• Ex-Post LMP
• Financial Transmission Rights (i.e., Congestion
  Reservation Rights)
• Facilitated Checkout (FCO)
• Updates to the CIM UML Rose model for Market
  Operations

22
Benefits Derived From CME Project

• Basis for defining standard messages for exchange
  of market operations data in support of SMD
• Provides semantic layer for ensuring consistency
  in meaning and use of information exchanged to
  support market operations and reliability
• Facilitates implementation of market business
  processes
• Provides architectural layer to map business
  terms to data definitions used in message
  payloads
• Basis for new RTO/ISO SMD development efforts
• Ex CAISO is using CME extensions on Market
  Redesign project as starting point for developing
  message payloads for information exchange between
  systems and applications
• Submitted to IEC for consideration as
  international standard
• Could lead to adoption by European Transmission
  Operators

23
CME Phase 3 Prioritized Activities

• High Priority
• Standard message definitions
• SCED and Ex-Ante LMP message standards
• FCO revisit other ISO/RTO requirements
• Network Analysis and Ex-Post LMP
• Financial Transmission Rights
• Market participant interaction - Upload
  electronic bids to RTO/ISO and download results.
• Market participant interaction - Settlement data
  exchange and True-Ups
• Plan and conduct a Workshop or Webinar on CME
  results for interested users (after Phase 2
  message definition complete)
• High to Medium Priority
• Control Area seams-related data exchange
• Applications include ramp data, Total
  Transmission Capacity (TTC), ATC, Available
  Flowgate Capacity (AFC), etc. that are exchanged
  among control areas

24
CME Phase 3 Prioritized Activities

• Medium Priority
• Network model maintenance component (i.e.,
  complete model transfers, incremental model
  updates, and partial model transfers)
• Intelligent Alarming
• Sharing relaxant relevant alarms with neighbors
  electronically
• Visualization
• Information exchange to enable display of Market
  and Reliability data in a graphical form that
  will assist in decision making
• Low Priority
• Market monitoring information
• Plan for and conduct an Interoperability test in
  2006 for CME standard messages developed on the
  extended CIM
• Market participant interaction Outage reporting
• Develop a User Guide on how to use the CIM for
  market operations messaging.

25
CIM XML Interoperability Tests

• EPRI has sponsored six interoperability tests
  based on the CIM XML standards
• Six interoperability tests successfully completed
  exchanging real-world large scale models (12,000
  bus) and several sample models (40 to 100 bus)
• December 2000 Orlando, Florida
• April 2001 Las Vegas, Nevada
• September 2001 Monterey, California
• July 2002 San Francisco, California
• November 2003 Cleveland, Ohio
• July 2004 Folsom,California
• Validated the use and acceptance of this standard
  by suppliers who provide products to the
  electric utility industry
• Test reports available from EPRI

26
CIM and Interoperability Tests

• Interoperability Tests very important
• Test 6 completed in 7/2004 Results Exchange
  ICCP Object IDs, Full model, Incremental
  updates, partial model, new validator tools,
  clean up items, etc
• Include all transmission grid power system model
  (NERC) Requirements
• Actual testing between vendors
• Added distribution application plus applications
  from Control Centers, Substations, etc
• CIM/GID/CIS progress as STANDARDS

27
CIM Status and Access Information

• CIM exists as ROSE model and IEC standard (MS
  Word)
• Complete CIM (61968, 61970, and Market Operations
  packages in UML) available on IEC CIM User Web
  site (www.cimuser.com)
• Also available for download
• Current 61970 CIM model (cim10_030501.mdl)
• RDF Schema Version for CIM Version 10
• XML Message Schemas for 61968 messages
• EPRI published reports on Control Center
  Application Program Interface (CCAPI)
• Site includes CIM 10,IOPs 1-6, CME reports
  downloadable

28
CIM Status and Access Information

• Survey ( 2 years old) shows over 47 CIM
  installations in US and over 55 applications
  delivered. New survey to be done in 2005.( How do
  you count rabbits?) USA started 2 years ahead of
  other countries
• Globally accepted now. Known implementations in
  process or done in Belgium, Brazil, China,
  France, Ireland, Jordan, Russia, Slovenia, South
  Africa, Spain, others(?)

29
New names of people to contact

• David Becker, EPRIdbecker_at_epri.com650-8552307
• Terry Saxton, Xtensible Solutionstsaxton_at_xtensibl
  e.net763-4733250
• For general assistance
• Angelica Kamau, EPRIakamau_at_epri.com650-85579
  87