Coordinated Data Exchange FERC Technical Conference

1
Coordinated Data ExchangeFERC Technical
Conference July 14, 2004 Information Technology
for Reliability and Markets

• Russell Robertson
• frrobertson_at_tva.gov
• 423-751-4183

2
MISO / PJM / TVA Coordination

• Memorandum of Understanding April 2003
• Data Exchange Agreement May 2004
• Reliability Coordination Agreement 2005

3
MISO / PJM / TVA Data Exchange

• Phase 1 (Grid Visibility Enhancement) Late
  Summer 2004
• SCADA Data ICCP
• Unit Commitment Web Services
• Merit Order FTP
• Transmission and Generating Outages SDX
• Reservations and Schedules OASIS
• EMS and PSSE Models File Exchange
• Phase 2 (Reliability Coordination) 2005
• Redispatch
• Flowgates
• Transmission Service Reservations
• Load Forecasts
• Generator Data
• Net Interchange
• Dynamic Schedules

4
MISO / PJM / TVA Data Exchange

• TVA is complying with previously established
  MISO-PJM data exchange requirements
• These requirements are based on existing data
  standards where possible
• TVA is participating on committees as new
  requirements are developed

5
Model Driven Integration (MDI)
NERC
Business Process Modeling
Data Fields Mapped To Semantic Model
Functional Model
BusinessVocabularyManagement Supporting Semanti
c Mapping, Cataloging Of Data Assets,
Unified Model Data Queries, etc.
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)
Other Models
Utility Application Database Interfaces
Application Database Interface Transformations
6
Mapping to the CIM Message

Generate Run-Time XSLT
7
Transformation using CIM XML
8
A Common Message Library

• Eliminates inconsistencies and ambiguities
• Speeds software development and allows
  interoperability
• Allows vendors to write applications using the
  same API opening up plug-and-play.

9
TVA Message Management Portal

1. Publish and catalog messages
2. Test and validate messages
3. Notify users of message updates and additions
4. Links to public information on best practices for
   CIM implementation

Next Step A National Portal ??
10
(No Transcript)