Knowing what caused stop events is important for production analysis and future planning. Reporting the reason can be done either in real-time, or retroactively.

Reporting stop event reasons is available in these four contexts:

  • The production module's Reporting Stop events log, which aggregates the stop events from all machines. There you can update multiple machines at once with the stop reason.

  • The department online dashboard, for a specific machine's events.

  • The selected machine's page Events tab.

  • The Reports module's history of a shift's events.


Reporting stop reasons for multiple machines

  1. Go to Production > Reporting Stop events.

  2. Select those events for which you want to enter the stop reason.

  3. Click the Report Stop Event control which is now visible (the control isn't visible until you select an event record from the list).

  4. In the Stop events dialog select the event group and event reason.

  5. Click Save.

walkthrough example of reporting multiple stop reasons using the Reporting stop events page

Reporting stop reasons for a specific machine from the Online dashboard

  1. Go to Production Floor > Department view and select the department from the drop-down list.

  2. In the Online tab, click the actions menu of the target machine and choose Report Stop Event.

  3. A list of all the machine's logged stop events will be displayed. Select those events for which you want to enter or change the stop reason to the reason you will soon set.

  4. Click the Report Stop Event control which is now visible (the control isn't visible until you select an event record from the list).

  5. In the Stop events dialog select the event group and event reason.

  6. Click Save.

walkthrough example of reporting a stop reason through the cube of a selected machine in the online dashboard

Reporting stop reasons for a specific machine from its Events tab

  1. Click the machine's name hyperlink (wherever you are in the system).

  2. In the machine's page, click the Events tab.

  3. A list of all the machine's logged stop events will be displayed. Select those events for which you want to enter or change the stop reason to the reason you will soon set.

  4. Click the Report Stop Event control which is now visible (the control isn't visible until you select an event record from the list).

  5. In the Stop events dialog select the event group and event reason.

  6. Click Save.

walkthrough example of reporting a stop reason by clicking the machine name and reaching its page

Reporting Stop events from System Reports

Note: When Reporting Stop events through System Reports you can go back in history to search for events. Inputting the stop reason in this context is done individually, for each event.

  1. Go to Reports > System Reports.

  2. Click index #4, History.

  3. Click index #26, the 5.01 Events in a shift report.

  4. Click Search (usually after applying search criteria).

  5. In the table of search results, click the index number of the event.

  6. In that event's page, first select the event group from the Event Group list and then the event reason from the Event list.

  7. Click Save Changes.

walkthrough example of reporting a stop reason through system reports history

Automation note for admins

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.

To activate it:

  1. Go to Setup > Site Configuration > index 5 (Step 5 - Define Machine Types).

  2. Click the index of the machine type.

  3. In the machine type's form click the Machines tab.

  4. Select the machine by clicking its index number.

  5. In the machine's form > General tab > Machine Stops section select the Classify Stop Event by Open Call check box.

  6. Click Save Changes.


Related articles

Opening service calls from stop events

Retroactive reporting of stop events

Reporting Stop Events via the Op App

Did this answer your question?