| The CPM Procedure |
Example 2.17: INFEASDIAGNOSTIC Option and Aggregate Resource Type
The INFEASDIAGNOSTIC option instructs PROC CPM to continue scheduling
even when resources are insufficient. When PROC CPM
schedules subject to resource constraints, it stops the
scheduling process when it cannot find sufficient resources
(primary or supplementary)
for an activity before the activity's latest possible start time
(L_START 
DELAY).
In this case, you may want to determine
which resources are needed to schedule all the activities and when the
deficiencies occur. The INFEASDIAGNOSTIC option is equivalent to
specifying infinite supplementary levels for all the resources under
consideration; the DELAY= value is assumed to equal the default
value of +INFINITY, unless it is specified otherwise.
The INFEASDIAGNOSTIC option is particularly useful when there are several resources involved and when project completion time is critical. You want things to be done on time, even if it means using supplementary resources or overtime resources; rather than trying to juggle activities around to try to fit available resource profiles, you want to determine the level of resources needed to accomplish tasks within a given time frame.
For the WIDGET manufacturing project, let us assume that there are four resources: a design engineer, a market analyst, a production engineer, and money. The resource requirements for the different activities are saved in a data set, WIDGR17, and displayed in Output 2.17.1. Of these resources, suppose that the design engineer is the resource that is most crucial in terms of his availability; perhaps he is an outside contractor and you do not have control over his availability. You need to determine the project schedule subject to the constraints on the resource deseng. Output 2.17.2 displays the RESOURCEIN= data set, RESIN17.
Output 2.17.1: Data Set WIDGR17Output 2.17.2: Resourcein Data Set RESIN17
In the first invocation of PROC CPM, the project is scheduled subject to resource constraints on the single resource variable deseng. Output 2.17.3 displays the resulting Schedule data set WIDGO17S, which shows that the project is delayed by five days because of this resource. The project finish time has been delayed only by five days, even though R_DELAY='10' for activity 'Write Specs'. This is due to the fact that there was a float of five days present in this activity.
proc cpm date='01dec03'd interval=weekday
data=widgr17 holidata=holdata resin=resin17
out=widgo17s;
tailnode tail;
duration days;
headnode head;
holiday hol;
resource deseng / period=per obstype=otype
delayanalysis;
id task;
run;
Output 2.17.3: Resource-Constrained Schedule: Single Resource
|
Now suppose that you have one production engineer available, but you could obtain more if needed. You do not want to delay the project more than five days (the delay caused by deseng). The second invocation of PROC CPM sets a maximum delay of five days on the activities and specifies all four resources along with the INFEASDIAGNOSTIC option. The resource availability data set (printed in Output 2.17.2) has missing values for the resources mktan and money. Further, the resource money is defined to be a consumable aggregate resource (its value is '4' in the first observation). Thus, this resource is used by the CPM procedure only for aggregation purposes and is not considered as a constraining resource during the scheduling process. The INFEASDIAGNOSTIC option enables CPM to assume an infinite supplementary level for all the constraining resources, and the procedure draws upon this infinite reserve, if necessary, to schedule the project with only five days of delay. In other words, PROC CPM assumes that there is an infinite supply of supplementary levels for all the relevant resources. Thus, if at any point in the scheduling process it finds that an activity does not have enough resources and it cannot be postponed any further, it schedules the activity ignoring the insufficiency of the resources.
proc cpm date='01dec03'd interval=weekday
data=widgr17 holidata=holdata resin=resin17
out=widgo17m resout=widgro17;
tailnode tail;
duration days;
headnode head;
holiday hol;
resource deseng prodeng mktan money / period=per obstype=otype
delayanalysis
delay=5
infeasdiagnostic
cumusage
rcprofile avprofile;
id task;
run;
The Schedule data set WIDGO17M (for multiple resources) in Output 2.17.4 shows the new resource-constrained schedule. With a maximum delay of five days the procedure schedules the activity 'Anal. Market' on January 21, 2004, using an extra production engineer as indicated by the SUPPL_R variable. Note that the SUPPL_R variable indicates the first resource in the resource list that was used beyond its primary level. Note also that it is possible to schedule the activities with only one production engineer, but the project would be delayed by more than five days.
The Usage data set, displayed in Output 2.17.5, shows the amount of resources required on each day of the project. The data set contains usage and remaining resource information only for the resource-constrained schedule because PROC CPM was invoked with the RCPROFILE and AVPROFILE options in the RESOURCE statement. The availability profile contains only missing values for the resource money because it was used only for aggregation purposes. Further, since this resource is a consumable resource as per the RESOURCEIN= data set, and since the CUMUSAGE option is specified, the value for Rmoney in each observation indicates the cumulative amount of money that would be needed through the beginning of the date specified in that observation if the resource constrained schedule were followed.
For the other resources, the availability profile in the Usage data set contains negative values for all the resources that were insufficient on any given day. This feature is useful for diagnosing the level of insufficiency of any resource; you can determine the problem areas by examining the availability profile for the different resources. Thus, the negative values for the resource availability profile Aprodeng indicate that, in order for the project to be scheduled as desired, you need an extra production engineer between the 21st and 27th of January, 2004. The negative values for Amktan indicate the days when a market analyst is needed for the project.
Output 2.17.4: Resource-Constrained Schedule: Multiple Resources
|
Output 2.17.5: Resource Usage: Multiple Resources
|
Copyright © 2008 by SAS Institute Inc., Cary, NC, USA. All rights reserved.