Frame

Meeting Summary - 02/10/2025 NOGRR245 Workshop I

Grid Monitor AI
02/10/2025

<div class="news-image-container"><img src="/storage/docs/2025/02/02-10-2025-NOGRRWorkshop-Hero_17sbmdvbv8sy.png" /></div> <h3><a href="/sharing/?token=92b1d185-bd40-4f79-9301-d19fbe5c83d9">▶️</a>1 - Agenda Review</h3> <h3><a href="/sharing/?token=e09e23cc-1fec-48d4-bb8c-da79e4e5b057">▶️</a>2 - Review of NOGRR245 Requirements</h3> <a href="/storage/docs/2025/02/Ride-Through_Workshop_Requirements_AAG.pdf">Ride-Through_Workshop_Requirements_AAG.pdf</a> <ul> <li style="font-weight: 400;" aria-level="1">The initial draft of NOGRR245 was filed in January 2023 and approved by the board in August, with the Commission's approval effective October 1, 2024.</li> <li style="font-weight: 400;" aria-level="1">Market participants were expected to maximize frequency and voltage ride-through capabilities using software, firmware, and parameterization changes without requiring new hardware.</li> <li style="font-weight: 400;" aria-level="1">Frequency ride-through requirements: Resources must ensure settings meet maximum levels allowed by equipment standards by 12/31/2025 or synchronization date if after this deadline.</li> <li style="font-weight: 400;" aria-level="1">Resources unable to meet the frequency ride-through requirements must submit a report by 04/01/2025 and request an extension or exemption.</li> <li style="font-weight: 400;" aria-level="1">Voltage ride-through requirements: Applicable to all resources to meet or exceed IEEE 2800-2022 standards, with deadlines similar to frequency.</li> <li style="font-weight: 400;" aria-level="1">Clarification on different terms used, including synchronization dates and commercial operation dates, was provided.</li> <li style="font-weight: 400;" aria-level="1">For resources unable to meet voltage ride-through requirements, reports and an extension request are necessary, adhering to historical standards until maximization can be achieved.</li> <li style="font-weight: 400;" aria-level="1">Questions around repowering projects, particularly around interconnections and modifications, led to further clarifications on applying new standards.</li> <li style="font-weight: 400;" aria-level="1">Questions about resource equipment limitations due to obsolescence addressed the need for detailed documentation.</li> <li style="font-weight: 400;" aria-level="1">Discussion highlighted the necessity for such documentation to support requests and ensure compliance, emphasizing accurate and honest submissions.</li> </ul> <h3><a href="/sharing/?token=6843f25c-caba-44e4-ba38-4a3e3f771a2c">▶️</a>3 - Initial Data Collection Process</h3> <a href="/storage/docs/2025/02/ERCOT_NOGRR245_Workshop1_Data_Collection_Koepke_020725.pdf">ERCOT_NOGRR245_Workshop1_Data_Collection_Koepke_020725.pdf</a> <ul> <li style="font-weight: 400;" aria-level="1">Two paths for data submission depending on the resource status: operational or interconnection queue.</li> <li style="font-weight: 400;" aria-level="1">Operational resources will receive DocuSign requests.</li> <li style="font-weight: 400;" aria-level="1">Resources in the interconnection queue need to request exemptions/extensions via the RIOO system.</li> <li style="font-weight: 400;" aria-level="1">DocuSign emails will be sent on February 19 for applicable resources.</li> <li style="font-weight: 400;" aria-level="1">The deadline for responses from all resources is April 1.</li> <li style="font-weight: 400;" aria-level="1">The process mirrors a successful past approach used for weatherization data collection.</li> <li style="font-weight: 400;" aria-level="1">Concerns addressed over the repetitive and manual nature of the DocuSign process.</li> <li style="font-weight: 400;" aria-level="1">Requests for alternative data submission methods like an FTP site were discussed but not adopted.</li> <li style="font-weight: 400;" aria-level="1">Authorized reps will receive DocuSign; a single person should complete the submission.</li> <li style="font-weight: 400;" aria-level="1">Responses will be integrated into the RIOO system, with development completed by Q3 of 2023.</li> <li style="font-weight: 400;" aria-level="1">In the interconnection queue but without a PLD, resources must submit exemption/extension requests via RIOO by April 1.</li> <li style="font-weight: 400;" aria-level="1">New attachment type for exemptions/extensions to be available on February 28 in RIOO.</li> <li style="font-weight: 400;" aria-level="1">Concern over meeting the April 1 deadline for updated models due to OEM dependency was noted.</li> <li style="font-weight: 400;" aria-level="1">Resources need to proactively comply with NOGRR245 without explicit ERCOT request if meeting certain criteria.</li> <li style="font-weight: 400;" aria-level="1">Significant changes in models might trigger a new QSA and require re-evaluation.</li> <li style="font-weight: 400;" aria-level="1">Continuous collaboration and adjustments to the process based on feedback are expected.</li> </ul> <h3><a href="/sharing/?token=d2ef0ffb-2f7e-46eb-b808-b55003ec102a">▶️</a>4 - Review of DocuSign Template</h3> <a href="/storage/docs/2025/02/NOGRR245_Workshop021025_DocuSign_review.pdf">NOGRR245_Workshop021025_DocuSign_review.pdf</a> <ul> <li style="font-weight: 400;" aria-level="1">The meeting's goal was to review a draft DocuSign template regarding resource integration and requirements.</li> <li style="font-weight: 400;" aria-level="1">General information and pre-population intentions for DocuSign were discussed, focusing on resource names and site names.</li> <li style="font-weight: 400;" aria-level="1">Key questions focused on SGIA dates pre and post-08/01/2024 for determining requirement paths.</li> <li style="font-weight: 400;" aria-level="1">Frequency and voltage ride-through capabilities were critically reviewed with emphasis on maximization and settings.</li> <li style="font-weight: 400;" aria-level="1">Tables and capability curves were introduced to provide a clear understanding of frequency and voltage capabilities.</li> <li style="font-weight: 400;" aria-level="1">Discussions included how balance of plant equipment affects the overall resource capability.</li> <li style="font-weight: 400;" aria-level="1">Participants raised concerns and questions about table interpretations, extensions, exemptions, and the methodology for translating turbine-level settings to POIB voltages.</li> <li style="font-weight: 400;" aria-level="1">Attestations regarding model accuracy and changes were addressed, touching on the compliance with standards and requirements.</li> <li style="font-weight: 400;" aria-level="1">Clarifications were sought on the requirements and whether these apply to all resources or only new units post specific dates.</li> <li style="font-weight: 400;" aria-level="1">The meeting included a discussion on various ERCOT requirements, including the steps for requesting exemptions and extensions.</li> </ul> <h3><a href="/sharing/?token=47ec3517-18b3-4e44-b7ac-e1d8fc927942">▶️</a>5 - Questions</h3> <ul> <li style="font-weight: 400;" aria-level="1">Discussion on requirements for DocuSign submission even without exemptions, and the process for testing maximum capability before the December deadline.</li> <li style="font-weight: 400;" aria-level="1">Clarification that maximization efforts should not just meet the bare minimum standards but should enhance equipment's ride-through capabilities.</li> <li style="font-weight: 400;" aria-level="1">Emphasis on compliance with PGRR109 when making modifications to improve dynamic response.</li> <li style="font-weight: 400;" aria-level="1">Information on planned changes to resource integration templates and guidance on waiting for final versions to avoid issues from changes discussed in the meeting.</li> <li style="font-weight: 400;" aria-level="1">Finalized versions of templates expected by February 19, providing guidance on exemption and extension requests.</li> <li style="font-weight: 400;" aria-level="1">Concerns raised about regional differences not considered in IEEE 2800 standards and suggestions that performance requirements be managed by ERCOT.</li> <li style="font-weight: 400;" aria-level="1">Questions about the definition of 'maximizing' and its implications for response time and reactive power, with responses indicating the need for a practical approach based on good utility practice and ERCOT feedback.</li> <li style="font-weight: 400;" aria-level="1">Discussion on the binding nature of pre- and post-maximization values submitted by April 1, and recognition that estimates at different stages might vary.</li> <li style="font-weight: 400;" aria-level="1">Importance of reflecting current capabilities in models and providing best estimates in good faith with the understanding that actual values might adjust as validated through testing.</li> </ul> <h3><a href="/sharing/?token=1d9cd75c-b017-452f-aa80-2c696d1f788f">▶️</a>6 - Conclusion</h3> <ul> <li style="font-weight: 400;" aria-level="1">Unanswered questions can be sent to NOGRR245@ERCOT.com.</li> <li style="font-weight: 400;" aria-level="1">A version of the frequently asked questions will be posted before sending the DocuSign, scheduled for next Wednesday, 2/19/25.</li> </ul>