Rto ss
This presentation is the property of its rightful owner.
Sponsored Links
1 / 20

RTO_SS PowerPoint PPT Presentation


  • 88 Views
  • Uploaded on
  • Presentation posted in: General

RTO_SS. Electronic Scheduling System For Southwest Power Pool. What is RTO_SS?. The result of a three year effort Electronic scheduling system that utilizes existing infrastructure and replaces the “1960’s” style of scheduling. Meets all FERC requirements under Order 2000

Download Presentation

RTO_SS

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Rto ss

RTO_SS

Electronic Scheduling System

For Southwest Power Pool


What is rto ss

What is RTO_SS?

  • The result of a three year effort

  • Electronic scheduling system that utilizes existing infrastructure and replaces the “1960’s” style of scheduling.

  • Meets all FERC requirements under Order 2000

  • Meets all NERC scheduling requirements


Design goals

Design Goals

Flexibility

  • Data must be easily viewable and downloadable

    • Allows users to access data in multiple ways

  • 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


Status of rto ss

Status of RTO_SS

  • Currently in SPP Testing Phase

  • User Testing Set for April 17, 2001

  • Parallel Testing begins April 27, 2001

    • Details to be published later

  • System Online May 15, 2001

  • Schedule Monitored by SPP STF


Design goals cont

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

  • Fully functional by 5/15/01


Roles of rto ss participants

Roles of RTO_SS Participants

  • Transmission Provider (TP1, TP2)

  • Generation Provider (GP)

  • Generation Control Areas (GCA)

  • Load Serving Entity (LSE)

  • Load Control Area (LCA)

  • Purchasing/Selling Entity (PSEs)

  • Scheduling Control Areas (CA1, CA2)

  • 1st Tier Control Areas (First Tier In / Out)


Rto ss

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


Rto ss

RTO_SS Process

PSE Generates Tag

Schedules

NSI

Optional

Connections

Internet

SPPnet

Internet

OATInet

OATInet

Approval

EMS (AGC)

Internet

PSE

OATI

GP

Tag Authority

SPP

GCA

Source

SPPnet

Tag Approval

Checkout

LSE

Sink

webScheduler

MOSDW

Internet

TP


Schedule types

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


Data exchange

Data Exchange

  • OATI’s webData Product at SPP

    • Contains all schedule data locally to SPP

  • SPP Methods for Exporting sched data

    • OPS1 Web Access for Viewing/Download

    • Automated Procedures by SPP Staff based on User Needs

    • ODBC Backend Connectivity

  • Currently configuring this setup


Rto ss displays

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.


Rto ss displays1

RTO_SS Displays


Rto ss displays2

RTO_SS Displays


User requirements

User Requirements

  • User Registration with the SPP

    • For Sources and Sinks

    • Proxies

  • RTOSS Access

    • Already done if current OATI user under SPP

    • PSE

    • 1st Tier CA

    • Generation Providers

    • LSE’s


Contingency plans

Contingency Plans

  • System Redundancy

    • Redundancy at OATI

    • Redundancy at SPP

    • ICCP Redundancy

    • Redundant Communication Access


Contingency plans1

Contingency Plans

  • What if ICCP link is down?

    • Data is still viewable from GUI

  • What if SPPNET is down?

    • Access RTO_SS via the Internet

  • What if OATI has major failure?

  • What if SPP has major failure?

  • Any other major points of failure?


Rto ss milestones

RTO_SS Milestones

  • April 17, 2001 –

    • Unstructured Testing Began for SPP and Members

  • April 11-12, 17-19, 24-26 2001 –

    • SPP User Training Sessions for Members

  • April 27, May 1, 2, 4, 8, 9, 11, 2001 –

    • Parallel Testing

  • May 15, 2001 –

    • RTO_SS fully operational

  • June 1, 2001 –

    • Begin testing requirements for interface between RTO_SS and Market Operations System


Summary

Summary

  • RTOSS is still a work in progress

    • HTML screens 95%+ complete, may see some additional changes, additions

    • Still have “back office” interfaces to complete at SPP

  • STF is working on some business rules.

    • Tariff vs Tagging timing requirements

    • Unique Schedules

  • STF encourages the users to utilize the automated features in their systems.

    • Automated access to schedules

    • Net schedule totals for AGC control


Rto ss

Contacts at SPP:501-664-0146

Technical Questions:Barbara Gibson ext. 245

Joshua Kirbyext. 306

Aaron Rallsext. 279

Operational Questions:Shari Brownext. 236

John Taylorext. 266

www.spp.org


  • Login