RCM Guide
Get funding

RCM ROI and risk calculator

Expected annual loss, avoided loss, payback and NPV from your inputs. Free to use in the browser. Not a guarantee of savings.

Estimates from your inputs. Not a guarantee of savings. This calculator runs in your browser. Calculator inputs stay in your browser and are not included in the follow-up request form. It is not financial, insurance, or legal advice. Starting values below are clearly labeled illustrative examples — replace them with your plant’s numbers.

Downtime economics

These fields build a downtime cost per hour from contribution margin, not from gross revenue. If you already have a figure finance accepts, use the override at the bottom of this panel instead.

Profit on one unit of output you cannot recover, not selling price or gross revenue. Using revenue here would double-count costs that are still incurred.
How many units that constrained line would have made in one hour of downtime.
Illustrative starting value: 100%. Use 100% if lost output cannot be made up later. Use a lower share if some production is recoverable on overtime or later shifts. Only the unavoidable share belongs in downtime cost.
People who are still paid but cannot work while the asset is down.
Hourly cost for one idle person, including typical burdens if you use them at your plant.
A premium added once per event, such as overtime to recover production. This is not the same as the hourly downtime cost.
Illustrative starting value: $1,500 per hour, from the synthetic example — not a plant-specific default. If this field has a number, it is used instead of the margin ingredients above. Clear it to build $/hour from those ingredients.

How to build dollars per hour →

Program cost and assumptions

What you would spend once to put the program in place. Leave 0 if you are only looking at annual loss, not payback or NPV.
Yearly cost to keep the program running. Net annual benefit is gross avoided loss minus this amount.
Illustrative starting value: 10% per year. Replace it with your plant’s rate. Used only for net present value.
Illustrative starting value: 5 years. How many years of cash flows to include in NPV (1–100). Payback uses a steady-year ratio, not this horizon.
Illustrative starting value: 70%. Enter a value from 0 to 100. This is your assumption about whether the avoided-loss benefits materialize, not the event frequency (n / T) and not a validated probability of failure. Expected NPV weights only those benefits; upfront and recurring program costs stay certain. The binary model is not statistical validation.

Reduction assumptions (not promises)

These percentages are assumptions you supply, not measured results. Illustrative starting values — frequency 10 / 25 / 40 percent and severity 10 / 20 / 40 percent — are examples only. Change them. “Frequency” here means how often events occur, not a failure probability.

How much you assume annual event rate would fall in a conservative case.
How much you assume the cost of one event would fall in a conservative case.

Failure modes (up to 20)

For each mode, enter how many times it happened (n) and over how many years you counted (T). Event frequency is n / T events per year. Also enter downtime hours per event and repair or other fixed cost per event (dollars). A 90 percent Poisson interval is shown on the rate. The first row is an illustrative synthetic example; replace it with your history.

Failure mode inputs: name, event count n, observation years T, downtime hours per event, and fixed repair or event cost
Failure mode nameEvent count (n)Observation period (years T)Downtime hours per eventRepair or fixed cost per event ($)

One mode per line. The example row “Seal failure,4,2,6,3000” is synthetic.

Packaged offer

A $3,000 remote funding-case package for one reliability pilot

When you want the memo built with you, the published package is $3,000, remote, for one reliability pilot. It uses failure history and cost data you supply. The write-up states low, base, and high expected-loss assumptions, and it includes a written memo plus one review meeting.

  • Data readiness. You need adequate data: failure counts or work-order history for the assets in scope, and a downtime cost you can defend (or the ingredients to build one). If the file is too thin, that is said before the work is accepted — a case will not be invented from a gap.
  • What is not included. Extensive investigation and implementation are quoted separately.
  • Independent conclusion. The memo may conclude that the pilot is not worth funding.
  • No performance or approval guarantee. This work does not guarantee uptime, OEE improvement, or budget approval.

You can also request a 20–30-minute fit conversation first. That is a fit conversation, not a free analysis.

Ask about the $3,000 funding-case package

Send a request through the inquiry form or contact Apex by email.

Ask about the $3,000 funding caseOr email .

Formulas and limitations are written in full on the method page. Full scope is also on the reliability business case page. If you still need a ranked view of plant risk first, start with the downtime priorities self-check or a focused one-day assessment ($2,400 plus agreed travel costs).