Documente Academic
Documente Profesional
Documente Cultură
ordered to draw up a disaster plan for assigning casualties to hospitals in the event of a serious
earthquake. For simplicity, we will assume that causalities will occur at two points in the city and will
be transported to three hospitals. It is estimated that there will be 300 casualties at point A and 200
at point B. Travel times to hospitals 1, 2, and 3 are 25, 15, and 10 minutes, respectively; from point B
they are 20, 5, and 15 minutes. Hospital capacities for emergency cases are 250, 150, and 150 patients.
How should the victims be assigned to hospitals to minimize the total time lost in transporting them?
The variables that the policy maker controls are the number of victims sent to each hospital to each site
(2 sites X 3 hospitals = 6 variables).
The constraints are the capacity of each hospital and the number of victims at each site.
The empty solver table looks like this if Xab represents number transported from site a to hospital b:
The weights in the objective function are the minutes per victim for each transportation option: 25, 10,
15, 20, 5, 15:
Site A 300, Site B 200, Hospital 1 250, Hospital 2 150, Hospital 3 150. Each variable contributes to the
hospital and site constraints of the entities at either end of the transport. These get a 1 in the table with
other entries being 0. The equations are
Document1 1 of 4 2018-04-14
Hospital 3 Capacity XA3 + XB3 ≤ 150
We set this up in solver for simplex-LP with the addition of integer constraints and non-negative
variables.
In other words, we send 150 victims from site A to hospital 1, none from that site to hospital 2, and the
other 150 to hospital 3. From site B we send 50 to hospital 1, 150 to hospital 2 and none to hospital 3.
REPORTS
Solver generates three reports (shown below).
Binding Constraints and Slack. From the Answer report, in addition to the information already
mentioned, we see which of our constraints are binding or not. In this case, the hospital 2 and 3
capacities are binding, as are the number of victims, but the capacity of hospital 1 is not. In other words,
this resource is not maxxed out by this situation but the others are. The slack value of 50 means that at
this optimal point there are 50 capacity units at hospital 1 that are not being used.
Allowable Increase/Decrease and Shadow Prices. For each variable and constraint, Solver gives us an
allowable increase and decrease. For variables, this represents how much the coefficient could change
(up or down) without changing the values of the variables in the solution (though it might change the
value of the objective function). In this case we see that XB2 could be infinitely higher or lower without
changing the solution. This means that the optimal solution is independent of the length of the trip from
site B to hospital 2.
The increase/descrease on the constraints is one measure of how sensitive the solution is to changes in
this constraint. In this case,
Document1 2 of 4 2018-04-14
All three hospitals’ capacity can increase by any amount without changing the solution but any decrease
in 2 or 3 would change it while hospital one could have up to 50 fewer slots without changing the
solution. The number of victims cannot increase without changing the solution but the number at site B
can be as low as 50 before the solution would change.
Finally, the shadow prices indicate the marginal cost of the constraint – telling us what change we can
expect for a one unit change in the value of the constraint. In the table below what we see is that a one
unit increase in hospital 2 or 3 capacity will result in a 15 minute savings in total transport time. An
increase in one victim at either site, though, will increase the total transport time (A by 25 and B by 20
minutes).
Document1 3 of 4 2018-04-14
Microsoft Excel 14.1 Answer Report
Worksheet: [hospital-transport-solver-solution.xlsx]Hospital Transport
Report Created: 10/17/2013 1:36:49 PM
Result: Solver found a solution. All constraints and optimality conditions are satisfied.
Solver Engine
Engine: Simplex LP Solution Time: 0.571563 Seconds. Iterations:
1 Subproblems: 0
Solver Options
Max Time Unlimited, Iterations Unlimited, Precision 0.000001
Max Subproblems Unlimited, Max Integer Sols Unlimited, Integer Tolerance 1%, Assume NonNegative
Document1 4 of 4 2018-04-14