I'll use a simple example to illustrate what I am trying to do:
Given a 5 task project. R1 and R2 each have 100% available units.
1) Start Duration = 0d
2) T1 Duration = 1d, Pred = Start, Resource = R1 (100%)
3) T2 Duration = 1d, Pred = Start, Resource = R1 (100%)
4) T3 Duration = 1d, Pred = Start, Resource = R2 (100%)
5) End Duration = 0d, Pred = T1, T2, T3
Without resource leveling, all tasks are critical (no slack).
When you level the resources (assume T1 has higher priority than T2), T1 &
T3 start on Day 1, T2 starts on Day 2. T2 is now the only task that is
critical, T1 & T3 each have 1 day of slack. BUT, if T1 slips, because of
resource constraints, T2 will slip. So T1 acts like it has no slack.
A PM that just followed the CPM used by project would think T1 could be
delayed by 1 day and not affect the project when in actuality, a delay in T1
will delay the project end date. I want to know which tasks that if delayed,
will cause the project to be delayed. To get this info, you could go in and
put hard links to represent the resource constraints (i.e. make T1 a pred of
T2), but that is a lot of extra work for a decent size project
Cris