Stop Production

Explanation

This activity is used to register that an ongoing production has been stopped for one or several shop order operations.

To stop production from Shop Floor Workbench select the operation(s) to stop and click Stop Production. You can also select the operation in Shop Floor Workbench, click Operation Guide and then click Stop Production.

In Stop Production dialog:

• Select an appropriate option in the Stop Reason drop-down. When selecting stop reason Interrupted, an interruption cause must be entered in the Interruption Cause field. If the interruption cause has been connected to a park reason, you can enable the Park option to launch the Park Shop Order dialog.
• When stopping labor time in anonymous reporting mode, you can optionally edit the crew size.
• If you stop production for an operation started in sequence with others (sharing the same clocking sequence), time will be stopped for all operations in the same sequence.
• Operations connected to an operation block is expected to be stopped together. You are still allowed to stop them individually, but a warning will be given.

To stop production when approving the operation, select the operation, click Approve and enable the Stop Clockings option.

To stop setup from the Time Clock client:

• Click Stop Production and enter the Employee or Team.
• Enter the Operation to start time for. You can select only operations started by the employee or team.
• If you want to stop the machine runtime clocking also, select Yes in Machine Time.
• If you want to report an interruption, select an interruption cause, else leave the field empty.
• If you want to close the operation select Yes in Close Operation.
• Note: Depending on the Time Clock configuration, some of these fields may be automatically filled with default data and thereby the fields may be disabled or unavailable for editing.

This activity contains a Security Checkpoint which can be activated by an administrator. With an activated security checkpoint on a function you will have to authenticate yourself again in order to fulfill the function. Additionally, whenever a security checkpoint is successfully passed a security checkpoint log is written, creating an audit trail of what is done.

Prerequisites

The production (runtime) must have started on the operation.

System Effects

• The started production will be stopped for the selected operation and all operations with the same clocking sequence.
• The stop time will be recorded on the clocking record(s). The clockings can be viewed in the Clockings tab. 
• If Stop Reason is set to Interrupted an interruption clocking will be created with the start time same as the stop time of the runtime clocking.
• If the selected Interruption Cause is connected to a park reason, and the Park option is enabled, the Park Shop Order dialog will appear assumed the operation is stopped from the Shop Floor Workbench page.
• If the selected Interruption Cause is connected to a downtime cause, a machine downtime clocking will be started for the work center resource running the operation, assuming that it does not perform any other operation.
• If the selected Interruption Cause is connected to an indirect job, an indirect labor clocking will be started for each employee running the operation assuming that he/she does not perform any other operation. If the site is configured to report labor time anonymously, no indirect clocking will be started.
• The status of the operation is set to either Partially Reported or Interrupted depending on the selected Stop Reason.
• Transactions are created in operations history:
  • The total time is calculated and one transaction per clocking and operation is created in operation history.
  • Time is calculated as: Stop Time - Start Time; calendar consideration
  • For Machine Time the work center calendar is used.
    • If the Calculate Actual Resource Share option is enabled for the work center, the resource share is calculated with regards to other overlapping clockings for the work center resource. If the option is disabled, the planned resource share from the shop order operation is reported.
  • For Labor Time either employee HR schedule or a calendar will be used:
    • If the person connected to the employee is not defined as a resource in a labor class, the employee HR schedule will be used if a valid schedule exists, otherwise the calendar for the primary labor class of the shop floor employee.
    • If the person connected to the employee is defined as a resource in a labor class, and if Use HR Schedule is enabled on the person resource, the HR schedule will be used.
    • If Use HR Schedule is disabled, the person resource calendar will be used. To avoid hard stops for the operator when reporting, the calendar of the labor class will act as the last resort if Use HR Schedule is enabled, but no valid schedule is found and no resource calendar is defined for the person either.
    • Depending on the site settings either all time, only calendar time or calendar and overtime is included.
    • In anonymous reporting mode, the crew size defined in the start dialog will be saved on the labor transaction and used in the cost calculation.
    • In employee reporting mode, one transaction per employee is created and the crew size is calculated with regards to other overlapping clockings for the employee.
    • The total time on the operations started at the same time (with the same clocking sequence) will be proportionally divided among the operations according to the remaining runtime for each shop order operation.
      • Example: three operations have 10, 15, and 22 remaining minutes (total of 47 minutes), and in total 62 actual minutes are reported.
        • 10/47x62=13.1915
        • 15/47x62=19.7872
        • 22/47x62=29.0213
        • 13.1915 + 19.7872 + 29.0213 = 62

Pages

Shop Floor Workbench
Time Clock

Activity Diagrams

Report Operations from Time Clock
Report Operations from Shop Floor Workbench