Resource Leveling vs Crashing

shift noncritical work within T F (C unchanged if T F respected)

Leveling moves activities that have float so the daily crew/equipment histogram is smoother without extending the project if total float is respected. Crashing shortens critical activities at extra direct cost. Resource-limited scheduling may extend duration.

$T F$ (d): Total float
$C$ (d): Project duration

Step-by-step solved example

Activity with TF=5 d needs 4 extra carpenters on days 3–4 that are already overloaded. Can you delay it 3 d to level without delaying the project?

Shift noncritical work inside total float so crews stay level.

1. Float
3 < 5, so yes: new TF=2 d, project C unchanged.

Answer: Yes — 3 d delay fits in 5 d float

10 practice questions

0/10 correct

1.Leveling that stays inside TF

2.If resources are strictly limited, the schedule may

3.Crashing should start with

4.A dummy has D=

5.Histogram leveling tries to cut

6.Free float is the delay that does not change

7.Parallel critical paths mean

8.Resource calendar (crew days off) can

9.Crash cost per day is

10.After you delay a noncritical activity, recompute