Frame

Meeting Summary - 04/16/2025 PDCWG Meeting

Grid Monitor AI
04/17/2025

<div class="news-image-container"><img src="/storage/docs/2025/04/PDCWG%2020250416.png" width="830" height="466" /></div> <h3><a href="/sharing/?token=22170393-f1e6-43b3-82bf-5859475495b2">▶️</a>1 - Antitrust Admonition</h3> <h3><a href="/sharing/?token=29e5541b-90e7-4719-bb75-46e55ba8924e">▶️</a>2 - Annual Inertia Presentation</h3> <a href="/storage/docs/2025/04/ERCOT_Annual_Inertia_2014-2024_2025_PDCWG_Final.pdf">ERCOT_Annual_Inertia_2014-2024_2025_PDCWG_Final.pdf</a> <ul> <li style="font-weight: 400;" aria-level="1">Presentation on ERCOT's annual inertia analysis by Jorge Cantu.</li> <li style="font-weight: 400;" aria-level="1">Integration of inverter-based resources has been increasing, leading to lower system inertia overall.</li> <li style="font-weight: 400;" aria-level="1">Higher system inertia results in lower rate of change of frequency (RoCof), while lower inertia increases RoCof.</li> <li style="font-weight: 400;" aria-level="1">Fast Frequency Response (FFR) has been implemented, making the static value of critical inertia more dynamic.</li> <li style="font-weight: 400;" aria-level="1">Real-time inertia calculation has been in place since 2015 to analyze impacts on system inertia.</li> <li style="font-weight: 400;" aria-level="1">Action is considered when system inertia falls below certain thresholds, but no actions have been taken yet.</li> <li style="font-weight: 400;" aria-level="1">FFR was introduced in 2020 and helps reduce minimum inertia levels required for reliable operation.</li> <li style="font-weight: 400;" aria-level="1">In 2025, the maximum FFR procurement was 450 MW; FFR was activated in September 2023.</li> <li style="font-weight: 400;" aria-level="1">Significant increases in solar and battery capacity from 2023 to 2024; wind generation capacity increased by 776 MW.</li> <li style="font-weight: 400;" aria-level="1">2024 similar to 2023 in terms of inertia levels; lowest synchronous inertia noted during specific times.</li> <li style="font-weight: 400;" aria-level="1">A strong correlation exists between inertia and net load: as net load increases, so does total inertia.</li> <li style="font-weight: 400;" aria-level="1">2024 experienced less overall hours with very low inertia compared to previous years.</li> <li style="font-weight: 400;" aria-level="1">Shift in lowest net load and lowest inertia periods due to increase in solar generation.</li> <li style="font-weight: 400;" aria-level="1">Combined cycle generation has a strong correlation with total inertia.</li> <li style="font-weight: 400;" aria-level="1">FFR participation has increased since 2023, leading to lower critical inertia levels.</li> <li style="font-weight: 400;" aria-level="1">Observations include shifts in timing of lowest inertia hours and net load due to solar capacity growth.</li> </ul> <h3><a href="/sharing/?token=96164539-a519-4640-86c6-3386faad3437">▶️</a>3 - NPRR1278 - Establishing Advanced Grid Support Service as an Ancillary Service</h3> <ul> <li style="font-weight: 400;" aria-level="1">The primary focus of NPRR1278 is to establish certain grid support capabilities as an ancillary service that utilities can contract for, rather than as a standard or mandatory requirement.</li> <li style="font-weight: 400;" aria-level="1">The proposed ancillary service would be contracted annually and would operate similarly to a Black Start service, ensuring providers supply the service when online, with penalties for unavailability.</li> <li style="font-weight: 400;" aria-level="1">The service is designed to mirror the reliability requirements in NOGRR272, without altering ERCOT's overall reliability goals.</li> <li style="font-weight: 400;" aria-level="1">This new proposal would allow flexibility for modifications over time, based on ERCOT’s assessment of market needs and reliability requirements.</li> <li style="font-weight: 400;" aria-level="1">There was discussion regarding how this approach might enable more rapid deployment of grid-forming technology by opening participation to a wider range of resources including those upgrading their technology.</li> <li style="font-weight: 400;" aria-level="1">Questions were raised about how to quantify and determine the procurement process for this service, including locational requirements.</li> <li style="font-weight: 400;" aria-level="1">Fred Huang highlighted benefits associated with inverter-based resources transitioning from grid following to grid forming, particularly in areas with smaller synchronous machine concentrations.</li> <li style="font-weight: 400;" aria-level="1">Fred Huang mentioned that the recommended technology for providing this service is currently advanced grid support capabilities, especially focusing on newer energy storage resources.</li> <li style="font-weight: 400;" aria-level="1">It was suggested that a presentation outlining the value of this service to the grid and its integration with existing systems would be valuable.</li> <li style="font-weight: 400;" aria-level="1">The topic of exploring international markets where similar concepts have been applied was discussed, with the UK, Australia, and Hawaii as examples where grid-forming technologies have been implemented.</li> <li style="font-weight: 400;" aria-level="1">There was agreement on the necessity of this service for grid reliability, but further discussion is required on the adoption method and market design.</li> </ul> <h4>Next Steps:</h4> <ul> <li style="font-weight: 400;" aria-level="1">Further development of a presentation to demonstrate the integration and value of the proposed service to the existing grid system.</li> <li style="font-weight: 400;" aria-level="1">Engagement with international markets and further research on international practices readying grid-forming technologies.</li> <li style="font-weight: 400;" aria-level="1">Consideration of technical specifications and market design for this service, including how to effectively quantify and contract it.</li> </ul> <h3><a href="/sharing/?token=c3cb4745-be31-4521-b1be-50e8952f2338">▶️</a>4 - RTCB Telemetry for Resources with Power Augmentation Capacity</h3> <a href="/storage/docs/2025/04/Resources-with-NFRC_RTCB-Telemetry_PDCWG_041625.pdf">Resources-with-NFRC_RTCB-Telemetry_PDCWG_041625.pdf</a> <ul> <li style="font-weight: 400;" aria-level="1">The objective of the agenda is to discuss new telemetry points introduced by RTC+B for resources with power augmentation capacity and seek feedback.</li> <li style="font-weight: 400;" aria-level="1">RTC+B aims to improve telemetry for offline capacity that can be made online through technologies like duct firing.</li> <li style="font-weight: 400;" aria-level="1">New telemetry points include high and low limits of frequency responsive capacity, frequency responsive capacity factor, and inactive augmentation capacity.</li> <li style="font-weight: 400;" aria-level="1">The new telemetry will inform SCED about the frequency responsive capacity of resources to ensure regulation and RRS-PFR awards are within limits.</li> <li style="font-weight: 400;" aria-level="1">Current setup burdens QSEs to manage regulation and RRS-PFR obligations away from steamer capacity, involving real-time checks and post-hoc analysis.</li> <li style="font-weight: 400;" aria-level="1">The new telemetry will eliminate this burden on the QSEs and ERCOT by providing accurate data on available capacity.</li> <li style="font-weight: 400;" aria-level="1">Frequency responsive capacity high limit will be used in SCED calculations, and the new telemetry points will use analogs from the ICCD handbook.</li> <li style="font-weight: 400;" aria-level="1">Inactive power augmentation capacity will provide data on offline power augmentation, turning zero when technologies like duct firing are activated.</li> <li style="font-weight: 400;" aria-level="1">An example of a two GTs configuration with steamer illustrates how new telemetry points would work without considering certain constraints.</li> <li style="font-weight: 400;" aria-level="1">With RTC+B, current NFRC telemetry will be replaced with new telemetry points, impacting BAL-TRE-2 and NFRC calculations.</li> <li style="font-weight: 400;" aria-level="1">ERCOT is contemplating retaining NFRC telemetry in RTC+B for continuity with existing calculations.</li> <li style="font-weight: 400;" aria-level="1">Feedback on this approach is requested by April 28, and it affects how ERCOT will handle telemetry for regulation and RRS.</li> <li style="font-weight: 400;" aria-level="1">Meeting participants can reach out with questions, and ERCOT will be working to test telemetry points.</li> </ul> <h3><a href="/sharing/?token=a7a7ee31-a124-4ec1-8172-c9dc538c62d1">▶️</a>5 - NPRR1257/NOGRR271 - RRS Limits Update</h3> <a href="/storage/docs/2025/04/NPRR1257-Update_PDCWG_V1_041625.pdf">NPRR1257-Update_PDCWG_V1_041625.pdf</a> <ul> <li style="font-weight: 400;" aria-level="1">NPRR1257 and NOGRR271 became effective on 04/01/2025.</li> <li style="font-weight: 400;" aria-level="1">Establishes a maximum limit of 157 MW for RRS-PFR a resource can provide, based on GE's recommendations and ERCOT's study.</li> <li style="font-weight: 400;" aria-level="1">The limit will be reevaluated annually as part of the ancillary service methodology study.</li> <li style="font-weight: 400;" aria-level="1">No immediate system changes by ERCOT; changes will align with the completion of RTC+B.</li> <li style="font-weight: 400;" aria-level="1">Market participants are requested to self-limit RSF-PFR offers to 157 MW.</li> <li style="font-weight: 400;" aria-level="1">ERCOT will monitor and flag resources exceeding 157 MW of RRS-PFR.</li> <li style="font-weight: 400;" aria-level="1">Clarity sought regarding implementation across individual resources and sites.</li> <li style="font-weight: 400;" aria-level="1">ESRs must limit RRS-PFR from both charging and discharging to 157 MW combined.</li> <li style="font-weight: 400;" aria-level="1">Questions from participants on whether limits apply to each point of interconnect and detailed ESR limits clarified.</li> </ul> <h3><a href="/sharing/?token=9e65ff6f-f089-48cb-8e2f-e8985917aca4">▶️</a>6 - Frequency Control & Regulation Report</h3> <h4><a href="/sharing/?token=1f63c170-392f-4f6d-962f-364740f782e5">▶️</a>6.1 - Feb & Mar</h4> <a href="/storage/docs/2025/04/PDCWG-Frequency-Control-Report-for-March-2025-.pdf">PDCWG-Frequency-Control-Report-for-March-2025-.pdf</a> <ul> <li style="font-weight: 400;" aria-level="1">Frequency control report for March: CPS score of 175.89%.</li> <li style="font-weight: 400;" aria-level="1">March 5 and 12 had CPA scores of 99.4% and 97.28%, related to solar generation and manual GTBD adjustments.</li> <li style="font-weight: 400;" aria-level="1">No BAAL exceedances or violations observed in March.</li> <li style="font-weight: 400;" aria-level="1">12-month rolling average CPS1 score at 17.63, RMS1 frequency lower than in 2024.</li> <li style="font-weight: 400;" aria-level="1">Negative time error observed in March; collaboration ongoing with market participants to address operational issues.</li> <li style="font-weight: 400;" aria-level="1">Updates on BAL-003 performance expected next month.</li> <li style="font-weight: 400;" aria-level="1">Slight increase in total energy, mainly attributed to wind and solar.</li> </ul> <a href="/storage/docs/2025/04/Regulation-Analysis-Post-SCR-773_PDCWG_Mar-25.pdf">Regulation-Analysis-Post-SCR-773_PDCWG_Mar-25.pdf</a> <ul> <li style="font-weight: 400;" aria-level="1">Regulation price analysis showed GTBD parameter changes including PSSR dynamic threshold for sunrise/sunset.</li> <li style="font-weight: 400;" aria-level="1">Discussed the projected wind and solar ramp rate errors.</li> <li style="font-weight: 400;" aria-level="1">Regulation deployment trends show a bias towards reg-down during ramping and peak hours, with more reg- up towards late peak hours.</li> <li style="font-weight: 400;" aria-level="1">“Zero” crossing during ramping hours was low compared to previous years.</li> <li style="font-weight: 400;" aria-level="1">Increased time error accumulation compared to the last two years linked to real-time telemetry and operational issues with wind and solar units.</li> <li style="font-weight: 400;" aria-level="1">Increase in total hourly load for March, with less net load during ramping and peak hours.</li> <li style="font-weight: 400;" aria-level="1">Short term load forecast errors include a peak under forecast during peak load hours.</li> <li style="font-weight: 400;" aria-level="1">Expected generation deviation seen during ramp hours, mainly contributed by solar and wind.</li> <li style="font-weight: 400;" aria-level="1">Non-scale qualified flexible loads show correlation with regulation exhaustion.</li> </ul> <h3><a href="/sharing/?token=fc68add4-b0c5-4694-9733-7e27043d4237">▶️</a>7 - Texas RE Report</h3> <ul> <li style="font-weight: 400;" aria-level="1">The Spring standards, security, and reliability workshop is scheduled for April 23rd.</li> <li style="font-weight: 400;" aria-level="1">Participants are encouraged to check the calendar for other meetings of interest.</li> </ul> <h3><a href="/sharing/?token=0c68572e-1b54-4e1c-9d43-0ad351592b60">▶️</a>8 - Analysis of Disturbances (Feb and Mar)</h3> <a href="/storage/docs/2025/04/Non-FMEs-for-Mar-25_PUBLIC.pdf">Non-FMEs-for-Mar-25_PUBLIC.pdf</a> <a href="/storage/docs/2025/04/Non-FMEs-for-Feb-25_PUBLIC.pdf">Non-FMEs-for-Feb-25_PUBLIC.pdf</a> <h4><a href="/sharing/?token=8782061c-d5d6-4b5e-a86c-75fc7e879e8b">▶️</a>8.1 - FME: 3/18</h4> Event on 03/18 <ul> <li style="font-weight: 400;" aria-level="1">Unit trip for a loss of 777 megawatts</li> <li style="font-weight: 400;" aria-level="1">Starting frequency was 60.014 Hz</li> <li style="font-weight: 400;" aria-level="1">Minimum frequency was 59.917 Hz</li> <li style="font-weight: 400;" aria-level="1">A to C time was 3 seconds</li> <li style="font-weight: 400;" aria-level="1">Recovery time was approximately 3 minutes and 17 seconds</li> <li style="font-weight: 400;" aria-level="1">Trip reason is unknown</li> </ul> <h3><a href="/sharing/?token=93f98271-091e-4159-a255-9d14500c41c9">▶️</a>8.2 - Non FMEs: 2/12, 2/13, 2/15, 2/16, 2/18, 2/25, 3/1, 3/5, 3/17</h3> <h5>Event on 02/12</h5> <ul> <li style="font-weight: 400;" aria-level="1">Unit experienced a runback and tripped offline at 813 megawatts</li> <li style="font-weight: 400;" aria-level="1">Starting frequency was 60.002 Hz</li> <li style="font-weight: 400;" aria-level="1">Minimum frequency was 59.923 Hz</li> <li style="font-weight: 400;" aria-level="1">A to C time was 3 seconds</li> <li style="font-weight: 400;" aria-level="1">Recovery time was about 4 minutes and 6 seconds</li> <li style="font-weight: 400;" aria-level="1">224 MW of regulation up deployed</li> <li style="font-weight: 400;" aria-level="1">Trip reason unknown</li> </ul> <h5>Event on 02/13</h5> <ul> <li style="font-weight: 400;" aria-level="1">Unit tripped offline at 571 megawatts</li> <li style="font-weight: 400;" aria-level="1">Starting frequency was 60.14 Hz</li> <li style="font-weight: 400;" aria-level="1">Minimum frequency was 59.947 Hz</li> <li style="font-weight: 400;" aria-level="1">A to C time was 3 seconds</li> <li style="font-weight: 400;" aria-level="1">Recovery time was about 2 minutes and 54 seconds</li> <li style="font-weight: 400;" aria-level="1">Trip reason unknown</li> </ul> <h5>Event on 02/15</h5> <ul> <li style="font-weight: 400;" aria-level="1">Unit tripped for a loss of 582 megawatts</li> <li style="font-weight: 400;" aria-level="1">Starting frequency was 60.013 Hz</li> <li style="font-weight: 400;" aria-level="1">Minimum frequency was 59.928 Hz</li> <li style="font-weight: 400;" aria-level="1">Recovery time was about 2 minutes and 42 seconds</li> <li style="font-weight: 400;" aria-level="1">Trip reason: boiler circulating water pump issues</li> </ul> <h5>Event on 02/16</h5> <ul> <li style="font-weight: 400;" aria-level="1">Unit tripped for a loss of 582 megawatts</li> <li style="font-weight: 400;" aria-level="1">Starting frequency was 60.05 Hz</li> <li style="font-weight: 400;" aria-level="1">Minimum frequency was 59.944 Hz</li> <li style="font-weight: 400;" aria-level="1">A to C time was 4 seconds</li> <li style="font-weight: 400;" aria-level="1">Recovery time was about 6 minutes and 6 seconds</li> <li style="font-weight: 400;" aria-level="1">255 MW of regulation up deployed</li> <li style="font-weight: 400;" aria-level="1">Trip reason unknown</li> </ul> <h5>Event on 02/18</h5> <ul> <li style="font-weight: 400;" aria-level="1">Unit tripped offline for 437 megawatts</li> <li style="font-weight: 400;" aria-level="1">Starting frequency was 59.975 Hz</li> <li style="font-weight: 400;" aria-level="1">Minimum frequency was 59.943 Hz</li> <li style="font-weight: 400;" aria-level="1">Recovery time was about 4 minutes and 55 seconds</li> <li style="font-weight: 400;" aria-level="1">352 MW of regulation deployed</li> <li style="font-weight: 400;" aria-level="1">Trip reason unknown</li> </ul> <h5>Event on 02/25</h5> <ul> <li style="font-weight: 400;" aria-level="1">Multiple units tripped for a total loss of 582 megawatts</li> <li style="font-weight: 400;" aria-level="1">Starting frequency was 59.98 Hz</li> <li style="font-weight: 400;" aria-level="1">Minimum frequency was 59.937 Hz</li> <li style="font-weight: 400;" aria-level="1">Recovery time was about 3 minutes and 42 seconds</li> <li style="font-weight: 400;" aria-level="1">Trip reasons unknown</li> </ul> Event on 3/1 <ul> <li style="font-weight: 400;" aria-level="1">Megawatts: 563</li> <li style="font-weight: 400;" aria-level="1">Starting Frequency: 60.06 Hz</li> <li style="font-weight: 400;" aria-level="1">C Point: 59.931 Hz</li> <li style="font-weight: 400;" aria-level="1">A to C Time: 3 seconds</li> <li style="font-weight: 400;" aria-level="1">Recovery Time: 4 minutes 54 seconds</li> <li style="font-weight: 400;" aria-level="1">Trip Reason: generation voltage issue</li> <li style="font-weight: 400;" aria-level="1">Regulation Deployed: 313 MW</li> <li style="font-weight: 400;" aria-level="1">Nonselection Reason: c point was too high</li> </ul> Event on 3/5 <ul> <li style="font-weight: 400;" aria-level="1">Megawatts: 793</li> <li style="font-weight: 400;" aria-level="1">Starting Frequency: 59.975 Hz</li> <li style="font-weight: 400;" aria-level="1">C Point: 59.902 Hz</li> <li style="font-weight: 400;" aria-level="1">A to C Time: 3 seconds</li> <li style="font-weight: 400;" aria-level="1">Recovery Time: 6 minutes 52 seconds</li> <li style="font-weight: 400;" aria-level="1">Trip Reason: air preheater issues</li> <li style="font-weight: 400;" aria-level="1">Regulation Deployed: 247 MW</li> <li style="font-weight: 400;" aria-level="1">Nonselection Reason: event occurred outside of the dead band</li> </ul> Event Date: 3/17 <ul> <li style="font-weight: 400;" aria-level="1">Megawatts: 567</li> <li style="font-weight: 400;" aria-level="1">Starting Frequency: 60.15 Hz</li> <li style="font-weight: 400;" aria-level="1">C Point: 59.941 Hz</li> <li style="font-weight: 400;" aria-level="1">A to C Time: 3 seconds</li> <li style="font-weight: 400;" aria-level="1">Recovery Time: 4 minutes 43 seconds</li> <li style="font-weight: 400;" aria-level="1">Trip Reason: electric hydraulic control leak</li> <li style="font-weight: 400;" aria-level="1">Nonselection Reason: c point was too high</li> </ul> Questions: <ul> <li style="font-weight: 400;" aria-level="1">Inquiry: Question on the 6 minute recovery time during 02/16 event; reason for slower-than-expected recovery</li> <li style="font-weight: 400;" aria-level="1">Response: Possible factors include scheduling procedures and manual interventions during smaller events.</li> </ul> <ul> <li style="font-weight: 400;" aria-level="1">Inquiry: Whether multiple units tripped at the same point of interconnection</li> <li style="font-weight: 400;" aria-level="1">Response: Yes, some were at the same point, others were independent</li> </ul> <h3><a href="/sharing/?token=e269cd82-cd83-485e-bea5-83acbede7981">▶️</a>9 - Other Items</h3> <h3><a href="/sharing/?token=a247ca3d-8b4e-4d20-a264-341d6835386a">▶️</a>9.1 - Analysis – Why are there fewer FMEs? (future PDC)</h3> <ul> <li style="font-weight: 400;" aria-level="1">Question raised about the number of FMEs in the last twelve months.</li> <li style="font-weight: 400;" aria-level="1">No FMEs reviewed in recent meetings; an FME will be reviewed in the current closed session.</li> <li style="font-weight: 400;" aria-level="1">6 FMEs in 2024 and only one so far in 2025.</li> </ul> <h3><a href="/sharing/?token=0a289fce-2d6b-41cf-baae-d2e70db3d650">▶️</a>9.2 - ERCOT AS Methodology – new probabilistic method – (June PDC)</h3> <ul> <li style="font-weight: 400;" aria-level="1">ERCOT is working on developing a new probabilistic AS methodology internally.</li> <li style="font-weight: 400;" aria-level="1">There are no specific software tools being used; the work is based on internal analysis and tools.</li> <li style="font-weight: 400;" aria-level="1">A brief timeline was discussed, with plans to discuss the methodology at the PDCWG in June.</li> <li style="font-weight: 400;" aria-level="1">Upcoming TAC meetings will introduce the methodology to the group without detailed information.</li> <li style="font-weight: 400;" aria-level="1">Workshops will be announced shortly to discuss the new probabilistic method due to significant changes.</li> <li style="font-weight: 400;" aria-level="1">The first workshop is scheduled to occur before the June PDCWG meeting.</li> <li style="font-weight: 400;" aria-level="1">Stakeholders are encouraged to participate in the working groups and workshops to provide feedback.</li> <li style="font-weight: 400;" aria-level="1">An introductory slide will be presented at the upcoming TAC meeting to announce the start of AS methodology discussions.</li> </ul> <h3><a href="/sharing/?token=b28443d4-03b3-4cf3-8c13-c399cfb7314b">▶️</a>9.3 - IBRs under deep curtailment (future PDC & IBRWG)</h3> <ul> <li style="font-weight: 400;" aria-level="1">Potential future meeting with the IBR working group.</li> </ul> <h3><a href="/sharing/?token=46a23a7c-64df-4a1c-a280-9e971960000b">▶️</a>9.4 - Status on BAL-001-TRE, SAR-13</h3> <ul> <li style="font-weight: 400;" aria-level="1">Reported that progress is being made on the BAL-001-TRE, SAR-13</li> <li style="font-weight: 400;" aria-level="1">Three topics in SAR identified that required language adjustments.</li> <li style="font-weight: 400;" aria-level="1">Consensus reached on two out of the three topics.</li> <li style="font-weight: 400;" aria-level="1">First topic: Addressing deadband and expected changes for those qualified or not qualified for AS.</li> <li style="font-weight: 400;" aria-level="1">Second topic: Clarifying language around resetting rolling average score and clear process.</li> <li style="font-weight: 400;" aria-level="1">Third topic: Necessary changes to standards for evaluating ESRs related to batteries.</li> <li style="font-weight: 400;" aria-level="1">Ongoing discussions and efforts on the third topic.</li> <li style="font-weight: 400;" aria-level="1">Plan to submit changes for discussion and review through PDC once complete.</li> </ul> <h3><a href="/sharing/?token=621264f1-0431-442d-9bbf-af19e650ea46">▶️</a>10 - Adjourn</h3>   <h3> </h3>