Meeting Summary - 09/06/24 LFLTF Meeting

Grid Monitor AI
09/06/2024

<p><img src="/storage/docs/2024/09/LFLTF%20Sept%20Hero.png" width="571" height="322" /></p> <p><a href="/sharing/?token=2304da63-e37b-4c5d-b3f7-aaa26f2b9c7c"><span style="font-weight: 400;">1 </span></a><span style="font-weight: 400;">- Antitrust Admonition - Bill Blevins</span></p> <p><a href="/sharing/?token=bcc5e54f-79eb-4b1d-a910-de24968f2dcb"><span style="font-weight: 400;">2 </span></a><span style="font-weight: 400;">- Large Load Queue Update - ERCOT Staff</span></p> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Julie Stittman, supervisor of the large load integration team, presented the </span><a href="https://ercot-control-docs.s3.us-west-2.amazonaws.com/05/LLI%2520Queue%2520Status%2520Update%2520-%25202024-9-6.pdf"><span style="font-weight: 400;">large load interconnection status update.</span></a></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Over the past twelve months, the combination of new standalone and co-located projects, as well as several project cancellations, has increased the total queue capacity by 4439 MW.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Current Large Load Interconnection Queue broken into 4 categories</span></li> <ul> <li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Approved to energize</span></li> <li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Planning studies approved</span></li> <li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Under ERCOT review</span></li> <li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">No studies submitted</span></li> </ul> </ul> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Approved to energize:1570 MW approved over the past year; total of 5496 MW currently approved, with 2854 MW in load zone west and 2642 MW in other zones.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The breakdown of approved projects: 4421 MW standalone and 1075 MW co-located.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Observed non-simultaneous peak consumption is 3282 MW; simultaneous peak consumption is 2815 MW.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Discussion on whether the load is flexible or not: currently no such categorization in the process, dependent on future commission projects.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">By 2028, ERCOT has effectively approved a little over 14 gigawatts for large loads.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Clarification on load ramps and submission requests: both the load ramp and potential transmission upgrades are considered.</span></li> </ul> <p><a href="/sharing/?token=e2c18652-f45c-4a4e-8365-90ee5b2d4c4a"><span style="font-weight: 400;">3 </span></a><span style="font-weight: 400;">- NPRR1238 Discussion - ERCOT Staff</span></p> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Discussion on NPRR1238, focused on how the language might adjust load shed percentages.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Clarification on concerns and misunderstandings about NPRR1238 raised by stakeholders, especially regarding its impact on NOIE areas.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Explanation of the intent behind NPRR1238: to remove interruptible loads from load shed tables and calculate requirements based on actual firm loads.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">ERCOT's ongoing efforts to develop scenarios based on NPRR1238 language and its load shed impacts.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Stakeholder concerns about sequencing NPRR1238 with NPRR1234 due to dependencies and the need to move forward collectively.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Discussion on using NPRR1238 during transmission emergencies and its limitations, with suggested clarifications in the language.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Importance of moving NPRR1238 along with NPRR1234 due to interconnect limitations and urgency emphasized by stakeholders.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">ERCOT working to provide comments about timeline with NPRR 1234 and to bring a scenario for discussion to the OWG surrounding load shed percentages</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Methodologies for calculating load shed percentages explained, including considerations of changing load ratios over time.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Approval of NPRR expected around Q1 of next year.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Manual nature of load shed processes and preference for system-based operations over manual management highlighted.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Stakeholders' input sought on the desired length of time for exiting the VECL program and related operational considerations.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Acknowledgment that changes in load dynamics and flexible loads over time will necessitate ongoing adjustments.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Consensus on creating a path for transitioning between different load categories, with considerations for transmission studies, interconnection agreements, and system updates.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Estimated minimum six-month timeline for implementing major changes in load registrations and categories stressed for reliability reasons.</span></li> </ul> <p><a href="/sharing/?token=fac4ac05-ca86-4fdd-91b8-e98dc0be126a"><span style="font-weight: 400;">4 </span></a><span style="font-weight: 400;">- Maximum Size of Single Large Load Connection &ndash; Discussion of Revised Concept - ERCOT Staff</span></p> <h3><strong>Key Topics Discussed:</strong></h3> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Feedback from previous meeting and internal discussions led to a revised approach to large load connections.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Concept to simplify large load interconnection with a focus on a 1000 MW limit at a single point.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Plans to file a PGRR (Protocol Revision Requests) and update planning criteria.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Potential need for updated studies to validate the 1000 MW limit, based on Southern Cross project.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Operation challenges in maintaining grid stability with large load connections.</span></li> </ul> <h3><strong>Major Decisions Made:</strong></h3> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">In comments to PGRR115, a new paragraph will limit large load interconnection at a single point to 1000 MW.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">A separate PGRR will establish that no more than 1000 MW can be lost for any single contingency in a planning study.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">ERCOT will commit to updating studies before final approval of these changes to ensure reliability.</span></li> </ul> <h3><strong>Questions and Concerns Raised:</strong></h3> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Clarification on the term 'single point of interconnect' there are ongoing discussions on using either POI or POIB.whether POI or another definition.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Management of faults in ring bus or breaker schemes; distinction between voltage ride-through and contingency scenarios.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Modeling requirements for stability studies and potential updates for better load model accuracy.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Possibility of grandfathering existing points of interconnection versus requiring compliance with new criteria.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Operational feasibility and potential design challenges if loads exceed the 1000 MW threshold, particularly concerning process interconnections.</span></li> </ul> <h3><strong>Follow-up Actions Planned:</strong></h3> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">ERCOT to work on drafting and filing comments for PGRR115 and a separate PGRR for a new planning criterion.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">ERCOT to conduct updated studies to validate or adjust the 1000 MW limit based on current data and scenarios.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Further discussions and engagement anticipated with stakeholders to refine and finalize these plans.</span></li> </ul> <p><a href="/sharing/?token=7c74c212-aa21-4e1e-8c56-5a28feaf63d2"><span style="font-weight: 400;">5 </span></a><span style="font-weight: 400;">- Schedule of Future Meetings - Bill Blevins/Bob Wittmeyer</span></p> <ul> <li style="font-weight: 400;" aria-level="1"><strong>Participant:</strong><span style="font-weight: 400;"> Bill Blevins</span></li> <ul> <li style="font-weight: 400;" aria-level="2"><strong>Discussion:</strong></li> <ul> <li style="font-weight: 400;" aria-level="3"><span style="font-weight: 400;">The task force hasn't met initial expectations such as developing ways for flexible loads to participate in ancillary services.</span></li> <li style="font-weight: 400;" aria-level="3"><span style="font-weight: 400;">After completing NPRR134, PGRR115, and NPRR1238, it may be time to hibernate the task force.</span></li> <li style="font-weight: 400;" aria-level="3"><span style="font-weight: 400;">Future issues to be presented by the legislature by next June are anticipated.</span></li> </ul> </ul> <li style="font-weight: 400;" aria-level="1"><strong>Participant:</strong><span style="font-weight: 400;"> Martha Henson</span></li> <ul> <li style="font-weight: 400;" aria-level="2"><strong>Discussion:</strong></li> <ul> <li style="font-weight: 400;" aria-level="3"><span style="font-weight: 400;">Clarification requested on the handling of ERCOT NPRR1234.</span></li> <li style="font-weight: 400;" aria-level="3"><span style="font-weight: 400;">Anticipated that future comments on NPRR1234 will be discussed at ROS.</span></li> </ul> </ul> <li style="font-weight: 400;" aria-level="1"><strong>Participant:</strong><span style="font-weight: 400;"> (unknown)</span></li> <ul> <li style="font-weight: 400;" aria-level="2"><strong>Discussion:</strong></li> <ul> <li style="font-weight: 400;" aria-level="3"><span style="font-weight: 400;">Suggests hibernating after the current meeting unless specific issues arise, like interconnection discussions.</span></li> </ul> </ul> <li style="font-weight: 400;" aria-level="1"><strong>Participant:</strong><span style="font-weight: 400;"> Clayton Stice</span></li> <ul> <li style="font-weight: 400;" aria-level="2"><strong>Discussion:</strong></li> <ul> <li style="font-weight: 400;" aria-level="3"><span style="font-weight: 400;">Discussion on managing transition between CLR and non CLR within markets area.</span></li> <li style="font-weight: 400;" aria-level="3"><span style="font-weight: 400;">Recommendation to shift this discussion to relevant markets forums like WMS or WMWG.</span></li> </ul> </ul> <li style="font-weight: 400;" aria-level="1"><strong>Participants:</strong><span style="font-weight: 400;"> Group Discussion (General)</span></li> <ul> <li style="font-weight: 400;" aria-level="2"><strong>Discussion:</strong></li> <ul> <li style="font-weight: 400;" aria-level="3"><span style="font-weight: 400;">Question on nodal versus non-nodal status raised, with emphasis on consistent nodal load.</span></li> <li style="font-weight: 400;" aria-level="3"><span style="font-weight: 400;">Some loads seek to switch based on market conditions, suggesting consistent nodal status to prevent such shifts.</span></li> <li style="font-weight: 400;" aria-level="3"><span style="font-weight: 400;">Attempts to expand nodal pricing to all large loads were discussed but lacked support.</span></li> </ul> </ul> <li style="font-weight: 400;" aria-level="1"><strong>Participant:</strong><span style="font-weight: 400;"> Lee Bracher</span></li> <ul> <li style="font-weight: 400;" aria-level="2"><strong>Discussion:</strong></li> <ul> <li style="font-weight: 400;" aria-level="3"><span style="font-weight: 400;">Bitcoin mining and large load participation awareness in other forums suggested.</span></li> <li style="font-weight: 400;" aria-level="3"><span style="font-weight: 400;">Broadly supportive for nodal pricing.&nbsp;</span></li> <li style="font-weight: 400;" aria-level="3"><span style="font-weight: 400;">Brought up the need to address interconnection queue and PFR requirements for CLRs.</span></li> </ul> </ul> <li style="font-weight: 400;" aria-level="1"><strong>Participants:</strong><span style="font-weight: 400;"> Agee Springer</span></li> <ul> <li style="font-weight: 400;" aria-level="2"><strong>Discussion:</strong></li> <ul> <li style="font-weight: 400;" aria-level="3"><span style="font-weight: 400;">Clarified that issues needing NPRR1188 is separate from PFR requirements for CLRs.</span></li> <li style="font-weight: 400;" aria-level="3"><span style="font-weight: 400;">Discussed timelines for NPRR1188 and related actions.</span></li> </ul> </ul> <li style="font-weight: 400;" aria-level="1"><strong>Participant:</strong><span style="font-weight: 400;"> Michael Jewell (Priority Power)</span></li> <ul> <li style="font-weight: 400;" aria-level="2"><strong>Discussion:</strong></li> <ul> <li style="font-weight: 400;" aria-level="3"><span style="font-weight: 400;">Provided updates on timelines for NPRR1244 related to NOGRR263, at PRS next week.</span></li> </ul> </ul> <li style="font-weight: 400;" aria-level="1"><strong>Discussion:</strong></li> <ul> <li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Queue updates to continue at WMS unless a more public reporting method is established.</span></li> </ul> <li style="font-weight: 400;" aria-level="1"><strong>Participants:</strong><span style="font-weight: 400;"> Group Discussion on Next Steps</span></li> <ul> <li style="font-weight: 400;" aria-level="2"><strong>Discussion:</strong></li> <ul> <li style="font-weight: 400;" aria-level="3"><span style="font-weight: 400;">Cancellation of some scheduled LFL meetings anticipated unless specific issues arise.</span></li> <li style="font-weight: 400;" aria-level="3"><span style="font-weight: 400;">Request to TAC for guidance on the best venue for queue updates.</span></li> </ul> </ul> </ul> <p><span style="font-weight: 400;">Meeting Adjourned.</span></p> <p><br /><br /></p>