Primavera P6 Fundamentals Rel 19 Ed 1 — Lesson 4: Progress Updates, Data Date, Analysis, Layouts, Reports, and Closeout

Learning Objectives

• Explain the architecture, workflow, or business purpose behind status date, actual dates, remaining duration, units, and percent complete.
• Apply schedule update, recalculation, variance, critical path, and forecast and filters, grouping, layouts, reports, printing, and stakeholder views in a controlled scenario.
• Validate outcomes and troubleshoot risks involving issue review, change control, archive, lessons learned, and scheduler handoff.

Detailed Topics

• status date, actual dates, remaining duration, units, and percent complete
• schedule update, recalculation, variance, critical path, and forecast
• filters, grouping, layouts, reports, printing, and stakeholder views
• issue review, change control, archive, lessons learned, and scheduler handoff

Instructor Demonstration

Demonstrate status date, actual dates, remaining duration, units, and percent complete within a construction project schedule created, baselined, updated, analyzed, and communicated through a reporting cycle, then capture the exact configuration, command, transaction, report, model, query, code, or process evidence that proves the result for lesson 4.

Hands-On Exercise

Implement a controlled exercise covering schedule update, recalculation, variance, critical path, and forecast and filters, grouping, layouts, reports, printing, and stakeholder views, then introduce and resolve an exception involving issue review, change control, archive, lessons learned, and scheduler handoff while preserving before-and-after evidence.

1. Confirm the environment, identities, inputs, dependencies, risks, and expected outcome.
2. Complete the course-specific configuration, development, analysis, or process workflow.
3. Capture settings, commands, data, outputs, logs, reports, screenshots, calculations, or test results.
4. Compare the observed result with acceptance criteria and document corrective action.

Scenario Analysis

• Identify the technical or business decision that must be made.
• Compare valid approaches and their security, performance, reliability, cost, compliance, and support trade-offs.
• Define rollback, recovery, ownership, communication, and evidence requirements.

Troubleshooting Guidance

Diagnose issues across status date, actual dates, remaining duration, units, and percent complete, schedule update, recalculation, variance, critical path, and forecast, filters, grouping, layouts, reports, printing, and stakeholder views, issue review, change control, archive, lessons learned, and scheduler handoff without making an unverified production change. Separate symptoms from causes, gather evidence, test the smallest reversible correction, rerun validation, and record preventive action.

Validation Checklist

• The requirement, scope, inputs, dependencies, and expected result are documented.
• The result is reproducible and supported by course-specific evidence.
• Normal, boundary, failure, security, performance, and operational conditions are reviewed.
• Exceptions, rollback, ownership, and the next improvement priority are recorded.

Lesson Outcome

Learners can apply Progress Updates, Data Date, Analysis, Layouts, Reports, and Closeout in a realistic Primavera P6 Fundamentals Rel 19 Ed 1 scenario and validate the result with documented evidence.