Performance Drop Causes

Configuration

Configuration of performance drop causes is much like Stop Causes, only simpler. Your performance drop only needs a name, a color and an icon.

The big difference here with performances drop causes is how to answer the question "When to trigger a performance drop?" which is more complicated. Indeed, defining when to trigger an "OFF" event for a machine is simple: when the machine is OFF. But when do you consider that your performance is unsufficient compared to your goal? When you are producing at 25%, 50%, 75% or 95% of your goal? It all really depends on why you want to implement performances drop causes in your factory.

Knowing that, configuring them is very similar to Stop Causes. We can advice to use KPIs as variables to get the calculated live performance from 0 to 1 (percentage) directly from the app, for your machine.

Finally, it's important to note that performance drops will create more popups for your operator. With that, operator workload should be taking into account when configuring theses performance drops.