RCM Guide
Build a Reliability Funding Case

Get your reliability program funded by using the language finance understands

You see the failures. Finance sees the budget. Build the connection: one plant problem, a cost you can explain, and a practical next step worth considering.

From the plant floor to the budget meeting

A fundable first step may be closer than you think.

We know the frustration from firsthand plant maintenance and reliability work. The same asset fails again. The crew works overtime to recover. You can see why the improvement matters, but the funding request still comes back as “not this year.”

When Maintenance is viewed mainly as an expensive cost center, trimming its budget can look like a sensible saving. The repair invoices are easy to see. The production losses, extra recovery shifts and capacity at risk may sit elsewhere in the business. Reducing department spend does not necessarily reduce the plant’s total cost.

You do not have to win funding for an entire reliability program at once. A smaller, well-supported request can give Finance a clearer decision: what one problem costs, what a bounded improvement would cost, and how you will check whether it worked.

Why the disconnect happens

  1. The request describes work; the decision is about business value. “We need condition monitoring” names a method. Finance also needs to know which loss it could reduce, by how much, and why that use of money beats the alternatives.
  2. The bill and the benefit land in different places. Maintenance may pay for the program while Operations gets more usable production time. Bring the benefit owner into the case so the whole plant’s economics are visible.
  3. The spend is known; the return still needs evidence. A strong technical expectation is a starting point. Failure records, realistic unit values, a conservative range and a named owner make the estimate easier to evaluate.

The way through is a shared set of facts and assumptions. Ask Finance what decision rules it uses before polishing the ROI: its preferred template, payback horizon, discount rate and approval process. A useful case can still be declined because of cash, timing or competing priorities; the aim is an informed decision rather than an approval promise.

A practical path

Build the case in five clear steps.

Start where you are. The tools are free to use, with no email or account required. Use one named scope and one documented data period throughout.

  1. Step 1 · Choose

    Start with one recurring problem.

    Choose an asset, line or failure mode with a business consequence you can describe. Gather the work orders or downtime log and record how many months they cover.

    Leave with: a bounded problem, its evidence and a clear reason to act.

    Choose Your First Problem
  2. Step 2 · Cost

    Put a credible cost on the downtime.

    Use your plant’s production rate, unit value after variable costs and recovery assumptions. Separate physical product loss from output never produced. A short observation period can be annualized, with its limitations visible.

    Leave with: observed and annualized costs, plus a PDF, Word or Excel report to review with Finance.

    Use the Downtime Cost Calculator
  3. Step 3 · Compare

    Compare the current loss with the proposed spend.

    Test realistic reductions against upfront and recurring costs. Show low, base and high cases, payback and present value. Check whether you can actually use the capacity recovered; avoided downtime is not automatically cash savings.

    Leave with: a range, the assumptions behind it, and the conditions under which the proposal makes sense.

    Compare the Options
  4. Step 4 · Write

    Make one clear funding request.

    State the problem, evidence, options, cost, expected benefit range, implementation plan and decision you need. Name the owner of each benefit. Use the plant’s own capital or operating-budget format when required.

    Leave with: a concise memo a sponsor can take into a budget conversation.

    Use the Business-Case Template
  5. Step 5 · Agree and measure

    Ask for a bounded next step.

    Where appropriate, propose a small pilot with a spending limit, named owner, review date and measurable success criteria. Agree what would justify expanding it, changing it or stopping it.

    Leave with: a specific decision and a plan to check the result, rather than an open-ended program request.

    Prepare the Finance Conversation

Keep the numbers consistent: the tools do not transfer your inputs automatically. Carry your report or notes between them, keep the same scope and time basis, and count each cost only once. Do not add product or repair costs again if you already included them in an all-in downtime rate.

Choose the right tool

What each Funding menu item is for.

This page is the overview. The other items help you answer a particular question; you can return here at any point.

Downtime Priorities Self-Check
Which problem should we start with? Five questions give qualitative guidance about a useful next step. This does not calculate a dollar return.
Downtime Cost Calculator
What does this downtime cost us? Build a plant-specific estimate from your scope, records, production economics and recovery assumptions. Export or optionally email a report.
RCM ROI & Risk Calculator
Does the proposed improvement justify its cost? Compare expected losses and program costs, with ranges, payback and NPV under your assumptions.
Risk Quantification Method
How is the estimate built? Read the frequency-times-consequence method, uncertainty treatment and limitations. Use it when Finance wants to understand the working.
Business-Case Template
How do we present the request? Organize the scope, assumptions, alternatives, economics and requested decision into a written case.

Give Finance a decision it can evaluate.

Bring Maintenance, Operations and Finance into the same conversation early. Before asking for a large commitment, agree on:

  • The baseline: which failures and costs count, what period they cover, and where records are incomplete.
  • The business effect: where a benefit would land, who owns it, and whether it is cash avoided, capacity recovered or risk reduced.
  • The ask: the scope, spending limit, implementation cost, decision owner and review date.
  • The test: what will be measured, what success looks like, and what happens if the improvement falls short.

Keep safety and regulatory duties on their own required decision paths. A weak ROI estimate does not remove a safety obligation, and this guide does not establish compliance.

Want an engineer to help build the case?

Our $3,000 remote business-case pilot develops the assumptions and a funding memo for one agreed reliability pilot. We review your available records and scope before accepting the work. You can use all the free tools without buying this service.

Get Help Building Your Funding Case

Why maintenance funding requests stall

Same program. Different ledger.

Maintenance pays for a reliability program, but most of the payoff shows up somewhere else. Judge it on the wrong ledger and a good investment looks like a cost increase.

Waterfall chart: who pays for a reliability program and who benefits $0 WHAT THE MAINTENANCE BUDGET SEES Looks like a cost increase.
1

Figures from the fictional Program Assessment sample (PA-2027-001): year 3 at the expected run rate. Your split will differ. We build it from your general ledger and downtime log, and the controller validates it.

The fictional example in plain text

Annual program cost: $236,000. Benefit in maintenance: $65,784. Net maintenance budget effect: −$170,216. Benefit in production margin: $365,877. Net plant benefit: $195,661. Figures describe year 3 at the expected run rate of fictional sample PA-2027-001.