Optimization Run
You started the
optimization run interactively (for example, in the DS planning board)
or in the
production planning
run.
The system executes the following steps during the optimization run, as long as the maximum runtime specified in the optimization profile is not exceeded. As soon as the time limit is exceeded, the system terminates the optimization run, even if no solution was found.
...
1. The system executes pegging and converts the pegging relationships that lie partially or completely within the optimization range into time relationships or requirements dates. This provides hard or soft constraints for the optimization; that is, it limits the possible scheduling dates.
2. The system evaluates the time relationships between the activities. (Time relationships are defined in the production process model or in the iPPE process structure.) Relationships between activities that are not fixed represent hard constraints for the optimization. The system converts the relationships to fixed activities into earliest and latest start and finish dates for the non-fixed activities. The earliest dates represent hard constraints for the optimization. You can specify for the latest dates whether they are hard or soft constraints.
3. The system executes a consistency check.
4.
The system
optimizes the schedule in the optimization range
based on the specified objective
function, while considering all the constraints. To do
this, it varies the dates and the
resource
allocation for the activities. Optional: In the optimization, the
system can execute a campaign
optimization with a special objective function.
5. Optional: The system executes backward scheduling in which it tries to schedule the activities that were scheduled too early closer to the requirement dates.
6.
The system saves
the optimized schedule either in the planning version (
production planning
run) or in the simulation version (production planning run,
DS planning
board), depending on where you started the optimization.