Study guide
4.2 Resource Leveling vs. Resource Smoothing
AACE Planning and Scheduling Professional PSP
Track your progress as you read
Finished sections get a check mark.
1 Chapter 0: Introduction & AACE PSP Exam Structure
0.1 Current AACE PSP Exam, Eligibility, and Certification Facts 0.2 Planning and Scheduling Professional Roles and Competencies 0.3 Cost Engineering and Scheduling Terminology per RP 10S-90
2 Chapter 1: Scope Definition & Planning Fundamentals
1.1 Work Breakdown Structure (WBS) Architecture & RP 33R-15 1.2 Organization & Resource Breakdown Structures (OBS, RBS, RAM) 1.3 Project Planning and Activity-Logic Development 1.4 Contract Requirements and Delivery Constraints 1.5 Stakeholder Identification, Needs, and Plan Review 1.6 Constructability Methods and Value Engineering 1.7 Resource Identification and Project Variables 1.8 Scope, Goals, Project Plan, and Phase Definition 1.9 Cost Breakdown Structure and Cost Estimate Development 1.10 Phase Relationships, Baseline Plan, Forecasts, and Risk/Recovery Planning
3 Chapter 2: Critical Path Method Mechanics & Network Logic
2.1 Activity Definition and Logic Relationships 2.2 Activity Durations, Productivity, and Work Calendars 2.3 Forward and Backward Pass Mathematical Mechanics 2.4 Float Calculations and Critical-Path Identification
4 Chapter 3: Advanced Network Techniques & Schedule Constraints
3.1 Schedule Constraints and Their Impact on Dates and Float 3.2 Advanced Logic Modeling: Ladders and Fragnets 3.3 Schedule Levels of Detail and Schedule Basis Documentation 3.4 Schedule Scope and Schedule Specification 3.5 Breakdown-Structure Relationships and the Cost Estimate Model 3.6 Stakeholder Feedback and Types of Schedules 3.7 Activities, Milestones, Schedule Quality, and Basis Documentation
5 Chapter 4: Resource Management & Leveling
4.1 Resource Planning, Allocation, and Histograms 4.2 Resource Leveling vs. Resource Smoothing 4.3 Cumulative Resource S-Curves & Productivity Tracking
6 Chapter 5: Baseline Management & Schedule Updating
5.1 Baseline Establishment, Forecasts, and Controlled Revision 5.2 Progress Measurement and Data Date Mechanics 5.3 Out-of-Sequence Logic: Progress Override vs. Retained Logic 5.4 Schedule Update Review and Quality Verification per RP 53R-06 5.5 Cost/Resource Management, Schedule Change, and Feedback 5.6 Acceleration and Recovery Scheduling per RP 54R-07 5.7 Control Schedules, Variance Analysis, Forecasts, and Management Summaries
7 Chapter 6: Schedule Risk Analysis & Monte Carlo Simulation
6.1 Schedule Risk Principles, Risk Drivers, and Three-Point Estimates 6.2 Monte Carlo Simulation, Criticality, Correlation, and Merge Effects 6.3 Risk Outputs, Confidence Dates, Sensitivity, and Contingency
8 Chapter 7: Earned Value & Earned Schedule Management
7.1 Earned Value Foundations: PV, EV, AC, and Variances 7.2 Traditional EV Performance Indices & Late-Project Quirks 7.3 Earned Schedule (ES) Theory, SV(t), and SPI(t) 7.4 Independent Schedule Forecasting & IEAC(t)
9 Chapter 8: Forensic Schedule Analysis & Delay Claims
8.1 Delay Classification, Criticality, and Contract Questions 8.2 RP 29R-03 Taxonomy, Data Validation, and Method Selection 8.3 TIA, Windowed Analysis, and Subtractive Models 8.4 Concurrency, Pacing, and Float: Technical Analysis Before Entitlement
10 Chapter 9: Executive Communication & Practical Scenario Applications
9.1 Official PSP Memo Writing Framework 9.2 Structured Technical Problem-Solving for PSP Scenarios 9.3 Current Exam Strategy and Core Calculation Review
4.2 Resource Leveling vs. Resource Smoothing
Key Takeaways Explain This Topic AI
Resource Leveling (resource-constrained scheduling) enforces strict resource availability limits as hard constraints, resolving over-allocations by shifting activities beyond their late dates even if the project completion milestone is extended.
Resource Smoothing (time-constrained scheduling) optimizes resource utilization strictly within existing total float, evening out peaks and valleys without extending project completion or delaying contractual commitments.
Scheduling software uses priority heuristics during forward-pass leveling, most commonly Minimum Total Float (Early Late Finish), Shortest Duration, and Greatest Resource Demand, to decide which competing activities receive resources first.
Leveling establishes a Resource Critical Path (RCP) that links activities through both physical precedence logic and resource transfer dependencies (phantom logic), invalidating traditional unconstrained float values.
Activity splitting mathematically resolves temporary resource spikes by pausing and resuming tasks, but introduces significant physical penalties including demobilization/remobilization costs, concrete cold joints, and loss of learning curve momentum.
Last updated: October 2026
4.2 Resource Leveling vs. Resource Smoothing
AACE Professional Context: One of the most frequently tested distinctions on the AACE Planning and Scheduling Professional (PSP) examination is the technical difference between Resource Leveling and Resource Smoothing . While lay practitioners often use these terms interchangeably, in rigorous cost engineering and project controls they represent fundamentally opposing optimization constraints. Leveling prioritizes resource availability limits over completion time, whereas smoothing prioritizes completion time over resource demand. Schedulers must understand how these methods interact with project float, how leveling alters critical paths into Resource Critical Paths (RCP), and the operational hazards of activity splitting.
The Core Distinction: Leveling vs. Smoothing
The fundamental divide between Resource Leveling and Resource Smoothing centers on which project parameter is treated as a hard constraint (inviolable) and which is treated as a soft constraint (flexible).
- Technical Attribute Resource Leveling Resource Smoothing
- Formal Scheduling Term Resource-Constrained Scheduling (RCS) Time-Constrained Scheduling (TCS)
Hard Inviolable Constraint Resource Availability Ceiling ( L t L_t L t ): Demand must never exceed available supply under any circumstance. Project Completion Date ( T project T_{\text{project}} T project ): Contractual milestones and final project completion must never slip.
Soft Flexible Parameter Project Completion Date: The completion date is allowed to extend as far into the future as necessary to resolve bottlenecks. Resource Utilization Profile: Over-allocations are resolved only to the extent permitted by float; residual peaks may remain.
Float Mechanics Consumes all available float; delays activities beyond their original Late Dates ( L S / L F LS/LF L S / L F ); creates new critical paths. Shifts non-critical activities strictly within their available Total Float ( T F TF TF ) and Free Float ( F F FF FF ) .
Completion Date Impact Project completion date frequently extends. (Schedule lengthens). Project completion date NEVER extends. (Schedule length is preserved).
Over-Allocation Resolution 100% of over-allocations are resolved. Peak resource demand is capped at or below the threshold limit. Partial resolution. Only over-allocations on paths with sufficient float are eliminated; bottlenecks on critical paths remain.
Primary Application Fixed-capacity environments: remote mining sites, offshore rigs, shutdown turnarounds with fixed camp bed capacities. Fixed-deadline environments: commercial contracts with heavy liquidated damages, regulatory compliance deadlines, retail openings. [UNCONSTRAINED SCHEDULE (OVER-ALLOCATION)]
- Peak Demand
- ┌───────────┐
- │ Over-Cap │
- ─────────────┼───────────┼───────────── [Resource Limit]
- │ Base Load │
- ─────────────┴───────────┴─────────────► Time
- │
- ┌─────────────────────────────┴─────────────────────────────┐
- ▼ ▼
- [RESOURCE LEVELING] [RESOURCE SMOOTHING]
- Limit is a HARD ceiling - Project End Date is a HARD wall
- Activities pushed out - Activities shifted ONLY within float
- Project Duration EXTENDS - Project Duration CANNOT extend
- Limit Limit
- ──────────┬───────┬──────── ──────────┬───/\───┬──────── (Peak may breach)
- │ Level │ │ Smooth│
- ──────────┴───────┴───────► Time ──────────┴───────┴────────► Time
- ▲ ▲
- [LATER FINISH DATE] [SAME FINISH DATE]
Important
PSP Exam Rule of Thumb: If an algorithm resolves an over-allocation by pushing an activity beyond its late start date and causes the project completion milestone to slip, it is Resource Leveling . If the algorithm moves activities without extending the completion date, it is Resource Smoothing .
Algorithmic Priority Heuristics in Resource Leveling
Resource leveling is a computationally complex problem. In mathematics and computer science, finding the absolute optimal sequence that minimizes project duration under multi-resource constraints is proven to be NP-hard (non-deterministic polynomial-time hard). Exact analytical optimization is practically impossible for real-world project networks containing thousands of activities and dozens of shared resource pools.
Consequently, all major commercial scheduling software engines (e.g., Primavera P6, Microsoft Project, Asta Powerproject) utilize heuristic forward-pass simulation rules to resolve resource contentions. When multiple activities compete for the same scarce resource on a given working day, the leveling engine applies a defined Priority Rule to determine which activity receives the resource and which activity must wait.
The Standard Priority Heuristics
Minimum Total Float (Smallest Slack / Early Late Finish):
Mechanism: The activity with the smallest positive total float (or earliest Late Start / Late Finish date) is given first priority to the resource. Activities with larger float are delayed.
Engineering Rationale: This is the most widely utilized and mathematically defensible heuristic in project controls. Prioritizing activities with the least float minimizes the likelihood and magnitude of overall project completion delays.
Early Start Date (First-Come, First-Served):
Mechanism: The activity that was logically eligible to start earliest in the forward pass receives priority.
Engineering Rationale: Preserves the natural chronological build sequence of the project, though it may occasionally delay near-critical activities in favor of non-critical tasks that started earlier.
Shortest Activity Duration:
Mechanism: The competing activity with the shortest duration is scheduled first.
Engineering Rationale: Based on queuing theory ( Shortest Processing Time First ). Rapidly clearing short tasks frees up the resource pool quickly for larger, subsequent activities.
Greatest Resource Demand / Intensity:
Mechanism: The activity that requires the highest number of resource units per day is given priority.
Engineering Rationale: Prevents resource-heavy "monster" activities from being repeatedly postponed to the end of the project where they cannot be accommodated.
Activity Priority Codes (User-Defined Ranking):
Mechanism: Planners manually assign numerical priorities (e.g., Priority 1 = Top, Priority 10 = Low) based on external operational risks, permitting windows, or commercial milestones.
Engineering Rationale: Gives the project controls team direct governance over software decision-making for strategic project components.
The Resource-Constrained Critical Path (Resource Critical Path - RCP)
In classical CPM mechanics, the critical path is strictly defined as the longest continuous chain of logically linked activities from project start to finish, characterized by zero (or minimum) total float. This definition assumes that precedence arrows represent physical construction sequencing (e.g., foundations must cure before structural steel is erected).
When a schedule is leveled under resource constraints, this classical definition breaks down, giving rise to the Resource Critical Path (RCP) .
Phantom Dependencies (Resource Transfer Logic)
Consider two activities on completely separate physical branches of a project network:
Activity X (Turbine Foundation Excavation): Located in the power block.
Activity Y (Retention Basin Excavation): Located 1,000 meters away in the offsites area.
Physically, there is zero engineering logic connecting Activity X and Activity Y; they can proceed concurrently. However, if the project has only one large excavator , the leveling engine will force Activity Y to wait until Activity X finishes.
This introduces a Resource Transfer Dependency (often termed a phantom dependency or soft logic tie ):
Activity X (Power Block) → Resource Transfer: Excavator Activity Y (Retention Basin) \text{Activity X (Power Block)} \xrightarrow{\text{Resource Transfer: Excavator}} \text{Activity Y (Retention Basin)} Activity X (Power Block) Resource Transfer: Excavator Activity Y (Retention Basin) [PHYSICAL CPM NETWORK (Unleveled)] [RESOURCE-LEVELING RESULT (Leveled)]
- Path 1: Act X (Excavate Power Block) Path 1: Act X (Excavate Power Block)
- │
- ▼ [Resource Dependency: Excavator]
- Path 2: Act Y (Excavate Retention Basin) Path 2: Act Y (Excavate Retention Basin)
- (Independent, parallel paths) (Paths serialized by shared resource!)
- Structural Properties of the Resource Critical Path
Mixed Logic Chains: The RCP is composed of a hybrid sequence of physical engineering dependencies (FS, SS, FF) and resource-driven transfer dependencies.
Invalidation of Traditional Float: In an unconstrained network, total float is calculated as T F = L S − E S TF = LS - ES TF = L S − ES . In a leveled schedule, this mathematical value is misleading. An activity may appear to have 15 days of traditional float based on physical successors, but it has zero real float because delaying it would starve a downstream task of its required crew, causing project completion delay. The true float is Resource Total Float (RTF) .
Forensic significance: If credible resource constraints drove sequence, a delay analysis should test those resource effects rather than rely only on an unconstrained logic path. RP 29R-03 does not impose one universal resource-critical-path method; the contract, records, and chosen analysis protocol control. An owner delay to an activity that holds a driving resource can delay the entire project, even if that activity was technically "non-critical" in the original unconstrained logic network.
Activity Splitting Mechanics and Operational Hazards
During resource leveling, schedulers can enable a software parameter known as Activity Splitting (or Activity Preemption ).
How Activity Splitting Operates
When an in-progress activity encounters a resource shortage—or when a higher-priority task requires the same resource—the leveling engine pauses (splits) the lower-priority activity.
The activity's remaining duration is held in suspension while its assigned resources are temporarily reassigned elsewhere.
Once the higher-priority task completes and resources become available again, the split activity resumes execution. UNSPLIT: [===== 8 Continuous Days =====]
- SPLIT: [== 3 Days ==] ... [PAUSED: 4 Days] ... [===== 5 Days Remaining =====]
- ▲ ▲
- Demobilize Re-mobilize
- Resources Resources
- When Activity Splitting is Legitimate
Splitting is acceptable for non-continuous, easily interrupted tasks:
Software development, engineering drawing production, or administrative submittal preparation.
Off-site modular fabrication where pieces can sit in staging yards without deterioration.
Broad earthworks grading where equipment can be redirected between borrow pits without technical harm.
Severe Operational Risks and Hazards of Splitting
On industrial, infrastructure, and commercial construction projects, indiscriminate activity splitting creates severe operational disruption:
Setup and Demobilization Penalties: Re-mobilizing equipment is costly and time-consuming. If an activity requiring a 250-ton crane is split, the contractor incurs crane teardown, relocation, and re-rigging costs, along with re-inspection of rigging tackle.
Physical Quality Degradation: Many construction operations cannot tolerate work stoppages without destroying structural integrity:
Concrete Pours: Splitting a continuous structural foundation pour results in an unapproved cold joint , compromising the shear strength and watertightness of the structure.
Welding Operations: Pausing heavy-wall alloy pipe welding requires cooling, re-heating (preheat/PWHT cycles), and extensive non-destructive re-examination (radiography/ultrasonic testing).
Trench Excavation: Leaving an open trench split for two weeks risks sidewall collapse, water accumulation, and safety violations under OSHA trenching standards.
Productivity Degradation (Learning Curve Decay): When a crew is pulled off an active installation, they lose their daily rhythm, trade momentum, and tooling setup familiarity. Upon resumption, the crew suffers a learning curve reset, burning more hours to complete the remaining scope.
Subcontractor Delay and Disruption Claims: In fixed-price or unit-rate subcontracts, contractors base their bids on continuous, uninterrupted access to the workface. If a prime contractor repeatedly splits a subcontractor's activities to reassign shared equipment, the subcontractor will file commercial claims for idle labor, equipment standby, loss of productivity, and extended overhead .
Warning
Exam Trap Alert: A question may propose enabling activity splitting to resolve resource over-allocations without extending project duration. PSP candidates must recognize that while splitting is mathematically elegant in software, it is frequently prohibited by contract specifications (e.g., USACE UFGS 01 32 01) due to mobilization costs, quality risks, and subcontractor claim liabilities.
Worked Example: Step-by-Step Leveling with Minimum Total Float
Consider an industrial mechanical contractor executing piping modifications during plant operations. Two concurrent activities compete for the same scarce resource: Certified High-Pressure Rigging Crews .
Project Parameters
Available Resource Capacity: Exactly 1 Rigging Crew available per day.
Timeline: Both activities are logically ready to execute starting on Day 10 .
Activity 101 (Set Heat Exchanger E-101):
- Duration = 3 working days
- Resource Requirement = 1 Rigging Crew/day
- Early Dates: ES = Day 10, EF = Day 13
- Late Dates: LS = Day 10, LF = Day 13
Total Float ( T F TF TF ) = L S − E S = 10 − 10 = LS - ES = 10 - 10 = L S − ES = 10 − 10 = 0 days (Critical Path)
Activity 102 (Erect Flare Knockout Drum Platform):
- Duration = 4 working days
- Resource Requirement = 1 Rigging Crew/day
- Early Dates: ES = Day 10, EF = Day 14
- Late Dates: LS = Day 16, LF = Day 20
- Total Float ( T F TF TF ) = L S − E S = 16 − 10 = LS - ES = 16 - 10 = L S − ES = 16 − 10 = 6 days
- Step 1: Detect Resource Contention
On Days 10, 11, and 12, both Activity 101 and Activity 102 demand 1 Rigging Crew. Total Demand = 1 + 1 = 2 crews > 1 crew available (OVER-ALLOCATION) \text{Total Demand} = 1 + 1 = 2\text{ crews} > 1\text{ crew available (OVER-ALLOCATION)} Total Demand = 1 + 1 = 2 crews > 1 crew available (OVER-ALLOCATION)
Step 2: Apply Priority Heuristic (Minimum Total Float)
The leveling engine evaluates the competing tasks on Day 10 using the Minimum Total Float rule:
Activity 101 has T F = 0 TF = 0 TF = 0 days.
Activity 102 has T F = 6 TF = 6 TF = 6 days.
Decision: Activity 101 has smaller float ( 0 < 6 0 < 6 0 < 6 ). Activity 101 receives the Rigging Crew on Day 10. Activity 102 must be delayed.
Step 3: Forward Pass Simulation
Activity 101 Executes: Operates from Day 10 through Day 13. The crew is fully utilized.
Activity 102 Waits: Delayed from Day 10 until Day 13 when Activity 101 releases the rigging crew.
Activity 102 Resumes: Starts on Day 13 and finishes on Day 17 ( 13 + 4 = 17 13 + 4 = 17 13 + 4 = 17 ).
Step 4: Evaluate Impact on Float and Project Duration
Delay Incurred by Activity 102: Shifted from Day 10 to Day 13 (a 3-day delay).
Float Consumption: Activity 102 had 6 days of total float. Consuming 3 days of float leaves: Remaining Total Float = 6 − 3 = 3 days \text{Remaining Total Float} = 6 - 3 = 3\text{ days} Remaining Total Float = 6 − 3 = 3 days
Project Completion Date Impact: Because Activity 102 still has 3 days of positive float remaining upon completion at Day 17 (its late finish was Day 20), the project completion date did NOT slip by a single day .
Classification: This successful resolution represents Resource Smoothing within available float .
Contrast Scenario: Resource Leveling with Schedule Extension
What if Activity 102 also had T F = 0 TF = 0 TF = 0 days?
Delaying Activity 102 by 3 days would immediately force its Late Finish from Day 14 to Day 17, extending project completion by 3 working days .
This secondary scenario represents Resource Leveling (Resource-Constrained Scheduling) .