How the live fleet feed stays current

Live means live

Everything moving on your dashboard and map is driven by a continuous stream of position pings coming off each vehicle in the field. Understanding how that feed works makes the board easier to trust.

Pings from the field

Each operator's device reports its GPS position on a rolling basis. Snowmass adapts the ping rate to what's happening — faster when a machine is close to a stop, slower when it's in transit — so the map is precise where precision matters without flooding the network.

From ping to decision

Every ping does more than move a dot. It's also what the swarm runs on: each position update is a chance for a machine to claim its next best property. That's why liveness, progress, and claims all move together — they're powered by the same feed.

When a device goes quiet

If pings stop arriving, the vehicle slides from online to at-risk to silent, and after a sustained silence its claimed work is released back to the swarm. The feed going quiet is itself a signal — it's what powers the silent-vehicle and stranded-stop alerts.

Offline behaviour

If an operator loses signal, their device keeps buffering positions locally and syncs them on reconnect. They keep logging where they are; they just can't claim new stops until the connection returns, because that decision is made on the server.

Why it matters

The feed is the heartbeat of live operations. Because it's the same data behind the map, the alerts, and the dispatch engine, what you see is what's real.