Use simulations for staffing and equipment planning
Answer 'how many machines do we need?' with evidence instead of gut feel — before the storm.
Simulations
Updated 2026-08-09
The question every operator faces
How many machines should you field for a given storm and a given book of properties? Send too few and you fall behind; send too many and you burn money. A simulation turns that guess into a comparison you can see.
How to size your fleet
- Build a scenario from your real properties and a real service plan.
- Set a baseline vehicle count and run it. Note how long full coverage takes.
- Add a machine and run it again.
- Compare the two replays: how much sooner is the map cleared, and does the extra machine actually earn its keep?
Because you're changing only the fleet size, the difference between runs is a clean read on the value of that machine.
What it's good for
- Storm-day staffing — decide how many operators to call in for the forecast.
- Equipment decisions — model the effect of buying or renting another machine before you commit the capital.
- Setting expectations — show a customer or a partner, with a real replay, what coverage looks like at a given fleet size.
A note on precision
A simulation is a planning tool, not a promise. It runs on real road distances and the real dispatch logic, which makes it a strong guide — but live storms bring weather, breakdowns, and no-shows that no plan fully predicts.
← All help topics
Updated 2026-08-09
In this topic
- What a what-if storm simulation is
- Build a scenario: properties, service plan, and depot anchor
- Set vehicle count, type, and speed
- Run a simulation and replay with the scrubber
- Tenant simulations vs the public sales demo
- Rehearse a storm on your real properties and fleet
- Ghost Lap: ahead of pace or behind, live
- Rewind a completed storm: replay, why stops moved, and what-ifs
- Share a Storm Reel — a public, anonymized replay of your storm