Primavera P6 Professional Advanced Rel 21 — Lesson 4: Baselines, Earned Value, Risk Awareness, Reporting, and Project Recovery

Learning Objectives

• Trace how baselines, earned value, risk awareness, reporting, and project recovery changes data, application behavior, accounting, performance, or user experience.
• Configure a repeatable workflow with defined inputs, checkpoints, outputs, and exception paths.
• Defend functional correctness, access control, data quality, recoverability, and support readiness.

Detailed Topics

• Baselines
• Earned Value
• Risk Awareness
• Reporting
• Project Recovery
• requirements, ownership, prerequisites, data, and acceptance criteria for baselines, earned value, risk awareness, reporting, and project recovery
• security, controls, integration, performance, recovery, and support implications for baselines, earned value, risk awareness, reporting, and project recovery

Instructor Demonstration

Demonstrate baselines, earned value, risk awareness, reporting, and project recovery within a delayed engineering project that needs a defensible recovery schedule, optimized resources, and transparent variance reporting. Use representative data and capture project configuration, schedule-quality checks, multiple-float-path results, resource profiles, what-if comparisons, earned-value data, recovery options, and approved reports so another practitioner can independently verify the result.

Hands-On Exercise

Complete a controlled Primavera P6 Professional Advanced Rel 21 exercise focused on baselines, earned value, risk awareness, reporting, and project recovery. Introduce one realistic failure involving open ends, hard constraints, distorted float, overloaded resources, stale actuals, unsuitable baselines, optimistic recovery assumptions, and reporting inconsistency; 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 baselines, earned value, risk awareness, reporting, and project recovery 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 open ends, hard constraints, distorted float, overloaded resources, stale actuals, unsuitable baselines, optimistic recovery assumptions, and reporting inconsistency elsewhere in the process.

Validation Checklist

• Prerequisites, ownership, data context, settings, and expected outcomes are documented.
• The workflow is reproducible and supported by project configuration, schedule-quality checks, multiple-float-path results, resource profiles, what-if comparisons, earned-value data, recovery options, and approved 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 Baselines, Earned Value, Risk Awareness, Reporting, and Project Recovery in a realistic Primavera P6 Professional Advanced Rel 21 situation and defend the result with course-specific evidence.