Example 2.27: Auxiliary Resources and Alternate Resources
This example illustrates the use of Auxiliary resources. In the earlier
examples, the use of alternate resources enabled the allocation of
either John or Chris to the programming tasks. Now, suppose that each
of the programmers has a different tester, and whenever a particular
programmer is scheduled for a given task, his tester also needs to
allocate some part of his or her time, say 50 percent, to the same task. To
model such a scenario, specify Tester1 and Tester2 as
auxiliary resources for Chris and John, respectively. The
Activity and Resource data sets are printed in Output 2.27.1. Unlike the
earlier examples, all the activities are of fixed-duration.
Output 2.27.1: Auxiliary Resources: Input Data Sets
Plans & Reqts |
2 |
1 |
2 |
3 |
1 |
. |
. |
. |
. |
Product Design |
3 |
2 |
4 |
5 |
1 |
. |
. |
. |
. |
Test Plan |
3 |
3 |
6 |
7 |
. |
. |
. |
. |
. |
Documentation |
3 |
4 |
9 |
. |
1 |
. |
. |
. |
. |
Code |
10 |
5 |
8 |
. |
1 |
. |
. |
. |
. |
Test Data |
5 |
6 |
8 |
. |
. |
. |
. |
. |
. |
Test Routines |
5 |
7 |
8 |
. |
. |
. |
. |
. |
. |
Test Product |
6 |
8 |
9 |
. |
1 |
. |
. |
. |
. |
Finish |
0 |
9 |
. |
. |
. |
. |
. |
. |
. |
. |
altrate |
Programmer |
. |
1 |
1 |
. |
. |
. |
auxres |
Chris |
. |
. |
. |
0.5 |
. |
. |
auxres |
John |
. |
. |
. |
. |
0.5 |
12APR04 |
reslevel |
|
. |
1 |
1 |
1.0 |
1.0 |
|
The following statements invoke PROC CPM with the appropriate data sets
and resource variables. The resulting schedule is printed in
Output 2.27.2. Note the auxiliary resources that have been included in
the schedule corresponding to each primary resource: Tester1 whenever
Chris is used, and Tester2 whenever John is allocated.
proc cpm data=softaux out=sftaux rsched=rsftaux resin=resaux
date='12apr04'd interval=weekday resout=raux;
act act;
succ s1 s2;
dur dur;
res Programmer Chris John Tester1 Tester2 /
obstype=otype
period=per resid=resid
multalt rschedid=Activity;
id Activity;
run;
Output 2.27.2: Auxiliary Resources: Resource Schedule Data Set
1 |
|
|
2 |
. |
. |
12APR04 |
13APR04 |
12APR04 |
13APR04 |
12APR04 |
13APR04 |
1 |
Programmer |
FIXED |
2 |
. |
1.0 |
. |
. |
12APR04 |
13APR04 |
12APR04 |
13APR04 |
1 |
Tester1 |
FIXED |
2 |
. |
0.5 |
12APR04 |
13APR04 |
. |
. |
. |
. |
1 |
Chris |
FIXED |
2 |
. |
1.0 |
12APR04 |
13APR04 |
. |
. |
. |
. |
2 |
|
|
3 |
. |
. |
14APR04 |
16APR04 |
14APR04 |
16APR04 |
14APR04 |
16APR04 |
2 |
Programmer |
FIXED |
3 |
. |
1.0 |
. |
. |
14APR04 |
16APR04 |
14APR04 |
16APR04 |
2 |
Tester1 |
FIXED |
3 |
. |
0.5 |
14APR04 |
16APR04 |
. |
. |
. |
. |
2 |
Chris |
FIXED |
3 |
. |
1.0 |
14APR04 |
16APR04 |
. |
. |
. |
. |
3 |
|
|
3 |
. |
. |
14APR04 |
16APR04 |
14APR04 |
16APR04 |
21APR04 |
23APR04 |
4 |
|
|
3 |
. |
. |
19APR04 |
21APR04 |
19APR04 |
21APR04 |
06MAY04 |
10MAY04 |
4 |
Programmer |
FIXED |
3 |
. |
1.0 |
. |
. |
19APR04 |
21APR04 |
06MAY04 |
10MAY04 |
4 |
Tester2 |
FIXED |
3 |
. |
0.5 |
19APR04 |
21APR04 |
. |
. |
. |
. |
4 |
John |
FIXED |
3 |
. |
1.0 |
19APR04 |
21APR04 |
. |
. |
. |
. |
5 |
|
|
10 |
. |
. |
19APR04 |
30APR04 |
19APR04 |
30APR04 |
19APR04 |
30APR04 |
5 |
Programmer |
FIXED |
10 |
. |
1.0 |
. |
. |
19APR04 |
30APR04 |
19APR04 |
30APR04 |
5 |
Tester1 |
FIXED |
10 |
. |
0.5 |
19APR04 |
30APR04 |
. |
. |
. |
. |
5 |
Chris |
FIXED |
10 |
. |
1.0 |
19APR04 |
30APR04 |
. |
. |
. |
. |
6 |
|
|
5 |
. |
. |
19APR04 |
23APR04 |
19APR04 |
23APR04 |
26APR04 |
30APR04 |
7 |
|
|
5 |
. |
. |
19APR04 |
23APR04 |
19APR04 |
23APR04 |
26APR04 |
30APR04 |
8 |
|
|
6 |
. |
. |
03MAY04 |
10MAY04 |
03MAY04 |
10MAY04 |
03MAY04 |
10MAY04 |
8 |
Programmer |
FIXED |
6 |
. |
1.0 |
. |
. |
03MAY04 |
10MAY04 |
03MAY04 |
10MAY04 |
8 |
Tester1 |
FIXED |
6 |
. |
0.5 |
03MAY04 |
10MAY04 |
. |
. |
. |
. |
8 |
Chris |
FIXED |
6 |
. |
1.0 |
03MAY04 |
10MAY04 |
. |
. |
. |
. |
9 |
|
|
0 |
. |
. |
11MAY04 |
11MAY04 |
11MAY04 |
11MAY04 |
11MAY04 |
11MAY04 |
|
Copyright © 2008 by SAS Institute Inc., Cary, NC, USA. All rights reserved.