Maintenance
Breakdown maintenance: how to log a breakdown so it does not happen again
Breakdown maintenance is the repair you do after a machine has already stopped. You cannot avoid it completely, but you can make each breakdown the last of its kind. The way to do that is to log every stop at the machine, with the start time, what was seen, what was done and the cause, and then add one action that stops it coming back.
What breakdown maintenance is, and when it is the right call
Breakdown maintenance, also called reactive or run-to-failure maintenance, means you repair a machine after it fails, not before. EN 13306, the European standard on maintenance terms, puts it under corrective maintenance: work carried out after a failure is detected, to bring the asset back to a state where it can do its job. The U.S. Department of Energy's O&M best practices guide calls the pure form "run it till it breaks".
Sometimes that is the sensible choice. A cheap exhaust fan in a store room, a bench grinder with a spare next to it, or a light fitting: if failure is safe, cheap and quick to fix, a PM schedule for it costs more than the breakdown. Choose run-to-failure on purpose for these, and write that choice down.
The trouble starts when breakdown maintenance is the default for machines that matter. A stopped pressure die casting machine, a furnace hydraulic unit or the only compressor in the plant halts output, can damage other parts and puts people at risk during a rushed repair. The DOE guide lists the costs: unplanned downtime, overtime, damage to other parts, a bigger store of spares and shorter equipment life.
So the goal is not zero breakdowns on day one. It is two things: fewer surprises on critical machines, and a record of every stop good enough to learn from.
Why the same breakdown keeps coming back
In a typical plant the night shift calls the fitter, the fitter changes the bearing, the line restarts and everyone is relieved. The only record is a line in a register: "bearing changed, OK". Six weeks later the same bearing fails again, and a different fitter starts from zero.
Nothing in that story is careless. The repair was fast and correct. What was missing was the information that turns a repair into a lesson: what failed, why it failed, and what will stop it. Without it you cannot see that one gearbox has stopped the sand plant four times this quarter, and you cannot work out a real MTBF and MTTR for it.
ISO 14224, the reliability and maintenance data standard written for the oil and gas industry, is useful here even if you run a foundry or a food plant. It separates what you saw (the failure mode), how the part failed (the mechanism) and why (the cause), and it asks for downtime and repair time with every event. You do not need its full data model. You need the same habit: record the facts while they are fresh, in fields that can be counted later.
A breakdown log template to copy
Use one row per stoppage, filled at the machine or within the shift. The "good" column is the level of detail that lets you find a pattern three months later.
| Field | Who fills it | Weak entry | Useful entry |
|---|---|---|---|
| Machine (asset tag) | Operator | Press | HP-11 hydraulic press, line 2 |
| Start time | Operator | Night shift | 02:40, when the press stopped |
| What was seen or heard | Operator | Not working | Ram stopped mid stroke, oil on floor near cylinder |
| Failure mode | Technician | Breakdown | External hydraulic leak |
| What was found | Technician | Hose problem | Return hose cracked at the crimp, rubbing on frame |
| Action taken | Technician | Repaired | Replaced hose, added clamp to stop rubbing |
| Parts used | Technician | Hose | 1 hose assembly, 1 clamp, 12 litres hydraulic oil |
| Back in service | Technician | Done | 04:55, trial strokes OK |
| Cause | Supervisor | Wear | No clamp after last hose change, hose rubbed through |
| Prevention | Maintenance planner | Will monitor | Add hose routing check to monthly PM; keep one hose in stock |
| Repeat? | Planner | Blank | Yes, second hose failure on HP-11 in 60 days |
Downtime for the stop is the start time to back in service, 2 hours 15 minutes in this row. Write both times, not just the total, so nobody has to argue about it later.
From restart to root cause: five steps after every breakdown
Run these for every breakdown on a critical machine. For minor stops, steps 1 to 3 are enough unless the stop repeats.
- 01
Make it safe, then restore
Isolate the energy before anyone reaches in. A rushed repair under pressure is when people get hurt. Restore the machine first, then investigate with the facts still fresh.
- 02
Log it at the machine
The operator records the machine, start time and what was seen. Timestamps written at the end of the shift drift; times written at the machine do not.
- 03
Close it with facts
The technician records what was found, what was done, the parts used and the time back in service. "Repaired" is not a closing note.
- 04
Ask why on repeats
If the same machine stops for the same reason twice, ask why until you reach something you can change: a missing PM task, a wrong part, a setting, a skill gap. Five whys is enough for most shop floor failures.
- 05
Add one prevention and check it
Add a PM task, stock a spare, change a setting or train the crew. Put a date on it and an owner. After a month or two, check whether that failure has come back.
Worked example: a sand plant gearbox in a Rajkot foundry
Worked example (illustrative)
Take a grey iron foundry in Rajkot with one sand mixer that feeds two moulding lines. When the mixer stops, both lines stop. Every number below is illustrative.
Over one quarter the mixer gearbox stops five times. The old register said "bearing changed" three times and "gearbox jammed, freed" twice. When the team rewrote the five stops with the template above, using job cards and the fitters' memory, the picture changed.
| Stop | What was found | Downtime (hours) |
|---|---|---|
| 1 | Output shaft bearing seized, grease dry and dark | 4.0 |
| 2 | Sand in gearbox, breather cap missing | 2.5 |
| 3 | Output shaft bearing seized, grease dry | 5.0 |
| 4 | Bearing noisy, changed early | 1.5 |
| 5 | Output shaft bearing seized, seal worn | 4.5 |
| Total | 5 stops | 17.5 |
What the example shows (illustrative). MTTR is 17.5 / 5 = 3.5 hours, but the more useful fact is that four of five stops are the same bearing, with dry grease or sand. Asking why led to a grease point that sat behind a guard and was skipped, and a breather cap nobody owned. The team added a weekly greasing task with an extended grease line, a monthly breather and seal check, and one bearing in stock. If the next quarter shows one stop instead of five, the template has paid for itself. Use the downtime cost calculator to put a rupee value on the 17.5 hours for your own plant.
Common mistakes
- Logging after the shift. Times and symptoms written from memory are vague and often wrong. Log at the machine, even if it is two lines.
- "Repaired" as the closing note. It tells the next technician nothing. Write what was found and what was done.
- Mixing planned stops into breakdowns. A planned PM stop is not a breakdown. Mixing them hides your real failure rate.
- Cause and symptom in the same box. "Bearing failed" is what happened. "No grease because the point was hidden" is the cause.
- One free-text field for everything. You cannot count free text. Keep machine, failure mode and cause as separate fields with a short pick list.
- Treating every breakdown as a project. Run a full why analysis on repeats and on critical machines. For a one-off on a fan, log it and move on.
- No owner for the prevention. A good root cause with no task, no date and no owner is just a better story about the next breakdown.
Sources
- Operations and Maintenance Best Practices: A Guide to Achieving Operational Efficiency (Release 3.0), chapter 5: Types of maintenance programs (opens in a new tab), U.S. Department of Energy, Federal Energy Management Program
- Maintenance of work equipment and machinery (opens in a new tab), Health and Safety Executive (UK)
- ISO 14224: collection and exchange of reliability and maintenance data for equipment (opens in a new tab), Wikipedia
- Corrective maintenance (opens in a new tab), Wikipedia
- Five whys (opens in a new tab), Wikipedia
Frequently asked questions
What is breakdown maintenance?
Breakdown maintenance is repair work done after a machine has failed. It is a form of corrective maintenance, also called reactive or run-to-failure maintenance.
Is breakdown maintenance always bad?
No. For cheap, non-critical items where failure is safe and quick to fix, running to failure can cost less than a PM schedule. It becomes a problem when it is the default for critical machines.
What should a breakdown report include?
The machine, the start time, what the operator saw, what the technician found and did, the parts used, the time back in service, the cause and the action that will stop it coming back.
What is the difference between breakdown maintenance and corrective maintenance?
Breakdown maintenance is repair after a failure. Corrective maintenance is the wider term: it also covers fixing a defect found during an inspection before the machine stops.
How do you stop the same breakdown happening again?
Record the cause, not just the symptom. On repeat failures, ask why until you reach something you can change, then add one prevention such as a PM task or a stocked spare, with an owner and a date.