Configuring the stops finder correct is essential for getting valid data out of Factbird. Factbird is setting a sensible default which we allow our users to modify to their specific needs. The stops finder configuration is managed in sensor settings dialog.

Recommendation:

Start with following settings in the stops finder:

• Minimum stop duration: 10 or the cycle time - whatever is higher
• Value threshold: 0
• Stop registration threshold: 300

Run your operation with these settings for a while and then evaluate the amount of speed loss and micro-stops. Use the OEE page to easily see speed loss and micro-stop contribution.

If micro-stops are a significant contributor to downtime you can lower the stop registration threshold and hence ask operators to register more stops. You can also consider enabling automatic stop registration using PLC tags see: Register stop causes using PLC tags

If speed loss is a significant contributor to downtime you must first validate that the validated sensor speed is set correct. Second, using the live view evaluate if the line is actually running with a slower speed than expected. Third adjust the minimum stop duration to be closer to the cycle time.

If you are running very high cycle times, consider enabling cycle time subtraction

Settings

Enable/Disable finding stops

For counters that do not need stops finding, eg. scrap sensors, there is a cost optimization in disabling the stops finder.

<aside> 💡 Disable stop finder on scrap sensors to save cost (private cloud only)

</aside>

Minimum stop duration in seconds

Defining how small a stop can be before Factbird defines it as a stop. Setting the minimum stop duration to 10 seconds will result in:

• All stops with a duration below 10 seconds will be defined as speed loss.
• All stops with a duration above will be created as a unregistered stop.

<aside> 💡 Never set the minimum stop duration below the cycle time of the product.

</aside>