1 / 5

Load Resource Allocation for EECP

Load Resource Allocation for EECP. 6.5.9.4.1 EECP Steps

mayhewr
Download Presentation

Load Resource Allocation for EECP

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. Load Resource Allocation for EECP WMS Meeting

  2. 6.5.9.4.1 EECP Steps (b) Deploy half of the Responsive Reserve that is supplied from Load Resources (controlled by high-set under-frequency relays) by instructing the QSE representing the specific Load Resource to interrupt Load providing Responsive Reserve. ERCOT shall develop a procedure for determining which Load Resources to interrupt and to equitably allocate Load Resources to one of two deployment stacks to enable a 50% deployment, which must be approved in advance by TAC. WMS Meeting

  3. ERCOT Proposed Procedure: • Map DA LMPs to each Load Resource procured to provide RRS in the DA A/S Market. • Stack LRs in descending order of their LMPs • Create two stacks; highest LMPs included in first deployment stack and while lowest LMPs included in second deployment stack • 24 hourly stacks will be created • Once deployed all LRs providing RRS will remain deployed throughout event WMS Meeting

  4. Why this method? • ERCOT believes this is the most equitable approach to the market as a whole • By reducing load in high LMP areas first this approach has the greatest potential for relieving congestion in those areas and thus freeing up additional generation to help avoid further operator action WMS Meeting

  5. Next Step • At PRS Tomorrow: • NPRR 076 is up for discussion • Comments provided remove the existing language in (b) and require ERCOT to use a “random processor to create the two deployment stacks • ERCOT intends to verbally comment on those changes WMS Meeting

More Related