PM Resource Leveling
PM Resource Leveling
PM Resource Leveling
Resources
Resource Loading
Example:
Programmer
160 hrs.
Systems Analyst
40 hrs.
Mainframe Computer 10 hrs.
Suppose
160 hrs
2 wks
= 80
hrs.
wk
hrs
wk
80
= 4
hrs
20programmer
programmers
wk
Project Network
A
End
Start
C
Activity
Immediate
Predecessors
Time
(weeks)
Resource
(Programmers)
---
---
---
---
D, F
B, G
E, 9
B, 8
C, 6
F, 7
G, 2
H, 1
D, 4
Key:
CP
9
10
11
Gantt Chart
A, 3
E, 9
B, 8
C, 6
F, 7
G, 2
H, 1
D, 4
1
24
22
20
18
16
14
12
10
8
6
4
2
16
F
11
G
B
A
1
10
11
24
21
So, 9 + 8 + 7 = 24
2
7
H
8
1
9
10
11
Resource Leveling
24
21
D
C
16
Suppose maximum number of
programmers available for
project in any given week = 12
G
B
A
2
week
H
8
1
10
11
Use trial and error, delay activities along their slack ties, check impact
on total required resources.
*For example, delay
A by 2 weeks
B by 4 weeks
E by 5 weeks
A*
E*
B*
10
11
12
Resource Leveling
Viola!
Project can be completed in 11 weeks with no more than
10 programmers per week
A*
E*
B*
Programmers
10
8
6
4
2
A*
E*
C
1
B*
G
2
10
11
10
8
6
4
2
A*
B*
E*
10 11
Multi-Project Scheduling
Project A
B
D
Tasks
C
E
F
B
D
Time
Project B
E
F
Time
Multi-Project Scheduling
24
22
20
18
16
14
12
10
8
6
4
2
Project A
Project B