Key Takeaways: Unplanned downtime is not eliminated by maintenance effort alone, it's eliminated by data precision. The Fabrico 4-step framework combines real-time OEE failure detection, computer vision root cause analysis, condition-based PM optimization, and the automated work order loop that turns detection into action in under 60 seconds. Manufacturing operations using this framework consistently reduce unplanned downtime by 35-60% within 90 days.
See our fuller guide to equipment downtime.
Most manufacturing plants have a preventive maintenance program. Most manufacturing plants still have significant unplanned downtime. This apparent contradiction resolves when you understand the gap between having a PM program and having a PM program that matches your actual failure patterns.
The root causes of persistent unplanned downtime in plants with active PM programs fall into four categories, each requiring a different solution:
Wrong PM intervals: PM schedules set to manufacturer recommendations or initial estimates rarely reflect actual failure patterns. A bearing PM scheduled every 90 days based on manufacturer specification may fail in 60 days under your operating conditions, or survive 150 days, making the 90-day PM unnecessary. Calendar-based intervals that don't adapt to actual failure history leave preventable failures in the schedule.
Wrong PM tasks: A PM checklist that says "inspect bearing" without specifying measurement method, acceptance criteria, and action thresholds produces wildly inconsistent results between technicians. One technician replaces a bearing that has years of life remaining. Another leaves a bearing that will fail in two weeks. The PM was "completed" both times.
Invisible losses: Between 8-15% of production capacity is lost to events under 30 seconds that PLCs don't register as stoppages, micro-stops that operators clear manually, feed jams that never trigger an alarm, material presentation issues that add 10-15 seconds to every cycle. These losses accumulate silently into significant OEE performance gaps, but because no sensor detected them, no maintenance action is ever created to address their root cause.
Slow response: Even when failures are detected, the 15-35 minute response time typical in plants without automated work order creation means the machine generates OEE availability loss at full rate for 15-35 minutes before a technician arrives. Faster detection without faster response leaves half the problem unsolved.
Fabrico's framework addresses all four failure modes simultaneously.
The framework operates as a continuous cycle: detect faster, understand deeper, prevent smarter, close the loop.
Step 1: Detect Faster (under 60 seconds from failure to work order)
Fabrico's OEE monitoring reads directly from PLCs and machine controllers, detecting machine state changes within one sensor scan cycle, typically under 5 seconds. The system creates a CMMS work order automatically within 60 seconds of the OEE availability signal, pre-populated with asset ID, failure time, duration, OEE context, and maintenance history. The assigned technician receives a mobile push notification immediately.
Comparison: in plants without Fabrico, detection + coordination + work order creation averages 15-35 minutes. The 15-34 minute reduction in response time per failure event × 20 failure events per month × $4,000/hour production value = $20,000-45,000/month in recovered production capacity from response improvement alone, before any reliability improvement.
Step 2: Understand Deeper (root cause from video evidence, not guesswork)
When a failure occurs, Fabrico's Inefficiencies Zoom-In computer vision system automatically flags video clips from the period preceding and during the failure. Maintenance technicians see exactly what happened, not a fault code interpretation, but visual evidence of the failure sequence.
For recurring failures, the AI Agent analyzes the pattern across historical events: Does this failure mode consistently precede specific OEE performance rate declines? Does it correlate with specific production orders, shift changes, or material batches? Does it cluster around the end of a maintenance interval, suggesting a PM interval that's too long, or occur randomly, suggesting a different failure mode than the PM is designed to prevent?
The root cause identified from this analysis is the actual root cause, not the most plausible explanation from a technician's experience, but the data-supported root cause from the operational record.
Step 3: Prevent Smarter (PM optimization from OEE cycle data)
Fabrico connects OEE cycle counts directly to CMMS PM scheduling. This is the transition from calendar-based preventive maintenance to usage-based maintenance, the highest-impact reliability improvement available in manufacturing without capital investment.
A press die that receives a PM every 90 days under a calendar schedule gets its PM when usage dictates it under Fabrico's cycle-count trigger system. The die running at 200 strokes per minute gets its PM after 1.2 million cycles, which might happen in 6 days on a high-speed line or 21 days on a slower line. The calendar doesn't matter. The usage does.
The AI Agent continuously analyzes the correlation between PM execution timing and failure occurrence. If failures consistently appear before the scheduled PM interval, the interval is too long. If PMs consistently find no defects, the interval may be too short. Fabrico surfaces both patterns automatically and suggests interval adjustments with the supporting data.
Step 4: Close the Loop (OEE recovery verification after every maintenance action)
Fabrico monitors OEE for 7 days after every work order closure on a monitored asset. The system compares OEE performance in the 7 days before the maintenance action to OEE performance in the 7 days after. If OEE improved: the maintenance action was effective. If OEE didn't improve: the root cause was either misidentified or the corrective action was insufficient.
This closed loop, failure detection, root cause identification, corrective action, recovery verification, creates the compounding reliability improvement that open-loop maintenance programs never achieve. Every failure event generates data that makes the next failure less likely or faster to resolve.
Fabrico tracks unplanned downtime at four levels simultaneously, giving operations leaders the analysis depth they need and the summary metrics they can present to boards:
Asset level: Which specific machines have the highest unplanned downtime frequency? Which have the longest MTTR? Which show declining MTBF trends, indicating emerging reliability problems before they become production crises? The AI Agent surfaces this data automatically in the management dashboard without requiring manual analysis.
Failure mode level: Which failure types are most common? Which are recurring despite corrective maintenance, indicating incorrect root cause identification? Which cluster around specific PM intervals, indicating interval optimization opportunities? Fabrico categorizes every failure by mode and presents trend data across all categorized events.
Response time level: What is the actual mean time from OEE detection to technician arrival? How does this compare to target? Which failure events had unusually long response times, indicating dispatch or staffing issues rather than equipment issues? Fabrico's integrated OEE-CMMS timestamp data produces this analysis automatically.
Financial level: What is the production cost of unplanned downtime per month? How does this trend compare to the previous 3 months and the same period last year? What is the recovery value of each percentage point of MTBF improvement on critical assets? Fabrico connects OEE loss data to production revenue rates to produce these financial metrics without manual data assembly.
The unplanned downtime reduction that Fabrico deployments consistently produce, by timeframe:
These results require the integrated OEE+CMMS platform that Fabrico provides. They cannot be achieved with a CMMS alone, the production performance feedback loop that drives PM optimization requires OEE data. They cannot be achieved with OEE alone, the maintenance execution and PM compliance tracking requires CMMS. The integration is not a feature; it's the mechanism that makes systematic unplanned downtime elimination possible.
Login
Blog