<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=220094881825886&amp;ev=PageView&amp;noscript=1">
Skip to content
Create a support ticket
  • There are no suggestions because the search field is empty.

How to Code a Production Stop

Learn how to assign a Stop Reason to an uncoded production stop so that production losses are correctly recorded and analysed.

Coding a production stop means assigning a Stop Reason that explains why production was not running.

This helps keep production data accurate and makes it easier to understand where production time is being lost.

Code a production stop
  1. Open Operator Tools.
  2. Go to the Stops page where production stops are shown.
  3. Find the uncoded stop you want to update.
  4. Select the stop.
  5. Choose the Stop Reason that best describes why production stopped.
  6. Write a comment to clarify the stop reason, if necessary. 
  7. Confirm or save your selection.

The stop is now coded and will be included under the selected Stop Reason in reports and analysis.

Choosing the correct Stop Reason

Select the reason that most accurately describes the cause of the stop.

For example:

  • Machine breakdown
  • Material shortage
  • Cleaning
  • Setup or adjustment
  • Waiting for operator
  • Quality issue

The available Stop Reasons depend on how your Good Solutions environment has been configured.

Why coding stops is important

Correctly coding production stops helps your team:

  • Understand why production time is being lost
  • Identify recurring problems
  • Analyse Availability losses
  • Compare Stop Reasons and Stop Categories
  • Improve the accuracy of OEE and production reports
If you selected the wrong Stop Reason

If a stop has been coded incorrectly, you can open the stop again and re-code the stop reason.