Tool 04
Drive Time and Downtime Planner
Set how many units you need to put through, how long each is out, what a day of production is worth and whether you plan to stagger them. The tool returns total exposure and the schedule shape. It models the cost of the vehicle not working, which is usually larger than the repair invoice.
Inputs
Output
$6,492
Total exposure
Lost revenue plus transport across all units.
$6,300
Lost revenue
$192
Transport cost
Schedule shape
14 day window, 1 unit out at once
Assumptions
- Drive modeled at 20 miles each way between Eastvale and the Yorba Linda facility.
- Operating cost placeholder of $0.85 per mile plus roughly 1.1 hours of driver time per round trip.
- Driver time valued at the daily revenue figure spread across an eight hour day.
- Lost revenue assumes the unit produces its full day rate every calendar day it is out.
- Staggering keeps one unit in the shop at a time, which lengthens the total window but protects coverage.
- Parts delays are not modeled. On a multi unit program they are usually the binding constraint.
Production loss usually beats repair cost
An operator looking at a body repair estimate is looking at roughly half the exposure. A fourteen day repair on a unit that produces four hundred and fifty dollars a day carries more than six thousand dollars of lost production alongside whatever the shop charges. On a longer structural job the production loss can be the larger figure by a wide margin.
That changes what a good decision looks like. Paying for overtime or a second technician to compress a repair is often cheaper than the days it saves, which is the opposite of the instinct most people bring to a repair quote. It also means deferring a small repair until it becomes a large one is expensive twice over.
Staggering is the other lever. Sending an entire group at once minimizes total elapsed weeks and maximizes simultaneous disruption, which is the version most operations cannot absorb. Running one unit at a time keeps coverage intact at the cost of a longer program. The planner shows both shapes so the trade is explicit rather than accidental.
What no model handles well is parts. On a multi unit program they are almost always the binding constraint, and the delay does not distribute evenly. Five units move through cleanly and the sixth waits a month on a discontinued component. Planning slack for exactly one unit doing that is realistic.
About this planner
01Why stagger units instead of sending them together?
02Is the transport cost realistic?
03Why does the revenue figure matter more than the repair cost?
04What is the biggest thing this does not model?
05Does this apply to a single personal unit?
- DWG
- TOOL-04
- SCOPE
- DOWNTIME PLANNER
- SHEET
- 05 OF 05
- SCALE
- 1:1
- MARKET
- EASTVALE, CA
- SHOP
- YORBA LINDA, CA
Plan the program before the first unit moves
Send the list and the constraint. Scheduling a group properly is a different conversation than scheduling one repair, and it is worth having up front.
