Tennessee Valley Authority

1
Tennessee Valley Authority
Implementing the Common Information Model (CIM)
2
Why do we need a Common Vocabulary?

• To eliminate inconsistencies and ambiguities when
  sharing information

3
Must demonstrate internal controls

Sarbanes-Oxley Legislation Must demonstrate and
implement internal controls for all systems used
to generate financial reports
4
Why the CIM as the Vocabulary?

• Common Information Model development started
  through efforts of EPRI, vendors and utilities
  through EPRI CCAPI Task Force
• CIM was adopted by International Electrotechnical
  Commission working groups for use in standards
  development
• CIM has become an international standard, IEC
  61970-301 through the efforts of TC57 WG13
• CIM being extended for Distribution and Markets
  by TC57 WGs 14 and 16
• CIM has been harmonized with IEC 61850 through
  the efforts of AHWG07

5
Example Utilities With CIM-Based Integration
Projects (presented in public domain)

• Exelon
• Control Area Management System, Supervisory
  Control And Data Acquisition (SCADA), Outage
  Management System (OMS)
• Florida Power and Light
• Asset Management System (AMS) to provide entire
  distribution network model to Distribution
  Management System (DMS).
• Kansas City Power and Light
• Energy Management System (EMS), DMS, Customer
  Information System (CIS) and Inter-Control Center
  Communications (ICCP) Protocol Server.
• PacifiCorp
• Systems required to support retail access (CIS,
  meter reading, et al.) and data warehouse
• Southern California Edison
• Four Control Centers, OMS, Distribution
  Monitoring Control, Event Logging, and
  Maintenance and Inspection (MI).
• Electricity de France
• Transmission, Asset Management, Customer
  Information, Metering, Network Management

6
Must go from vocabulary to messages

• Websters Dictionary CIM
• Just as you must have sentences to communicate
  orally, you must have messages to share data
  electronically.
• We must develop the standard messages we will all
  share to communicate electronically.

7
Why do we need Common Messaging

• Eliminate inconsistencies and ambiguities
• Eventually will speed up software development and
  interoperability
• Will allow vendors to write applications using
  the same API opening up plug-and-play.

8
Do we develop individual interfaces?
NYISO
TVA
MISO
PJM
DUKE
Hasso Plattner, Keynote Speech, SAP TechEd01
Los Angeles
9
Standardize on Same Messages
Eliminating the complexities and maintenance
costs with hundreds of point-to-point connections
ltmany to manygt growth
ltmany to onegt growth
Total Cost of Ownership
Total Cost of Ownership
of Connections
of Connections
results in lower total cost of ownership
10
Historic Opportunity
We can either take care of ourselves and
implement our own internal systems, or take this
opportunity to take the industry a giant leap
forward in reliability and interoperability
11
Example XML Schema Generated From Energy
Transaction Message Package
12
Auto-Map Semantic Equivalents
Choose Pre-Modeled CIM Message
Import CIM Concept Mappings
Generate Run-Time XSLT
Execute Auto-Mapping
Load Native XML
13
Transformation using CIM XML
14
NERC
Functional Model
Business Process Modeling
Data Fields Mapped To CIM Elements
CIM Thesaurus Catalog Of Data Assets
Common Information Modeling
Use Cases
Interface Reference Model
Information Exchange Requirements
Information Exchange Modeling
IEC
Mapped Interfaces
Common Information Model (CIM)
Implementation (ETL, EAI, Web Services)
Application Database Interface Transformations
TVA Application Database Interfaces
15
Sample CIM Messages TVA completed

• Unit Commitment
• Merit Order
• Flow Gates
• Marginal Zones
• Generation and Transmission Outages
• Available Flowgate Capability
• Load Forecast
• Economic Dispatch
• Redispatch

16
Tennessee Valley Authority Ken Newberry kenewberry
_at_tva.gov [phone]