13.02.2013 Views

BOOKS OF RtfiDIfGS - PAHO/WHO

BOOKS OF RtfiDIfGS - PAHO/WHO

BOOKS OF RtfiDIfGS - PAHO/WHO

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

First, the policy that minimizes the total expected one-period cost was derived<br />

[5]. It was shown that this policy involves the following operaiions:<br />

(I) first allocate all available retention units so as to equalize the utilization<br />

rates at all HBB's;<br />

(2) then allocate all available rotation units (which are not subject to spoilage)<br />

so as to equalize the availability rates at ai1 HBB's.<br />

It was shown thait this pucicy is independent of the unit penalty. costs, and that is<br />

maximizes both the availability and the utilization of blood in the region, simultaneously.<br />

That is, any deviation froni the policy that would reduce utilization would also<br />

result in reduced availability for the next period, and vicc versa. It was next shown<br />

[6] that this policy was not only myopically optimal but also approximately optimal<br />

in the long run. Further, in a large number of cases that were tested by computer, the<br />

utilization and availability rates computed froni the myopic results also corresponded<br />

to the absoluite optimal values comnputed.<br />

This result established the principle that a distribution policy should seek to<br />

equalizc utilization rates and availability rates. This is also a policy that has thc<br />

essential elerents of "fairness' in equally spr!ading the nonavailability and<br />

nonutilization risks among hospitais regardless of their relative size and is consequently<br />

a highly defensible policy.<br />

Finally, it was shown that the highest possiblc regionil availability and utilization<br />

rates are achieved whcin the desired inventory level for each blood type in each<br />

HBB is at the value that minimizes the total number of rotational units that are<br />

required to achieve these availability and utilization rates.<br />

It is a straightforward effort by computer to calculate the combination of inventory<br />

level and schcduling factor that requires the minimum number of rotational<br />

units. The minimum number of rotational units required to achieve a fixed utilization<br />

rate of 98% and an availability rate of 95% are indicated by the points connected by<br />

the straight line segments in Figure 2. Thc irregular behavior of this solution is due to<br />

the fact that inventory levels must be integer values and rounding occurs on very<br />

small absolute values. As an example, the minimum rotational shipments required to<br />

an HBB of mean usage of 1.5 units daily to obtain the target goals above occur when<br />

the desired inventory is 5 units, and the scheduling factor is set to 0.67. The trend<br />

line which is drawn in the heavy line in Figure 2 is meant to indicate simultaneously<br />

the optimal values in inventory level and scheduling factor for given values of mean<br />

usage.<br />

Adding operational constrainis<br />

The above distribution model of equalizing availability rates and utilization<br />

rates among the HBB's is illustrated by the two curved lines in Figure 3. The upper<br />

curved line shows the minimum total shipments required to achieve a fixed<br />

availability rate at a HBB of a given mean usage. The lower curved line shows the<br />

maximum retention shipments to achieve a fixed utilization rate. The area between<br />

the curves would have to be met by rotational shipments. As can be seen from the<br />

right end of the curves where the tails meet, this results in a situation where the larger<br />

usage HBB's receive almost all of their shipments in older retention units, while the<br />

smaller usage HBB's receive almost all of their shipments in fresh rotation units.<br />

UITERFACES November 1979<br />

- 314 -

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!