Primavera P6 Professional Advanced Rel 19 Ed 1 — Lesson 4: Portfolio Views, Global Change, and Recovery Planning

Technical Scope

• layouts, filters, grouping, codes, and portfolio dashboards
• global change design, preview, safeguards, and controlled execution
• what-if copies, compression options, sequencing trade-offs, and recovery schedules
• executive report, schedule assurance checklist, rollback, and governance handoff

Instructor Demonstration

The instructor will troubleshoot and harden layouts, filters, grouping, codes, and portfolio dashboards in the context of a complex capital program requiring defensible schedule logic, resource decisions, performance forecasts, and recovery options. The demonstration captures commands, configuration, transactions, output, logs, plans, or screenshots that prove both the intended behavior and the control boundary.

Applied Workshop

Learners complete a controlled exercise covering global change design, preview, safeguards, and controlled execution and what-if copies, compression options, sequencing trade-offs, and recovery schedules, then introduce a realistic exception involving executive report, schedule assurance checklist, rollback, and governance handoff. They record assumptions, exact steps, expected and observed results, a reversible correction, and the evidence required for operational acceptance.

1. Confirm scope, identities, data, dependencies, controls, and expected result.
2. Perform the product-specific configuration, development, analysis, or business-process task.
3. Capture reproducible technical or transaction evidence and compare it with the expected value.
4. Explain the operational, security, performance, data-quality, or business trade-off.

Validation Standard

Acceptance for Portfolio Views, Global Change, and Recovery Planning requires the result to be reproducible, traceable to approved inputs, consistent with the relevant Oracle or platform behavior, and supported by checks for security, data integrity, reliability, performance, and recoverability.

• The intended target, scope, and ownership are verified.
• Expected-value and negative-path checks pass.
• Security, reliability, performance, data quality, and support impacts are reviewed.
• Unexpected behavior is resolved before acceptance.

Failure Analysis

When the result differs from expectation, learners isolate the smallest proven cause across layouts, filters, grouping, codes, and portfolio dashboards, global change design, preview, safeguards, and controlled execution, what-if copies, compression options, sequencing trade-offs, and recovery schedules; they avoid speculative production changes, preserve evidence, apply the lowest-risk correction, rerun the test, and document prevention.

Practical Outcome

Complete and defend a validated result for Portfolio Views, Global Change, and Recovery Planning with a reusable implementation record or runbook.