Skip to content
Qualityforeveryone
Lesson 1 of 5β‰ˆ 2 min read
View All Lessons β†’

Defining a Failure Before You Count One

Audio Narration (Voxtral)Voxtral♀ Female Voice

Defining a Failure Before You Count One

Every reliability number starts with a count of failures. If two technicians disagree about what a failure is, their MTBF figures will disagree too, and nobody will trust either one. So the first job is not arithmetic. It is writing down, in one or two sentences, what counts as a failure for the machine you are tracking.

A workable definition for most production equipment is this: an unplanned stop that requires a maintenance intervention before the machine can run again. Planned cleaning, scheduled changeovers, and product-driven adjustments are not failures. A jam the operator clears in under a minute without tools is usually treated as a minor stop, not a failure, and is tracked separately.

Write the definition on the log sheet or in the maintenance system so it travels with the data. When a borderline event happens, decide once, record the decision, and apply it the same way next time. Consistency matters more than the exact wording.

Key Concept
A failure is an unplanned stop that needs maintenance to fix; the definition must be written down and applied the same way every time.
Practical Example
A bakery tracks a 300 kg spiral dough mixer. Over one week the log shows: two drive belt breaks (each needed a technician and a new belt), one planned 40-minute bowl wash between dough types, three dough hook jams cleared by the operator in under 2 minutes, and one safety guard switch fault that stopped the machine until an electrician replaced the switch. Using the definition above, the failure count for the week is 3: two belt breaks plus the switch fault. The bowl wash is planned and the three jams are minor stops.

Standard Procedure

  1. 1Write a one-sentence failure definition for the machine and post it where the log is kept.
  2. 2List the common stop types for that machine and mark each as failure, planned, or minor stop.
  3. 3Review the log at the end of each week and confirm every stop has been classified.
  4. 4When a new type of event appears, classify it once and add it to the list.

Lesson Summary

  • βœ“Agree on the failure definition before collecting any data.
  • βœ“Planned work and short operator-cleared jams are not failures and should be tracked separately.

Progress Tracking

Sign in to save your lesson completion markers.