New York City 911 system upgrade failures
New York City's project to unify and modernize its 911 emergency dispatch systems ran years behind schedule and roughly $1 billion over its original budget, drawing sharp criticism after dispatch delays during major incidents.
The damage was public. The root cause was preventable.
New York City's project to unify and modernize its 911 emergency dispatch systems ran years behind schedule and roughly $1 billion over its original budget, drawing sharp criticism after dispatch delays during major incidents.
What the software actually got wrong
The Emergency Communications Transformation Program's software was repeatedly redesigned amid shifting requirements and poor project oversight, and integrating it with the city's existing, disparate police, fire, and EMS dispatch software proved far more complex than planned.
The Emergency Communications Transformation Program's software was repeatedly redesigned...
The Emergency Communications Transformation Program's software was repeatedly redesigned amid shifting requirements and poor project oversight
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.
Integrating it with the city's existing, disparate police, fire
integrating it with the city's existing, disparate police, fire
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
EMS dispatch software proved far more complex than planned
EMS dispatch software proved far more complex than planned
Requs AI Edge Case and Software FMEA together treat this as a known, catalogued defect pattern — not a novel surprise — so it gets tested for deliberately rather than discovered after deployment.
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.