Primavera P6 Professional Project Management Rel 19 Ed 1 — Lesson 3: Resources, Costs, Baselines, and Plan Approval

Technical Scope

• resource and role dictionaries, rates, assignments, and workload review
• expenses, budgeted units, time-phased cost, and profile interpretation
• baseline creation, assignment, comparison, and controlled plan approval
• resource conflicts, budget checks, plan narrative, and authorization evidence

Instructor Demonstration

The instructor will analyze and reconcile resource and role dictionaries, rates, assignments, and workload review in the context of a new infrastructure project moving from enterprise setup through a controlled status cycle and stakeholder report. 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 expenses, budgeted units, time-phased cost, and profile interpretation and baseline creation, assignment, comparison, and controlled plan approval, then introduce a realistic exception involving resource conflicts, budget checks, plan narrative, and authorization evidence. 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 Resources, Costs, Baselines, and Plan Approval 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 resource and role dictionaries, rates, assignments, and workload review, expenses, budgeted units, time-phased cost, and profile interpretation, baseline creation, assignment, comparison, and controlled plan approval; 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 Resources, Costs, Baselines, and Plan Approval with a reusable implementation record or runbook.