Configuring the stops finder correctly 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 stop finder configuration is managed in the sensor settings dialog.

Recommendation:

Start with the following settings in the stops finder:

• Minimum stop duration: 10 or the cycle time - whichever 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.

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

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.

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

Default: 10 seconds

Value threshold for when the sensor is stopped

Sometimes a line will not stop completely during a problem but run at a much lower speed. To take this scenario into account we have created a speed threshold for when the line is considered as stopped. The value threshold is taking in to account the sensor data multiplier, or if running batches the batch data multiplier.

Default: 0

⚠️ Setting the value threshold above 0 can result in positive speed loss in the OEE calculation because the stop duration used for the OEE calculation is not taking into account the pieces produced during the stop.

Stop Registration threshold in seconds

This threshold will define the minimum stop duration that we will prompt to the user in the register stop view. All stops with duration between the minimum stop duration and the stop registration threshold will be considered as micro stops.

Default: 60 seconds

Cycle time subtraction

If you have high cycle times or changing speeds on your line, activating Cycle Time Subtraction can help get more accurate downtime durations.

💡 Example If you have a Factbird on a line that counts 1 item every 5 minutes, and you have a 1 minute stop on the line, this will show up as a 6 minute stop in Factbird. With “Subtract Cycle Time” enabled, the first 5 minutes will be subtracted, so you’ll see a 1 minute stop

Cycle time subtraction works by subtracting the cycle time before determining whether there is a stop in Factbird. The cycle time is derived from the validated speed of the sensor/batch/product. That means that the stops finder automatically takes into account the cycle time of the product that is currently running in a batch.

 ⚠️ Please note that enabling cycle time subtraction on lines with high cycle time most likely requires reducing your stop registration threshold and minimum stop duration as these durations no longer have to take into account the cycle time of the line