CMMS or Excel: when a maintenance management system starts paying off

Inspection dates in Excel, breakdowns reported by phone, repair history in a binder. That is what maintenance looks like in most plants with a few dozen machines, and it is nothing to be ashamed of: a spreadsheet works as long as one person who remembers everything keeps an eye on it. The question is when it stops working and what then. This post shows the signs that a maintenance management system will start paying off, the minimum scope worth starting with, and what to do in the meantime if it is still too early for a rollout.

Why Excel works in maintenance, and then suddenly does not

A spreadsheet is a good register and a bad process. It holds the list of equipment and dates, but it does not chase deadlines, does not take reports from an operator on the shop floor and does not know who did what. As long as the plant has twenty machines and one mechanic, that gap does not hurt. It hurts when equipment, shifts and people multiply: statutory inspection dates depend on memory, a breakdown from the night shift gets lost between a note and an email, and the cost of maintaining a specific machine can only be worked out from spare-part invoices. There is no moment when the spreadsheet breaks. There is a moment when it starts costing more than a system.

Six signs it is time for maintenance software

• Dates in one person's head. If the maintenance manager takes two weeks off and nobody knows what is due in that time, that is not inspection management, it is risk management.
• Breakdowns with no owner. The operator reports verbally, the foreman writes it on a note, the mechanic hears about it an hour later. Nobody knows how long the breakdown lasted or whether it has happened before.
• Repair history in a binder. When a mechanic leaves, the knowledge of what has already been replaced in that press, and why, leaves with them.
• Parts bought when the machine is already down. No minimum stock levels means downtime lasts as long as the delivery.
• An auditor or a customer asks for inspection reports. And the search through drives and mailboxes begins.
• You do not know what a specific machine costs to maintain. The decision to replace it is made by gut feeling, not numbers.

Three out of six is usually the point where a breakdown log and an inspection schedule in one system pay off faster than expected.

CMMS: the minimum scope worth starting with

The biggest rollout mistake is implementing everything at once: ten modules, ERP integration, sensors. The plant does not have the people for it, and the system ends up as another spreadsheet, only more expensive. The first version should do three things: keep an equipment register with documentation and a responsible person, compute an inspection schedule with reminders (in-house inspections, statutory checks, calibrations), and accept breakdown reports in a way that lets the operator at the machine do it in half a minute, ideally by scanning a QR code with a phone. Repair history then builds itself, because every report and every inspection leaves a trace. Spare parts, costs and a dashboard come in the second step, once the basic flow works and people actually use it.

What not to implement first

Predictive maintenance with vibration and temperature sensors. It is a different class of solution and a different order of budget, and without a solid breakdown history there is nothing to predict. ERP integration in the first version: exporting costs to a file is enough, and an API comes later, once you know which data really has to flow. And a configurable rules engine with no code changes, which in practice is configured by one person in the company while nobody else understands it.

Off-the-shelf CMMS or custom?

Off-the-shelf systems make sense when your process is standard and the team will accept their way of working. A custom system makes sense when you have specific cycles (statutory checks, legalisations, running hours), your own numbering and reports that must look the way the auditor wants, or when a per-user subscription for thirty operators with QR codes stops adding up. Do the maths honestly: our custom vs SaaS calculator compares both options over three years. We have also written at more length about when a company should move from Excel to its own system.

What to do today, before you implement anything

Two things cost nothing. First, list every piece of equipment with the date of its last inspection and the interval, and generate a year of due dates from that. Our maintenance schedule generator does it in a quarter of an hour and gives you a file for Excel or your calendar, with overdue items on top. Second, for one month record every breakdown in one place: machine, time reported, time repaired, what was replaced. After a month you will know whether your problem is dates, breakdowns or parts, and which module to start with.

Where we start

That minimum scope is what we build as a custom maintenance system: an equipment register with import from Excel, an inspection schedule with reminders, breakdown reporting from a QR code, repair history and PDF reports. No price list at this stage and no screenshots from production that do not exist yet, but a clear plan for the first version. If you recognise three of the six signs above, describe how you track inspections today in our quote calculator: you get a ballpark instantly and a reply from a human within 24 hours. Production in a spreadsheet is covered separately in our post on a simple system for a small manufacturing company.