Presentation is loading. Please wait.

Presentation is loading. Please wait.

Use of ONTEST Resource Status over Telemetry: – ERCOT protocol permits the use of telemetered Resource Status code “ONTEST” during periods of start-up.

Similar presentations


Presentation on theme: "Use of ONTEST Resource Status over Telemetry: – ERCOT protocol permits the use of telemetered Resource Status code “ONTEST” during periods of start-up."— Presentation transcript:

1 Use of ONTEST Resource Status over Telemetry: – ERCOT protocol permits the use of telemetered Resource Status code “ONTEST” during periods of start-up and shut-down sequence, Section 6.5.7.8 (1), Dispatch Procedures – ERCOT Operations is observing that some QSEs are ramping units off-line in “ONTEST” status well above the LSL and at relatively high ramp rates. This is creating operational concerns, particularly, at or around 2200 – ERCOT is making the following changes effective immediately: Generation Resources are expected to be on normal SCED control until reaching no greater than 110% of the units normal LSL before changing status to "ONTEST” To accomplish this, the QSE should do one of the following: 1.Allow SCED to move the unit down to LSL by normal dispatch; 2.The QSE may telemeter the unit’s HSL = LSL in order for SCED to move the unit to LSL at normal ramp rate; then when at or below 110% of LSL the QSE changes the unit status to “ONTEST” for shut-down sequence, – If the QSE is unable to accommodate option one or two, then the QSE shall contact the ERCOT operator and request to switch unit to "ONTEST” for unit shut-down. The ERCOT operator will make every attempt to accommodate this request if and when system conditions allow – Note that his change is for shut-down sequence only. The associated business practice, “ERCOT and QSE Operations Practices During The Operating Hour”, will be updated to reflect this change ONTEST use during Startup/Shutdown

2 Evening Ramp of December 21 st The number of Resources “ONTEST” during the period of largest concern was 9

3 AS OFFERS COMING INTO SASM DAM publishing updates AS offers by subtracting corresponding DAM AS awards. So the following SASM is aware of DAM AS awards. SASM publishing updates AS offers again by subtracting corresponding SASM AS awards. A following SASM is aware of DAM and previous SASM AS awards.

4 AS OFFERS COMING INTO SASM (contd) SASM only uses AS offers with expiration time later than SASM starting time. AS offers resubmitted in the adjustment period are capped for amounts up to the quantity previously offered but not awarded. The additional quantity is capped at SWCAP. Resubmitted AS offers are not adjusted by previous awards

5 Constraints Modeling in SASM vs DAM SASMDAM Values AS schedules in COP.Doesn’t value AS schedules in COP. Values COP status of the study period.Doesn’t value COP status of OD. Only take COP status of the execution date for resource initial status decision. Temporary constraints (min on time, min off time, combine cycle transition constraints, etc.) are not considered. Considers temporary constraints. Any issues related to linking to a three- part offer in DAM is ignored. Considers links between AS offers with three part offers.

6 Post Go-Live Timeline

7 Type your search here

8 Post Go-Live Timeline From 4.4.11, System Wide Offer Caps and Power Balance Business Practices Document First 45 Operating Days – SWCAP set at higher of $180/MWh or 18 MMBTU * FIP – EOC Floor -$50/MWh – Power Balance under-generation penalty price >=50MW is $2251 – All transmission constraints are non-competitive (SCED Step 2) 46 th – 59 th Operating Day – HCAP $2,250; LCAP higher of $500 or 50*FIP – SWCAP is HCAP until Peaker Net Margin exceeds $175,000, then becomes LCAP – EOC Floor -$250/MWh – Competitive constraints used in SCED Step 1 60 th Operating Day forward – HCAP $3,000; LCAP higher of $500 or 50*FIP – Power Balance under-generation penalty price >=50MW is $3001

9 Post Go-Live Timeline From 3.2.5, Publication of Resource and Load Information 60 th Operating Day forward New Report Requirements: Seven days later than OD - For Settlement Intervals with LMPs > 50 * FIP, EOCs at or above 50*FIP Two days later then OD - Entity and Offer price of highest offer dispatched by SCED Resource / Offer information for SCED/DAM 60 days prior to Operating Day

10 Confirmed Energy Trade Behavior From 4.4.2.2, Energy Trade Validation The QSE that first reports the Energy Trade to ERCOT is considered to have confirmed the Energy Trade unless it subsequently affirmatively rejects it. The QSE that first reports an Energy Trade may reject, edit, or delete an Energy Trade that its counterpart has not confirmed. The counterpart is deemed to have confirmed the Energy Trade when it submits an identical Energy Trade. After both the buyer and seller have confirmed an Energy Trade, either party may reject it at any time, but the rejection is effective only for any ERCOT process for which the deadline for reporting Energy Trades has not yet

11 Confirmed Energy Trade Behavior A confirmed trade may only be rejected (i.e. canceled), by either party. Once canceled, the MP that canceled the trade has no trade left to modify. The other party still has an unconfirmed trade, which they may cancel or modify. It has been suggested that it may be better for an MP to be allowed to modify a confirmed trade, which would then turn the trade into an unconfirmed trade until they other party confirms it by submitting the identical modification.


Download ppt "Use of ONTEST Resource Status over Telemetry: – ERCOT protocol permits the use of telemetered Resource Status code “ONTEST” during periods of start-up."

Similar presentations


Ads by Google