Resgrid Blog
Resgrid.com Blog | Open Source Dispatch
The call comes in just before shift change. Multi-vehicle crash. One lane blocked. Then two lanes. Then a report of entrapment. Your dispatchers are juggling radio traffic, texting supervisors, calling mutual aid, and trying to figure out whether the heavy rescue is already committed across town. Somebody writes unit status on a whiteboard. Somebody else …
A radio failure rarely starts with the radio. It starts with a battery that looked fine at morning check-in, made it through a routine shift yesterday, and then folds under stress when traffic gets heavy, weather turns rough, or a team moves into a weak-signal area and the radio has to work harder. That’s why …
A lot of departments are one dead battery, one missed service interval, or one undocumented repair away from a bad day getting worse. You know the kind of problem. A unit tones out, the vehicle starts rough, a monitor fails its self-check, or a radio cache comes up short because nobody updated the last checkout. …
You hear a siren, see an ambulance roll past, and somebody says, “EMS is here.” A minute later, another person says, “The EMTs are on scene.” These terms are often used interchangeably. They don’t. That difference matters more than vocabulary. It affects who gets dispatched, what care happens on scene, how agencies staff units, and …
At 2:14 a.m., the lobby panel says waterflow on an upper floor. Security says they smell smoke but can’t confirm the location. An elevator is recalled. One stair door shows trouble. The first-arriving company gets a report of people still inside, while another crew hears the alarm may be false. If nobody is pulling those …
You probably have one right now. A handheld in a charger with a fading label. A spare mobile in a cabinet with no clear owner. A tablet that still powers on, but nobody knows whether it belongs on a rig, in a command vehicle, or in surplus. That kind of equipment drift is normal in …
A lot of city and campus managers are in the same spot right now. They have aging blue light towers, a few dead spots where mobile service is unreliable, a dispatch team already juggling too many systems, and a budget that won’t tolerate a vanity project. The easy mistake is to treat emergency call boxes …
At 02:17, the plan still looks clean. Three engines are assigned. Mutual aid is en route. Dispatch has the addresses. The board says the operation is under control. By 03:05, it isn’t. One road closure wasn’t pushed to everyone. A crew got sent twice to the same task while another assignment sat open. Relief staffing …
The call comes in during dinner, during a staff meeting, or halfway through the only hour of sleep a volunteer firefighter was going to get that night. Cell coverage is weak on one side of town. The CAD notification hits some phones late. One person’s app is muted. Another has no signal in the machine …
Your fleet manager just asked a simple question that usually turns into an expensive mistake: “Should we buy Motorola wireless mics for the radios?” The right answer isn’t yes or no. It’s, “For which users, on which radios, in which vehicles, tied to which workflow?” That’s where agencies either build a clean, reliable setup or …