How to calculate the ROI of an industrial automation project
A practical method for turning gains in availability, quality, and labor into a number the investment committee will actually engage with.
Automation projects often die not for lack of technical merit, but for lack of a defensible number. This piece describes the calculation we use with clients before writing a single line of code.
1. Establish the baseline
Without a baseline there is no return — only opinion. Before proposing any intervention, measure for at least four weeks:
- Actual equipment availability (productive hours / planned hours)
- Scrap and rework rate
- Labor hours spent on manual tasks that will be automated
- Mean time between failures and mean time to repair
2. Translate each gain into cash flow
Every gain hypothesis needs to become an annual monetary line item.
| Gain | Formula | Caution |
|---|---|---|
| Availability | hours recovered × margin per hour | only counts if there's demand for the extra output |
| Quality | scrap reduction × unit cost | include raw material cost, not just sale price |
| Labor | hours freed × hourly cost | reallocation, not layoffs, in most cases |
| Energy | consumption avoided × tariff | validate with metering, not with a datasheet |
Rule of thumb: if a gain can't be measured after delivery, it doesn't go into the calculation. It goes on the list of qualitative benefits.
3. Add up the total cost of ownership
The most common mistake is comparing the annual gain against the project's price tag. The correct denominator includes:
- 1.Implementation (hardware, integration, engineering)
- 2.Recurring licenses and infrastructure
- 3.Evolutionary maintenance — set aside 15% to 20% of the implementation value per year
- 4.Training and the cost of the adoption curve in the first months
4. Calculate payback and NPV
Simple payback = Initial investment / Annual net gain
NPV = Σ (Cash flow in year n / (1 + rate)^n) − Initial investmentIn shop-floor automation, a payback of 12 to 24 months is usually approved without much pushback. Beyond 36 months, the project needs a strategic argument — capacity, compliance, or risk — not just a financial one.
5. Define how the return will be audited
Write into the scope who measures it, how often, and with which data source. A project that commits to publishing its own results 90 days after go-live has a much better chance of becoming the second project.
Conclusion
Automation ROI isn't an exercise in optimism — it's an exercise in traceability: a measured baseline, attributable gains, an honest total cost, and an agreed-upon audit. With these four elements, the conversation stops being about technology and becomes about capital allocation — which is the language of whoever approves it.