Why do so?

Knowing the reason for stop events is important for production analysis and future planning. Reporting the reason can be done either in real-time, as explained next and in the following sections, or retroactively (this is explained in a separate article).


Best practice: report the stop event when it happens

Stop events trigger a change in the machine/production line dashboard to present the options for reporting the reason (either as buttons or as tiles--you can change the display per your preference).

  1. The current event will be selected by default in the events panel. If the stop reason you're about to report applies to additional stop events, select them too since that will be most efficient.
    Tip: There are two event panel views to choose from per your personal preference. The line view's advantage is that you can see more events at once and also see a proportionate time representation of the stop events (red) and the working time (green) duration. Select events there by tapping their node.

  2. If there's a comment to add, tap the Add comment control to enter the comment that will be submitted with this event reason reporting.

  3. Select the stop reason from the applicable event group.
    Tip: You can use the search box to quickly locate the event group and reason.

  4. If you're prompted to add a comment, you can add information that will help others investigate this event.
    Tap SUBMIT to save this comment, or tab X to close the dialog without entering anything.

  5. A 'Success' confirmation will appear briefly, and the stop event will now have its reason shown in the event panel.

walkthrough example of reporting a reason for a logged stop event, showing both views for both the events panel and the stop reasons.

Use the Reported stop event widget

If you haven't reported the stop event reason when it happened, it's recommended to use the Reported stop event widget.

  1. In the Reported stop event widget tap REPORT.

  2. The events panel will be filtered automatically to show unreported stop events. Select the event(s) to which you need to apply the stop reason.

  3. If there's a comment to add, tap the Add comment control to enter the comment that will be submitted with this event reason reporting.

  4. Select the stop reason from the applicable event group.
    Tip: You can use the search box to quickly locate the event group and reason.

  5. Following the success message, the widget will update its data with the current information of how many minutes of the stop events are now accounted for with a reason. The progress bar indicates this proportionally.
    When all stop events have been reported the progress bar will be filled completely and the percentage will be 100%.

walkthrough of reporting stop event reasons using the widget

Report the stop event reason without being prompted

The stop-event reasons reporting screen can be closed manually through the close button ('X'), and it will close automatically when the tablet refreshes the data. To open it again for reporting a stop event reason, simply tap an event in the event panel and follow the steps in the best practice above.


Troubleshooting

Error message: "missing reports"

No stop event reasons were configured for this specific machine, so you will not be able to report stop event reasons.

Error message: "You are not allowed to report events on SETUP, please contact system administrator for more permissions"

If the machine was not configured to allow performing actions on setup events, you will get this message. These permissions need to be enabled in order to report reasons for setup events.

Only setup stop-reasons are shown, why is that?

When the machine is in setup state, for example in Working Setup, the only stop event reason group available is Setup.


Administration info

There's an optional system setting for auto-classifying stop events. If active, the stop reason reported when opening a service call is automatically assigned to all following stop events--up to the completion of the service call.


More training articles

Basic training program


Related articles

Operator App - Report Stop Reasons Screen (descriptions of the interface)

Retroactive reporting of stop events via the Op app (splitting stop events)

Opening service calls from stop events in the Operator app

Reporting Stop Events (Web app)

Retroactive reporting of stop events via the Web app

Color Coding Machines with Stop Event Reasons


Did this answer your question?