Ring to clear, on one system.

The screen your dispatchers spend the shift in, laid out the way your centre actually works rather than the way a vendor shipped it.

• Layouts you author. Fields, tabs and columns arranged per position — fire dispatch and call taking do not need the same screen.
• Saved per position. Someone working three different desks gets the right layout at each, chosen at sign-in.
• Changed by you. A layout change is an afternoon, not a change request and a release.

Search the way a caller actually describes where they are, against your own GIS data.

• Numbers and streets — the ordinary case, matched as it is typed.
• Cross streets — main & elm resolves to the intersection.
• Street only — everything known on a road, for when the caller knows nothing else.
• Common names — the high school, the stadium, the mile marker, named the way people say it.

ANI/ALI arrives on the call rather than on a separate screen the call taker has to read from and retype. The location is matched against your address data on the way in, so a 911 call starts with a verified location instead of a string.

Standard operating procedures attached to a problem nature, on screen the moment that nature is chosen. No binder, no second window, and no relying on someone remembering that this particular call type has a notification attached to it.

Sectors, districts, still-alarm areas, beats — whatever your agency calls them. They come from your own boundary polygons, so the map and the dispatch agree by construction.

• Baked from boundaries. Every street and address carries its area as an attribute, so dispatch is an instant lookup rather than a geometry calculation.
• Left and right. A centreline can be the boundary — odd numbers one district, even numbers another.
• Overlays for shared ground. A county or regional sector covering the same streets as a town, with the incident type deciding which one responds.
• Coverage testing. Simulate a response at a real address before you rely on it.

Plans ask for what a unit can do, not for a unit by name. A plan naming Engine 3 is wrong the day Engine 3 is out of service; a plan asking for an engine never is.

• Capability-based. Ask for extrication, ALS, hazmat — or for an engine that is also hazmat.
• Alarm levels. Every line at the current level fires as one wave; escalation pulls the next, in one action.
• Tiered alternatives. This station, then the neighbour, then mutual aid — and once the line is satisfied it stops.
• Reusable groups. A full structure assignment maintained once and inserted into any plan.

Units ranked by travel time over the road network, not by straight-line distance — a unit across a river is not close.

When units commit, coverage develops holes. P1 shows the hole while you can still do something about it, and posting a unit to cover it is recorded rather than shouted over the radio and forgotten by the next shift.

An in-vehicle terminal that mirrors the console rather than approximating it. Crews see the call as dispatch sees it, set their own status, read and add notes, and are on the same map.

• Status from the vehicle appears on the board immediately, attributed to its source.
• Emergency button — press and hold, unmistakable on every board, and only dispatch can clear it.
• Built for the connection a vehicle actually has, and honest about it when the link drops.

Stations tone out as part of the dispatch, not after somebody remembers to do it separately. One action sends the call, alerts the station and pages the crew.

Live unit positions on the map, with the age of each fix shown — a stale position is shown as stale rather than quietly drawn as current.

• Auto-status can flip a unit on arrival, by geofence and dwell time, instead of waiting for a radio call.
• Closest unit and closest hospital, ordered by travel time from the incident.
• Your own layers — hydrants, pre-plans, hazards, box areas, mile markers.

Outbound alerting to pagers and phones, driven by the same dispatch that lit the station, so the volunteer on the other end gets the call at the same moment the room does.

The nature is what you thought at intake. The disposition is what it turned out to be, and it is the field every later report is built on.

On an incident involving several agencies, each closes its own part: fire closes as a good intent, EMS closes as a transport, on the same call. Nobody's numbers are wrong because somebody else picked the outcome.

NIBRS, NFIRS and NEMSIS come out of the same record your dispatchers already filled in — no re-keying into a second system.

The geography behind all of the above is yours to maintain, with tools built for the people who actually maintain it.

• Import what your county already publishes — street centrelines, address points and boundaries, reprojected on the way in.
• Review before it goes live. Address imports stage into a queue; you accept or decline before anything reaches a call.
• Draw boundaries in the browser rather than waiting on a GIS analyst and a desktop package.
• Verify before you trust it — data health checks, and a preview of exactly what a dispatcher's search would return.