PSAP consolidation gets sold on a simple premise: fewer centers, lower costs, better service. Combine three small dispatch centers into one, eliminate redundant infrastructure, and produce a larger, more capable operation.
Sometimes that's exactly what happens. And sometimes what happens is that three groups of dispatchers who've never worked each other's jurisdictions are put on the same floor, given a merged CAD with 40 agency configurations, and told to figure it out while the politicians hold a press conference about efficiency gains.
I work in a consolidated center. 150+ telecommunicators, 40+ agencies, 19 jurisdictions. It works. But it works because of years of operational integration work that doesn't fit on a PowerPoint slide, not because someone drew a circle on a map and declared it consolidated.
What consolidation actually requires from the comm center
The public conversation about PSAP consolidation focuses on facilities, technology, and headcount. Building, CAD, positions. Those are the visible costs. The invisible cost is operational integration - the work of turning dispatchers who know one jurisdiction into dispatchers who know twelve.
A dispatcher who's worked Agency A for eight years knows the geography, the unit numbering, the mutual aid triggers, the supervisor preferences, the addresses that generate repeat calls, and the shortcuts that make the shift work. On day one of the consolidated center, they're dispatching for Agency B, which has different unit numbers, different geography, different SOPs, different radio procedures, and a different relationship between patrol and dispatch.
That dispatcher isn't incompetent. They're displaced. And training them to be functional across all agencies in the new center isn't a weekend project - it's a multi-year developmental effort that rarely gets the resources or the timeline it requires.
The geography problem
Dispatchers develop geographic intuition over time. They know which intersections are actually the same intersection with two different names. They know which addresses are in the county's jurisdiction and which are in the city's. They know that "behind the Walmart" means something different in each of the three towns they serve.
Consolidation multiplies the geographic knowledge requirement by the number of merged jurisdictions. A dispatcher who had encyclopedic knowledge of one city's street grid is now expected to develop that same knowledge for six cities and an unincorporated county. CAD helps. GIS helps. But the situational awareness that comes from geographic familiarity - the ability to hear an address and immediately picture the area, the access routes, the nearby resources - takes years to build and can't be installed by software.
When it works and when it doesn't
Consolidation works when it's driven by operational necessity, funded adequately, given a realistic integration timeline, and staffed by people who understand that merging centers is fundamentally a human problem, not a technology problem.
It doesn't work when it's driven by political pressure to cut costs, funded based on the assumption that three centers' budgets can simply be combined into one, given a timeline determined by a grant deadline or an election cycle, and managed by people who've never worked a console.
The difference between those two scenarios is almost never discussed honestly in the public meetings where consolidation gets approved. The dispatchers who'll live with the decision aren't usually at the table when it's made.