When a machine (or workstation) that is expected to be running but instead it is off, it costs money instead of making it. Therefor minimizing the frequency and the duration of the stops is important. The reasons for the unexpected downtime can be various and can mostly not be blamed to the operator. This article is about Alert Tickets that allow to detect downtime.
The ticket system in M-Box can be used in 2 main ways to achieve the objective to minimize stop-time and duration:
When a machine is off for a certain time (default 3 minutes) the system registers it as an operational stop.
Stops with a duration longer than (default) 10 minutes trigger a ticket generation.
If (before the default time is elapsed) the reason for a stop is identified (via operator button on the M-Box or via the portal) a ticket is generated immediately.
All tickets need acknowledgement from the supervisor (any employee registered with supervisor role with an active equipment filter that includes that resource).
Tickets can also be generated manually by the supervisor. The manager with an equipment filter that includes that specific resource will have to acknowledge all tickets generated on that resource.
Notes on filters:
When the machine goes back to work, an unresolved ticket will be marked resolved.
If a tickets is manually marked resolved (supervisor) the machine status will be refreshed at the time of resolution
Note on orders:
Look up and filter status history:
Please leave the questions you have after reading this article, so that we may be able to improve our explanations for better understanding.
How useful was this post?
Click on a star to rate it!
We are sorry that this post was not useful for you!
Let us improve this post!
Tell us how we can improve this post?