Primavera P6 to Oracle Primavera Cloud:
The EPS vs. Workspaces
Author: Kari Jackson, PMP, PMI-ACP
Are you planning to migrate from Primavera P6 to Oracle Primavera Cloud (OPC)? While it might seem straightforward to replicate your P6 setup in OPC, understanding the core differences between the two platforms is essential for designing an effective OPC environment. Let’s explore the distinctions between P6’s Enterprise Project Structure (EPS) and OPC’s Workspaces to help you make informed decisions.
Core Organizational Structures
Both Primavera P6 and Oracle Primavera Cloud rely on foundational frameworks to manage projects and control data access. In P6, the Enterprise Project Structure (EPS) serves as a hierarchical system, much like a digital filing system, grouping projects by shared attributes. The EPS, paired with the Organizational Breakdown Structure (OBS), organizes projects and ensures users have appropriate access to data and functionalities within those projects.
In Oracle Primavera Cloud, Workspaces take on this organizational role. Workspaces are containers for various objects, such as projects, programs, portfolios, and ideas. These structures are critical to the functionality of their respective platforms, and their design should align with your organization’s specific needs and the platform’s capabilities. Understanding how EPS and Workspaces differ is key to determining whether your P6 EPS structure can seamlessly translate to OPC Workspaces.
Data Management: P6 vs. OPC
Primavera P6 categorizes data as either Enterprise or project-specific. Enterprise data is globally accessible across all projects and users, while project-specific data is confined to individual projects and not shared. This creates a binary approach to data availability.
In contrast, Oracle Primavera Cloud eliminates global or enterprise-level data. Instead, data is managed at the workspace level, offering greater flexibility to standardize data dictionaries based on organizational requirements. Each data dictionary is owned by a single workspace and can optionally be inherited by child workspaces or projects. These dictionaries include elements like calendars, cost breakdown structures, project/activity codes, and resources, and they can be defined at any workspace or project level.
Key Considerations for OPC Workspaces
When designing your OPC Workspaces, the primary question is: How should data be standardized or shared, and at what level? Unlike P6’s all-or-nothing data model (global or project-specific), OPC allows for granular control, enabling you to tailor data standardization to specific business needs at various levels of the workspace hierarchy.
What’s Next?
If you’re interested in learning more about how OPC manages resources compared to P6, stay tuned for our next post, where we’ll dive deeper into resource management in Oracle Primavera Cloud.
Give Us a Call!
Call us at (985) 781-9190 to speak with an Oracle-certified representative to learn more.
