How to Build the Business Case for Predictive Maintenance as a Maintenance Manager

The budget conversation you are preparing for is not primarily a technical conversation. Your Plant Manager is not evaluating whether condition monitoring technology works. They are evaluating whether this specific investment is worth the risk of committing the capital, the time, and their own credibility to approving something that a maintenance manager they trust has proposed.

Your job in that conversation is to make the financial case so clearly that the decision is straightforward, and to anticipate every objection so that none of them require another meeting to resolve.

This guide covers the complete process: building the baseline from your work order history, calculating the business case, structuring the one-page presentation, and handling the three objections that will come up. Everything is built from your plant's actual data, not industry benchmarks. A case built from benchmarks gets challenged. A case built from your work order history does not.

• How Tractian Supports the Business Case

Step 1: Build Your 12-Month Downtime Baseline

Pull the following from your work order history and production data. If some fields are in different systems, pull them separately and combine.

1. Every unplanned downtime event on Tier 1 assets in the last 12 months
2. Duration of each event in hours
3. Which asset and which line
4. Production value per hour on each affected line (get this from production planning or finance if not in your system)
5. The cost of each emergency repair (parts plus labor at actual cost)
6. What the equivalent planned repair would have cost (if known; estimate if not)
7. Any OEM penalties documented for missed shipments associated with those events

Sort the list by total cost per event. The top 20% of events by cost will account for 70 to 80% of your total baseline. Those are the assets and failure modes your business case is targeting.

This data pull typically takes two to four hours. It is the most important two to four hours in the business case process. The number you surface is almost always larger than expected.

Step 2: Calculate the Full Five-Component Cost

With the data from Step 1, calculate each component:

Component 1: Production loss

Unplanned downtime hours (by line) x Production value per hour (by line) = Production loss per event

Sum across all events. This is the floor of your baseline.

Component 2: Emergency repair premium

For each emergency work order: actual repair cost minus estimated planned repair equivalent cost.

If you do not have the planned repair equivalent on record, use a ratio of 2.5 as the emergency premium factor (actual cost divided by 2.5 equals the estimated planned equivalent). This is conservative and defensible.

Sum the premium across all events. This is typically 20 to 40% of the production loss number.

Component 3: OEM penalty exposure

For JIT suppliers: any documented OEM penalties from missed shipments associated with the failure events. If penalties were not tracked, review the supply agreements for the penalty rate per hour of late delivery and calculate against the documented late deliveries from failure events.

If your plant does not operate JIT contracts, this component is zero.

Component 4: Displaced planned work cost

For each event where an emergency repair displaced a scheduled planned overhaul: estimate the cost of the deferred work plus the risk premium from running the overdue asset in subsequent production. A conservative estimate is 50% of the planned overhaul cost as the risk premium for running overdue. Sum across deferred work orders.

Component 5: Secondary damage cost

For any failure events where cascade damage occurred: the additional repair cost above the primary component repair. Damaged shafts, housings, coupling replacements, gearbox damage. Document separately from the primary repair cost.

Sum all five components. That total is your annual cost of unplanned downtime on Tier 1 assets.

Sample calculation (substitute your actual numbers):

This number is the anchor for everything that follows. Keep it in the presentation.

Step 3: Estimate the Preventable Portion

Condition-based failures, where degradation develops gradually and continuously, represent 50 to 70% of unplanned events in most discrete manufacturing environments. These are the events that continuous monitoring can detect before they reach the production floor.

Conservative year-one estimate: 20% of current unplanned events are detected and repaired before failure. This is the primary avoided cost figure.

At your per-event cost from Step 2, 20% prevention applied to the full five-component baseline gives your primary benefit figure.

Floor case for sensitivity analysis: 10% prevention. In most discrete manufacturing plants, even the floor case produces a positive return against the program cost. Present both in your business case. Showing the floor case signals that you have done rigorous financial work.

Using the sample numbers above:

• 20% prevention: $744,000 x 0.20 = $148,800 in avoided cost
• 10% floor case: $744,000 x 0.10 = $74,400 in avoided cost

Step 4: Get an Accurate Program Cost

Request a formal quote covering all cost components: hardware (sensors and gateways per Tier 1 asset), software subscription (annual), and onboarding and implementation support.

Do not estimate this number. An estimated program cost that differs from the actual quote undermines the credibility of the entire calculation. Get the actual number before the presentation.

For a typical Tier 1 asset coverage proposal targeting your five to eight highest-risk assets: ask for a line-item quote so you can present the cost with clarity.

Step 5: Calculate Net ROI and Payback

Net annual benefit (year one) = Avoided cost at 20% prevention minus Annual program cost

Payback period = Total first-year investment (hardware + first-year software + onboarding) divided by Monthly net benefit

A payback under 12 months is defensible in most capital budget processes. Under 6 months is difficult to reject under almost any budget pressure. If your payback calculation exceeds 18 months, revisit the scope: you may be covering too many assets in the first year relative to your documented risk concentration.

Using the sample numbers:

• 20% prevention avoided cost: $148,800
• Program cost (example): $72,000 per year
• Net year-one benefit: $148,800 minus $72,000 = $76,800
• Total first-year investment (including hardware): $95,000
• Monthly net benefit: $76,800 / 12 = $6,400
• Payback: $95,000 / $6,400 = approximately 15 months

If the payback period is longer than desired, focus the proposal on the three highest-cost assets only. A tighter scope with a shorter payback is a stronger initial case than a full program with a longer payback.

One page. Three numbers. No technical specifications.

The appendix can include the detailed five-component breakdown if the Plant Manager wants to review the methodology. Do not lead with it.

How to Present This to Your Plant Manager

The 90-second version:

"Last year, unplanned failures on our five highest-cost Tier 1 assets generated $[baseline] in combined production loss, emergency repair premium, and OEM penalty exposure. A condition monitoring program covering those assets costs $[program cost] annually. At 20% failure prevention in year one, we protect $[avoided cost]. Payback is [N] months. Even at 10% prevention, the program is cash-positive."

Then stop talking. Let the Plant Manager respond. The most common response is one of the three objections below, or a question about scope. Be ready for both.

If they ask about scope: "I am proposing we start with the five assets that account for 78% of our downtime cost over the last 12 months. Those are [asset list]. If the first 90 days shows at least one prevented production event, we expand to the next tier."

This conversation should not need a slide deck. One page, three numbers, and specific answers to the three objections. If it goes to a formal presentation, the one-page template above is the slide.

The Three Objections and How to Handle Them

"We already have a PM program."

Your answer: "Our PM program schedules service at fixed intervals. Three of our last five unplanned events occurred on assets that had been serviced within the prior 60 days. Those were condition-based failures that developed between service dates. Fixed intervals catch the average case. Continuous monitoring catches the degradation as it develops on each specific asset, regardless of when the last service was. Our PM program and condition monitoring are not alternatives; they address different failure modes."

Then offer to show the specific work orders. Pull them in advance. The visual of three recent failures on recently serviced assets is more persuasive than the argument alone.

"We cannot afford it right now."

Your answer: "I understand. Here is the cost of our last three unplanned events on Tier 1 assets, using the five-component formula: [event 1: $X, event 2: $Y, event 3: $Z, total: $sum]. The program cost is $[program cost] annually. We spent more than the annual program cost on those three events alone. The question is not whether we can afford the program. It is whether we can afford another year at the current event rate."

If they push back on the five-component formula being too aggressive: use only production loss and emergency repair premium. Even with the two most conservative components, the argument usually holds.

"The team will not use it."

Your answer: "The platform delivers interpreted alerts that specify the asset, the component, the failure mode, and the recommended action window. A maintenance planner creates the work order directly from the alert. No vibration analysis background required. I have reviewed sample alerts from comparable plants and the format is designed for maintenance planners, not analysts. I am confident the team can work with it, and I will own the adoption."

That last sentence matters. Taking ownership of the adoption removes the objection from the Plant Manager's risk list.