How will ERCOT handle Responsive Reserve Service (RRS) and Non-Spin Reserve Service (NSRS) deployments?
To Generation Resources and Controllable Load Resources, the deployment sequence is as follows: 1. Generation Subsystem issues a Portfolio Responsive Reserve Service (RRS) deployment MW amount to a Qualified Scheduling Entity (QSE) via ICCP. 2. The QSE receives this deployment and adjusts the RRS schedules of each Generation Resource and Controllable Load Resource (CLR) participating in RRS down to reflect that this capacity is no longer reserved for RRS service. 3. The QSE proportionally directs its CLRs to decrease load and increase generation of ONRR Resources by its participation factor applied to the MW deployment amount. 4. The QSE notifies ERCOT of the adjusted RRS schedules via ICCP (within 20 seconds). 5. Upon receipt of the adjusted RRS schedules, ERCOT’s Resource Limit Calculator revises the High Dispatch Limit (HDL) and High Ancillary Service Limit (HASL) of the Resources affected. 6. ERCOT, after waiting for schedule adjustments for ~20 seconds, triggers Security Constrain
Related Questions
- How will the QSE know when their Balancing Energy Capable Non-Spin Reserve Service (BESCNSRS) resource is deployed when the MCPE is greater than FIP*15 + $120?
- What format is used for Non-Spin/Responsive Reserve Service (RRS) deployment messages in the interface?
- How will ERCOT handle Responsive Reserve Service (RRS) and Non-Spin Reserve Service (NSRS) deployments?
