How to set up clear stop causes and categories
This lesson shows you how to create stop categories and specific stop causes in Factbird so operators can register downtime accurately and consistently. Clear, structured categories make it easier for operators to log stops in real time and help you analyze downtime more effectively later.
You’ll learn how to set up “umbrella” stop categories that group related issues; for example, grouping unplanned technical faults under “loss during operation.”
You’ll also see how to create individual stop causes within these categories, with options to require operator initials or comments for more detailed reporting.
Understanding the four main stop categories is key to accurate analysis:
- No activity at line – Planned non-production periods.
- Non-production activity – Planned stops during operating hours, such as meetings or breaks.
- Batch-specific non-operation – Necessary stops like cleaning or changeovers.
- Loss during operation – Unplanned downtime and technical faults.
What you’ll learn:
- Creating umbrella stop categories in Factbird.
- Adding specific stop causes with optional operator initials or comments.
- Understanding Factbird’s four main stop categories and when to use each.
- Structuring downtime reporting to improve operational insights.