Job Shop Schedule Runs (tisch1100m000)

Use this session to manage Job Shop Schedule Runs.

Your Concept

Field Information

Site

The site ID.

Run Start Date

The date on which the schedule process started for the specified schedule run.

Plan Group

The plan group ID.

Run

The run ID.

The run ID consists of two parts to distinguish different runs calculated from the same input data.

  • A meaningful code based on a mask. (9 positions, including a counter)
  • A sequence that is controlled by LN.

If the run is based on new input data the sequence number is 01.

If the run is based on existing input data the sequence number is 02, 03 and so forth.

/

The iteration of the run.

Objective

Minimizing of maximal lateness of the production orders for which the scheduler is run.

Algorithm

The scheduler uses the earliest due date algorithm to generate run output.

Start State Empty

If this check box is selected, the changeover critical machine has all states empty at the start of the run.

If this check box is cleared, the last known state of the changeover critical machine is taken at the start of the run.

Time Fence Date

The time fence date defined in days.

Horizon Date

The date up to which production orders are considered for scheduling.

Actual Run

The time fence date calculated based on the calendar for the specified site.

Automatic Update Production Orders

If this check box is selected, production order planning is automatically updated with the results once the scheduler is run.

Run by

The employee responsible for generating the run.

Number of Orders

The total number of production order with the status Created, Printed, Released or Active within the time frame of the scheduler run.

If one or more operations of a production order have a start date within the time frame of the scheduler run the whole order is considered for scheduling. If an order doesn't have operations, the start date of the order is determining.

Production orders with the status Created and an end date before the time fence are considered to fall into the time frame of the scheduler run.

Number of Operations

The total number of machine operations of the production orders that are defined as within the time frame. An order operation without machine operations is considered as one machine operation.

Average Lateness

The lateness of an order is defined as the time difference between the due date and planned finish date using the site calender. The total days the order is late divided by the number of orders, expressed in whole days.

All operations of a production order are scheduled if one or more (machine) operation of the production order are in the time frame that is scheduled. The scheduler determines the due date for each (machine) operation and schedules accordingly.

Once scheduling is complete, (machine) operations can have a new planned finish dates which will influence the planned finish date of the production order

Input Total Changeover Time

The total changeover time sums up the changeover times of all machine operations in the schedule which are on a changeover critical machine capacity group.

Note: The setup time of a machine operation on a changeover critical machine consists of the fixed setup time as well as the changeover time.
Average Bottleneck Utilization

The sum of the utilizations of the machines divided by the number of machines, expressed as a percentage.

The machine utilization is calculated for the period of the time frame as:

Total number of Setup Hours (created, scheduled, active, completed)
+
Total number of Setup Hours (created, scheduled, active, completed)
/
Total number of available Machine Hours
-
Any applicable Time Out
Number of Conflicting Operations

The number of operations for which the planning could not be resolved.

Conflicts can be caused by:

  • Overlapping operations on a machine
  • A uncompleted operation within the time frame

The number of conflicts is an indicator how feasible the schedule is.

Creation Date

The date the scheduler run was generated.

Production Order Update
Production Orders Updated

If this check box is selected, the selected production orders were updated.

Time Fence

The time fence for the schedule run calculated from the creation date onwards.

Horizon

The time period for which LN schedules the production orders. The horizon is expressed in a number of working days.

Production orders with a start date after the horizon date are not included in the production schedule.

You can set the time fence for the plan group in the Scheduler Settings (tisch0140m100) session. You can start the session from the menu.

Note: You can only set scheduler settings for plan groups which are scheduler controlled.

The horizon is calculated from the creation date onwards.

Production Orders Updated by

The name of the employee who updated the production orders.

Run Finish Date

The date the scheduling run was finsihed.

Run Time (hh:mm:ss)

The duration of the run in hours, minutes, and seconds.

Objective
Minimize Maximum Lateness

The schedule run has as objective to minimize the maximum lateness with which the production orders are delivered.

Minimize Total Setup

The schedule run has as objective to minimize the total setup time for the machine capacity groups needed for the production of the order.

Algorithm
Earliest Due Date (EDD)

The algorithm calculates the scheduling run based on the earliest possible due date for the completion of the production order.

EDD, SST | EDD

The algorithm calculates the scheduling run based on the earliest possible due date rule for not changeover critical machine capacity groups and the shortest setup time rule for the changeover critical machine capacity group. The shortest setup time rules has the earliest due date rules as a tie breaker.

Predicted Orders Completed in Time

The numbers of orders that are on time or early divided by the total number of orders, expressed as a percentage.