Utilization Analytics: From Device Ledgers to Operating Insight
Three Layers of Utilization
- Powered utilization: powered hours ÷ business hours — scheduling and dispatch.
- Capacity utilization: actual sessions ÷ theoretical capacity (the ceiling from ROI logic) — demand match.
- Revenue utilization: contribution margin ÷ allocated holding cost — commercial quality; the basis of renew-or-retire decisions.
Read them together: high powered + low capacity = demand problem; high capacity + low margin = pricing or consumables problem.
The Minimal Data Setup
- Log at session end: device, program, duration, operator (system or sheet).
- Monthly roll-up: one table, three layers per device.
- Quarterly review: trends plus anomaly attribution (season? clientele? competition?).
Three Remedies for Underuse
| Cause | Action |
|---|---|
| Thin demand | Focus packaging and acquisition (local acquisition); set an observation-period target |
| Scheduling conflicts | Device calendar + certification matching (certification ladder) |
| Structural surplus | Mismatched with positioning: transfer or trade in — cutting losses is a decision too (retirement) |
FAQ
What utilization is healthy?
40-60% capacity utilization is the realistic healthy band for core devices (ramp-ups excluded). Sustained <20% triggers a strategic review.
Isn’t the tracking a chore?
The minimal setup is five minutes a day; the pain usually comes from back-filling — log at the chair, not later.