ERCOT's RUC Process for Ancillary Services
Learn about how opting out of the RUC process impacts obligations to provide Ancillary Services in ERCOT, with insights on potential protocol issues and ways to improve the process for better clarity.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
RUC for AS If the Resource opts out of the RUC does it impact the obligation to provide AS? It shouldn t, but Protocols are not clear
Definitions Reliability Unit Commitment (RUC) A process to ensure that there is adequate Resource capacity and Ancillary Service capacity committed in the proper locations to serve ERCOT forecasted Load. Reliability Unit Commitment (RUC) Buy-Back Hour An Operating Hour for which a QSE with a Resource that is not an RMR Unit that has been committed to come On-Line by a RUC process or Verbal Dispatch Instruction (VDI) may choose, at its sole discretion, to self-commit that Resource in lieu of the RUC instruction or VDI. Reliability Unit Commitment (RUC)-Committed Hour An Operating Hour for which a RUC has committed a Resource to be On-Line and the QSE has not designated a RUC Buy-Back Hour. Reliability Unit Commitment (RUC)-Committed Interval A Settlement Interval for which there is a RUC instruction to commit a Resource.
5.5.2 (10) (10) A QSE that has one or more of its Resources RUC-committed to provide Ancillary Services must increase its Ancillary Service Supply Responsibility by the total amount of RUC-committed Ancillary Service quantities. The QSE may only use a RUC-committed Resource to meet its Ancillary Service Supply Responsibility during that Resource s RUC-Committed Interval if the Resource has been committed by the RUC process to provide Ancillary Service. The QSE shall indicate the exact amount and type of Ancillary Service for which it was committed as the Resource s Ancillary Service Resource Responsibility and Ancillary Services Schedule for the RUC- Committed Intervals for both telemetry and COP information provided to ERCOT. Upon deployment of the Ancillary Services, the QSE shall adjust its Ancillary Services Schedule to reflect the amounts requested in the deployment. If a Resource opts out of its RUC instruction is it still a RUC- committed Resource ? Does it have RUC-Committed Intervals ?
Related Issues Clarify instructions from ERCOT specify AS details in RUC? Separate AS and RUC instructions? Seems there is room for improvement here. Other thoughts to improve this process: SASM after RUC? Min(DAM MCPC, SASM MCPC) -> RUC for AS?
