1 Electric System OperationsTennessee Valley Authority

Coordinated Data Exchange

FERC Technical Conference

July 14, 2004

Information Technology for Reliability and Markets

Russell Robertsonfrrobertson@tva.gov

423-751-4183

2 Electric System OperationsTennessee Valley Authority

MISO / PJM / TVA CoordinationMISO / PJM / TVA Coordination

• Memorandum of Understanding – April 2003

• Data Exchange Agreement – May 2004

• Reliability Coordination Agreement – 2005

3 Electric System OperationsTennessee Valley Authority

MISO / PJM / TVA Data ExchangeMISO / 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 Electric System OperationsTennessee Valley Authority

MISO / PJM / TVA Data ExchangeMISO / 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

Model Driven Integration (MDI)Model Driven Integration (MDI)

NERC

Functional Model

CommonInformation

Modeling

Business ProcessModeling

IEC

InterfaceReferenceModel

Application & Database InterfaceTransformations

Implementation(ETL, EAI, Web Services)

BusinessVocabulary

ManagementSupporting:

Semantic Mapping,Cataloging Of

Data Assets, UnifiedModel & Data Queries,

etc.

BusinessVocabulary

ManagementSupporting:

Semantic Mapping,Cataloging Of

Data Assets, UnifiedModel & Data Queries,

etc.

Mapped Interfaces

Data Fields Mapped To Semantic Model

Use Cases

InformationExchange Modeling

Utility Application& DatabaseInterfaces

Utility Application& DatabaseInterfaces

Common InformationModel (CIM)

InformationExchangeRequirements

OtherModels

6 Electric System OperationsTennessee Valley Authority

Generate Run-Time XSLT

NativeInterface

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

CIMInterfaceCIM Concepts

TroubleTicket-TroubleTicket-name

Document NumberTroubleTicket-TroubleTicket-aliasName

TroubleTicket-TroubleTicket-typeOfCall

TroubleTicket-…CustomerAccount-name

TroubleTicket-TroubleTicket-timeOfCall

TroubleTicket-TroubleTicket-hazardCode

TroubleTicket-ActivityRecord-remarks

Mapping to the CIM MessageMapping to the CIM Message

7 Electric System OperationsTennessee Valley Authority

Transformation using CIM XMLTransformation using CIM XML

8 Electric System OperationsTennessee Valley Authority

A Common Message LibraryA 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

TVA Message Management PortalTVA 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 ??

Next Step … A National Portal ??