Previous Page

|

Next Page

Example 2.16: Using Supplementary Resources

In this example, the same project as in Example 2.15 is scheduled with a specification of DELAY=0. This indicates to PROC CPM that a supplementary level of resources is to be used if an activity cannot be scheduled to start on or before its latest start time (as computed in the unconstrained case). The schedule data and resource usage data are saved in the data sets WIDGO16 and WIDGRO16, respectively. They are displayed in Output 2.16.1 and Output 2.16.2, respectively.

  
    title 'Using Supplementary Resources'; 
    proc cpm date='01dec03'd interval=weekday 
             data=widgres holidata=holdata resin=widgrin 
             out=widgo16 resout=widgro16; 
       tailnode tail; 
       duration days; 
       headnode head; 
       holiday hol; 
       resource engineer engcost / period=per obstype=otype 
                                   cumusage 
                                   delay=0 
                                   delayanalysis 
                                   routnobreak; 
       id task; 
       run;
 

To analyze the results of the resource constrained scheduling, you must examine both output data sets, WIDGRO16 and WIDGO16. The negative values for Aengineer in observation numbers 22 through 25 of the Usage data set WIDGRO16 indicate the amount of supplementary resource that is needed on December 22, 23, 24, and 25, to complete the project without delaying any activity beyond its latest start time. Examination of the SUPPL_R variable in the Schedule data set WIDGO16 indicates that the activity, 'Prototype', is scheduled to start on December 22 by using a supplementary level of the resource engineer.

The supplementary level is used only if the activity would otherwise get delayed beyond L_START + DELAY. Thus, the activity 'Anal. Market' is delayed by five days (S_START = '15DEC03') and scheduled later than its early start time (E_START = '08DEC03'), even though a supplementary level of the resource could have been used to start the activity earlier, because the activity's L_START time is equal to '21JAN04' and DELAY = 0.

Further, note the use of the option CUMUSAGE in the RESOURCE statement, requesting that cumulative resource usage be saved in the Usage data set for consumable resources. Thus, for the consumable resource engcost, the procedure saves the cumulative resource usage in the variables Eengcost, Lengcost, and Rengcost, respectively. For instance, Eengcost in a given observation specifies the cumulative value of engcost for the early start schedule through the end of the previous day.

This example also illustrates the use of the ROUTNOBREAK option to produce a resource usage output data set that does not have any breaks for holidays. Thus, the output data set WIDGRO16 has observations corresponding to holidays and weekends, unlike the corresponding resource output data sets in Example 2.15. Note that for consumable resources with cumulative usage there is no accumulation of the resource on holidays; thus, the cumulative value of engcost at the beginning of the 7th and 8th of December equals the value for the beginning of the 6th of December. For the resource engineer, however, the resource is assumed to be tied to the activity in progress even across holidays or weekends that are spanned by the activity's duration. For example, both activities 'Drawings' and 'Write Specs' start on December 8, 2003, requiring one and two engineers, respectively. The 'Write Specs' activity finishes on the 12th, freeing up two engineers, whereas 'Drawings' finishes only on the 19th of December. Thus, the data set WIDGRO16 has Rengineer equal to '3' from 8DEC03 to 12DEC03 and then equal to '1' on the 13th and 14th of December. Another engineer is required by the activity 'Anal. Market' from December 15, 2003; thus, the total usage from 15DEC03 to 19DEC03 is '2'.