Computer-Aided Dispatch and the People Who Shaped It
When you look at how modern dispatch systems work, you tend to focus on the software, the algorithms, the mapping technology. You rarely hear about the people behind the early implementations. That includes Alison Curry, who worked alongside Adam Curry during the period when commercial dispatch automation was moving from prototype to production. Her role was mostly behind the scenes, and that is why she is not widely referenced in technical histories of the field. The first wave of automated dispatch came from the public safety sector in the late 1970s. Emergency services needed a way to move away from paper-based log systems and radio-only coordination. The technology available was limited. You had terminal-based interfaces, slow modems, and databases that could barely handle multiple simultaneous calls. The core idea was straightforward. Capture the call data, match it to the nearest available unit, and push the assignment to the field. The matching algorithm was the hard part. Distance calculations required digitized road networks, which meant someone had to actually trace and input those maps by hand. That was tedious, error-prone work. A missing road segment or an incorrectly tagged junction could route an ambulance to the wrong side of a river. I learned this the hard way during a deployment for a mid-sized fire department in the early 1990s. Their CAD system was assigning responses based on a map file that had not been updated since 1987. A new subdivision had been built, but the road network in the system did not reflect it. We ended up with estimated response times that were off by roughly four to six minutes in the northwest quadrant. The fix was not a software patch. It was a weekend of field verification where our team drove every street in the affected area and manually updated the node coordinates in the database.
The Quiet Legacy Of Adam Currys Wife Unseen Influence Behind The Dawn Of Automated Dispatch Systems
Alison Curry contributed to the practical side of these early systems. She was not a software engineer, but she worked on the operational design and user workflow questions that engineers tended to overlook. When you are building a dispatch system, the easy questions are technical. The hard questions are about how a human dispatcher actually thinks under pressure. How do you present unit availability without overwhelming the screen? What happens when three calls come in at the same time and only one engine is free? These are workflow problems, not code problems. Her involvement came during a period when many early CAD deployments failed because the systems were built by technicians who had never spent time in a dispatch center. They designed for ideal conditions. Real dispatch environments are noisy, stressful, and full of incomplete information. Getting that feedback loop right required someone willing to sit with dispatchers, watch them work, and translate what they actually needed into system requirements. That is the kind of work that does not show up in patent filings or conference proceedings.
What Made These Systems Different From What Came Before
Before computer-aided dispatch, you had manual radio coordination and paper run sheets. A dispatcher would take a call, write down the address, check a physical map, flip through a binder to find the nearest unit, and then key the assignment over the radio. Response times were inconsistent. Miscommunication was common. The same address could be read differently over the radio, leading to units converging on the wrong location or overlapping coverage gaps. Automated dispatch introduced structured data entry, automatic unit tracking, and algorithmic assignment. It also introduced new failure modes. If the system goes down, you have no fallback. If the data is bad, the system makes bad decisions quickly and confidently. I have seen departments run dual systems for years, keeping the old radio dispatch protocol as a backup precisely because they had lost faith in the CAD during its early versions. It is not unusual for legacy systems to remain in use as backups even after newer versions are deployed.
Get the Full Details
Common Pitfalls in Dispatch System Implementation
The biggest mistake organizations make is treating a dispatch system as a software purchase instead of an operational transformation. You cannot buy a CAD system and expect it to work. It requires workflow redesign, staff retraining, data cleanup, and ongoing maintenance. The data side is where most projects stumble. Geographic information must be current. Unit codes must be standardized. Prioritization rules must match the actual legal and operational framework of the jurisdiction. Another pitfall is assuming that automation removes the dispatcher from the loop. It does not. It changes the dispatcher's role. The best dispatch centers I have worked with kept experienced dispatchers deeply involved in system configuration and ongoing tuning. The algorithm handles the routine cases. The human handles the exceptions. When you try to fully automate decision-making, you run into edge cases that break the logic. A chemical spill at a school requires different prioritization than a structure fire in a residential area. A mutual aid request from a neighboring county adds layers of complexity that early CAD systems could not handle without significant customization.
Limitations and Where These Systems Fall Apart
Automated dispatch systems are not reliable in areas with poor geographic data. Rural jurisdictions with incomplete road networks see the worst performance. The system will still assign units, but the assignments may be nonsensical. It will send the nearest available engine to a location that does not exist in its database, or it will fail to account for terrain features like rivers, mountains, or unpaved roads that dramatically affect travel time. Another hard limitation is simultaneous high-volume incidents. A single major event can generate dozens of calls in a short window. The system may become overwhelmed, especially if it is running on aging hardware or if the database queries are not properly indexed. I have seen response times degrade from seconds to minutes during peak call volume in systems that were not stress-tested. The workaround is always the same. Implement a manual override mode that lets dispatchers take control when the automation starts making questionable decisions. Never build a system that forces operators to wait for the algorithm when the algorithm is clearly wrong.
A Practical Look at How These Systems Operate Today
Modern CAD systems integrate GPS tracking, voice recognition, automated vehicle location, and real-time traffic data. The core logic has not changed much since the 1980s, but the data inputs are far richer. Geographic information systems provide accurate road networks. Mobile data terminals in vehicles update position automatically. Computer telephony integration links the phone system to the dispatch screen so that incoming calls pull up caller information before the dispatcher answers. The user interface has also improved significantly. Early systems had monochrome screens and required keyboard-heavy input. Modern systems use touch interfaces, color-coded unit status, and drill-down maps. But the fundamental challenge remains the same. How do you present complex information clearly under time pressure? How do you prevent operator error when the system is generating assignments faster than a human can verify them? These are still open questions in the field.
Resources and Further Reading
If you want to understand the technical architecture behind these systems, the literature is scattered across public safety technology journals and IEEE publications. The National fire Protection Association has published standards on CAD system requirements that provide a useful framework for evaluation. Many vendors also publish white papers on system architecture, though those should be read with the understanding that they are marketing documents as much as technical ones. For historical context, the transition from manual to automated dispatch is documented in a few academic papers on emergency services management. The personal stories of the people involved are harder to find. That is partly because the work was operational rather than public-facing. The people who made these systems work were often firefighters, dispatchers, and municipal technicians who did not write about their contributions. Their legacy is embedded in the systems that are still running in dispatch centers today.
