SUMMARY
Use this guide to configure barcode scanning for stop cause registration. Once configured, operators can scan a barcode to automatically register the corresponding stop cause, reducing manual input and improving the consistency of downtime data.
WHEN TO USE THIS
Use this guide if:
- You want operators to register stop causes by scanning barcodes.
- You want to reduce manual stop cause selection.
- You are using a handheld or fixed-mount Factbird barcode scanner.
- You want to standardize downtime registration across production lines.
PREREQUISITES
Before starting:
- A Factbird barcode scanner has been installed and configured.
- Stop causes have been created for the production line.
- Each stop cause has a unique barcode assigned.
- You have permission to configure barcode workflows.
STEPS
1. Create or verify your stop causes
- Open the stop cause configuration for the production line.
- Create any required stop causes.
- Verify that each stop cause represents a unique downtime reason.
2. Assign barcodes to stop causes
- Assign a unique barcode value to each stop cause.
- Ensure every barcode corresponds to only one stop cause.
Tip
Use printed barcode labels near the machine so operators can quickly select the correct downtime reason.
3. Configure the barcode scanner
- Verify the scanner is connected and communicating with Factbird.
- Confirm the scanner reads the barcode format used for your stop cause labels.
- Test that scanned barcode values are received correctly.
4. Register a stop cause
When a machine stop occurs:
- Scan the barcode corresponding to the correct stop cause.
- Factbird automatically assigns that stop cause to the detected stop.
- If required, add comments or additional information before saving the registration.
5. Verify the registration
- Open the recorded stop.
- Confirm the correct stop cause has been assigned.
- Verify the stop appears correctly in Stop Analytics and reporting.
EXPECTED RESULT
After completing these steps:
- Operators can register stop causes by scanning a barcode.
- Downtime is classified consistently.
- Stop registrations are immediately available for reporting and analytics.
- Manual navigation through stop cause lists is reduced.
TROUBLESHOOTING
Issue: Scanning the barcode does not register a stop cause.
Try: Verify the barcode is assigned to a stop cause.
- Try: Confirm the scanner is connected correctly.
- Try: Check that the stop has been detected before scanning.
Issue: The wrong stop cause is assigned.
Try: Verify each barcode is unique.
- Try: Check that the printed label matches the configured stop cause.
- Try: Confirm the barcode mapping has not been changed.
Issue: The barcode cannot be read.
Try: Clean the scanner lens.
- Try: Replace damaged barcode labels.
- Try: Confirm the barcode symbology is supported by the scanner.
STILL NEED HELP?
Contact Support and include:
- The production line name.
- The barcode value being scanned.
- The expected stop cause.
- The barcode scanner model.
- A description of the issue.
RELATED ARTICLES