Planned vs Unplanned Downtime: The Pit Stop Strategy

The myth is that planned downtime is a "cost." It is not. It is the lowest-cost form of stoppage you have. Avoiding planned downtime to "keep running" is what creates the unplanned downtime that costs 8x more.

Three preparation levers turn unplanned into planned:

• Spare parts policy: failure-mode-driven stock based on MTBF data. Top 10% of EU plants have 95%+ on-shelf availability for critical-path parts.
• Standardized procedures: every changeover and major PM has a written sequence with timings. SMED methodology (Single-Minute Exchange of Die).
• Pre-positioned technicians: schedule major PM during planned shutdowns when the crew is already on-shift, not at 03:00 on Sunday after a breakdown.

EU benchmark: plants that nail these three reduce unplanned events 50-70% in 12 months. The 6 OEE losses map every unplanned event to one of these levers.

Formula 1 teams plan every pit stop down to 1.8 seconds. The car comes in fast, the crew is already in position, tires are ready, fuel is staged. The stop is fast because everything was prepared before the car arrived.

Apply the same logic to your plant. Two columns:

• Column 1: Planned: scheduled, parts staged, technicians assigned, sequence rehearsed. EU benchmark median: 30-45 minutes for a major changeover.
• Column 2: Unplanned: surprise, no parts on hand, scrambling for technicians, no procedure. EU benchmark median: 4-6 hours for the same type of repair.

Same machine, same repair, 8-12x difference. Every event in column 2 that you can move to column 1 saves 3-5 hours of lost production.

See OEE benchmarks by sector for column-1 medians by industry.

The move is not magic. It is detection plus preparation. Each unplanned event you eliminate is one of these three patterns:

Pattern 1: Recurring failure on the same asset. The asset failed last month, this month, and will next month. Move to column 1 by scheduling PM at the cycle interval the data shows.

• How to find: OEE data collection shows MTBF per asset. Anything with MTBF under 200 hours is a candidate.

Pattern 2: Predictable wear signature. Vibration rising, temperature climbing, micro-stops accumulating. Move to column 1 by triggering PM at the signal, not the calendar.

• How to find: Computer Vision + sensor data show the wear curve. Reliability paradox covers the metric stack.

Pattern 3: Process-driven failure. Operator setup error, contamination, wrong parameter. Move to column 1 by standardizing the setup procedure.

• How to find: cluster unplanned events by changeover. If 40%+ happen in the first 90 minutes after changeover, the setup is the cause.

See the 6 root causes of unplanned downtime for the full taxonomy.

The goal is not zero downtime. The goal is to make every downtime event a pit stop, not a flat tire.

A modern OEE solution with native CMMS drives this automatically: failure pattern detected → spare auto-reserved → technician auto-scheduled → procedure auto-attached. The plant turns column-2 events into column-1 events in real time.

That is the difference between Fabrico and a maintenance calendar that pretends every asset is the same.