Which available unit is closest — and can I commit it now?

It's the most-asked question in a 911 center and an EOC resource desk, and today the answer is assembled, never bought whole. The dispatch stack owns the unit feed but locks it behind a six-figure system of record. Fleet-telematics platforms have a beautiful live map — but they don't know what an incident is. The mapping platform ships the pieces — a stream here, a nearest-facility solver there — and leaves you to wire them.

And nearly all of it is cloud-first: unit positions and responder PII leave the jurisdiction to answer a local question.

Click the incident. Rank the nearest available unit.

• An incident lands on the map — a live weather alert, a wildfire, a call. One click ranks the closest available units, draws the spokes, flashes #1, and the map flies in to frame the incident with its connected units.
• Pre-position instead of react: click any point for staging, before the call.
• Distance is the honest default; drive-time (the true closest-facility rank) is one wizard step when a routing service is wired — never faked.

"E-14 — 2.1 km, available, fix 30 s old." A defensible answer, in under a second.

The fleet's vital signs — always on screen.

• Not a unit list — the fleet's status. Online, available, enroute, on-scene, out-of-service, average fix age: the numbers a watch officer reads at a glance, with a delta since the last refresh.
• An availability gauge answers "how much can I still dispatch?" in one dial.
• A red exception banner surfaces the stale, out-of-service, and low-battery units — click it to isolate them everywhere at once.

Every number is a filter — the whole board moves together.

• Click a vital — Available, Enroute, On-scene, Out-of-service — and the map, the roster table, and the type breakdown all narrow to it at once.
• Click a resource type — Engine, Medic, Truck — and the vitals, the availability gauge, and the map re-scope to that class.
• Status × type combine; click again to clear. One selection, applied everywhere — no dashboard-hopping, no query builder.

"Show me the available Engines" is two clicks — and the map, the table, and the counts already agree.

One click. The shift report. Zero re-typing.

• Generated situation report: the vitals — online, available, enroute, on-scene, out-of-service, average fix age — plus the full unit roster, rendered from live state, every operational period.
• Feed vintage printed on the brief: leadership reads not just the counts but how fresh the source was. Accountability travels with the page.
• Filtered CSV / GeoJSON for the next system; a share deep-link for the next watch.

The neutral overlay — on your servers.

• Not a CAD. It reads a published live layer — from your stream processor, field-tracking app, or a vendor AVL — and interoperates with the incumbent (EIDO / CAD-to-CAD sharing), never fights it.
• Sovereign: unit positions and responder PII stay on-prem, behind your SSO. The answer to the CJIS "where is it, who controls it" question.
• Flat-licensed: no per-seat CAD meter, no per-vehicle telematics fee, no map-credit tax — the affordability story for rural and volunteer agencies.
• Speaks the language: the status lifecycle, mutual-aid regions, NIMS resource typing — your staff needs no retraining. Runs on Strata or ArcGIS. Bilingual EN/AR (RTL). Wall mode for the EOC floor.

No open feed is both live and dense. We say so.

The truth every vendor demo hides: no public California feed is both live-moving and a dense vehicle fleet. The aircraft feed is real but sparse; the fleet AVL layer is a real schema but a frozen Aug-2024 snapshot. (The one feed that is live & dense — CAL FIRE Helicopter Water Drops, 38k+ pts refreshed to today — rides along as a real air-ops overlay.)

So the populated default is a clearly-labeled synthetic fleet — clean statuses, heading, a ticking fix — with both real feeds one toggle away, each marked for exactly what it is. Your own published live layer is the production source; the synthetic fleet is an honest stand-in, never a disguise.