Primavera P6 EPPM, The Full Ecosystem Components
Mastering Primavera P6 EPPM
An Administrator’s Guide to Core Structures & Management
The P6 EPPM Ecosystem
Primavera P6 EPPM is more than a single application; it’s a suite of tools operating across distinct layers. Understanding this architecture is the first step for any administrator, as it clarifies how data flows from user interfaces down to the database and back out through reports and analytics.
Application Layer
User interaction points like P6 Web, P6 Professional, Mobile Apps, and Team Member interfaces.
Functional Layer
The core engine for planning, scheduling, resource management, reporting, and administration.
Database Layer
The P6 EPPM database and a separate reporting database that stores and secures all enterprise project data.
The Twin Pillars: EPS & OBS
The entire P6 environment is built upon two fundamental hierarchies: the Enterprise Project Structure (EPS) and the Organizational Breakdown Structure (OBS). The EPS organizes projects, while the OBS organizes the people responsible for them. A logical and often parallel design of these two structures is the key to effective project management and security.
Enterprise Project Structure (EPS)
A hierarchy used to organize all the projects within your enterprise. Think of it as a folder system for your projects, allowing for roll-up reporting and logical grouping.
Example:
- All Initiatives
- Engineering & Construction
- Information Technology
- System Upgrades
- New Development
Organizational Breakdown Structure (OBS)
A hierarchy of managers responsible for the projects in the EPS. The OBS is the primary mechanism for controlling user access to projects and their data.
Example:
- CEO
- VP of Operations
- Chief Information Officer
- Director of Infrastructure
- Director of Applications
User Access Control
User access isn’t just about a login; it’s a combination of their position in the OBS and the specific permissions granted by Security Profiles. This ensures users only see and modify the projects they are responsible for.
Organizational Roles & Responsibilities
Different roles are required to successfully deploy and maintain a P6 environment. The P6 Application Administrator is central, but collaborates with IT, Database, and Project Management teams. This chart highlights the primary focus for each key role.
A Structured P6 Implementation
Implementing P6 successfully is a structured process. It begins with understanding business needs and establishing clear processes before defining the technical environment. Each step builds upon the last to create a robust and effective project management system.
Assess Needs & Establish Policies
Define the organization’s project management goals, processes, and governance policies before any technical setup.
Define Core Structures
Build the foundational EPS, OBS, and Resource hierarchies that reflect the organization’s structure.
Configure Enterprise Data & Settings
Establish enterprise-wide standards like calendars, codes, and application-wide settings for consistency.
Establish User Access
Create user accounts, define security profiles, and assign users to the OBS to control project access.
Define Services & Reporting
Set up automated services (like scheduling and summarizing) and configure reporting and team member contribution methods.
Enterprise Data Categories
Enterprise Data provides the standards and structure for centralized project and resource management. This data is available to all projects across the organization and is divided into several key categories, each managed by the P6 Administrator.