Primavera Unifier: Administration — Lesson 1: Company Workspace, Shells, Users, Groups, and Administration Structure

Learning Objectives

• Explain the architecture, workflow, or business purpose behind company workspace settings, administration modes, and environment structure.
• Apply shell types, project shells, hierarchy, numbering, and status and users, groups, partner organizations, licenses, and lifecycle in a controlled scenario.
• Validate outcomes and troubleshoot risks involving administration ownership, naming, access reviews, and configuration inventory.

Detailed Topics

• company workspace settings, administration modes, and environment structure
• shell types, project shells, hierarchy, numbering, and status
• users, groups, partner organizations, licenses, and lifecycle
• administration ownership, naming, access reviews, and configuration inventory

Instructor Demonstration

Demonstrate company workspace settings, administration modes, and environment structure 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 1.

Hands-On Exercise

Implement a controlled exercise covering shell types, project shells, hierarchy, numbering, and status and users, groups, partner organizations, licenses, and lifecycle, then introduce and resolve an exception involving administration ownership, naming, access reviews, and configuration inventory 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 company workspace settings, administration modes, and environment structure, shell types, project shells, hierarchy, numbering, and status, users, groups, partner organizations, licenses, and lifecycle, administration ownership, naming, access reviews, and configuration inventory 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 Company Workspace, Shells, Users, Groups, and Administration Structure in a realistic Primavera Unifier: Administration scenario and validate the result with documented evidence.