The Whiteboard, the Spreadsheet and the Fitter Who Remembers
Many plants run maintenance on three systems: a whiteboard of jobs, a spreadsheet of scheduled tasks that was last fully up to date some time ago, and the memory of an experienced tradesperson who knows when every gearbox was last changed. It works, until the plant grows, an auditor asks for records or that tradesperson retires.
A computerised maintenance management system, or CMMS, is meant to replace all three. This guide explains what a CMMS does, how to tell whether your plant needs one, what to look for when choosing and why so many implementations disappoint.
What a CMMS Is
A CMMS is software that holds a plant’s maintenance information in one place and manages the work that flows from it. Whatever the product, the core functions are the same.
An asset register. A structured list of every piece of equipment, usually arranged as a hierarchy from site to line to machine to component.
Work orders. A record of every job: what was requested, who did it, how long it took, what parts were used and what was found.
Preventive maintenance scheduling. Recurring tasks generated automatically by calendar date, by running hours or by production count.
Spare parts. Stock levels, locations, reorder points and which parts fit which machines.
History. Everything that has been done to each asset, searchable.
Reporting. Backlog, compliance with the schedule, cost by asset and failure trends.
Larger systems are sold as enterprise asset management and add purchasing, contractor management and financial integration. For a single manufacturing site the distinction matters less than whether the system is actually used.
Seven Signs Your Plant Needs One
Scheduled maintenance is missed and nobody notices until something fails. The same fault recurs and there is no record of what was done last time. Spare parts are bought in a hurry because nobody knew the shelf was empty. An audit asks for evidence that a task was done and producing it takes a day. Maintenance cost cannot be attributed to a line or a machine. Knowledge of the plant sits with one or two people. Work requests arrive by phone, radio, email and conversation, and some are lost.
One or two of these can be managed with discipline and a good spreadsheet. Four or more suggest the plant has outgrown its tools.
When a Spreadsheet Is Enough
A small site with a few dozen assets, a maintenance team of two or three and a stable schedule can run well on a carefully kept spreadsheet. The test is not size alone. It is whether work is being done on time, whether history can be found when needed and whether the system survives a change of personnel. If the answer to all three is yes, software will add cost without adding much.
What a CMMS Makes Possible
The first benefit is that scheduled work stops being forgotten. The second is more valuable and takes longer: decisions based on history. With a year or two of reliable work orders you can see which machines consume the most labour, which failures recur, which preventive tasks never find anything and could be done less often, and which assets are costing more to keep than to replace.
It also changes the conversation with production and finance. A request for a shutdown day or a capital replacement backed by data is harder to refuse than one backed by experience alone.
Why So Many Implementations Disappoint
Buying the software is the easy part. Most disappointment comes from what happens next.
Poor asset data. The register is built from an old equipment list that does not match the floor. Work orders are raised against the wrong machine and the history is useless.
Too many scheduled tasks. Every recommendation from every manual is loaded on day one. The system generates more work than the team can do, compliance collapses and people stop trusting the schedule.
Work orders with no information. A job closed with the single word fixed tells the next person nothing. The value of the system is in the detail recorded at close out.
Tradespeople do not use it. If entering a job takes longer than doing it, it will not be entered. Systems that work on a phone or tablet at the machine are used. Systems that need a desktop in the office are not.
No owner. Someone has to keep the data clean, adjust schedules and chase open work. In most successful sites that is a maintenance planner, even a part time one.
Reports nobody reads. A system that produces data but changes no decisions is an expensive diary.
Choosing a System
The market is crowded and the products are more alike than their marketing suggests. For a manufacturing plant the following matter most.
Ease of use on the floor. Can a tradesperson open, update and close a work order on a mobile device in under a minute? Test this with your own people before deciding.
Simple work requests. Can an operator report a fault without training, ideally by scanning a code on the machine?
Flexible scheduling. Does it handle tasks based on running hours or production counts as well as dates?
Spare parts linked to assets. Can you see what parts a machine needs and whether they are in stock?
Useful standard reports. Schedule compliance, backlog, and the split between planned and reactive work, without custom development.
Integration. Can it take running hours or fault signals from your control systems, and exchange data with purchasing or finance, if you want that later?
Getting your data out. If you change systems in five years, can you export your history?
Resist buying for features you might use one day. The best system is the one your team will keep up to date.
A Sensible Order for Implementation
Start with the asset register, and build it by walking the plant, not from an old list. Agree a naming and numbering convention and label the equipment to match. Load a small number of critical preventive tasks, the ones you are confident are worth doing, and add more later as the team shows it can keep up. Get every job, including breakdowns, recorded as a work order from day one. Define what must be written at close out: what was found, what was done, what parts were used. Add spare parts once work orders are flowing. Introduce reports only when there is enough data to mean something.
Expect the first six months to be about habits and the real payoff to come in the second year.
The Measures Worth Watching
Schedule compliance. The share of preventive tasks completed on time. If it is low, there are too many tasks or too few people.
Planned versus reactive work. The proportion of labour hours spent on planned jobs against breakdowns. Movement towards planned work is the clearest sign that maintenance is getting ahead.
Backlog. How many weeks of work are waiting. Some backlog is healthy. A growing one is a warning.
Repeat failures. The same fault on the same asset, which a CMMS makes visible for the first time.
Where BevTech Fits
BevTech is a family owned engineering business in Richlands, Brisbane, with more than 25 years in beverage and FMCG manufacturing. We are not a software supplier. We do the work a maintenance system depends on and generates: electrical condition audits that establish what equipment a site has and what state it is in, as-built drawings that match the plant, planned maintenance and shutdown crews to clear the schedule, and 24/7 breakdown support for the faults that still occur. When we attend a job we record what we found and what we did, so that your history stays complete whichever system holds it.
If your maintenance schedule is asking more than your team can deliver, use the contact form at bevtech.com.au/contact.
