1. What stops
2. What keeps costing money while nothing moves
3. Cost of catching back up
Per event4. How often, and for how long
5. Apply it to guarding & framing changes
OptionalThis is where the number becomes an argument. Modular framing rarely wins on purchase price — it wins because the line is down for hours instead of days.
What makes up that hour
Scaled up
Framing changeovers
Your hourly rate is saved locally and will pre-fill there.
How this is calculated
The hourly rate
Three components, added together:
- Lost contribution margin — output you don't produce, reduced by the share you genuinely make up later.
- Idle labor — people you're paying who can't work, reduced by the share of that time you redeploy usefully.
- Unabsorbed fixed overhead — only if you chose to count it.
Recovery costs — overtime premium, startup scrap, expediting — are charged per event rather than per hour, because they don't scale linearly with stoppage length.
Where people get it wrong
- Counting revenue instead of margin. You don't lose the material cost of a unit you never built. Using revenue overstates the number and gets the whole analysis dismissed.
- Assuming full recovery. If the plant is near capacity, lost hours are lost permanently — set recovery low.
- Double-counting recovery. Output you make up isn't lost margin, but the overtime to make it up is a real cost. This model separates the two.
- Ignoring restart. Scrap and requalification on restart are often the single largest per-event cost in process operations.
A planning estimate built from the inputs shown. Not a quotation, and not a substitute for your own cost accounting. Validate against actual downtime records before using it in a capital request.