Resgrid Blog
Resgrid.com Blog | Open Source Dispatch
At 2:17 a.m., the storm hits, alarms start coming in, and the room changes fast. One dispatcher is juggling radio traffic. Another is writing addresses on a legal pad because the whiteboard is already full. A supervisor is trying to figure out which crew is currently available, not just which unit was supposed to clear …
A city festival starts well enough. Traffic posts are staffed. Medical has a treatment tent. Security has a radio channel. Then the crowd shifts after a weather alert, one volunteer team loses contact, and three different supervisors start updating three different spreadsheets. Dispatch knows units are moving, but operations doesn't have a clean view of …
You usually notice the compliance problem after the incident is over. A reimbursement packet is due. An internal review has started. A grant file needs backup. Someone asks for the timeline, the personnel roster, the unit activity log, the patient handling record, and the reason one status change never made it into the final report. …
A call drops, units are moving, and then someone says the reserve ambulance has a charging issue and the frontline rig is already down for a repair nobody documented clearly. That's how many agencies discover their maintenance process isn't really a process. It's a mix of memory, sticky notes, paper check sheets, and a spreadsheet …
You probably already know the problem. Your people completed ICS courses, passed the quizzes, and walked away with binders or PDFs. Then six months later a real incident hits, the radio traffic gets messy, resources start moving without clear assignments, and the person in command has to think, talk, track, and prioritize all at once. …
It's the end of the shift. The rigs are back in service, the station has finally gone quiet, and someone still has to finish the incident report. That's usually the moment NFIRS becomes everybody's least favorite task. Most departments treat nfirs fire reporting like a compliance chore. Fill the boxes, pick the codes, send it …
At 2:13 a.m., the phones start stacking up. A transformer failure has knocked out power across several neighborhoods. Traffic signals are dark. A lift station is at risk. The fire department wants road closure support. Public works needs a priority list. The city manager wants a briefing in ten minutes. Dispatch is already juggling calls …
A storm cell rolls through the county. Power flickers at a nursing facility. A brush fire jumps a line and starts moving toward a subdivision. Your dispatch center is taking calls, field units are moving, and then the one thing nobody wants happens. Cellular service gets spotty, data sessions stall, and crews start repeating themselves …
A charger problem rarely shows up at the charging rack. It shows up in the middle of a call, when a portable that looked fine at shift start suddenly drops out on transmit, won’t power on after lunch, or comes back from staging with less runtime than the crew expected. That’s why experienced radio techs …
A lot of projects don’t fail all at once. They drift. A dispatch technology upgrade slips a few tasks. Training takes longer than expected. Overtime gets approved to keep momentum up. The monthly status meeting still sounds fine because each team lead can point to activity. What leadership still can’t answer is the question that …