A small plant outgrows the maintenance whiteboard almost immediately. Not because the equipment is complicated, but because the people are stretched.
Many hats, and nobody wearing the PM one
In a start-up or a 40-person shop, resources are thin and almost everyone wears several hats. The production lead is also the safety lead. The manufacturing engineer is also the buyer and the backup technician.
In that setting, preventive maintenance belongs to everyone, which means it belongs to no one. Nobody is assigned to look at the PM schedule, so nobody does.
A computerized maintenance management system (CMMS) fixes that one problem first. It gives the shop a single place where the work lives, so the right person sees the right task at the right time.
What breaks first: the schedule and the parts
When maintenance runs on memory, two things fail first, and they fail together.
The PM schedule gets ignored. Not out of neglect. Nobody knows what the schedule is supposed to be, because it lives in a binder, a spreadsheet on someone's laptop, or the head of the person who installed the machine.
The parts aren't there when the work finally happens. On the day someone does remember a PM, they open the machine and find they don't have the filter, belt or roller it needs. Then half a day goes to figuring out what part it is, who sells it, and how to get it ordered.
That half day usually lands on a manufacturing engineer, one of the most expensive and least replaceable people in a small plant. Every hour they spend chasing a part number is an hour not spent on yield, quoting or the next process improvement. The cost of a missing PM program is rarely the PM itself. It's the expensive people pulled away to clean up after it.
The six-week breakdown
One machine had a set of feed rollers: a consumable, but one that wears slowly, so nobody thought about it. There was no PM telling anyone to check them. Eventually they wore out and the machine stopped.
The replacement rollers weren't stocked locally. The only source was overseas, and the machine sat out of service for six weeks.
The diagram below lays out both paths. The first is what happened. The second is what the same wear looks like when a PM interval and one spare set are in place.
Everything about that failure was predictable. A PM interval on the rollers and one spare set on the shelf would have turned six weeks of lost capacity into a routine swap at a planned stop.
CMMS or a better checklist? Run the cost test
For a 40-person shop, the question isn't whether a CMMS is nice to have. It's whether it costs less than the problem it removes. Count both kinds of cost:
- Direct costs. Emergency freight, premium-priced parts, overtime and outside service calls that a planned PM would have avoided.
- Opportunity costs. The hours your most expensive people spend figuring out what a machine needs, when it needs it and where to get it. Plus the output you lose while a machine sits.
If a single avoided breakdown or a few hundred engineering hours a year cover the cost, the decision is made. A checklist can work for a handful of machines and one disciplined owner. Once maintenance spans several people, shifts or sites, the checklist stops being anyone's job.
The catch is price. Much of the CMMS market is built and priced for large plants, which makes it hard to justify for a small one. Shop for something sized to your operation, not a scaled-down enterprise system.
What a technician needs on day one
Vendor demos lead with dashboards, KPIs and reports. A maintenance technician needs something much simpler: a to-do list. What is due today, on which machine, and the parts and steps to do it.
That list only works if someone has done the setup behind it. A small investment up front, entering each machine's PM tasks and intervals, is what lets the system hand the team a clean daily list and take away the noise. So the setup itself has to be easy. If building a PM schedule takes a consultant, it won't get built.
Before you buy, insist on two things:
- A simple screen for the people doing the work. Have a technician try it, not a manager. If they can't see their day's work at a glance, adoption will stall.
- Easy initial data entry. Ask the vendor to show you, live, how long it takes to add a machine, its PM schedule and its critical spares.
Walk away if the pitch is mostly about reports. Reports are only as good as the data behind them, and the data only exists if the people on the floor actually use it. Judge the system through the technician's eyes first and the manager's second.
The first-90-days mistake: "we'll build it out as we go"
The most common way a CMMS rollout fails is quiet. Loading the initial data takes real time, so it gets pushed to the back burner with a promise to fill it in as you go.
Then technicians log in and find half the equipment missing, no PM schedules and no parts lists. After a few of those visits, they stop logging in. The system never recovers its credibility.
Make a concerted push before go-live instead:
- Every machine entered, with its location and basic details.
- A PM schedule for each machine, starting from the manufacturer's recommendations.
- Critical spare parts listed for each machine, with a supplier and lead time.
- Each technician's first week of work already showing on their list.
The goal is simple: the first time someone opens it, everything they need is already there. Make it easy for the user, and they'll keep using it. That's the whole PM program.