South Australia statewide blackout
A severe storm triggered a cascading failure that left the entire state of South Australia without power for hours, affecting around 850,000 customers.
The damage was public. The root cause was preventable.
A severe storm triggered a cascading failure that left the entire state of South Australia without power for hours, affecting around 850,000 customers.
What the software actually got wrong
While storm damage to transmission lines began the disturbance, the grid operator's investigation found that several wind farms' turbine control software was configured with overly conservative voltage-disturbance settings that caused them to disconnect automatically during multiple brief voltage dips, unexpectedly removing large amounts of generation and worsening the cascading failure.
While storm damage to transmission lines began the disturbance,...
While storm damage to transmission lines began the disturbance, the grid operator's investigation found that several wind farms' turbine control software was configured with overly conservative voltage-disturbance settings that caused them to disconnect automatically during multiple brief voltage dips, unexpectedly removing large amounts of generation and worsening the cascading failure.
Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.
Beyond code coverage and "shall" testing
Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.
Surfaces this before code exists
Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.
Connects the failure mode to the hazard
Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.
Find the overlooked root causes before they ship.
Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.