CMMS stands for computerised maintenance management system. Behind the acronym the idea is plain: put in one place what currently lives in notebooks, on a whiteboard, and in three spreadsheets only one person knows how to open.
In practice a CMMS holds four things together.
The four objects
Equipment. Every machine with its model, serial number, location, department and criticality. Nothing else works without it — a job has to attach to something.
Requests and work orders. These are two separate records, deliberately. A request is what somebody saw. A work order is what the team decided to do about it. Collapsing them into one is how you lose track of everything that was reported and never actioned.
Preventive plans. Triggered by a date or by a meter reading, writing the work order ahead of time instead of waiting for the breakdown.
Stock. Spare parts tied to the jobs that consume them, so levels fall on their own when a technician logs a part.
Everything else — reports, history, cost — is not entered separately. It is a by-product of those four.
What a CMMS does not do
It does not replace a technician who knows the machine, and it does not infer anything. A CMMS only knows what it is told: if nobody logs the fault, the fault does not exist as far as the system is concerned.
It also does not predict failures. The word comes up constantly in this industry's marketing, but prediction means sensor-fed models, not management software. A CMMS tells you what happened and what is scheduled — not what is about to break.
When it starts to pay
Below a handful of machines and a single technician, a spreadsheet is honestly fine. The tipping point is when any of these becomes true:
- More than one person needs to read and edit the same history.
- Somebody asks what was done to a machine eight months ago and nobody can answer inside an hour.
- Preventive work exists on paper but is the first thing dropped when something urgent lands.
- You discover a part is out of stock at the moment the technician reaches for it.
- The knowledge leaves with the person: when they are on holiday, so is the history.
That last one is the most expensive, and the hardest to see coming.
The real obstacle is not the software
Most CMMS rollouts fail for one reason: the technicians do not use it. A tool that wants an account, a password and six screens before you can report a leak will not be used standing at the machine. It gets filled in on Friday afternoon, from memory, roughly — or not at all.
Which is why the entry point matters more than the feature list. In MainteNeat, reporting starts at the machine: scan the QR code stuck to the equipment, say how bad it is, add a photo, send. Half a minute, no account. The equipment is already attached, because the code identifies it.
The manager receives the request with the machine named, approves or refuses it, and their name stays on the decision. Approving it writes the work order with the safety steps already in place.
Where to start
Do not start with preventive maintenance. Start with the equipment list: name the machines, put the codes on them, and let corrective requests run for a few weeks. You will then know which machines actually cost you time — and it is that list, rather than an instinct, that should decide your first preventive plans.
Once the history exists, the reports arrive with no extra effort: they are calculated from work that has already been logged.