Equipment Digitalization ROI Calculator
Enter your asset count, downtime loss and expected warning hit rate. In about 30 seconds you get payback period, first-year ROI and 3-year NPV, plus a clear view of how payback moves when the hit rate and downtime loss change. The calculation conventions match the Smart O&M Toolbox mini program exactly.
Unit prices are illustrative, not a quotation · Results are not a performance guarantee
Calculation conventions: three rules we will not relax
Many ROI spreadsheets produce a three-month payback because they treat a warning as a repair waiver and assume a 100% hit rate. Our conventions are written out below — challenge every one of them.
① Avoidable faults ≠ baseline faults
Avoidable faults = baseline faults per year × warning hit rate
The hit rate is the share of faults correctly warned and successfully avoided — not algorithm accuracy. The default is 50%; move the slider from 0 to 100% to see the effect.
② Only the difference is saved
Hours saved per event = MAX(unplanned downtime − planned repair, 0)
A warned asset still has to be shut down for repair. What improves is that an emergency breakdown becomes a scheduled maintenance window. Counting the whole unplanned duration as benefit is the most common way to inflate these numbers.
③ Payback must be divide-by-zero safe
Payback = net investment ÷ annual net benefit × 12 (net investment > 0 and annual net benefit > 0)
Net investment ≤ 0 or annual net benefit ≤ 0 → "Not determinable"
If you enter zeros or a negative return, the page will not print Infinity or a negative month count. It tells you plainly that payback cannot be determined and which input to check.
Full formulas
Net investment = sensors + gateways + installation + software licence + other − subsidy offset
Annual benefit = avoidable faults ×(downtime saved × CNY/h + repair cost) + labour + other
Annual net benefit = annual benefit − platform fee (cloud only)
3-year NPV = −net investment + first-year net ×(1+8%)⁻¹ + annual net ×(1+8%)⁻² + annual net ×(1+8%)⁻³
First-year benefit is discounted to 60% because baseline build-up and trial operation mean the hit rate is not yet at steady state; years two and three are.
Six questions we hear most about these numbers
How long does equipment digitalization (predictive maintenance) usually take to pay back?
It depends on three things: how large the loss per unplanned downtime event is, how many baseline faults occur per year, and what warning hit rate can be achieved. In practice, assets with high downtime loss (continuous process lines, kilns, chemical pump sets) and high fault frequency usually pay back in 6 to 18 months. Low-criticality auxiliary assets may exceed 24 months and are generally not the first priority. Run the calculator with your own figures, then start with the three to five assets showing the shortest payback.
Are the prices in the calculator a real quotation?
No. Every unit price is a neutral illustrative value used to demonstrate the method and orders of magnitude. It is not a quotation and does not represent any customer's actual contract price. All fields can be edited with your own figures. A formal quotation is subject to a price sheet confirmed by both parties.
Why is hours saved per event calculated as "unplanned downtime minus planned repair"?
Because an early warning is not a repair waiver. Once an asset is flagged, it still has to be shut down for planned repair. What changes is that a multi-hour emergency breakdown becomes a controlled maintenance window that can be scheduled into production. The saving is the difference between the two, not the entire unplanned downtime. Counting the full unplanned duration as benefit significantly overstates the payback speed.
What warning hit rate is reasonable to assume?
The hit rate is the share of baseline faults correctly warned and successfully avoided — not algorithm accuracy. Rotating-equipment faults (bearing, gear, imbalance, misalignment) are detected reliably, typically in the 60% to 90% range; incipient and intermittent faults are lower. This calculator defaults to 50%, which is deliberately conservative. First-year benefit is discounted to 60% to reflect baseline build-up and trial operation.
Is the calculated result a performance guarantee?
No. It is a projection from the parameters you enter, supporting investment decisions. It is not a commitment regarding energy savings, downtime duration or asset life. The closer your inputs are to reality, the more useful the projection. We recommend recalculating with three to six months of real operating data before scaling up.
Cloud deployment or on-premise deployment?
Cloud deployment charges a platform service fee per monitoring point, keeping upfront spend low and activation fast — suited to a pilot-then-scale approach. On-premise deployment is a one-off perpetual software licence, suited to organisations with hard requirements that data must not leave the plant or that the network must be isolated, but upfront investment is higher. Hardware is identical in both cases. This calculator supports switching between the two so you can compare before deciding.
Run the numbers before you buy
Turn this calculation into pilot-asset recommendations and a formal quotation. JinBond handles equipment management assessment, monitoring point selection and implementation, delivered with the DHMS Lingtong (DHMSCare) integrated product line — one project team, one point of accountability.
Submit and request a review