Downtime tracking has always depended heavily on operator input. On a busy line, that means short stops are rarely written down, micro-stops are almost never recorded and root causes become guesswork. The result is a distorted picture of performance that hides real improvement opportunities.
Modern plants are moving to automatic collection of downtime from machine signals and computer vision. Platforms like Fabrico connect directly to machines and combine those signals with a built-in maintenance layer, so every stop is captured in real time and turned into actionable work for production and maintenance teams.
Request a demo
Why manual downtime logs undercount losses
Manual logs made sense when equipment was simple and data collection options were limited. Today they are a bottleneck that skews OEE and misdirects improvement efforts. Common issues include:
- Missing short stops: Operators focus on major breakdowns. A 2-minute jam or 45-second sensor fault repeated many times in a shift is usually ignored, even though the accumulated loss is significant.
- Rough estimates instead of precise times: Downtime is recorded as round numbers such as 5 or 10 minutes. Over a week, this rounding error can hide hours of real loss or inflate issues that are actually minor.
- Inconsistent cause codes: The same event might be logged as "mechanical," "breakdown," or "line issue" depending on who is on shift. This inconsistency blocks accurate Pareto analysis.
- Logging delayed until the end of shift: When operators are busy, they postpone entries. By the time they update the log, details are forgotten and root causes are simplified or guessed.
- Pressure to keep numbers looking good: When downtime metrics are seen as a personal scorecard, some losses are left unrecorded or moved into "changeover" or "meeting" to avoid scrutiny.
The biggest problem is not dishonesty, it is cognitive overload. Operators are hired to run equipment safely and consistently, not to act as data-logging terminals. Any process that relies on perfect manual entry in a high-intensity environment will fail.
Automatic downtime capture from machine signals
Machine signals solve the first half of the problem. By connecting to PLCs, sensors or existing controllers, a platform like Fabrico can detect when a machine is running, idle, blocked or starved and can time those states with second-level precision.
This type of machine monitoring system transforms the quality of downtime data:
- Every stop is captured: If the machine stops, it is recorded. Micro-stops, frequent short jams, starved or blocked conditions and low-speed losses appear automatically in the event stream.
- Precise timestamps: Start and end times are captured directly from the machine. OEE metrics such as Availability and Performance are built from objective data, not memory.
- Standardized state definitions: States are configured once, then applied consistently across shifts, lines and plants, which makes benchmarking possible.
- Minimal operator burden: Operators focus on confirming or refining the cause of a stop, not on starting and stopping timers.
With this foundation, operations and continuous improvement managers can trust their production monitoring data. The conversation shifts from "Are these numbers correct?" to "What is the best next action?"
Where machine signals fall short
Machine signals show when the asset is not producing, but they do not always explain why. Typical gaps include:
- Ambiguous states: The PLC may show the machine is stopped, but the true cause could be material, quality, a blocked conveyor or an upstream machine.
- Complex lines: In lines with multiple interconnected machines, one stop can ripple across the line. It is hard to see which machine is the initiator and which are just blocked or starved.
- Human-driven issues: Operator absence, incorrect setup, slow manual packing or visual quality checks are rarely visible in PLC data.
- Manual workstations: Assembly cells or inspection stations without sophisticated controls can remain blind spots if you rely on signals alone.
This is where computer vision complements machine data and fills in the remaining blind spots.
How computer vision exposes unrecorded stops
Computer vision uses cameras and AI models to interpret what is happening on and around the machine. It can identify motion, material flow, accumulation, operator presence, and in some cases visual defects or misalignments. When combined with machine signals, it enriches downtime tracking in several ways:
- Detecting line-level blockers and starvation: Vision can see an upstream conveyor that is full or an empty infeed, making it clear whether a stop is caused by the machine itself or another asset.
- Distinguishing mechanical from material issues: If the PLC shows a stop and the camera sees an empty pallet, missing boxes or no operator, the system can categorize the loss more accurately.
- Tracking manual micro-stops: In semi-automatic cells, small hesitations and repeated manual interventions become visible as slowdowns that OEE calculations can incorporate.
- Supporting setup and changeover analysis: Vision can segment changeover tasks and highlight where time is lost on manual steps, which helps SMED and standard work projects.
Vision does not replace machine signals, it adds context. Combined, they deliver a far more truthful account of what is hurting throughput than any manual log can provide.
From raw downtime data to practical actions
Capturing every stop is only valuable if teams act on the information. Fabrico brings together automatic data capture, OEE analytics and a built-in maintenance management layer so that downtime events are naturally connected to actions.
Typical workflows include:
- Production actions: When recurring short stops are linked to changeover, cleaning or material handling, production teams can standardize work, adjust staffing or re-balance tasks directly from a prioritized list of losses.
- Maintenance actions: Repeated faults from specific sensors, drives or subsystems can automatically raise maintenance tasks inside the platform. Maintenance managers can plan inspections or replacements based on real failure patterns.
- Shared view for operations and maintenance: Both teams work from the same timeline of stops, causes and actions. There is less debate about "Is this downtime really maintenance or operations" because the data is granular and transparent.
- Structured improvement cycles: Pareto charts of downtime and speed loss, fueled by accurate signals and vision, point CI teams to the next most valuable improvement project.
The result is a production environment where OEE improvements are built on evidence, not on partial or biased logs.
Where AI fits into modern downtime tracking
AI adds another layer of intelligence on top of raw signals and images. In Fabrico, AI can help classify events, suggest root causes and identify patterns that are difficult to see in spreadsheets or static reports.
Examples of AI-driven value in AI production monitoring include:
- Automatic cause suggestions: Combining PLC fault codes, machine state patterns and vision input, AI can propose the most likely cause for a stop so operators only need to confirm or adjust.
- Pattern detection across shifts and products: AI can highlight that minor stops spike on specific SKUs or during certain shift combinations, pointing to training or setup issues.
- Prioritization by impact: Rather than a long list of small problems, AI can show which combination of recurring stops and speed losses actually restricts throughput on key products.
AI does not replace engineers. It speeds up their analysis and lets them focus on solving problems instead of assembling data.
Key evaluation questions for MES and OEE buyers
When you evaluate MES and OEE platforms, especially those that claim to track downtime automatically, it is useful to ask:
- How do you connect to machines and what events can you capture from PLCs or controllers
- How do you handle semi-automatic or manual workstations where signals are limited
- Do you support computer vision, and how is it integrated into downtime classification and OEE
- How is the maintenance layer integrated so that downtime patterns can trigger and prioritize maintenance work
- What tools exist for operators to confirm or refine causes with minimal clicks
- How do you present downtime and OEE metrics to different roles: operators, team leaders, CI managers and maintenance
Fabrico is designed to address these questions in one platform: it collects data from machine signals and, where relevant, computer vision, calculates real-time OEE, and ties every significant loss to production and maintenance actions through its built-in maintenance management capabilities.
Moving beyond manual logs to real-time loss visibility
For mid-size and large manufacturers, the limitations of manual downtime logs have become a strategic issue. As product mixes grow and supply chains tighten, unmeasured losses translate directly into missed orders, overtime and capital spending that may not be necessary.
By combining machine signals, computer vision and integrated maintenance management, Fabrico gives plant managers, operations directors and maintenance leaders a clear view of where capacity is really going. Manual logs can still play a role as a backup or for special cases, but they no longer define the data.
To see how this approach could work on your lines, you can Contact us.
Login
Blog
