Incident command platform · Accredited NERIS vendor
A unified command platform connecting incidents, crews, apparatus, GIS, preplans, accountability and operational intelligence.
Step 01 · Call received
A single point. CAD hands off by webhook, email, file drop or pager text, and the address, box and closest-due units are on the board before the bay door opens.
Step 02 · Units dispatched
E1, E4, L2, R1 and BC1 roll from three stations. AVL updates every five seconds, so the picture shows who actually moved, not what the run card assumed.
Step 03 · Command established
BC1 assumes command and the incident becomes an organization: Operations, Division A, Division C, RIT, Water Supply, Rehab. Every assignment is a node on the same board every officer sees.
Step 04 · Live GIS intelligence
Hydrants with flow classes, the building footprint, the preplan, hazmat, utilities, parcels, water supply, the hospital and road closures. Layers your department already built, on the map the moment they matter.
Step 05 · Accountability
PAR counts riders, not radios. Air is tracked per firefighter with the low-air alarm and exit-time math already done. A MAYDAY turns the board red and keeps it red until it is resolved.
Step 06 · Incident closed
The board becomes the record. Unit assignments, benchmarks, hose lines, PAR history and rehab records become the narrative draft, validated and filed to NERIS without re-keying.
GIS · Spatial operations
Every emergency happens somewhere. Your operational intelligence should understand where.
Apparatus · Incidents
Apparatus position from AVL, incident points from CAD, status from the board. The map is the command board.
Hydrants
NFPA 291 flow classes populate every street from the state hydrant import and your own flow tests.
Preplans · Buildings
Footprints come from your GIS, not a tile provider. Buildings with a pre-incident plan light up before arrival.
Hazards · Road closures
Tier II facilities gain warning overlays. A closed street reroutes the closest-due calculation.
Hospitals · Districts
Response districts, first-due areas and transport destinations, one tap from the incident.
Mutual aid · Evacuation zones
Units from neighboring departments appear the moment they commit. Evacuation zones draw where the plume says.
Platform
Neither should your command software.
Fire
The map is the command board. Units, assignments, water and accountability are drawn on the fireground itself.
EMS
From dispatch to destination on one picture. Unit status, transport, ETA and priority move with the ambulance, not behind it.
Pre-incident planning
Every inspection, every survey, every Knox box your department already logged, rendered where the crew will see it: on the way in.
01 · Exterior
Two stories, steel frame, roof hatch on the B side. The FDC and the Knox box are where the survey put them.
02 · Tactical plan
Entrances, the sprinkler riser, the alarm panel, utility shutoffs and the hazmat storage room, flattened into the plan command reads on the tablet.
03 · GIS context
The plan snaps back into its footprint, with the nearest hydrants and their flow classes on the same street.
Incident command
The board starts with one node and branches as the incident grows. Every assignment carries its crew, its air and its last PAR.
Live operations
Seven benchmarks, timestamped by the board, not by memory. The same apparatus, tracked through every one.
Mutual aid
The closest ten fire or EMS units, whatever the patch on the sleeve. A commit puts the accepted unit straight on the call, read-only for the guest, revoked when the incident closes.
Data · Analytics
Platform · Integrations
Departments do not get to pick their dispatch center, and a CAD replacement is not a prerequisite for better command. The call arrives however dispatch can send it. The mapping is our work, not yours.
Bring your worst call. We will run it on the board with your addresses, your apparatus and your protocols on the screen.