Primavera P6 Advanced Rel 21 Ed 1 — Lesson 3: Resources, Roles, Costs, Leveling, Capacity, and Optimization

Learning Objectives

• Describe how resources, roles, costs, leveling, capacity, and optimization changes data, application behavior, accounting, performance, or user experience.
• Construct a repeatable workflow with defined inputs, checkpoints, outputs, and exception paths.
• Evaluate functional correctness, access control, data quality, recoverability, and support readiness.

Detailed Topics

• Resources
• Roles
• Costs
• Leveling
• Capacity
• Optimization
• requirements, ownership, prerequisites, data, and acceptance criteria for resources, roles, costs, leveling, capacity, and optimization
• security, controls, integration, performance, recovery, and support implications for resources, roles, costs, leveling, capacity, and optimization

Instructor Demonstration

Demonstrate resources, roles, costs, leveling, capacity, and optimization within a complex capital programme that must expose schedule risk, resolve resource conflicts, preserve baselines, and provide credible management forecasts. Use representative data and capture EPS and OBS assignments, schedule logs, constraint and float analysis, resource histograms, leveling results, baseline comparisons, earned-value indicators, and reports so another practitioner can independently verify the result.

Hands-On Exercise

Complete a controlled Primavera P6 Advanced Rel 21 Ed 1 exercise focused on resources, roles, costs, leveling, capacity, and optimization. Introduce one realistic failure involving invalid calendars, excessive constraints, broken logic, negative float, overallocated resources, misleading progress, uncontrolled baselines, and unreliable forecasts; isolate the cause, apply the smallest reversible correction, and rerun the acceptance checks.

1. Record the requirement, environment, identities, dependencies, data, controls, and expected result.
2. Perform the lesson workflow and capture evidence before and after each material change.
3. Test normal, boundary, failure, security, reconciliation, recovery, and operational conditions relevant to the topic.
4. Document the root cause, correction, rollback, owner, support action, and next improvement priority.

Scenario Analysis

• Separate mandatory business requirements from convenience requests and local workarounds.
• Evaluate data, security, control, usability, performance, integration, and audit trade-offs.
• Choose the smallest supportable change and define evidence for normal, boundary, and failure conditions.

Troubleshooting Guidance

When resources, roles, costs, leveling, capacity, and optimization does not produce the expected result, confirm scope, effective dates, identities, data context, dependencies, and recent changes. Review the Oracle-specific logs, reports, traces, calculations, workflow history, transaction status, or diagnostic output relevant to the lesson. Test one reversible hypothesis at a time and verify that the correction does not create invalid calendars, excessive constraints, broken logic, negative float, overallocated resources, misleading progress, uncontrolled baselines, and unreliable forecasts elsewhere in the process.

Validation Checklist

• Prerequisites, ownership, data context, settings, and expected outcomes are documented.
• The workflow is reproducible and supported by EPS and OBS assignments, schedule logs, constraint and float analysis, resource histograms, leveling results, baseline comparisons, earned-value indicators, and reports.
• Security, controls, data quality, integration, performance, recovery, and support conditions are reviewed.
• Exceptions, corrective action, rollback, approvals, monitoring, and handover are recorded.

Lesson Outcome

Learners can apply Resources, Roles, Costs, Leveling, Capacity, and Optimization in a realistic Primavera P6 Advanced Rel 21 Ed 1 situation and defend the result with course-specific evidence.