Primavera Unifier: Administration — Lesson 4: Templates, Configuration Packages, Deployment, Audit, and Support

Learning Objectives

• Explain the architecture, workflow, or business purpose behind shell templates, BP templates, standards, and inheritance.
• Apply configuration package design, migration, dependency checks, and promotion and test, cutover, rollback, audit logs, and change documentation in a controlled scenario.
• Validate outcomes and troubleshoot risks involving performance, queues, failed workflows, support triage, and administration runbook.

Detailed Topics

• shell templates, BP templates, standards, and inheritance
• configuration package design, migration, dependency checks, and promotion
• test, cutover, rollback, audit logs, and change documentation
• performance, queues, failed workflows, support triage, and administration runbook

Instructor Demonstration

Demonstrate shell templates, BP templates, standards, and inheritance within a capital-project organization standardizing a controlled Unifier template from configuration through rollout and operations, 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 configuration package design, migration, dependency checks, and promotion and test, cutover, rollback, audit logs, and change documentation, then introduce and resolve an exception involving performance, queues, failed workflows, support triage, and administration runbook 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 shell templates, BP templates, standards, and inheritance, configuration package design, migration, dependency checks, and promotion, test, cutover, rollback, audit logs, and change documentation, performance, queues, failed workflows, support triage, and administration runbook 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 Templates, Configuration Packages, Deployment, Audit, and Support in a realistic Primavera Unifier: Administration scenario and validate the result with documented evidence.