When we switch to the evolutionary solver, we are very likely to find improve-
ments. Recall that there is some built-in randomness and the evolutionary solver
does not necessarily stop with the same solution each time. In addition, the developers
of the evolutionary solver offer the following advice for producing solutions.
†
Restart the evolutionary solver, using the solution it produced on the first run, to
see if an improvement can be found.
†
Restart the evolutionary solver with changes in the Convergence value (tighter)
or the Tolerance value (tighter, if it’s not already zero).
†
Restart with a larger Population Size parameter and/or a larger Mutation Rate
parameter. These changes will result in longer runs, and they tend to examine a
larger number of candidate solutions.
†
Switch to the nonlinear solver and see whether it can produce an improvement.
Finally, some insight may come from examining Solver’s Population Report. Stability
in the Best Values and relatively small Standard Deviations are signs to look for. Those
signs suggest little room for improvement.
Using just the first of the listed suggestions, and restarting Solver a few times, we
are likely to encounter a solution that is significantly better than those found with the
nonlinear solver. For example, the evolutionary solver may find the objective function
value of 217.61 at a plant location of (87.33, 53.43). By using the evolutionary solver,
Drezner can find a location that improves on the solution generated by the nonlinear
solver. If the distance metric is a good proxy for annual distribution expenses,
Drezner will be able to reduce its expenses more than 13 percent by using the evol-
utionary solver, as compared to the decisions it would have reached using the non-
linear solver.
9.6. LINE BALANCING
The line-balancing problem arises in the design of a new production process for
assembled products. Examples might include home appliances (refrigerators), elec-
tronics (televisions), light vehicles (lawn mowers), and automobiles. At the end of
the product design phase, the product and its components are well known, and so
are the specific tasks that must be carried out to make the product. The next step is
to design the production line on which the product will be assembled.
The first type of information is the time required for each task. Required times
might be based on previous experience with the same task in other lines or estimated
by experts in work measurement techniques. The second type of information is pre-
cedence information. In other words, we need to know which tasks must be completed
before some other task can begin. We say, “task j precedes task k” to mean that k
cannot begin until j is completed. Precedence information can be expressed in a list
or in a diagram.
The production line typically has a target output rate—so many units per hour.
The cycle time is the inverse of the output rate. For example, if we specify a target
of five units per hour, the cycle time is 1/5 of an hour, or 12 minutes.
354
Chapter 9 Heuristic Solutions with the Evolutionary Solver