Guide: what a CMMS solves, by problem

We’ve written a fair amount about what a maintenance system solves, and the material is scattered. This is the guide that sorts it by problem, so you can go straight to what affects you.

If you’re not sure where to start, the twelve-question test points you there in five minutes.

Day-to-day problems

The ones you feel this week: notifications that get lost, work with no owner, site visits you have to repeat, material that never shows up, hours logged from memory.

These are covered in problems a CMMS solves, part 1, with twelve concrete situations and what solves each one.

Underlying problems

The ones that take longer to hurt and cost more: not knowing what each piece of equipment costs, not knowing which contract is profitable, knowledge that lives in two people’s heads, not being able to prove what was done.

In part 2 and, in more detail on the whole picture, in the gaps a CMMS solves.

If the problem is that the plan isn’t followed

Reviews that slip past without anyone noticing, preventive maintenance that always gives way to urgent work.

Start with how to set up a preventive plan, continue with the three types of preventive maintenance —by time, by counter, and by condition— and look at how one gets executed, which is where half the value gets lost.

If the problem is cost

Not knowing how much it costs to maintain a piece of equipment, or whether a contract makes money.

Cost control in maintenance explains how the figure is built, and spare parts management covers the materials side, which is where most of it leaks away unseen.

If the problem is paperwork

Documentation that never turns up, certificates that expire without anyone noticing.

Digitizing documentation and document management in a CMMS.

If the problem is proving it

Inspections, claims, client audits.

Legal maintenance: how it’s proven and documenting the work, which explains what counts as a valid record.

If the problem is the team

That nobody uses the system, that the data isn’t reliable.

The human factor in rollout is the one that matters most on this whole list, because without it nothing else happens.

If the problem is time

That there aren’t enough hours in the day.

The technician’s time is the scarce resource and planning the week.

If you’re looking to choose

How to choose the best CMMS for the criteria, looking for a CMMS program for the process, and do you need a CMMS? to know if it’s the right moment.

And if there’s an ERP in the mix, integrating a CMMS with the ERP.

If you’re looking for your sector

There are dedicated articles on industry, retail, hospitality, healthcare, buildings, fleets, and third-party maintenance, among others. They’re all on the blog, with a tag filter.

The concepts that repeat across all of them

There are half a dozen ideas that keep coming back, and understanding them saves you a lot of reading.

The cascade. Almost everything is configured by equipment family, not equipment by equipment: the checklist is looked up on the asset, then on its model, then on its subfamily, then on its family. With two hundred identical units, that’s the difference between an afternoon and several weeks.

Values, not checkboxes. A checklist that logs numbers turns a round into a time series, and a time series shows a trend. A checklist of ticks only proves someone walked past.

The record made in the field. If work gets logged at the end of the day, the data exists but isn’t reliable: hours skew downward and readings get rounded. That’s why offline mode isn’t a convenience but a requirement.

Closing the loop. What gets detected has to turn into work or into an explicit decision to do nothing. If it’s logged and nothing happens, people stop logging it.

Cost per asset. It’s the figure that drives investment decisions, and the one that can’t be reconstructed after the fact.

Recording and proving, not certifying. No software guarantees compliance with a standard. What it does is leave proof of what was done.

The four articles I’d read first

If you don’t want to go through the whole guide, these four cover 80% of what you need to know before deciding anything.

The twelve-question test, to find out if your case calls for it and what your specific gaps are.

How to choose the best CMMS, because the criteria that really separate one system from another aren’t on any product sheet: how pricing works as your team grows, whether technicians will actually use the app, what happens to old versions, and how you get your data out.

The human factor, which is what most determines whether the project works, and what gets looked at least when comparing options.

The first four weeks, to avoid the most common mistake: starting with the full inventory and wearing the team out before seeing a single result.

How the rest is organized

The articles follow three formats. Problem articles, which start from a specific situation. Feature articles, which explain how a piece of the system works —work orders, assets, warehouse, reports—. And sector articles, which cover what changes for each type of facility.

They’re all on the blog, with search and tag filtering.

What no article is going to fix

Worth closing with this. A system doesn’t fix a process that doesn’t exist: if today nobody decides who handles what and with what priority, it will just log the same disorder with more precision.

Nor does it supply technical judgment —how often to inspect something is set by the manufacturer, the standard, or experience— or guarantee compliance with any regulation.

Where to start if you’re not going to read anything else

Two things, and neither depends on choosing a tool.

Write the list of your critical assets: the ones that stop production or service if they fail, and the ones with a regulatory obligation behind them. Usually fewer than fifty.

And for each one, what gets done to it and how often. Even if today that only lives in someone’s head.

That’s the work that takes the longest in any rollout, holds equally true regardless of the system, and if you finish it and discover you had everything under control, you’ll have learned something too.

If you’d rather skip the reading and see it on your own equipment, you can request a demo.