- Spoke article

Automation ROI calculator. Indicative payback for Australian manufacturers.

The framework most capex committees actually use to evaluate an automation project, written for the engineer or plant manager scoping the conversation. With an embedded calculator that gives an indicative payback in months. Indicative, not committee-ready.

01 / framework

The framework most capex committees actually use.

How often does the headline payback number on an automation proposal survive contact with the finance team?

The framework that consistently survives review across Australian manufacturing capex committees has the same shape regardless of sector. Cost on one side; benefit on the other.

The cost side.

Three components: the equipment capex (PLCs, instruments, motors, cabling, panels, the line modifications), the integration cost (engineering, software, commissioning), and the operating-cost delta (energy, maintenance, ongoing licences, training). Operating costs can be positive or negative — automation often reduces some opex categories and increases others.

The benefit side.

Four categories: throughput change (more units per hour), quality improvement (lower reject rate, less rework, fewer customer returns), labour redeployment (the dollars released by reassigning operators to higher-value tasks, not just headcount reduction), and risk reduction (the cost of a bad event averted, applied with appropriate probability).

The headline metric.

Simple payback in months. Annual benefit divided into total project cost. The Australian capex committee's first question is almost always "what is the payback period," and a working answer there decides whether the project gets the second meeting.

02 / calculator

The calculator.

Enter the values for your project below. The output recalculates as you type. All values are indicative.

Indicative payback calculator
Australian dollars. Annual benefits are computed from inputs and divided into total cost.
PLCs, instruments, panels, motors, line modifications.
Engineering, software, FAT, commissioning, training.
Positive if automation increases opex (licences, maintenance); negative if it reduces opex (energy, consumables).
Loaded annual cost of the operators directly affected by the project.
Fraction of the labour cost redeployed or reduced. 40% is typical for partial automation; 75-90% for full automation of a discrete task.
Total annual revenue produced by the line or scope the project covers.
Headline points of OEE improvement attributable to the project. 2-4 is conservative; 5-8 is typical for a meaningful upgrade; over 10 needs strong justification.
Reduction in reject/rework/returns expressed as a percentage of annual revenue. Often 0.5-2.0%.
Annual benefit $248,000 AUD per year
Total project cost $700,000 Capex + integration
Simple payback 33.9 months (indicative)

Indicative only. The calculator does not account for time-value of money, financing cost, depreciation, capex hurdle rates, project risk, or the operational maturity of the assumptions. Use for early triage, not for capex committee submissions. For a working ROI suitable for committee review, see the feasibility study article.

03 / sensitivity

Sensitivity — what moves the number most.

Adjusting the inputs above is the fastest way to see this directly. The patterns that turn up consistently in real projects:

Labour redeployment factor.

The single biggest lever on payback for most projects. Partial automation that retains the operator for unrelated tasks redeploys 30-40% of the labour cost. Full automation of a discrete task can redeploy 75-90%. The honest answer about which case you are in is the most-tested assumption in capex review.

OEE lift.

Each percentage point of OEE on a high-revenue line is worth substantial money, and capex committees know it. Five points of OEE lift on a line producing AUD 5 million of revenue per year is worth roughly AUD 250,000 a year in additional output value. The risk is over-claiming: projects often deliver one-third to one-half of the OEE lift assumed at the proposal stage.

Quality margin.

The cheapest input to over-claim and the hardest to verify after the fact. Customers often see this as small numerically; in practice for plants with significant reject rates or warranty exposure, quality margin recovery is sometimes the dominant payback driver. Worth segmenting in the analysis: reject reduction is one number, customer return reduction is another.

Equipment capex.

Less sensitive than the benefits side on most projects, because capex is bounded by quotes from real vendors. The pattern to watch is the integration cost: a project costed at AUD 500,000 capex and AUD 100,000 integration often delivers at AUD 500,000 capex and AUD 200,000 integration, especially in brownfield. Pad the integration estimate at the proposal stage; do not pad the benefit estimate to compensate.

04 / sectors

Typical payback by Australian manufacturing sub-sector.

Working ranges from finished projects. The bands are wide because individual projects vary, but the central tendencies are useful for triage.

  • FMCG packaging lines (high-volume, single-SKU): Typically the strongest payback case. The combination of high throughput, predictable cycle time, and clear labour-redeployment opportunity makes packaging the easiest automation business case to write.
  • Dairy / beverage filling and processing: Strong throughput and quality cases; labour redeployment is usually smaller because the existing line is already partly automated.
  • Multi-SKU / high-changeover food manufacturing: Quality and traceability gains often dominate; throughput gains are bounded by changeover frequency.
  • Process plant brownfield upgrades: Driven by reliability, risk reduction, and platform-EOL avoidance more than by direct payback. Strategic justification often outweighs the headline number.
  • Logistics / sortation: Direct labour-redeployment story is the strongest in this sector; throughput effects are real but secondary.
05 / dont-automate

When not to automate, even with positive ROI.

A positive payback number is a necessary condition, not a sufficient one. Three patterns where the calculator says yes and the right answer is no.

The line is about to be replaced.

Investing in automation for a line approaching end-of-life almost never pays back, even if the calculator shows a positive result. The benefit window is too short to absorb the disruption. Wait, automate the replacement, capture the savings against the new asset.

The operations team is not on board.

Automation projects with no operational champion fail at commissioning, regardless of the engineering quality. If the operations team views the project as something done to them rather than for them, the headline ROI will not survive contact with operator-induced rework, slow ramp-up, and quiet under-utilisation.

The plant has no realistic commissioning window.

Some plants run flat-out for months at a time with no scheduled downtime large enough to commission a meaningful project. ROI on the back of a phantom commissioning weekend is ROI that will not be delivered. Either the project needs to be scoped to fit the available windows (often module-by-module), or the commissioning constraint needs to change before the project can proceed.

06 / beyond

What the calculator does not capture.

An indicative simple-payback calculator is right enough for early triage and wrong enough to be dangerous if used beyond it. Five things it leaves out.

  • Time-value of money. The capex committee discounts future benefits. NPV and IRR matter for any project above a meaningful threshold. The simple-payback calculator ignores both.
  • Depreciation and tax effects. The accounting treatment of the capex affects the cash-flow shape and, on larger projects, the after-tax payback materially.
  • Risk-weighted benefit. A project that promises an 8-point OEE lift with high confidence is different from a project that promises the same lift with medium confidence. The calculator weighs them the same; capex committees should not.
  • Strategic benefits. Supplier-of-choice positioning, compliance with retailer roadmaps, AS IEC 62443 cyber posture, and corporate-parent standardisation often justify projects whose narrow ROI is marginal. None of these appear in the calculator.
  • Opportunity cost. Capital deployed on this project is capital not deployed on another. The calculator measures absolute payback, not relative payback against the next-best use of the money.

For projects that survive the indicative triage, the next step is a proper feasibility study (see the feasibility study article) or a vendor-selection process (see the vendor selection article). Pac Technologies' consultancy practice handles both. The calculator above is the conversation starter; the working ROI is the conversation that follows.

07 / faq

Common questions.

What does the ROI calculator actually compute?

An indicative simple-payback period in months. The model takes the customer-supplied capex, integration cost, current annual labour cost on the affected scope, expected OEE improvement, expected throughput effect, expected quality improvement, and operating-cost delta, then computes the annual benefit and divides capex plus integration by it. The output is indicative, not a substitute for a full capex business case. Use it for early triage, not for board-level decisions.

Why is the result called indicative?

Because a calculator with seven inputs cannot replace the work that a real feasibility study and FEED engagement do. The benefit categories interact (a throughput lift can hide a quality regression, an OEE improvement can be eaten by an unexpected opex increase). Real ROI work prices each category against bounded assumptions the controls layer can actually verify. The calculator's output is right enough to tell whether the project is worth investigating further; it is not right enough to commit capex against.

What payback period is acceptable in Australian manufacturing?

It depends on the corporate parent and the capex committee. As a working guide for Australian manufacturers: under 24 months is typically straightforward to approve, 24-48 months is the standard band most capex committees consider, and over 60 months requires a strategic justification beyond ROI alone (regulatory compliance, risk reduction, supplier-of-choice positioning). Lines with shorter payback than 12 months are sometimes treated with suspicion — the assumptions may be too optimistic.

Should we automate if the calculator shows positive ROI?

Not on the calculator alone. Positive ROI is a necessary condition, not a sufficient one. A project with positive ROI but no operations-team buy-in, no realistic commissioning window, or no clear post-go-live support owner is a project that will struggle regardless of the headline numbers. The calculator surfaces the financial conversation; the rest of the conversation is operational, technical, and strategic.

- sources

Further reading.

Related Pac Technologies resources and capex-methodology references.

This article sits under Pac Technologies' consultancy service. The calculator above is indicative. For working ROI suitable for capex committee submission, see the feasibility study article.