Frame

Meeting Summary - PLWG 11/12/24 Meeting

Grid Monitor AI
11/13/2024

<img src="/storage/docs/2024/11/PLWG%20Hero%2020241112.png" width="858" height="647" /> 1 - Antitrust Admonition - Chair <a href="/sharing/?token=121d14db-198a-45c8-b4b7-4860de302fe3">2</a> - Agenda Review - Chair <a href="/sharing/?token=c06e739b-d364-4ef5-88a6-efa0a2719672">3</a> - Review of PLWG Meeting Minutes - Oct 16 & Oct 29 - Chair <ul> <li style="font-weight: 400;" aria-level="1">Confirmed October 16th and 28th meeting minutes as final with no additional comments or questions.</li> </ul> <a href="/sharing/?token=d32f6b2a-5e4c-4bf0-9b03-0bd10aebe0e1">4</a> - General updates - Chair <ul> <li style="font-weight: 400;" aria-level="1">Key issues and developments affecting ERCOT were highlighted.</li> <li style="font-weight: 400;" aria-level="1">The Chair emphasized the importance of current and upcoming initiatives.</li> <li style="font-weight: 400;" aria-level="1">Stakeholders were encouraged to stay informed and contribute feedback.</li> <li style="font-weight: 400;" aria-level="1">Brief mention of operational strategies adapting to changing demands.</li> </ul> <a href="/sharing/?token=635b9ca3-1b81-454f-9ba3-976a41a0c7a1">4.1</a> - At the Nov 7 ROS meeting, the following occurred <a href="/sharing/?token=478afc1b-0208-44a1-98ff-cff04cbcfbdd">4.1.1</a> - ROS referred PGRR120 to PLWG <ul> <li style="font-weight: 400;" aria-level="1">ROS referred PGRR120 to PLWG for discussion.</li> <li style="font-weight: 400;" aria-level="1">The topic will be covered in the morning meeting.</li> </ul> <a href="/sharing/?token=29c2de69-6c7e-483c-9b4e-f32d93818d52">4.1.2</a> - ROS voted to approve PGRR117 - ERCOT comments 101124 <ul> <li style="font-weight: 400;" aria-level="1">ROS voted to approve PGRR117.</li> <li style="font-weight: 400;" aria-level="1">Approval was based on ERCOT comments dated October 11th.</li> </ul> <a href="/sharing/?token=97bfb7f2-2bb7-4309-b10f-c1af9e3428d7">4.1.3</a> - ROS voted to approve NPRR1247 - ERCOT comments 102324 <ul> <li style="font-weight: 400;" aria-level="1">ROS voted to approve NPRR1247.</li> <li style="font-weight: 400;" aria-level="1">Approval was based on ERCOT comments posted on October 23rd.</li> </ul> <a href="/sharing/?token=9f3b97a3-d15e-4745-a6fc-033c44c6c678">4.2</a> - Leadership 25 update <ul> <li style="font-weight: 400;" aria-level="1">Leadership turnover typically occurs around October and requires a vote at ROS.</li> <li style="font-weight: 400;" aria-level="1">Opportunity highlighted for interested parties to engage in a rewarding leadership position in ROS.</li> <li style="font-weight: 400;" aria-level="1">Encouragement for individuals who have not participated in ROS leadership to consider the opportunity.</li> <li style="font-weight: 400;" aria-level="1">Discussion on taking agenda item PGRR115 out of order due to scheduling conflicts.</li> <li style="font-weight: 400;" aria-level="1">Introduction and fast-paced review of PGRR120 SSO Prevention and Generation for interconnection, newly assigned to PLWG.</li> <li style="font-weight: 400;" aria-level="1">Presentation feedback from a previous ROS meeting was mentioned for further discussion.</li> </ul> <a href="/sharing/?token=9f378967-ab20-45fd-b0cf-750ff8254b16">5</a> - PGRR115 - related to NPRR1234 – Interconnection Requirements for Large Loads and Modeling Standards for Loads 25 MW or Greater - PLWG <a href="/sharing/?token=e60cdcea-83e6-421e-8a8c-e47aeed82ccb">5.1</a> - ERCOT Comments TBD - ERCOT <ul> <li style="font-weight: 400;" aria-level="1">ERCOT filed comments on NPRR1234 and PGRR115, introducing a new concept requiring updates in protocols.</li> <li style="font-weight: 400;" aria-level="1">Clarified definition for 'initial energization' related to generation resource interconnections, making it applicable to both new and modified resources.</li> <li style="font-weight: 400;" aria-level="1">Introduction of a new defined term, 'Transmission service bus,' to address maximum load criteria of 1000 megawatts from a single bus.</li> <li style="font-weight: 400;" aria-level="1">Comments address load commissioning plans, clarifying requirements and stability assessments.</li> <li style="font-weight: 400;" aria-level="1">Clarifications on load inclusion in QSA, ensuring it's tied to loads undergoing commissioning processes.</li> <li style="font-weight: 400;" aria-level="1">Obligations for TSPs specified regarding submission and updating of dynamic load models.</li> <li style="font-weight: 400;" aria-level="1">TSP compliance clarification related to customer behavior and transmission system limitations.</li> <li style="font-weight: 400;" aria-level="1">Discussion around the maximum allowable load from a single transmission point due to frequency stability concerns.</li> <li style="font-weight: 400;" aria-level="1">Two-pronged approach: introducing a load limit of 1000 megawatts from a single point and planning criteria to prevent losing more than 1000 megawatts in a single contingency.</li> <li style="font-weight: 400;" aria-level="1">Addressing feedback from entities like ERCOT Steel Mills and Oncor to incorporate suggestions into ERCOT's revisions.</li> <li style="font-weight: 400;" aria-level="1">Planning further analysis to potentially adjust the 1000 megawatt limit based on study outcomes.</li> <li style="font-weight: 400;" aria-level="1">Comments on some proposals, such as AEP's, were considered but not largely adopted due to differing approaches.</li> <li style="font-weight: 400;" aria-level="1">Requests for more review time before finalizing PGRR115 to ensure all stakeholder concerns are considered.</li> </ul> <a href="/sharing/?token=df9f1f96-79af-4867-9880-efa402a8474b">6</a> - PGRR119 – PGRR119, Stability Constraint Modeling Assumptions in the Regional Transmission Plan - PLWG <a href="/sharing/?token=e7c1ce8a-a1fe-45bb-beb5-378f11544246">6.1</a> - 119PGRR-05 OPUC Comments 110624 <ul> <li style="font-weight: 400;" aria-level="1">ERCOT planning clarified that the reliability margin mentioned in OPUC comments is not intended to be created anew in the RTP process, but rather to be used consistent with current operating procedures.</li> <li style="font-weight: 400;" aria-level="1">Alex Miller  from EDF discussed the misunderstanding around the modeling of operating limits, emphasizing the modeling should reflect real-world limits and not just posted limits.</li> <li style="font-weight: 400;" aria-level="1">There was discussion on whether this PGRR is intended to capture similar concepts as in NPRR1070, specifically about modeling GTCs as they occur in reality.</li> <li style="font-weight: 400;" aria-level="1">ERCOT planning confirmed the intention to apply real-world stability limits and address similar concerns as in NPRR1070.</li> <li style="font-weight: 400;" aria-level="1">Alex Miller suggested including the impact of outages on D rates in the PGRR to improve clarity.</li> <li style="font-weight: 400;" aria-level="1">ERCOT planning explained ERCOT's discretion in applying additional analysis and benefits under PUC substantive rule, relating to outage-related benefits.</li> <li style="font-weight: 400;" aria-level="1">There was a proposal for offline discussions to further explore methodologies for modeling outages related to GTCs.</li> <li style="font-weight: 400;" aria-level="1">ERCOT's filed comments for NPRR1247 highlighted a white paper addressing weather uncertainty and transmission outages, though it wasn't specific to stability constraints.</li> <li style="font-weight: 400;" aria-level="1">It was noted that GTCs are uniquely challenging within ERCOT, requiring clarity for stakeholders about modeling processes.</li> <li style="font-weight: 400;" aria-level="1">Discussion on ERCOT's different activation procedures for IROL and SOL based on stability limits, with reliability margins noted as 10% or 15% depending on the limit type.</li> <li style="font-weight: 400;" aria-level="1">The PGRR119 was tabled previously pending comments, and OPUC's comments were discussed with a view to move the discussion forward in ROS.</li> <li style="font-weight: 400;" aria-level="1">There were thoughts on possibly refining language for transparency and clarity, with Alex intending to file written comments if needed.</li> </ul> <a href="/sharing/?token=8928af80-5ea5-4ab4-a8c0-9ff329486b7b">7</a> - PGRR120 – SSO Prevention for Generation Interconnection - ERCOT <a href="https://ercot-control-docs.s3.us-west-2.amazonaws.com/31/06-november_ros_sso_prevention_pgrr120.pdf">06-november_ros_sso_prevention_pgrr120</a> <ul> <li style="font-weight: 400;" aria-level="1">Series compensated circuits: Discussed the ownership and installation timelines, highlighting TSP and non-TSP owned locations.</li> <li style="font-weight: 400;" aria-level="1">Explanation of SSO: Defined subsynchronous phenomena, including SSR, SSCI, and SSFR, and outlined mitigation efforts.</li> <li style="font-weight: 400;" aria-level="1">Past SSR events: Reviewed occurrences since 2009, including forced outages and mitigation attempts, particularly in South Texas.</li> <li style="font-weight: 400;" aria-level="1">PGRR120 proposal: Aims to prevent new generation projects from interconnecting in a manner that renders them radial to a series capacitor.</li> <li style="font-weight: 400;" aria-level="1">Impact on existing projects: Clarified the effect on ongoing projects and the process for new and existing projects, potentially hindering some from continuing if screen checks are not completed in time.</li> <li style="font-weight: 400;" aria-level="1">Real-time SSO mitigation: ERCOT's ability to prohibit operations if real-time SSO is detected.</li> <li style="font-weight: 400;" aria-level="1">Project screening and check stage: Emphasized on topology checks as part of the interconnection process to ensure compliance with the PGRR.</li> <li style="font-weight: 400;" aria-level="1">Discussion on future transmission fix: Debated if TSPs should seek transmission solutions to allow new generation connections despite series caps.</li> <li style="font-weight: 400;" aria-level="1">Inverter OEM discussions: Mentioned ongoing considerations with OEMs regarding resonance prevention.</li> <li style="font-weight: 400;" aria-level="1">Complexity in addressing SSR: Highlighted difficulties in mitigation even when approved measures are in place or generators maintain compliance.</li> </ul> <h4>Questions and Comments:</h4> <ul> <li style="font-weight: 400;" aria-level="1">Monica Jha, Vistra: Question: Permanency of generation restriction near series caps if transmission fixes are made?</li> <li style="font-weight: 400;" aria-level="1">Mina: Question: Requested more detailed information on 2023 SSR events.</li> <li style="font-weight: 400;" aria-level="1">Nicholas Jalabar with RWE: Comment: Discussion on mitigating series compensation by grid infrastructure upgrades.</li> <li style="font-weight: 400;" aria-level="1">Brett Rollo with Green Belt Renewables: Question: Clarification on alternatives if screening study isn't completed before PGRR implementation.</li> <li style="font-weight: 400;" aria-level="1">Freddie and Megan, various participants: Discussion: Concerns around new resources and SSR mitigation effectiveness, including historical issues.</li> </ul> <h4>Action Items:</h4> <ul> <li style="font-weight: 400;" aria-level="1">ERCOT to take back questions regarding topology checks for existing projects.</li> <li style="font-weight: 400;" aria-level="1">Consider providing detailed statistics on potentially impacted generation capacity by proximity to series capacitors.</li> <li style="font-weight: 400;" aria-level="1">Ensure communication availability for reviewed processes in Interconnection protocols.</li> </ul> <a href="/sharing/?token=e999c4b3-3705-417c-a2dc-89ec2cfed34a">8</a> - NERC Topics Roundtable - future topics - PLWG <ul> <li style="font-weight: 400;" aria-level="1">Discussion on ongoing topics related to NERC roundtable.</li> <li style="font-weight: 400;" aria-level="1">Focus on future topics for PLWG.</li> </ul> <a href="/sharing/?token=551e5ec7-b682-4697-a1ac-3f0201d6104f">8.1</a> - CIP-014-4 - Physical Security <ul> <li style="font-weight: 400;" aria-level="1">Discussion on CIP-014-4 physical security revisions at the NERC level.</li> <li style="font-weight: 400;" aria-level="1">The latest ballot for CIP-014-4 failed again.</li> <li style="font-weight: 400;" aria-level="1">The drafting team plans to review comments and issues, especially with R2 and R3.</li> <li style="font-weight: 400;" aria-level="1">A new red line version will be posted for the next ballot.</li> </ul> <a href="/sharing/?token=e4883f0b-0a25-439e-b2dd-c7f68039dcb6">8.2</a> - TPL-008 - Transmission System Planning Performance Requirements for Extreme Temperature Events <ul> <li style="font-weight: 400;" aria-level="1">Discussion on TPL-008, which concerns transmission system planning for extreme temperature events.</li> <li style="font-weight: 400;" aria-level="1">A ballot vote comment period is open until November 21st for feedback to NERC.</li> <li style="font-weight: 400;" aria-level="1">This is the fourth version of the draft TPL-008, associated with project number 202307.</li> <li style="font-weight: 400;" aria-level="1">The draft includes requirement documents, technical rationales, responses to comments, and examples of benchmark extreme cold and heat events.</li> <li style="font-weight: 400;" aria-level="1">Significant changes have been made to address industry feedback.</li> <li style="font-weight: 400;" aria-level="1">The requirement to file TPL-008 with FERC is by December 15, based on order 896.</li> <li style="font-weight: 400;" aria-level="1">The ballot needs a 67% approval rate to pass, and the last approval rate was 58%.</li> <li style="font-weight: 400;" aria-level="1">Participants expressed appreciation for input from two standard drafting team members.</li> <li style="font-weight: 400;" aria-level="1">Discussion included open action items, particularly the use of big L, little L in the Planning Guide.</li> </ul> <a href="/sharing/?token=01f3f808-be0a-42ab-8c77-ebc9da0eadd1">9</a> - Review Open Action Items - Chair <ul> <li style="font-weight: 400;" aria-level="1">Consideration of a working draft approach to revise sections of the planning guide during each meeting.</li> <li style="font-weight: 400;" aria-level="1">Discussion on managing workload by revising sections one at a time, particularly the data and modeling section with numerous load references.</li> <li style="font-weight: 400;" aria-level="1">Bob Wittemeyer suggested a slower approach by revising the wording with each PGRR revision instead of an overall review.</li> <li style="font-weight: 400;" aria-level="1">Alex Miller inquired about the frequency of load references and the areas needing adjustment in the planning guide.</li> <li style="font-weight: 400;" aria-level="1">Aaron Gutierrez discussed different revision request options: PLWG could submit a request, draft could be sent to ROS, or a market participant could sponsor it.</li> <li style="font-weight: 400;" aria-level="1">Concerns about potential length and complexity of a full planning guide revision were discussed, with examples of similar past processes.</li> <li style="font-weight: 400;" aria-level="1">Consensus to proceed by addressing one section at a time in meetings to ensure manageability and currency of changes.</li> <li style="font-weight: 400;" aria-level="1">The possibility of scheduling discussions at the end of the agenda to allow participants to opt out if desired was suggested.</li> </ul> <a href="/sharing/?token=16d2b98c-56e8-440b-820a-4b5183091cc1">10</a> - Other business - Chair Brief overview of activities conducted: <ul> <li style="font-weight: 400;" aria-level="1">Discussion on PGRR120 - First reading of the SSO for generation single contingency outage revision requests; tabled for further discussion.</li> <li style="font-weight: 400;" aria-level="1">Discussion on PGRR115 - Tabled for one month with a goal to finalize in December; coordination with Bill and Agee required to address comments.</li> <li style="font-weight: 400;" aria-level="1">Discussion on PGRR119 - Consensus reached within PLWG; will be taken back to ROS for further action..</li> </ul> 11 - Adjourn - Chair