/
Reliability-Must-Run (RMR) Reliability-Must-Run (RMR)

Reliability-Must-Run (RMR) - PowerPoint Presentation

phoebe-click
phoebe-click . @phoebe-click
Follow
385 views
Uploaded On 2018-02-16

Reliability-Must-Run (RMR) - PPT Presentation

Dispatch and Commitment Jeff Gilbertson ERCOT RMR Workshop May 24 2016 Market Operations Commitment The QSE will submit the Availability Plan indicating availability of the RMR Unit by 0600 in the DayAhead Protocol 432 and will submit and keep the COP up to date Protocol 397 ID: 631940

sced rmr offer unit rmr sced unit offer protocol curve energy dispatch commitment ercot market reliability system operations day capacity mitigated swcap

Share:

Link:

Embed:

Download Presentation from below link

Download Presentation The PPT/PDF document "Reliability-Must-Run (RMR)" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

Slide1

Reliability-Must-Run (RMR)

Dispatch and Commitment

Jeff Gilbertson

ERCOT

RMR Workshop

May 24, 2016Slide2

Market Operations - Commitment

The QSE will submit the Availability Plan indicating availability of the RMR Unit by 0600 in the Day-Ahead (Protocol 4.3(2)), and will submit and keep the COP up to date (Protocol 3.9(7)).

In practice, RMR Units are not offered by ERCOT into the Day-Ahead Market.ERCOT will make the RMR Unit available for commitment by the Daily and Hourly Reliability Unit Commitment (RUC) processes only when it has determined that the RMR is likely to be needed in Real-Time for reliability reasons (Protocol 4.4.8).RUC processes will use a Three-Part Offer created by ERCOT which reflects contracted costs in Start-up and Minimum-Energy, with an Energy Offer Curve at the System-Wide Offer Cap.

2Slide3

Market Operations

- Commitment

An RMR Unit requiring a longer notification time to prepare for operation will be notified of their commitment at an appropriate time in advance of the Operating Day(s) and will be processed as commitments in the DRUC processes for each Operating Day.3Slide4

Market Operations - Dispatch

The RMR Unit will be online and available to SCED for each entire hour in which it was committed by a RUC process.

An Energy Offer Curve will be created by ERCOT at the System-Wide Offer Cap for use by SCED.When the RMR Unit is contracted for capacity, the verifiable O&M cost will be increased such that the Mitigated Offer Curve is greater than the SWCAP, resulting in an Energy Offer Curve priced at the SWCAP that will never mitigated by SCED (Protocol 4.4.9.4.1 (1)(a)).SCED will dispatch this RMR Unit above LSL for capacity only after all other available capacity with LMPs below SWCAP are used.4Slide5

Market Operations - Dispatch

When the RMR Unit is contracted for transmission congestion, the verifiable O&M cost will not be modified. The RMR EOC may be mitigated by SCED to an EOC reflecting verifiable costs when non-competitive transmission constraints are active.

SCED may dispatch the resource above LSL to resolve congestion or when the mitigated Energy Offer Curve is economic.Prior to declaring EEA Level 1, ERCOT may dispatch the RMR Unit to full capacity through use of a VDI or manual override (Protocol 6.5.9.4.1(c)).5Slide6

Market Operations – Reliability Deployment Price Adder

RMR Units that are on-line and available to SCED will have their inputs to the SCED pricing run modified as follows (Protocol 6.5.7.3.1(2)(a)):

LSL, LASL, and LDL set to zero MW.Energy Offer Curve extended at SWCAP to zero MWThe Reliability Deployment Price Adder will be determined by taking the positive difference between pricing-run System Lambda and SCED System Lambda, limited by (Value of Lost Load – SCED System Lambda).All other appropriate input modifications will apply. See Protocol 6.5.7.3.1 for details.6