How CMMS software has changed

Maintenance management software has been around for thirty years, and most of the changes it has gone through haven’t been about features: they’ve been about where the record happens. That’s the story worth telling, because it explains why two systems with the same feature list produce such different results.

Stage 1: paper

The job sheet in a pad, the checks on a wall calendar, the inventory in a filing cabinet. It worked, and in many companies it still works for the day-to-day.

Its limit isn’t organization: it’s that it can’t be queried. The question “how much has it cost us to maintain this machine over three years?” has no possible answer, because answering it would mean going through three hundred sheets of paper.

Stage 2: the in-house server

The first wave of digitalization moved the filing cabinet into a database installed on a company server. A huge gain: data could be searched, filtered and totaled.

It also brought costs that weren’t in the original budget. The server, its backups, its updates, the person who maintains it, and installing the program on every workstation. And a less obvious consequence: the system only existed inside the office, so the technician kept working on paper and someone later typed in what he had written.

In other words, the lookup got digitized, not the recording. The data was still born on paper.

Stage 3: the cloud

Taking the server out of the equation changed three things at once: the infrastructure cost disappeared, per-workstation installation disappeared, and the system became accessible from anywhere with the right permissions.

That last part is what opened the door to what really matters: if you can log in from a browser, you can also log in from a phone. And if the customer can also log in, there’s no longer any need for them to call and ask how their repair is going.

Stage 4: mobile, which is where the real problem was

This is the fundamental change, and it arrived considerably later than it seems it should have.

For years “mobile app” meant a stripped-down version of the web app, which stopped working the moment there was a basement in the way. Since maintenance happens precisely in basements, warehouses, plant rooms and elevator shafts, that was effectively the same as having no app at all: the technician kept writing in a notebook.

What changes the outcome is a genuine offline mode. In GMAO Cloud’s technician app, work orders, assets and documents are stored on the device itself, and every action taken without coverage — changing a status, logging hours with a stopwatch, consuming material, filling in a checklist, collecting a signature — goes into a queue that empties itself as soon as signal comes back. If one fails, it doesn’t vanish: it stays flagged with its reason.

From there, the record stops being a memory reconstruction done at seven in the evening and becomes a measured data point. It’s the difference between believing you know what an intervention costs and actually knowing it.

A precision worth keeping: that full offline mode belongs to the technician app. Customer access installs on the device, but it doesn’t work offline.

Stage 5: the customer inside the system

The last shift is that the party receiving the service stops being an outside actor. With their own access they open issues with a photo, follow the status of their work orders, download their job reports and see their upcoming preventive visits on a calendar.

That changes how administrative work is distributed: a good share of the calls a maintenance company receives aren’t asking for anything, they’re asking how something is going. That call stops happening.

This depends on something seemingly minor: the pricing model. If the system is priced per user, giving access to hundreds of customers is a financial decision, and it usually isn’t taken. In GMAO Cloud licenses are unlimited across all three plans.

And artificial intelligence

This is the stage currently underway, and it’s worth talking about it without overstating it.

In GMAO Cloud, AI does specific, bounded things today: an assistant that answers in plain language about your assets, your plans and your history — also inside the technician app, so you can check on the go what a piece of equipment’s manual says; document reading, so that a supplier’s PDF report turns into data without typing it in; help drafting work order text; translation of your own catalogs; and aggregated answers about your figures.

Two things matter more than the list. The first is that it proposes, it doesn’t execute: these features answer and suggest, they don’t close orders or assign work. The second is that each one has its own on/off switch, and most come switched off by default. It’s covered in more detail in AI in GMAO Cloud.

What hasn’t changed with AI is where the answers come from: the data someone recorded. An assistant sitting on top of an empty history knows nothing.

What hasn’t changed

Three things, and they’re what decides whether a system works.

You have to decide what’s critical. No software prioritizes for you. The equipment that halts production or service if it fails is what deserves a plan.

Preventive maintenance has to demand attention. A task that only lives on a calendar falls through silently. What sustains it is that it’s a work order with an owner and a date, and that’s exactly as true today as it was thirty years ago; the only thing that has changed is that the system generates it now instead of a person.

Knowledge has to be written down. If what needs to be checked on a piece of equipment lives in someone’s head, it leaves with that person. Checklists by equipment family are the modern version of a very old problem.

What to look at if you’re comparing

The feature list doesn’t discriminate: every system says the same thing. What discriminates is where the record happens, what happens without coverage, how you pay as your fleet grows, and what data travels to your ERP and in which direction — the integrations catalog has the scope of each connector, which isn’t the same for all of them.

There’s a full guide on how to choose the best CMMS, and if you’d rather see it on your own equipment you can request a demo.