Articles in this section

Why are my microstops not being recorded?

ANSWER

Microstops may not be recorded if Cycle Time Subtraction is enabled and the effective stop duration does not exceed the configured Minimum Stop Duration.

When Cycle Time Subtraction is enabled, Factbird deducts one full production cycle from the beginning of every detected stop. If the remaining stop duration is shorter than the Minimum Stop Duration, the stop is treated as normal production and is not registered as a stop or microstop.

 

ADDITIONAL DETAILS

For example:

  • Validated speed: 1.25 pcs/min
  • Cycle time: 48 seconds ( 60/validated speed)
  • Minimum Stop Duration: 50 seconds

With these settings, a gap between production signals must be at least 98 seconds (48 + 50 seconds) before Factbird registers a stop.

If production pauses for 75 seconds, Factbird subtracts the 48-second cycle time, leaving an effective stop duration of 27 seconds. Because 27 seconds is below the configured Minimum Stop Duration, no stop or microstop is recorded.

This behavior is expected and is designed to prevent the production cycle itself from being counted as downtime on lines with long cycle times.

 

LIMITATIONS (if applicable)

  • Cycle Time Subtraction reduces the effective duration of every detected stop.
  • Stops shorter than the configured Minimum Stop Duration after cycle time has been deducted are not registered.
  • If stop events are merged, the original stop records are overwritten and cannot be reviewed later.
     

Related Articles

 

Was this article helpful?
0 out of 0 found this helpful