How to justify a CMMS internally

Convincing your organization internally that a maintenance system is needed is a different problem from choosing one. The person who decides usually isn’t the one dealing with the problem, and the arguments that work on the shop floor — “we can’t keep working like this” — don’t work in a committee meeting.

This is about how to build the case with what you already have.

The starting mistake: selling efficiency

“We’ll be more efficient” convinces nobody, because it can’t be verified and everyone has heard it before.

What does work is a question that can’t be answered today. Pick one of these and raise it in the meeting:

• How much has it cost us to maintain this machine over the last three years?
• Which maintenance contract is losing money?
• Can we prove that the March review was done?

The value of the argument isn’t in the answer: it’s in the fact that there isn’t one. And that everyone in the room understands why that’s a problem.

The figures you already have without a system

You don’t need a CMMS to gather the material for the case. With an afternoon and last year’s invoices, you can pull together these four.

What was spent on urgent corrective work. Invoices for unscheduled interventions. It’s the figure that impresses the most because it’s almost always bigger than assumed.

Return visits. How many times a site was revisited for lack of materials or information. If nobody’s counting, ask the technicians: they know pretty precisely.

Warranty repairs. Check a handful of invoices against the equipment’s purchase date. It shows up with an uncomfortable frequency.

Administrative hours. How much time goes into writing up reports, chasing paperwork and answering calls that just ask how something’s going.

Those four figures are yours, verifiable, and no vendor put them there. They’re worth more than any percentage from a brochure.

The objections that will come up

“We already have a spreadsheet that works.” It’s not false, and it’s better not to argue against it head-on. The answer is the list of what the spreadsheet can’t do: it doesn’t flag when a review is missed, it doesn’t log in the field, and it doesn’t work as proof because a cell can be changed without leaving a trace.

“It’s just another program nobody’s going to use.” The most legitimate objection. The answer isn’t to promise it will be used: it’s to propose a scoped trial with a few assets and a few technicians over a few weeks. If it doesn’t get used, little will have been lost.

“We don’t have time to roll it out.” True, and that’s exactly why you don’t start with the full inventory. You start with critical assets, which are usually fewer than fifty.

“It’s outsourced, we don’t need it.” Then the question is whether you can verify that what you’re paying for is being done. The annual plan executed report answers exactly that, and to have it you need to register the contractors.

“What if we switch systems in two years?” Good question, and the answer is to demand in writing how the data comes out. If there’s no full export or API, the risk is real.

How to frame the trial

This is what turns an argument into a reversible decision, which is why it works.

Scope: the critical assets of one area, one line, or one contract. No more.

Duration: a few weeks, enough for real preventive maintenance to be generated and closed.

What to check at the end: whether orders were closed in the field with measured times, whether technicians kept using it in week three, and whether there’s a report with data that didn’t exist before. For that report to have something to pull from, what needs watching during the trial is that work orders get closed with an author, a date and measured time, not with a “done” added after the fact.

That third point is the definitive argument: showing a figure the company didn’t have before.

What to promise and what not to

It pays to be conservative here, because the project’s credibility is on the line.

You can promise: that the preventive plan will stop depending on someone remembering; that there will be a record with date and author for every intervention; that you’ll know how much it costs to maintain each piece of equipment; and that there will be fewer client calls asking how something’s going.

You can’t promise: a savings percentage. That figure doesn’t exist, and quoting one from a brochure is the fastest way to lose credibility when someone asks you to justify it six months later.

Who needs to back it

Two people, in this order.

A technician. If the field team sees it taking work off their plate — the equipment’s history on their phone, not going back for a part, not writing up paper reports — the system feeds itself. Without that, no amount of management support will save it.

Someone who can decide. They don’t need to be an IT person: they need to know the operation and be able to settle configuration questions without calling a meeting.

How to pitch it depending on who’s deciding

The same project gets defended differently depending on who you’re talking to, and it’s worth preparing all three versions.

To management, the argument is about control and risk: knowing how much each asset costs, being able to defend the budget with a real figure instead of an extrapolation, and being able to prove what was done if a claim or an inspection comes up.

To production or operations, it’s about availability: fewer unplanned stoppages, and the ones that do happen resolved faster because the technician arrives already knowing what was done last time.

To the technical team, it’s about daily work: not having to call the office, not going back for a part, not writing up paper reports in the afternoon, and what they log actually being useful for something.

All three are true at the same time. The mistake is bringing the management argument to the shop floor, or the other way around.

The cost of waiting

The argument that carries the most weight and gets used the least: the history you’re not building can’t be recovered later.

Today’s orders can still be logged tomorrow with some effort; what happened last year, if it wasn’t written down, doesn’t exist. Every month that passes is a month of data you’ll never have when deciding whether to repair or replace a piece of equipment.

If you want material for the meeting — seeing the system on your own equipment — you can request a demo.