Optimization of Delay Costs
Use
You can use the optimization to optimize the schedule according to the costs that are associated with the delayed completion of orders or activities. The following optimization criteria are available:
· The sum of the delay costs in the optimization horizon
· The maximum delay costs
There is a delay when:
· A receipt date/time is later than a requirement date/time
· The latest allowable start or finish date/time for an activity is before the actual start or finish date/time
The order priority and the duration of the delay determine how much the delay of a single order or activity costs. This is calculated as follows:
Delay costs = Costs dependent on priority x Duration of delay in seconds
You maintain the priority-dependent costs depending on the order priority. As the priority decreases, the costs must either decrease or stay the same. The order priority can be determined by the sales order, the planned independent requirement or – depending on the product – by the product master. Depending on the planning version, you specify in Model and Version Management the source of an order’s priority. An activity inherits the priority from the order. The system uses the duration of the delay in seconds to calculate the delay costs.
During optimization, in order to reduce delay costs, the system tries to schedule orders and activities that have a high priority with the smallest possible delay (if necessary, at the expense of orders and activities with lower priority for which greater delays are not so crucial).
Prerequisites
· You have defined the priority-dependent costs depending on the order priority in the optimization profile or when calling up the optimization on the Costs tab page. If you do not enter any costs, the system uses default values.
· You have weighted the delay costs in the optimization profile, on the Basic Settings tab page, in the objective function.
Features
When a receipt delivers several requirements with a delay, the system uses the biggest delay for this receipt for one of the requirements.
If you have defined in the optimization profile that the order validity represents a soft constraint for optimization, the system also evaluates violations of this validity as delays.