
Business Cases
Part of Automation business cases
Including support and maintenance in automation costs
Estimate automation costs for monitoring, exceptions, support, planned changes and retirement without counting work twice.
The purchase price is only the down payment
Approve an automation project on the purchase price alone and the second-largest cost never enters the room. Service agreements, spares, software licences, monitoring and technician time all accrue after commissioning, and they land in an operating budget rather than the capital spend.
Support and maintenance costs vary from supplier to supplier and range from around 18 to 22 per cent of the purchase price of the software, according to iTnews. Buying through an approved capital expenditure process without pricing that annual charge adds a large, recurring item to the operating budget afterwards.
Australian mid-market businesses allocate an average of 4.9 per cent of revenue to technology, up from 3.8 per cent in 2020, according to Deloitte's 2024 Global Technology Leadership Study. Support and maintenance is the recurring part of that line, and it has to be carried from the first year of service.
Treat the purchase order as a down payment on a multi-year relationship. Vendor response times, spare part availability and the software support path all carry a price, and that price belongs in the same payback calculation as the hardware.
The recurring cost lines to capture
Build the worksheet before the quote is signed, with a column for each of: cost line, frequency, annual amount, escalation rate, internal owner, and whether the cost continues while the system is idle.
Service and support agreements come first: the covered level, the guaranteed response time, and whether callouts, travel and parts are included or charged separately. Quote the covered hours, the response categories on offer (low, medium, high or critical), whether support staff sit in your time zone, whether breaches attract penalties, and whether custom configurations are priced separately.
Australian managed support is priced per user, per device or by the hour. Per-user managed support runs $100 to $250 per user per month, fully managed cover starts from $200 per user per month, and ad-hoc break-fix support runs around $150 to $250 an hour.
Per-device cover is quoted at $50 to $150 per workstation per month and $150 to $500 or more per server per month. Providers tier their service levels — Essential, Professional and Enterprise are common names — and comprehensive managed service for a 20 to 150 seat business sits at $130 to $180 per user per month. Compliance scope such as ISO 27001 or the Essential Eight adds cost.
Software items include version updates, licence renewals, and the network and data upkeep behind dashboards, edge devices and connectivity. Software maintenance is charged as a percentage rather than a fee — around 18 to 22 per cent of the purchase price per year — and it buys access to a support line, bug fixes and release updates. Ask whether bug fixes are included regardless of the contract.
Spare parts and consumables cover drives, sensors, network hardware and the shelf stock held to avoid waiting on a supplier, plus replacement devices as they age.
Add internal technician time for first-line checks, cleaning, restarts and log collection, costed at a loaded hourly rate. Where the automation hands exceptions to a person, price the fallback per contact: $2.70 for retail e-commerce, $18 to $35 for SaaS and $30 to $60 for B2B support, with agent labour at 70 to 80 per cent.
Where the automation sits behind a website or booking flow, Australian website maintenance pricing gives the smallest comparable line: $1,200 to $2,000 a year for a small business, or roughly $100 to $167 a month.
Top Recurring Costs in Automation Maintenance
- Software maintenance (18–22% of purchase price/year)Recurring annual fee tied to licence renewal
- Spare parts and consumablesIncludes drives, sensors, network hardware, shelf stock
- Internal technician timeLoaded hourly rate for log collection, restarts, first-line checks
Modelling support and maintenance across the asset's life
Model the costs over the expected service life of the asset, not over the payback period. A three-year payback case and a ten-year service life are different questions, and the maintenance lines dominate the difference.
Escalate service fees at the contracted rate, or at a stated assumption where none is fixed. Escalators compound: an annual increase applied across a decade produces a materially different total from the same increase applied once.
List every major component with an expected replacement year and a cost, so the model produces lumpy capital top-ups rather than a flat average. Add a contingency line for unplanned failures, sized from the callout history of similar equipment already on site; Australian project costing commonly uses 10 to 15 per cent.
Timing belongs in the same worksheet. Managed support is invoiced monthly per user or device, while software maintenance is charged annually as a percentage of the purchase price, so the renewal date and the escalation anniversary need fixed places in the model.
Run sensitivity tests on the assumptions that move the result most: downtime frequency, callout rate, spare part price and the escalation percentage. Show the base case and a pessimistic case side by side.
The Australian Government Department of Finance publishes a Commonwealth Investments Toolkit that includes guidance on developing a business case and on financial modelling. Structuring the maintenance model along those lines keeps it consistent with how board-level and publicly funded proposals are assessed.
Converting availability into dollars
The maintenance line pays for availability, and availability is bought as response time — the difference between a contractor arriving under a contract and a contractor arriving when the queue allows. Value an avoided stoppage at contribution margin, revenue less variable cost.
Measurement and condition monitoring reduce unplanned stoppages rather than planned ones. The saving to model is the difference between reactive repair time and a scheduled intervention, plus the output lost while a contractor is on the way.
Beckhoff Automation notes that the mechanical engineering sector works constantly to optimise machine availability and minimise fluctuations in production, and that integrating high-performance measurement into control systems overcomes performance limits once considered insurmountable.
Industry benchmarks show predictive maintenance reduces overall maintenance costs by 10 to 40 per cent compared with reactive approaches. On a support contract, that range is the maintenance-side saving for buying faster response and monitoring instead of paying per breakdown.
Skills, training and the people cost of automation upkeep
ANCA describes its AIMS automation technology as replacing the need for human operators to carry out routine tasks and allowing them to be upskilled to more critical and complex work. It also frames the technology as a way for companies to combat rising costs and address the growing skill shortage.
Process Evolution's commentary on the skills shift in Australian manufacturing frames automation as a change in skills, capability and strategic thinking rather than simply the installation of robots. That shift shows up as a training line in the cost model.
Training costs more than course fees. Add the release time of operators and trades while they learn new control systems, plus the productivity dip during the transition period.
Decide deliberately between building internal capability and buying support. Relevant tests: how often the equipment faults, whether the vendor restricts access to software and diagnostics, the response time the service contract guarantees, and how quickly trained staff tend to leave.
Where skilled maintenance people are hard to recruit, the practical answer is usually a service contract with defined response times, priced as a recurring line rather than a one-off repair bill. Keep at least enough internal knowledge to describe the fault accurately when you call.
Matching support costs to the type of automation
It helps to separate adaptive systems from rule-based automation. Adaptive systems can learn and act on changing conditions, while rule-based automation follows pre-defined rules to handle repetitive tasks.
Rule-based automation — fixed sequences, scheduled jobs, form routing — needs routine servicing, spare parts and disciplined version control. Keep backed-up copies of the programs and parameter sets, and record every change, because a system that behaves unexpectedly is usually running logic someone altered.
Adaptive systems add a different set of recurring costs: data quality checks, monitoring, tuning and periodic reassessment of whether the model still performs as intended. These costs recur continuously and generally grow with the volume of data and the number of decisions taken.
Set the support estimate against what is actually being deployed. A rule-based workflow and an adaptive decision system on the same site require different skills, different contract terms and different amounts of internal attention.
Metrics that keep the numbers honest
Track maintenance cost as a share of asset value, mean time between failures, and first-time fix rate on service callouts. These three show whether the support contract is delivering availability or simply absorbing spend.
Add cost per unit produced, which ties maintenance and consumables back to output, and overall equipment effectiveness, which multiplies availability by performance by quality. APQC's guidance addresses which measures organisations should use to assess process performance.
On the support side, track cost per issue resolved rather than cost per contact: a 2.3 contact-per-issue average means the real cost per issue is 2.3 times the cost per contact, and first-contact resolution determines how many contacts each issue generates.
Review the model annually against actuals while the asset still has years of service left. Correct the escalation rate, the callout frequency, the spare parts prices and the downtime hours from real records.
Use the review to reset the contingency line and the replacement schedule. An assumption that was wrong in year two is cheap to fix at year three; the same assumption carried to the end of life inflates or understates the case past the point where anything can be changed.
Further reading: Comparing Manual and Automated Warehousing Operations: A Cost-Benefit Analysis for Retailers (opex.com).



