For all connected digital sensors, Factbird offers an automatic stop detection algorithm, which can be customized to the cycle time of the individual line/machine (see above). Every identified downtime can then be reasoned for using PLC tags, if an integration is in place, or through manual user input of the operators using pre-defined stop reasons.
Stop Causes are linked to color codes as well as stop cause categories. The stop cause categories serve as a folder structure for stop causes so that operators can more easily navigate to the stop cause they are looking for. Additionally, in the analytics, line issues can be sorted and analyzed by stop cause categories.
The color codes serve to identify which type of OEE time loss the stop cause is associated with. There are four colours and based on Factbird’s definition, those should be used as described in the above illustration; however, customers do have the freedom to define the meaning of each color and attach stop causes as they see fit.
In case of an unregistered downtime, the field will automatically be marked bright red to draw the operator's attention to the UI (see Graphic below). The operator searches for the matching stop cause, clicks on it, and then a pop-up window will open, where there is the option to key in a comment and to split the stop in order to attach different reasons to different time spans. After confirming the registration, it is completed.