RTO_SS

2. RTO_SS Electronic Scheduling System For Southwest Power Pool

3. What is RTO_SS? • An electronic scheduling system that utilizes the existing infrastructure and replaces the “1960’s” style of scheduling. • Meets all FERC requirements under Order 2000 • Meets all NERC scheduling requirements • An interim step to OASIS Ver. 2

4. Design Goals Flexibility • Data must be easily viewable and downloadable • Must be able to handle different schedule types Use standard formats • Most Schedules will be entered through NERC tags • Downloaded Schedules will be in a standard format • Net Schedule Information posted on ICCP node Meet NERC and FERC requirements Reduce work load • Replaces tag approval interface • Most Schedules should be verified electronically • Simplify schedule checkouts

5. Design Goals (cont.) Reliability/Performance • Redundant servers at a remote site • Reliable and redundant communications • Must be responsive under heavy user use Meet future needs • RTO seams issues • FERC OASIS v. 2 • NERC Electronic Scheduling • Retail Open Access Cost Meet Time Line • Scheduling System to be available for testing 3/1/01 • Fully functional by 5/1/01

6. RTO_SS System Non-RTO_SS Participant Entities RTO_SS User CA, TP, GP, etc. Optional Connections OATInet Internet OATInet Internet Internet SPPnet ICCP OATI Tag Authority SPP SPPnet Tag Approval webData webScheduler MOSDW Internet

7. Schedule Types • Energy Schedules via Tags • Reserve Sharing Schedules via ARS • These will be uploaded via ARS for immediate notification and implementation by Control Areas • Loss Repayment Schedules • These are calculated from tags containing losses that were self-supplied and are to be distributed real-time • Dynamic Schedules via Tags • Dynamic schedules are identified by “DYN” in comments field on tag. • System is capable of defining new schedule types

8. RTO_SS Displays • Schedule Approval and Status Displays • Includes ability to view individual tags • Variety of Checkout Screens • Includes ability to checkout groups of individual schedules by totals, such as daily on/off peak totals • Includes ability to resolve schedule mismatches between control areas • Capable of receiving Schedule “Actuals” and calculating Inadvertent between members • Can view schedules by SOURCE or SINK within the member CA • Additional displays exist… OATI wants to meet the needs of the users.

9. RTO_SS Summary • SPP and OATI have nearly completed the detail design and functional requirements phase • SPP Members will access OATI via web browser for schedule approvals, review, checkout, etc. • System includes webData system at SPP for interfacing with SPP Members for data exchange

10. RTO_SS Milestones • March 7, 2001 – • Beta Version of webData with populated information to be installed at SPP • SPP will hold training session with Members’ IT Support Staff to discuss data exchange, I.e. Sched Net Interchange • Meeting details will be forthcoming • SPPNET and OATINET interconnection complete • March 19, 2001 – • Acceptance Testing Begins

11. RTO_SS Milestones • April 9, 2001 – • Unstructured Testing Begins for SPP and Members • April 11-12, 2001 – • SPP holds User Training Sessions for Members • May 1, 2001 – • RTO_SS fully operational • June 1, 2001 – • Begin testing requirements for interface between RTO_SS and Market Operations System

12. Upcoming SPP Systems • Market Operations Settlement System • Implements SPP supplied Ancillary Srvcs • Congestion Management System • Will eliminate TLRs by pricing the constraint.

13. RTO_SS Questions • Ask Jim Hon!!!!!!

14. www.spp.org