Two indicators, two questions
MTBF answers “how long does the equipment run between two failures?”. MTTR answers “how long does it take to bring it back into service?”. Both only make sense with failures recorded consistently.
- FailureCorrective request created
- RepairWork on the equipment
- ClosureRequest completed
- MTTRDays between request and closure
- MTBFTime since commissioning / number of failures
- Estimated next failure: last failure plus MTBF.
- Preventive work goes through recurring requests, separately.
- Without a recorded request, no failure is counted.
What Odoo computes
In Odoo Community, each piece of equipment shows an MTBF computed from completed corrective maintenance, an MTTR measured in days between request and closure, and an estimated next failure date equal to the last failure plus the MTBF.
Data-entry pitfalls
- A request closed late lengthens MTTR even though the repair did not take longer.
- A failure repaired without a request disappears from MTBF.
- Preventive work entered as corrective distorts both indicators.
- An MTTR in days hides stoppages of a few hours.
- A wrong commissioning date distorts MTBF.
Preventive maintenance
Odoo Community schedules preventive maintenance through recurring preventive requests, with an interval and a unit, linked to the equipment. Measure preventive work done on time against preventive work planned before looking for a finer indicator.
Limits
These calculations rely on request dates, not on the machines’ actual downtime. Hourly tracking or tracking fed by the machines requires an interface study.