A crusher that is scheduled for ten hours and produces for seven has lost three hours somewhere. Ask where, and the answers are usually general: power cuts, a belt problem, waiting for the loader. Without a record, the owner cannot tell which problem costs the most, so money gets spent on whatever was loudest last week.
A downtime log turns those general answers into numbers. This post explains what to record, the reason codes to use and the weekly review that turns the log into decisions.
Three numbers for every shift
- Scheduled hours: the hours the plant was meant to run.
- Running hours: from the hour meter on the primary crusher or main motor.
- Lost hours: scheduled less running, every minute of it explained by a stop entry.
Running hours divided by scheduled hours is your availability for the shift. Track it weekly. It is the simplest single measure of how well the plant is being run.
What to record for every stop
- Start time and end time of the stop.
- Which machine or section stopped: primary, secondary, VSI, screen, conveyor, generator.
- Reason code from a short fixed list.
- A one-line note in the supervisor’s words.
- Whether parts were used, with the store issue slip number.
Record stops of more than a few minutes. Set a threshold that suits your plant, such as ten or fifteen minutes, and stick to it.
Reason codes that work
Keep the list short enough that a supervisor can choose in seconds. A list of a dozen codes is usually enough:
| Group | Reason codes |
|---|---|
| Power | Grid power cut, voltage problem, generator fault |
| Mechanical | Crusher jam or choke, bearing or drive fault, belt tear or slip, screen mesh change |
| Electrical | Motor trip, starter or panel fault |
| Feed | No feed from quarry, loader or excavator not available |
| Planned | Wear part change, scheduled maintenance, shift change |
| Other | Weather, stack full, labour shortage |
“Stack full” deserves its own code. If the plant stops because finished stock has nowhere to go, the problem is in sales or yard space, not in the machines.
The weekly review
Once a week, sort the lost hours by reason code and look at the top three. In most plants, two or three causes account for most of the lost time. That is where effort should go.
- Frequent short stops on one conveyor suggest an alignment or skirt problem worth an hour of a fitter’s time.
- Long feed stops suggest the quarry or the loader is the bottleneck, not the crusher.
- Repeated chokes may point to wet feed, a closed setting or worn liners. Our post on wear part tracking shows how to check liner life.
- Power cuts at fixed times may justify changing shift timings or a discussion with the electricity board.
Turning hours into money
An hour of downtime costs you the tonnes you did not produce. Multiply the plant’s normal tonnes per running hour by the lost hours, and value it at your contribution per tonne (selling price less cash cost). Our note on cost per tonne explains how to work out the cash cost.
Seen this way, a spare belt in the store or a second loader on hire often turns out to be cheap compared with the hours it saves.
Planned maintenance from the log
The log also shows which stops could have been planned. If a bearing fails after a predictable number of running hours, it can be changed on a planned day. Over a few months, move as many stops as you can from the mechanical codes to the planned codes. Planned stops are shorter because the parts and the fitter are ready.
Frequently asked questions
Who should fill in the log?
The shift supervisor, during the shift. A log written at the end of the day from memory loses the short stops, which are often the ones that add up.
We already have a maintenance register. Is this different?
A maintenance register records what was repaired. A downtime log records how much production time was lost and why, including stops that needed no repair, such as power cuts and feed gaps. You need both.
What availability should we aim for?
Set your own target from your best months rather than borrowing a figure from another plant. Improvement against your own baseline is what counts.
Where this fits
Downtime matters most when it is seen next to production and dispatch. Quipu’s Stone Crusher and Quarry ERP puts the weighbridge dispatch log, stock and plant dashboard in one place, so the owner can see output and lost hours together. Book a demo to see it.
