Frame

Meeting Summary - 08/09/24 IBRWG Meeting

Grid Monitor AI
08/09/2024

0 - Antitrust Admonition - Julia Matevosyan. <a href="/sharing/?token=e244d590-7eaa-4d76-8f71-0e6500231f4a">1</a> - Last Update Request - Fred Huang <ul> <li style="font-weight: 400;" aria-level="1">Two presentations were given last month on advanced grid support and grid forming capability.</li> <li style="font-weight: 400;" aria-level="1">Presentations covered <a href="https://ercot-control-docs.s3.us-west-2.amazonaws.com/09/2024_07_ERCOT_IBRWG_Advanced%2520Grid%2520Support%2520Inverter-Based%2520ESR%2520Functional%2520Specification%2520and%2520Test%2520Framework.pdf">functional specification and test framework</a>, and an <a href="https://ercot-control-docs.s3.us-west-2.amazonaws.com/09/2024_07_ERCOT_IBRWG_ERCOT%2520Advanced%2520Grid%2520Support%2520Inverter-based%2520ESRs%2520Assessment%2520and%2520Adoption%2520Discussion_v1_.pdf">assessment of potential impacts</a> of reforming batteries on ERCOT grid stability and reliability.</li> <li style="font-weight: 400;" aria-level="1">Fred mentioned they are working on a draft revision request and plan to post it at least a week before the September IBRWG meeting.</li> <li style="font-weight: 400;" aria-level="1">The draft will be included on the agenda for the September meeting for review and discussion</li> </ul> <a href="/sharing/?token=e7559c39-8b1f-437d-b697-c2c506eade12">2</a> - SPWG/IBRWG Coordination, Auto-reclosing close to IBR plants - Mark McChesney - Oncor, SPWG chair <ul> <li style="font-weight: 400;" aria-level="1">Action item from March ROS meeting: Develop guidance for adjusting transmission reclosing and sectionalizing schemes to improve IBR ride-through probability.</li> <li style="font-weight: 400;" aria-level="1">Discussion on current practices: Oncor's <a href="https://ercot-control-docs.s3.us-west-2.amazonaws.com/08/Reclosing%2520Examples.pptx">reclosing philosophy</a> referenced IEEE standard c37.14.</li> <li style="font-weight: 400;" aria-level="1">Typical scenario: Faults on tie line lead to a 20-second open interval before reclosing.</li> <li style="font-weight: 400;" aria-level="1">Faults on adjacent lines: Typical 10-second open interval for remote terminal reclosing.</li> <li style="font-weight: 400;" aria-level="1">Oncor's sync check settings: Voltage > 75% of nominal, angle difference < 40 degrees, maximum slip frequency of 0.067 Hz.</li> <li style="font-weight: 400;" aria-level="1">Open discussion solicited for feedback and concerns from IBRWG.</li> <li style="font-weight: 400;" aria-level="1">Stephen Solis commented on the potential need to change reclosing parameters, considering IEEE 2800 requirements.</li> <li style="font-weight: 400;" aria-level="1">Diverse reclose schemes among TSPs: From no reclose to multiple attempts within a ten-second period.</li> <li style="font-weight: 400;" aria-level="1">Aim: Coordinate TSP's reclose schemes with IBRs to avoid unnecessary trips, considering IEEE 2800 requirements.</li> <li style="font-weight: 400;" aria-level="1">Oncor's approach: Longer open intervals and limited recloses around generating units.</li> <li style="font-weight: 400;" aria-level="1">Clarification on terminology: 'Open interval' as the time delay before a reclose attempt.</li> <li style="font-weight: 400;" aria-level="1">Discussion on the overall goal: Ensuring TSP reclose strategies don't trip IBRs.</li> <li style="font-weight: 400;" aria-level="1">Consideration of IEEE 2800 table relevant to multiple excursions.</li> <li style="font-weight: 400;" aria-level="1">Site-specific evaluation recommended for reclose schemes around IBR plants.</li> <li style="font-weight: 400;" aria-level="1">Need to capture coordination guidelines between TSPs and IBRs in documentation.</li> <li style="font-weight: 400;" aria-level="1">Potential requirement to discuss further and possibly introduce a rule change.</li> <li style="font-weight: 400;" aria-level="1">Differences in reclose scheme considerations for wind turbines compared to solar PV or batteries.</li> <li style="font-weight: 400;" aria-level="1">Importance of capturing and sharing the range of reclose schemes used by TSPs.</li> <li style="font-weight: 400;" aria-level="1">Plan to summarize and poll SPWG group on typical schemes and considerations.</li> <li style="font-weight: 400;" aria-level="1">Future coordination to discuss data and feedback in IBRWG meetings.</li> </ul> <a href="/sharing/?token=eccbb83f-67ed-40e8-93ec-89d12adf7f59">3</a> - ERCOT RFI to Support Single Model ESR - ERCOT, All <ul> <li style="font-weight: 400;" aria-level="1">Julia Matevosyan clarified a past miscommunication about single model representation of ESR within ERCOT systems. Will happen together with real time co optimization implementation.</li> <li style="font-weight: 400;" aria-level="1">Joel Koepke, ERCOT's grid coordination manager, provided an <a href="https://ercot-control-docs.s3.us-west-2.amazonaws.com/05/RIWG_ERCOT_RIOO_Data_Collection_July24.pptx">overview</a> of the Request for Information (RFI).</li> <li style="font-weight: 400;" aria-level="1">The RFI, initiated on August 6, targets resource entities of commissioned or near-commissioned ESRs.</li> <li style="font-weight: 400;" aria-level="1">Purpose of the RFI is to collect information to avoid validation issues during future submissions in the RIOO application.</li> <li style="font-weight: 400;" aria-level="1">Resources receiving the RFI include those commissioned, in commissioning process, or with approved production load date.</li> <li style="font-weight: 400;" aria-level="1">RTC+B aims to transition from a combo model representation to a single model representation of ESRs by Q4 2025.</li> <li style="font-weight: 400;" aria-level="1">RIOO will be the first application to make the transition, with downstream systems changing later.</li> <li style="font-weight: 400;" aria-level="1">The new single model representation will streamline the submission process, reducing errors and consolidating the load and generation aspects of ESRs.</li> <li style="font-weight: 400;" aria-level="1">Resource entities will receive an ERCOT-created ESR name to facilitate telemetry and testing for RTC to go live in Q4 2025.</li> <li style="font-weight: 400;" aria-level="1">Details of information requested in the RFI include substation details, ESR configuration, and reactive capability during charging.</li> <li style="font-weight: 400;" aria-level="1">Joel highlighted the setup for telemetry and system testing ahead of the RTC go-live date.</li> <li style="font-weight: 400;" aria-level="1">There will be updates to the RIOO application and subsequent changes will depend on the resource stage in the submission process.</li> <li style="font-weight: 400;" aria-level="1">Questions from participants addressed specifics about handling in-flight applications and interconnection procedures.</li> </ul> <a href="/sharing/?token=6cb3a0e4-d919-4b0d-827c-d779311546a9">4</a> - NERC Standards Update PRC-029, PRC-028, PRC-30 - Julia Matevosyan - ESIG <ul> <li style="font-weight: 400;" aria-level="1">Julia presented <a href="https://ercot-control-docs.s3.us-west-2.amazonaws.com/09/ERCOT_IBRWG_NERC_PRC_Updates_080924_.pptx">updates</a> on NERC standards PRC-029, PRC-028, PRC-030.</li> <li style="font-weight: 400;" aria-level="1">Emphasized that her interpretation should be cross-checked with original documents.</li> <li style="font-weight: 400;" aria-level="1">FERC Order 901 directed NERC to update or create new standards for inverter-based resources (IBRs).</li> <li style="font-weight: 400;" aria-level="1">Standards PRC-028, PRC-029, and PRC-030 are up for balloting by August 12.</li> <li style="font-weight: 400;" aria-level="1">PRC-028 focuses on disturbance monitoring and reporting for IBRs.</li> <li style="font-weight: 400;" aria-level="1">PRC-029 outlines frequency and voltage ride-through requirements for IBRs.</li> <li style="font-weight: 400;" aria-level="1">PRC-030 covers unexpected inverter-based event mitigation.</li> <li style="font-weight: 400;" aria-level="1">Stressed the importance of these standards with IBRWG scope and focus. Relating PRC-029 to NOGRR245 and PRC-028 to NOGRR255</li> <li style="font-weight: 400;" aria-level="1">There is a low approval rate for the current drafts; 66% approval needed.</li> <li style="font-weight: 400;" aria-level="1">Requested participation in the balloting process as this is NERC’s last opportunity to ballot project with traditional mechanism.</li> <li style="font-weight: 400;" aria-level="1">If not passed NERC will take requisite action during August Board of Trustees meeting to ensure requirements are completed and filed with FERC by 11/4/2024</li> <li style="font-weight: 400;" aria-level="1">Implementation of PRC-029 includes applicability to IBRs of 20 MVA capacity connected to systems  greater or equal to 60 kV.</li> <li style="font-weight: 400;" aria-level="1">Mentioned differences between PRC-029 and IEEE 2800 standards, notably that frequency ride-through requirements are wider in PCR-029.</li> <li style="font-weight: 400;" aria-level="1">PRC-029 includes specific volts per hertz capability requirements.</li> <li style="font-weight: 400;" aria-level="1">PRC-029 will be effective 12 months after NERC Board of Trustees adopts it; compliance for smaller IBRs by January 1, 2027.</li> <li style="font-weight: 400;" aria-level="1">PRC-028 compliance is necessary for PRC-029 operations monitoring.</li> <li style="font-weight: 400;" aria-level="1">Discussed PRC-029 exemptions for hardware limitations in meeting voltage ride-through requirements</li> <li style="font-weight: 400;" aria-level="1">Frequency ride-through, RoCoF, phase jump, and volts per hertz requirements apply universally.</li> <li style="font-weight: 400;" aria-level="1">Addressed questions regarding OEM involvement, limitations of type 3 wind turbines, and voltage ride-through criteria.</li> <li style="font-weight: 400;" aria-level="1">Mark Henry of TRE clarified that for NERC standards, ECORT is FERC jurisdictional</li> <li style="font-weight: 400;" aria-level="1">Voting on IBR definition glossary item by August 13.</li> </ul> <a href="/sharing/?token=490be44a-abdd-4a24-b042-b44356b84588">5</a> - NOGRR245 Update - Stephen Solis - ERCOT <ul> <li style="font-weight: 400;" aria-level="1">A detailed <a href="https://ercot-control-docs.s3.us-west-2.amazonaws.com/08/ercot-nogrr-245-webex-2024-08-07-1700-.pptx">presentation </a>by Andy Gallo from ERCOT is available on the meeting page.</li> <li style="font-weight: 400;" aria-level="1">Additional work has been done between ERCOT and joint commenters.</li> <li style="font-weight: 400;" aria-level="1">Comments from this work are expected to be posted by next Monday.</li> <li style="font-weight: 400;" aria-level="1">The R&M committee will review on the 19th and the board on the 20th.</li> <li style="font-weight: 400;" aria-level="1">Stephen addressed a question regarding how MQT changes tie into NOGRR245.</li> <li style="font-weight: 400;" aria-level="1">Further discussion on MQT changes will occur later in the meeting.</li> </ul> <a href="/sharing/?token=8fde9459-8984-4b1f-8140-18ee1a86a1fc">6</a> - RoCoF and Phase Jump Measurement Discussion - Stephen Solis - ERCOT, All <ul> <li style="font-weight: 400;" aria-level="1">A <a href="https://ercot-control-docs.s3.us-west-2.amazonaws.com/09/PAJ_RoCoF_IBRWG%2520Discussion_080924.pptx">presentation</a> by Stephen Solis initiated a discussion on RoCoF (Rate of Change of Frequency) and phase angle jump requirements, emphasizing the need for clarity and consistency in measurement methods.</li> <li style="font-weight: 400;" aria-level="1">Referenced ongoing discussions within IBRWG and NOGRR245, aiming for rule changes in line with IEEE 2800 standards.</li> <li style="font-weight: 400;" aria-level="1">Highlighted current IEEE 2800 guidelines on RoCoF, specifying that the averaging window must be at least 0.1 seconds, but not defining an upper limit.</li> <li style="font-weight: 400;" aria-level="1">Reviewed key points from the latest guidance from the P2800-2 drafting team regarding RoCoF and fault-related measurements.</li> <li style="font-weight: 400;" aria-level="1">Emphasized the need for consistent measurement methods and sufficient time delays to prevent erroneous triggers.</li> <li style="font-weight: 400;" aria-level="1">Need for discussion to define averaging window and to verify that 5hz/s is sufficient for ERCOT interconnection</li> <li style="font-weight: 400;" aria-level="1">Discussed recent event analysis (e.g., Odessa 2022) showing that the current 0.1-second window might not be adequate.</li> <li style="font-weight: 400;" aria-level="1">Introduced that validating and properly modeling capabilities may be important to verify IBR’s ability to ride-through load rejection and UFLS/UVLS simulations.</li> <li style="font-weight: 400;" aria-level="1">Explored the potential for using a half-second averaging window to improve the reliability of RoCoF measurements.</li> <li style="font-weight: 400;" aria-level="1">Transitioned to discussing phase angle jumps, referencing specific sections of IEEE 2800-2022 guidelines and identifying measurement challenges.</li> <li style="font-weight: 400;" aria-level="1">Shared insights from the P2800-2 drafting team on phase angle jumps, similar to RoCoF in terms of guidance but differing in specific application.</li> <li style="font-weight: 400;" aria-level="1">Highlighted that phase angle measurement should exclude fault events and should focus on post-event performance.</li> <li style="font-weight: 400;" aria-level="1">Emphasized the need for consensus and further discussions to draft appropriate rule changes for and to refine the measurement methods for both RoCoF and phase angle jumps.</li> </ul> <a href="/sharing/?token=417a234b-47db-4112-aeb9-987269c56150">7</a> - Draft DWG Procedure Manual Edits/ Comments ERCOT/ Southern Power/ Luminant/ All <ul> <li style="font-weight: 400;" aria-level="1">Sun Wook with ERCOT transmission planning gave the DWG <a href="https://ercot-control-docs.s3.us-west-2.amazonaws.com/07/DWG%2520Manual-NOGRR245_ROS_DWG%2520Item_08092024-r01.pdf">presentation</a></li> <li style="font-weight: 400;" aria-level="1">Since March, DWG, IBRG, and ERCOT have collaborated on developing testing methods as outlined in NOGRR245.</li> <li style="font-weight: 400;" aria-level="1">Comments were received from Southern Power and Luminant after the July 20 workshop, leading to a one-month extension for review.</li> <li style="font-weight: 400;" aria-level="1">The presentation covered responses to these comments and minor modifications made to the manual.</li> <li style="font-weight: 400;" aria-level="1">Southern Power requested more time for review, with ERCOT agreeing but stressing the importance of timely ROS approval.</li> <li style="font-weight: 400;" aria-level="1">Emphasis was placed on the generation owners’ responsibility to meet ERCOT rules and on the benefits of early testing with new IBR curves.</li> <li style="font-weight: 400;" aria-level="1">Southern Power suggested aligning the effective date of the ride-through test with the NPRR245 deadlines, which ERCOT acknowledged.</li> <li style="font-weight: 400;" aria-level="1">Clarification was given that the DWG manual is for technical guidance, not for defining deadlines or exemptions.</li> <li style="font-weight: 400;" aria-level="1">Both legacy and new IBR units must undergo testing with both the legacy and the new voltage dip test curves.</li> <li style="font-weight: 400;" aria-level="1">ERCOT added a new voltage dip in the test curve to improve efficiency and address operational feedback.</li> <li style="font-weight: 400;" aria-level="1">The preferred ride-through curve was renamed the "voltage dip test curve" to better reflect its function.</li> <li style="font-weight: 400;" aria-level="1">Southern Power raised concerns about maintaining accurate models, which ERCOT addressed by emphasizing the generation owner’s responsibility.</li> <li style="font-weight: 400;" aria-level="1">Updates were made to the DWG manual based on Luminant's suggestion to use actual IBR settings in modeling.</li> <li style="font-weight: 400;" aria-level="1">ERCOT clarified that the piecewise testing for the prepared IBR curve is not a new concept and offered assistance in performing the tests.</li> <li style="font-weight: 400;" aria-level="1">Stakeholders were asked to review the updated DWG manual and submit comments by August 16.</li> <li style="font-weight: 400;" aria-level="1">The final step is the recommendation of the DWG manual for approval at the September ROS meeting.</li> </ul> <a href="/sharing/?token=6860135e-9e14-4b39-9414-04ce6037b972">Q&A</a> <ul> <li style="font-weight: 400;" aria-level="1">Andrew Nigro, Invenergy, expressed confusion about the timeline for submitting capability reports and performing new tests. He asked when he could start testing with updated models, given that the manual is still in draft. <ul> <li style="font-weight: 400;" aria-level="1">Sun Wook responded, clarifying that the timeline for submitting models and tests is defined in the planning guide and the DWG manual. If there are no changes or updates needed, there is no requirement to submit anything new.</li> </ul> </li> </ul> <ul> <li style="font-weight: 400;" aria-level="1">Katie Rich from Luminant raised a concern about the difference between preferred and legacy curves for high and low voltage and questioned why both tests are necessary, given the costs involved in running additional tests. <ul> <li style="font-weight: 400;" aria-level="1">Sun Wook explained that both curves provide different valuable data. He mentioned that Jonathan would provide more detailed explanations in his presentation.</li> </ul> </li> </ul> <ul> <li style="font-weight: 400;" aria-level="1">Carol Chessmore, Oncor, asked if TSPs should encourage new generation facilities to implement new tests before NOGRR245 becomes effective, even though it's not yet required. <ul> <li style="font-weight: 400;" aria-level="1">Sun Wook agreed that it could be beneficial to start early testing, even if not required, as the requirements are mostly settled.</li> </ul> </li> </ul> <ul> <li style="font-weight: 400;" aria-level="1">Kristen Cook, Southern Power, followed up on Carol's question, asking for clarification on when the procedure manual becomes effective relative to NOGRR245. She expressed concern about ongoing modeling work being disrupted by new requirements. <ul> <li style="font-weight: 400;" aria-level="1">Sun Wook clarified that the DWG manual will be effective once NOGRR245 is effective, and there will be notes or watermarks in the manual to indicate this.</li> </ul> </li> </ul> <ul> <li style="font-weight: 400;" aria-level="1">Carol Chessmore, Oncor, asked whether there would be a section in the manual that indicates if a generator is exempt from certain requirements <ul> <li style="font-weight: 400;" aria-level="1">Stephen Solis from ERCOT clarified that any exemptions granted would only apply to the portion that does not meet the requirements, not the entire requirement set.</li> </ul> </li> </ul> <ul> <li style="font-weight: 400;" aria-level="1">Miguel Costa, Vestas, raised concerns about the thermal and mechanical stress caused by consecutive testing of voltage dips, suggesting the need for more flexibility in testing intervals. <ul> <li style="font-weight: 400;" aria-level="1">Jonathan Rose, ERCOT, responded that the DWG manual allows for spacing between disturbances to allow for recovery and that the intention is not to test multiple fault events but to test the profile effectively.</li> </ul> </li> </ul> <ul> <li style="font-weight: 400;" aria-level="1">Miguel Costa further discussed potential issues with reactive current injection and suggested more discussion might be needed to refine the testing approach. <ul> <li style="font-weight: 400;" aria-level="1">Jonathan Rose acknowledged the concern and agreed to discuss it further, emphasizing the need for testing that benefits the grid while also accommodating the unique characteristics of different equipment.</li> </ul> </li> <li style="font-weight: 400;" aria-level="1">Jonathan Rose and the meeting facilitators thanked the participants for their feedback and contributions to the discussion.</li> </ul> <a href="/sharing/?token=d4713203-198f-44ae-80ce-a9f60be7eca8">8</a> - Other Industry Updates - Julia Matevosyan - ESIG <ul> <li style="font-weight: 400;" aria-level="1">Meeting on July 30 discussed OEM readiness for IEEE 2800 by three OEMs.</li> <li style="font-weight: 400;" aria-level="1">Presentation recordings related to NOGRR245 and inverter capabilities are available.</li> <li style="font-weight: 400;" aria-level="1">Links provided for recordings, a webinar on grid forming capabilities from SMA, and a session on interconnection and modeling requirements.</li> </ul> 9 - Other Business <ul> <li style="font-weight: 400;" aria-level="1">Not Discussed</li> </ul> 10 - Adjourn - All