SUMMARY
Use this guide to understand how Stop Causes classify and explain machine downtime in the Factbird system. Stop causes help operators identify why production stopped and organize downtime data for analysis and performance improvement.
WHAT THIS IS
Stop Causes are predefined reasons used to explain machine downtime detected by the Factbird system. When the system identifies a stop through sensor data, the stop can be assigned a specific cause that describes why production was interrupted.
Stop Causes are organized using categories and color codes. Categories help structure and group similar stop reasons, while color codes indicate the type of production loss associated with the stop.
WHY IT MATTERS
Machine stops can occur for many different reasons. Without structured classification, it becomes difficult to understand recurring problems or prioritize improvements.
Stop Causes provides a consistent way to categorize downtime, making it easier to analyze operational losses, identify trends, and focus improvement efforts on the most impactful issues.
WHEN YOU WOULD USE THIS
Use this when:
Reviewing or classifying machine downtime
Analyzing production losses in the Factbird analytics
Organizing stop reasons for operator use
Linking downtime events to operational causes
HOW IT WORKS
Factbird automatically detects machine stops using connected digital sensors. The system analyzes the sensor signal and identifies downtime based on gaps in production activity.
Once a stop is detected, the system allows the downtime event to be assigned a Stop Cause. This assignment can occur automatically through PLC integrations using predefined tags or manually through operator input.
Stop Causes are organized into categories that act as folders, helping operators quickly locate the correct reason during downtime registration. These categories also allow downtime events to be grouped and analyzed in reports and analytics.
Each Stop Cause is also associated with a color code. The color indicates the type of production loss connected to the stop, based on OEE loss categories. This visual coding helps users quickly understand the nature of the downtime.
If a stop occurs without a registered cause, the system highlights the downtime with a bright red indicator to draw attention. Operators can then select the appropriate Stop Cause, optionally add comments, and associate different reasons with portions of the stop if needed.
KEY TERMS / COMPONENTS
Stop Cause:
A predefined reason used to explain why a machine stop occurred.
Stop detection:
The automatic process that identifies machine downtime by analyzing sensor signals.
Stop Cause category:
A grouping structure used to organize stop causes into logical folders for easier navigation and analysis.
Color code:
A visual indicator associated with a stop cause that represents a type of production loss.
OEE time loss:
A classification of production losses used in Overall Equipment Effectiveness analysis.
Unregistered downtime:
A detected machine stop that has not yet been assigned a stop cause.
PLC integration:
A connection between the Factbird system and a machine’s programmable logic controller that can automatically assign stop causes using machine tags.
COMMON MISUNDERSTANDINGS
Stop Causes do not detect downtime. Detection is performed automatically by the stop detection algorithm using sensor data.
Stop Causes are not limited to manual input. They can also be assigned automatically through PLC integrations.
Stop Cause categories are not only for navigation. They also enable structured analysis of downtime in the analytics tools.