SUPSupply & productionStop 11 of 12
Maintenance planning
Choosing between fixing things when they break, servicing on a schedule, and acting on condition data, and timing stops around production.
Read atChange any time
Machines wear out. The question is whether you stop them on your terms or theirs. There are four broad approaches:
- Reactive: run until it breaks, then fix it. Cheap until it happens on the bottleneck during the festive rush.
- Preventive: service on a fixed schedule (every 500 running hours, every month), whether the part needs it or not. Predictable, but you sometimes replace parts that had life left.
- Predictive (condition-based): measure vibration, temperature or oil quality and intervene when the data shows wear. Fewer surprises and fewer wasted services, but it needs sensors and analysis.
- TPM (total productive maintenance): operators own basic care such as cleaning, lubricating and inspecting, so small problems are caught before they become breakdowns.
Two numbers describe reliability:
- MTBF (mean time between failures): how long it runs between breakdowns.
- MTTR (mean time to repair): how long a repair takes.
Availability is roughly MTBF ÷ (MTBF + MTTR). A machine that fails every 190 hours and takes 10 hours to fix is available about 95% of the time. You can improve it by failing less often, or by fixing faster with spare parts on hand and trained technicians.
Planning matters as much as method: schedule stops in low-demand periods or alongside changeovers, protect the bottleneck most carefully, and build stock ahead of long shutdowns.
Words to use
- MTBF
- Mean time between failures: average running time between breakdowns.
- MTTR
- Mean time to repair: average time to get a failed machine running again.
- Predictive maintenance
- Maintenance triggered by condition data, such as vibration or temperature, rather than a calendar.
Availability, worked through
With MTBF = 190 hours and MTTR = 10 hours, availability is 190 / 200 = 95%. Two ways to improve it:
- Fail less often: raise MTBF by 50%, to 285 hours. Availability = 285 / 295 = 96.6%.
- Repair faster: halve MTTR to 5 hours, with a ready spare-parts kit, clear repair instructions and trained technicians. Availability = 190 / 195 = 97.4%.
Halving repair time beats a 50% gain in reliability here, and it is often cheaper. Repair time includes waiting for the technician, the diagnosis, the spare part and the restart, and the waits are usually the biggest part.
Choosing the approach for each machine
| Situation | Sensible approach |
|---|---|
| Cheap to fail, easy to repair, not a bottleneck | Run to failure |
| Wear that tracks usage, such as filters, belts and lubricants | Preventive, at fixed intervals |
| Failures give warning signs, such as vibration, heat or noise | Predictive, condition-based |
| Critical machine with costly failures | Predictive plus redundancy or critical spares |
How planned work flows
- Notification: an operator, an inspection or a sensor reports a problem or a due task.
- Planning: the planner defines the job, the parts, tools, permits and skills needed, and how long it takes.
- Scheduling: the job gets a slot agreed with production, ideally during a changeover or a low-demand shift.
- Execution and closing: technicians do the work and record what failed and why.
- Analysis: failure records feed improvements and adjust maintenance intervals.
ERP systems, including SAP’s plant maintenance module, manage this flow with maintenance plans, notifications and work orders.
Measures that matter
Planned work as a share of all maintenance work, schedule compliance, backlog in weeks of work, MTBF and MTTR for critical assets, and maintenance cost compared with the value of the equipment.
Most failures aren’t about age
Reliability-centred maintenance (RCM) grew out of airline studies in the 1960s and 1970s, summarized by Nowlan and Heap (1978). A key finding was that most failure modes of complex equipment were not related to age: the chance of failure didn’t rise steadily with time. For those failure modes, replacing parts on a fixed schedule doesn’t prevent failures and can even add early-life failures to freshly installed parts. That shifted maintenance towards condition monitoring and towards asking, for each failure mode, which task actually reduces its risk.
The P-F interval
Many failures announce themselves. The point when a developing failure first becomes detectable (P, potential failure) comes some time before the equipment stops working (F, functional failure). If vibration analysis can detect a bearing defect about six weeks before it seizes, inspecting every three weeks catches it with time to plan the repair. The rule: inspect more often than the P-F interval, and plan the fix inside it.
Predictive maintenance in practice
Sensors measure vibration, temperature, current, pressure or oil condition, and models flag patterns that typically come before failures. It works best where failures have a measurable signature, data is available over enough failures to learn from, and the cost of a surprise failure is high. Pitfalls: too many false alarms (technicians stop trusting them), too few historical failures to train on, and alerts that arrive without a process to plan and schedule the response.
Maintenance and the supply chain
- Spare parts: critical spares are classic intermittent-demand items, so stocking them is a service-level decision weighed against downtime cost.
- Shutdowns: planned plant shutdowns need stock built ahead, customers informed and contractors booked, and are managed like projects with a critical path.
- Bottleneck first: protect the constraint with the best maintenance, spares and response times, since its downtime is the plant’s downtime.
Criticality comes first
Before choosing tasks, rank equipment by what a failure would cost (safety, environment, output, quality, repair cost) and how likely it is. Failure mode and effects analysis (FMEA) does this systematically. High-criticality assets get predictive monitoring and spares; low-criticality ones may simply run to failure.
Interview kit
Practise it out loud
Answer each question yourself before opening the model answer.
Maintenance strategy ranges from reactive to preventive to predictive, with TPM adding operator ownership of basic care. I’d choose by criticality: predictive or preventive on bottlenecks and critical assets, run-to-failure on cheap redundant ones. Reliability is tracked with MTBF and MTTR, and stops should be planned around demand, with stock built ahead of long shutdowns.
A machine fails every 190 hours and each repair takes 10 hours. What is its availability, and how would you improve it?
About 190 ÷ 200 = 95%. Increase MTBF with preventive or predictive maintenance, or cut MTTR with spare parts kept on site, standard repair procedures and trained technicians. On a bottleneck, both are worth paying for.
When is run-to-failure a reasonable choice?
For cheap, non-critical equipment with backup capacity, where a failure doesn’t stop the line and preventive work would cost more than the occasional repair.
Connected stops
Where this idea feeds in, or gets its inputs from.
Sources and further reading
- Nakajima, S. (1988). Introduction to TPM: Total Productive Maintenance. Productivity Press.
- Hopp, W. J. & Spearman, M. L. Factory Physics. Waveland Press.
- Nowlan, F. S., & Heap, H. F. (1978). Reliability-Centered Maintenance. United Airlines, for the US Department of Defense.
- Moubray, J. (1997). Reliability-Centred Maintenance (2nd ed.). Industrial Press.