1 / 92

RPRS

RPRS. March 23, 2006. Presented by ERCOT Art Deller Bill Kettlewell. Market Support Services March 30, 2005. RPRS. Overview of RPRS Operations How and Why does ERCOT use it? How does a QSE bid it? How does a QSE deploy it? Settlements How does a QSE get paid?

Download Presentation

RPRS

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. RPRS March 23, 2006 Presented by ERCOT Art Deller Bill Kettlewell Market Support Services March 30, 2005

  2. RPRS • Overview of RPRS • Operations • How and Why does ERCOT use it? • How does a QSE bid it? • How does a QSE deploy it? • Settlements • How does a QSE get paid? • How does the Market get charged?

  3. RPRS • Overview of RPRS

  4. Definition • Capacity procured from Resources otherwise unavailable to ERCOT in the hours ERCOT requests RPRS. • Includes: • Generation Resources Off-line. • Generation Resources expected to be Off-line in the requested hours • LaaRs that are On-line and available time of procurement * * LaaRs will not be able to participate initially upon initiation of the RPRS functionality. Section 6.5.6

  5. Definition Two Components • Market Solution • Based on RPRS bids • Also can use Generic Cost • Out of Merit Capacity – OOMC • Capacity selected due to place, or absence, from the bid stack • LaaRs not availble for OOMC Section 6.1.6 and 6.1.10

  6. Definition Purpose: Purchase Capacity in order to make Energy available to solve the following system issues: • Capacity Insufficiency • Zonal Congestion • Local Congestion Section 6.1.6 and 6.1.10

  7. Definition Operational Assumptions • Units expected to come on-line in selected hours, to LSL. • Capacity considered on-line for Local and Zonal Congestion requirements • Energy from procured units is placed in the Balancing Energy Service bid stack • Quantity >= HSL (HOL) – LSL (LOL) Section 6.4.2 and 6.7.5

  8. Why do we need RPRS? RPRS Generation Available Online Forecast Load

  9. Payment to Providers Providers of RPRS are paid for three distinct types of service: • Capacity Insufficiency • Zonal Congestion • Local Congestion Section 6.8.1.10 and 6.8.1.11

  10. Payment to Providers Units selected for Capacity Insufficiency or Zonal Replacement are paid: • the higher of their bid or, • the highest MCPC for all RPRS procured during the procurement processes. Section 6.8.1.10 and 6.8.1.11

  11. Payment to Providers Units selected for Local Replacement are paid: • Resource Category Generic Startup Cost for starting • Resource Category Minimum Energy Cost minus MCPE for operating at the LSL. Section 6.8.1.10 and 6.8.1.11

  12. Payment from Market Payment from the Market is collected through the following charges: • Under Scheduled Capacity Charge • RPRS Zonal Congestion Charge • RPRS Uplift Charge Section 6.9.2.1.1

  13. Payment from Market Under Scheduled Capacity Charge • Costs for Capacity Insufficiency are directly assigned to the QSE whose schedules show insufficient capacity scheduled compared to Adjusted Metered Load. This can also result from Mismatches. Section 6.9.2.1.1

  14. Payment from Market RPRS Zonal Congestion Charge • RPRS Zonal Congestion costs will be directly allocated to QSEs whose schedules have an impact on a congested Commercially Significant Constraint Section 7.3.4.2

  15. Payment from Market RPRS Uplift Charge • The total payments for Zonal, Local and Capacity Insufficiency RPRS are netted with; • the direct assigned costs for Zonal RPRS plus direct assigned Congestion impact and TCR Payments • The difference is uplifted at Load Ratio Share to all QSEs. Section 6.9.2.1.2

  16. RPRS • Overview of RPRS • Operations • How and Why does ERCOT use it?

  17. Why Correct total Capacity Insufficiency, Zonal Congestion and Local Congestion • Based on scheduled resources and load forecasts • Procure Capacity in appropriate locations to provide for system security • To ensure operational security Section 6.4.2

  18. How Provide capacity from which energy would be available to solve the following system security violations: • System Capacity insufficiency • Using any RPRS bid (or Generic for units with no bids) • Zonal Congestion • Using RPRS bids by Zone in Merit Order (or Generic for units with no bids) • Local Congestion • Using Resource Category Generic Cost Section 6.6.3.2.1

  19. RPRS Inputs Inputs • Resource Plans (at time of procurement) • HSL • LSL • Load Forecast • QSE Schedules (at time of procurement) Section 6.6.3.2.1

  20. RPRS Outputs Output • Unit specific deployment for RPRS • Optimized for entire 24 Hr period Section 6.6.3.2.1

  21. RPRS • Overview of RPRS • Operations • How and Why does ERCOT use it? • How does a QSE bid it?

  22. RPRS Bid Bidding Requirements • Resource Parameters • Designation of specific Resource • Amount of Capacity • Time Constraints • Startup Time (Resource Plan) • Minimum Run Time (Registration) • Minimum Down Time (Registration) • Hours the bid is effective (Bid) • Expiration time of bid (Bid) • Costs • Start-up - $/MW (< $1,000/MW) • Operating - $/MW/Hr (<$1,000/MWh) • Balancing Energy Bid Point in $/MWh Section 4.4.16

  23. RPRS Bid Balancing Energy Bid Point in $/MWh Max price that balancing energy bids will be entered for the capacity accepted in the RPRS market. Section 4.4.16

  24. RPRS Bid Example <?xml version=”1.0”> <!DOCTYPE Bids SYSTEM “bids.dtd”> <Bids> <ReplacementBid> <DAY>20010101</DAY> <FIRSTHOUR>1300</FIRSTHOUR> <LASTHOUR>1800</LASTHOUR> <CAPACITY>100</CAPACITY> <RSRC_ID>GT-1</RSRC_ID> <RSRC_TY>GEN</RSRC_TY> <CMZONE>A</CMZONE> <STARTUP_PRICE>30.00</STARTUP_PRICE> <PERHOUR_PRICE>50.00</PERHOUR_PRICE> <EXPIRATION_DATE>20010101</EXPIRATION_DATE> <EXPIRATION_TIME>1100</EXPIRATION_TIME> <BES_BIDPOINT>9.99</BES_BIDPOINT> </ReplacementBid> </Bids> ERCOT Participant interface: XML v 4.o, Sec 3.4

  25. Requirements RPRS Requirements • Resources must provide telemetered output signal, including breaker status • Minimum amount is 1 MW • Resources must meet additional technical requirements (Protocol Section 6.10) Section 6.5.6

  26. Requirements RPRS Requirements cont. • Only one RPRS bid from any Resource • Selected Resource must be able to respond in the hours selected • QSEs supplying RPRS must comply with Balanced Schedule • Bids in accordance with Section 4 Section 6.5.6

  27. Requirements RPRS Requirements cont. • QSEs may not self-arrange RPRS • Eligible Resources with no bids can still be selected • Bid price set by generic cost times an adjustment factor • If selected, deployed and paid as an OOMC deployment Section 6.5.6

  28. RPRS • Overview of RPRS • Operations • How and Why does ERCOT use it? • How does a QSE bid it? • How does a QSE deploy it?

  29. Day-Ahead Procurement • RPRS procured at 1800, based on: • ERCOT’s 1100 Load forecast • 1100 Day-ahead schedules (unless modified by 1300 in accordance with 4.4.10) • Bids submitted by 1600 • Resource Plans • ERCOT notify accepted RPRS bids by 1800 * Insufficient RPRS bids addressed with OOMC Section 4.4.17

  30. Adjustment Period Procurement RPRS procured during Adjustment Period based on: • RPRS Bids (can be modified after 1800) • Resource Plans • ERCOT next day Load Forecast Section 6.6.3.2.1 and 4.5.6

  31. Objective of RPRS Engine The goal of the RPRS Clearing Engine is 24 Hour Optimization to minimize total cost, based on: • Resource Category Generic Cost • Capacity price • Operation Price • Resource Shift Factors And also respect; • Lead time • Minimum Up time • Minimum Down time For the whole Operating Day while meeting security constraints for each hour. Section 4.4.17 and 6.6.3.2.1

  32. RPRS Three Step Clearing Process • Local Congestion first • Zonal Congestion & System Balance simultaneously • Operator optional intervention • MCPC Calculation • Marginal cost for insufficiency determines MCPC • Marginal cost to solve CSC determines Shadow Price for Capacity for CSC Congestion Section 6.6.3.2.1

  33. RPRS Notification Example <?xml version=”1.0”?> <!DOCTYPE Notifications SYSTEM “notes.dtd”> <Notifications> <RepBidSelected> <DAY>20010101</DAY> <STRIKEHOUR>1200</STRIKEHOUR> <FIRSTHOUR>1100</FIRSTHOUR> <LASTHOUR>1800</LASTHOUR> <RSRC_ID>GT-1</RSRC_ID> <RSRC_TY>GEN</RSRC_TY> <BIDMW>100</BIDMW> <STRIKEMW>100</STRIKEMW> <STARTUP_PRICE>25.00</STARTUP_PRICE> <PERHOUR_PRICE>10.00</PERHOUR_PRICE> <LEADTIME>30</LEADTIME> <STARTHOUR>1200</STARTHOUR> <STOPHOUR>1600</STOPHOUR> <CONGESTION>F</CONGESTION> </RepBidSelected> </Notifications> ERCOT Participant interface: XML v 4.o, Sec 5.12

  34. RPRS Which Resources are Eligible for RPRS? • Local Congestion – any generation resource offline and available will be eligible. • Zonal Congestion, Capacity – any offline and available generator or online, available, and active LaaR* resource with a RPRS bid. • RMR units may be used to offset RPRS, if economical. * LaaRs will not be able to participate initially upon initiation of the RPRS functionality. Section 6.6.3.2.1

  35. RPRS What does the QSE do when RPRS is Procured from the QSE? • Updates their Resource Plan accordingly • Adds Capacity from RPRS resource into Balancing Bids • Brings specified resource online for specified hours at LSL • Incorporate LSL into Energy Schedules. Options include: • Reducing output of other Resources • Selling additional BES • Using Relaxed Balanced Schedules • RPRS is not an instructed deviation Section 6.4.2

  36. RPRS • Overview of RPRS • Operations • How and Why does ERCOT use it? • How does a QSE bid it? • How does a QSE deploy it? • Settlements

  37. RPRS Settlement Inputs to Settlements: • RPRS Procured (Type and Quantity) • MCPC and Shadow Prices • Bids • Schedules • Resource Plans • Generic Cost • Adjusted Metered Load

  38. RPRS Settlement Process: • Pay Providers: • Capacity Insufficiency • Zonal Congestion • Local Congestion • Collect from Users: • Under Scheduled QSEs • Zonal Congestion • Uplift to Market

  39. RPRS • Overview of RPRS • Operations • How and Why does ERCOT use it? • How does a QSE bid it? • How does a QSE deploy it? • Settlements • How does a QSE get paid?

  40. Payment If a unit was selected for Local Congestion, how does the QSE get paid?

  41. Decide if deployment was Local, Zonal or System Balance Local Award Determine Awarded Amount Determine Hours Of Award Determine Startup and Operating Payment

  42. RPRS Local Replacement Reserve (LCFLAG = 1) Steps • LRPQ – Awarded amount • LRPHR – Number of hours awarded • LPS – Start up payment • LPO – Operation price

  43. Hours Hr03 Hr04 Hr05 Hr06 Hr07 Hr08 Hr09 Hr10 Hr11 Hr12 Hr13 Hr14 Hr13 LCFLAG ........ 2 2 1 1 1 0 0 0 2 2 2 2 ....... Interval Int17 Int18 Int19 Int20 Int21 Int22 Int23 Int24 Int25 Int26 Int27 Int28 Hour 4:15 4:30 4:45 5:00 5:15 5:30 5:45 6:00 6:15 6:30 6:45 7:00 HSL ........ 141 145 151 155 160 165 170 165 161 155 151 145 ....... Hours Hr03 Hr04 Hr05 Hr06 Hr07 Hr08 Hr09 Hr10 Hr11 Hr12 Hr13 Hr14 Hr13 LRPQ ........ 0 0 148 165 153 0 0 0 0 0 0 0 ....... RPRS LRPQ – Local Replacement Quantity Hour 5 (Intervals 17 – 20): LRPQ = ( 141 + 145 + 151 + 155 ) / 4 = 148 (Used to calculate RCGSC)

  44. Hours Hr03 Hr04 Hr05 Hr06 Hr07 Hr08 Hr09 Hr10 Hr11 Hr12 Hr13 LRPQ ........ 0 0 148 165 153 0 0 0 0 0 ....... LRPHR ........ 0 0 3 3 3 0 0 0 0 0 ....... RPRS LRPHR – number of hours instructed LRPHR = 3

  45. RPRS • LPS – Local RPRS start up payment • Determine if “Hot” or “Cold” start (Combined Cycle only) • Hot = Less than 5 hours from shut down to start up • Cold = 5 hours or more from shut down to start up. Section 6.8.1.11

  46. RPRS • LPO – Local RPRS Operating payment • Unit will get paid for what it generated, up to it’s LSL. Section 6.8.1.11

  47. RPRS LSL < GSITETOT 120 GSITETOT 100 Low Sustainable Limit 30MWh 25MWh 0

  48. RPRS LSL > GSITETOT 120 Low Sustainable Limit 100 GSITETOT 30MWh 25MWh 0

  49. RPRS • LPCRPAMT – Local Procured Capacity Replacement Amount Section 6.8.1.11

  50. Local Replacement Payment Local Replacement Section 6.9.2.1.2

More Related