Primavera P6 Advanced Rel 21 Ed 1 — Lesson 4: Baselines, Earned Value, Portfolio Analysis, Reporting, and Control

Learning Objectives

• Assess the Oracle objects, services, calculations, reports, interfaces, or code involved in baselines, earned value, portfolio analysis, reporting, and control.
• Operate a hands-on implementation or diagnostic sequence without bypassing governance or approvals.
• Resolve reproducibility by comparing expected and actual results and documenting corrective action.

Detailed Topics

• Baselines
• Earned Value
• Portfolio Analysis
• Reporting
• Control
• requirements, ownership, prerequisites, data, and acceptance criteria for baselines, earned value, portfolio analysis, reporting, and control
• security, controls, integration, performance, recovery, and support implications for baselines, earned value, portfolio analysis, reporting, and control

Instructor Demonstration

Demonstrate baselines, earned value, portfolio analysis, reporting, and control 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 baselines, earned value, portfolio analysis, reporting, and control. 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

• Map the end-to-end flow from source input through Oracle processing to the business output.
• Locate the control point where incorrect data, configuration, access, or integration could alter the result.
• Recommend preventive monitoring and an operational handoff with named ownership.

Troubleshooting Guidance

When baselines, earned value, portfolio analysis, reporting, and control 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 Baselines, Earned Value, Portfolio Analysis, Reporting, and Control in a realistic Primavera P6 Advanced Rel 21 Ed 1 situation and defend the result with course-specific evidence.