110 likes | 119 Views
This meeting discussed load registration in the nodal market and the proposed procedure for load resource allocation. The goal was to minimize iterations and ensure equitable allocation of load resources.
E N D
Demand Side Working Group MeetingAugust 10, 2007 Mary Anne BrelinskyEagle Energy Partners
#3 Load Registration in Nodal • Load Resources do NOT need to complete the Resource Registration at this point in time • ERCOT is continuing to refine the RARF (Resource Asset Registration Form), and as such would like to minimize the iterations for the market in completing the registration. • Since Load Resources are not involved in Nodal EDS3-SCED testing, ERCOT can wait on getting the first round of registration data until later in the year- possibly in late October.
Load Resource Allocation for EECPPresented at WMS July 18, 2007
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.
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
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
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