1. Electric System OperationsTennessee Valley Authority 1 Coordinated Data Exchange FERC Technical Conference July 14, 2004 Information Technology for Reliability and Markets Russell Robertson frrobertson@tva.gov 423-751-4183

2. Electric System OperationsTennessee Valley Authority 2 MISO / PJM / TVA Coordination Memorandum of Understanding – April 2003 Data Exchange Agreement – May 2004 Reliability Coordination Agreement – 2005

3. Electric System OperationsTennessee Valley Authority 3 MISO / PJM / TVA Data Exchange Phase 1 (Grid Visibility Enhancement) – Late Summer 2004 SCADA DataICCP Unit CommitmentWeb Services Merit OrderFTP Transmission and Generating OutagesSDX Reservations and SchedulesOASIS EMS and PSSE ModelsFile Exchange Phase 2 (Reliability Coordination) – 2005 Redispatch Flowgates Transmission Service Reservations Load Forecasts Generator Data Net Interchange Dynamic Schedules

4. Electric System OperationsTennessee Valley Authority 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. Electric System OperationsTennessee Valley Authority 5 Model Driven Integration (MDI) NERC Functional Model Common Information Modeling Business Process Modeling IEC Interface Reference Model Application & Database Interface Transformations Implementation (ETL, EAI, Web Services) Business Vocabulary Management Supporting: Semantic Mapping, Cataloging Of Data Assets, Unified Model & Data Queries, etc. Mapped Interfaces Data Fields Mapped To Semantic Model Use Cases Information Exchange Modeling Utility Application & Database Interfaces Common Information Model (CIM) Information Exchange Requirements Other Models

6. Electric System OperationsTennessee Valley Authority 6 Generate Run-Time XSLT Native Interface Auto-Map CIM Concepts TroubleTicket-TroubleTicket-name TroubleTicket-TroubleTicket-aliasName TroubleTicket-TroubleTicket-typeOfCall TroubleTicket-…CustomerAccount-name TroubleTicket-TroubleTicket-timeOfCall TroubleTicket-TroubleTicket-hazardCode TroubleTicket-ActivityRecord-remarks CIM Interface CIM Concepts TroubleTicket-TroubleTicket-name Document Number TroubleTicket-TroubleTicket-aliasName TroubleTicket-TroubleTicket-typeOfCall TroubleTicket-…CustomerAccount-name TroubleTicket-TroubleTicket-timeOfCall TroubleTicket-TroubleTicket-hazardCode TroubleTicket-ActivityRecord-remarks Mapping to the CIM Message

7. Electric System OperationsTennessee Valley Authority 7 Transformation using CIM XML

8. Electric System OperationsTennessee Valley Authority 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. Electric System OperationsTennessee Valley Authority 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 ??