Asset Performance Management projects can fail.

Not with a bang, though. Nobody switches the system off and calls a post-mortem. They just quietly fade.

The dashboards are still there. The licence still renews. The sensors still send their data somewhere. But the maintenance team is still firefighting, the same pumps are still failing, and when the finance director asks what the return on investment was, nobody has a straight answer.

If you’ve been in this industry for any length of time, and been involved in CMMS, EAM, ERP, APM or any industrial software projects, you’ve probably seen it happen.

Pretending the problem doesn’t exist helps nobody, least of all the people being asked to sign off the next investment.

So let’s look at why it happens, and what you can do to be on the right side of the statistics.

What do the numbers actually say?

Here’s the first uncomfortable truth: there is no reliable, published “software project failure rate”.

You’ll see plenty of confident percentages on vendor websites. Trace most of them back and they lead nowhere, or to something much broader than APM. So rather than invent one, let’s look at what credible research says about industrial software and digital projects more widely.

And the story has changed in the last few years.

Getting out of the pilot is no longer the main problem. Back in 2019, the World Economic Forum and McKinsey reported that more than 70% of industrial companies were stuck in pilot purgatory. (World Economic Forum) Fast forward to 2026, and Rockwell Automation’s survey of more than 1,500 manufacturers found only 18% still in pilot mode, with 59% actively using smart manufacturing technology in day-to-day operations. (Rockwell Automation)

That’s real progress. But here’s the catch.

Deployed doesn’t mean delivering. The same Rockwell study found that only 43% of the data manufacturers collect is being used effectively. And in MaintainX’s 2026 survey of more than 2,200 maintenance and operations leaders, nearly eight in ten said their unplanned downtime had stayed the same or got worse over the past year. (MaintainX)

Proactive in theory, reactive in practice. The same survey found 64% of leaders say they run a preventive maintenance programme, yet half of teams spend less than 40% of their time on planned work. The systems and the plans exist. The way the work actually gets done hasn’t changed.

APM specifically is still a work in progress. ARC Advisory Group surveyed industrial leaders on their APM journeys. Fewer than a quarter said their APM strategy had actually been implemented, and around 40% were still developing one. Asked what gets in the way, almost six in ten pointed to data management and almost half to the new work processes APM requires. (ARC Advisory Group)

Notice something?

The software is rarely the problem.

Why do APM Projects fail?

Just like failure modes on an asset, projects have their own failure modes and causes. Here are the five we see most often.

1. Software first, strategy second

This is the big one.

A business buys an APM platform, connects it to everything it can find, and waits for the insights to roll in. But nobody has decided which assets matter most, how they fail, or what the right maintenance response is.

The result? A very expensive system managing and monitoring the wrong things.

APM facilitates and sits on top of a reliability strategy. It doesn’t replace one. If you haven’t done the criticality assessment and the FMECA work, the technology has nothing to anchor to. It’s worth noting that in an earlier ARC Advisory Group APM benchmarking study, only around a third of respondents felt their reliability-centred maintenance was working well. (ARC Advisory Group, via AspenTech) That foundation is often shakier than people think.

2. Weak data foundations

APM runs on data. Poor data in, poor decisions out.

Inconsistent failure codes. Work orders closed with “fixed” in the comments box. Asset registers that haven’t been updated since the plant was commissioned. Process data in one system, maintenance history in another, and nobody quite sure which version is right.

It’s no coincidence that data management was the number one challenge in the ARC survey. Fix the data input, or at least know where its gaps are, before you ask an algorithm to make sense of it.

3. Insights that go nowhere

An alert that doesn’t become a work order is just noise.

The system did its job. The process around it didn’t.

If APM isn’t wired into how work is planned, scheduled and executed, it will never change what happens on the shop floor. And if nothing changes on the shop floor, nothing changes on the balance sheet.

4. No baseline, no ROI

Nodding your head at this one?

If you didn’t measure unplanned downtime, maintenance cost and risk exposure before the project, how will you prove the improvement afterwards? You can’t. And a project that can’t prove its value is first in line when budgets get cut.

This is usually the honest answer to the question “what’s the overall ROI of APM?” Often, the value was there. Nobody set up the means to show it.

5. No owner, no skills

Somebody or some group has to own it.

Not IT. Not the vendor. Someone in the business who understands reliability, is accountable for the outcomes, and has the time to actually do it.

The skills gap in our industry is real and growing. An APM system without a reliability engineer behind it is like a condition monitoring report that nobody reads. Technically present. Practically useless.

The data backs this up. In MaintainX’s 2026 survey, 36% of maintenance leaders pointed to labour shortages as a reason for increased downtime, and 28% blamed a lack of the necessary skills on the team.

Reducing the chances of failure

The good news is that none of this is inevitable. Here’s how to stack the odds in your favour.

Start with critical assets, not all assets

Run a criticality assessment first. Then focus APM where failure actually hurts: safety, environment, production and cost. A handful of critical assets done well beats a whole site done badly.

Define success as a business outcome

“Go-live” is not success.

That is not the success you are looking for. Set targets the business cares about: fewer unplanned stops on critical equipment, lower reactive maintenance spend, reduced stockouts, reduced risk exposure. Then measure your baseline before you start.

Close the loop into work management

Every insight should have a route to action. Agree up front how project actions and alerts become notifications and work orders, who reviews them, and how the outcome feeds back into the strategy. If the loop isn’t closed, the value leaks out.

Phase it, and plan the scale-up from day one

Pilots are useful. Pilots that never end are not.

Design the pilot as the first phase of a rollout, not a standalone demonstration. Decide in advance what results will trigger the next phase and make sure the people and budget for it exist.

Get executive buy-in, and keep it

Without senior backing, any project will slowly fall through the cracks. Leaders need to support it publicly and privately, and keep supporting it after the launch photo has been taken.

Invest in people

Train the people who will use it. Give someone clear ownership. The right reliability engineers and technicians are the bedrock of a successful APM implementation.

Get them, develop them, and make sure you keep them.

Keep a risk register

Finally, treat the project like an asset. Identify what could go wrong, rate it, and manage it actively. The bumps in the road will come. Spot them early and they stay bumps

Where ProAIM fits

This is exactly why we built our platform the way we did: strategy first, advanced technology second.

ProAIM starts with the reliability groundwork that most APM projects skip, including master data, criticality analysis, FMECA, maintenance strategy development, spares & BOMs, so that monitoring and analytics are pointed at the assets and failure modes that genuinely matter. When something does go wrong, root cause analysis feeds the lessons back into the strategy.

That’s how you get out of pilot purgatory. Not with more dashboards, but with a clear line from strategy, to insight, to action, to measurable results.

If you’re planning an APM project, or quietly wondering why the last one didn’t deliver, let’s talk.

Make it pay back.