APRIL ISSUE OF THE CURRENT
Since 2016, grid disturbances have triggered more than 15,000 MW of unexpected generation loss from inverter-based resources. These weren’t equipment failures or extreme weather events. They were generators that were online, connected, and behaving exactly as their software told them to, on a grid whose planning models had no idea.
October 1, 2026 is when that starts to change.
When Physics Stopped Being Enough
For most of the grid’s history, generation reliability was a physics problem. Synchronous generators, spinning turbines locked to the electromagnetic frequency of the interconnection, respond to disturbances the way a spinning top responds to a push. They resist. They stay connected. The response is inherent, predictable, and doesn’t require anyone to configure it correctly.
Inverter-based resources don’t work that way. They respond to grid conditions through software. The inverter reads the voltage and frequency at its terminals, runs those values through control algorithms, and decides in milliseconds whether to stay connected, ramp down, or trip offline. That decision is programmable. And it’s been programmed, across thousands of facilities over the past decade, primarily to protect the equipment.
“An inverter configured to protect itself will trip offline during a disturbance. A grid that built its stability models around generators that stay connected doesn’t know the difference until the fault happens.”
In June 2022, a routine fault on a 345 kV transmission line in West Texas triggered an unexpected loss of approximately 1,711 MW of solar generation across the ERCOT system. Normal fault. Normal clearing time. ERCOT frequency dropped to 59.7 Hz. The solar facilities that tripped weren’t malfunctioning. Their inverters saw the fault, calculated that staying connected posed a risk to the equipment, and disconnected. Exactly as programmed. Nothing in the interconnection study had predicted it because nothing in the interconnection study had accurately modeled what those inverters would actually do.
That event was one data point in a much larger pattern. Since 2016, NERC has documented major disturbances totaling more than 15,000 MW of unexpected IBR losses, 10,000 MW of which occurred in just the four years between 2020 and 2024. In every case, the behavior that caused the loss wasn’t captured in the planning models. The models said the generators would stay connected. The generators didn’t.
Why the Models Are Wrong
The gap between modeled behavior and actual behavior isn’t primarily a design problem. It’s a data management problem.
IBR facilities are modeled at interconnection, when the inverter manufacturer provides a set of parameters that get baked into the planning studies. Those parameters reflect the equipment as configured on the day of interconnection. What they don’t reflect is every firmware update, protection setting adjustment, or plant controller reconfiguration that happens afterward. And there have been many. Inverter manufacturers push updates. Operators adjust settings to optimize performance or extend equipment life. Plant controllers get reconfigured as operating conditions change. None of it automatically propagates to the transmission planner’s model.
The result is a fleet of generators whose actual behavior under fault conditions is systematically different from what the grid’s planning models assume. NERC’s Level 3 Alert, issued in May 2025, was direct about what it found: previous technical recommendations had been largely unimplemented by generator owners, and data submission rates remained unacceptably low. Many entities couldn’t provide basic technical information about their own equipment. Does this sound familiar to anyone?
“The models were built at interconnection and never updated. The inverters were updated constantly. After a decade of that divergence, what the grid thinks it’s running and what it’s actually running are not the same thing.“
What October 1 Requires
Three standards close that gap, on a compliance schedule that is already running.
PRC-028-1 requires IBR facilities to install disturbance monitoring equipment capable of recording voltage, frequency, and real and reactive power during grid events, with UTC time synchronization and mandatory data submission to NERC within 90 days of qualifying events. This is the foundation. Without it, the operational compliance requirements of the other two standards can’t be demonstrated.
PRC-029-1 establishes mandatory ride-through requirements. IBRs must remain connected and continue delivering real and reactive power through defined voltage and frequency disturbance profiles. The standard distinguishes between design compliance, verifying that inverter settings and protection schemes are configured correctly, and operational compliance, demonstrating through actual disturbance data that the facility performs as designed. Design compliance is required by October 1. Operational compliance follows once PRC-028 monitoring is installed and generating records.
PRC-030-1 governs what happens after a disturbance. When a facility experiences an unexpected loss of 20 MW or more, or 10 percent of gross nameplate capacity within four seconds, the generator owner must detect it, analyze the event and identify root causes within 90 days, and develop a corrective action plan within 60 days of completing the analysis. This is continuous, ongoing compliance. There’s no one-time certification. Every qualifying event opens a new clock.
The dependency chain matters. Design compliance under PRC-029 requires reviewing and potentially updating inverter settings and protection schemes, which often requires an outage window to implement. Scheduling outage windows in summer means coordinating with transmission operators who are managing the highest load days of the year. Many generator owners haven’t started that process. Summer is six weeks away.
The Data Infrastructure Behind Compliance
To detect a qualifying event, a facility needs monitoring equipment generating timestamped, synchronized records. To analyze the event within 90 days, the generator owner needs validated models that accurately reflect current inverter settings, not the settings from the original interconnection study. To develop a defensible corrective action plan, they need to understand whether the issue is hardware, firmware, settings, or something in the plant controller that has drifted from the original design.
Most of that data doesn’t exist in a clean, queryable form. Event records live in historian systems with inconsistent tagging. Inverter settings documentation, if it exists at all, lives in commissioning binders that haven’t been touched since the facility energized. The firmware version running on the inverters may or may not match what was submitted to the modeling team. We’ve seen this pattern before. The shadow tool problem isn’t limited to interconnection queues and study workflows. It runs all the way through the operating fleet.
The generator owners who will absorb PRC-028, PRC-029, and PRC-030 without a compliance crisis are the ones who already have continuous disturbance monitoring, model validation processes that track inverter changes, and clear documentation of what their fleet is actually doing under fault conditions. The ones who will struggle are the ones trying to reconstruct that picture from scratch with October on the horizon.
How many generator owners reading this have a clear, current picture of what their IBR fleet’s actual inverter settings are versus what’s sitting in their planning models? Our guess is that number is smaller than anyone is comfortable admitting. If you’re working through this, we’d like to hear what you’re running into. Drop it in the comments.
Thanks for reading. Subscribe to The Current and follow Simple Thread on LinkedIn for fresh analysis, project highlights, and event updates, delivered straight from the front lines of utility software.
Loved the article? Hated it? Didn’t even read it?
We’d love to hear from you.
