Data Organization
Projects in P6 are organized using a hierarchical method called the enterprise project structure (EPS). The EPS enables you to group projects according to your organization's preferred structure, such as by company division, phase, geography, or project size. P6 also supports managing related projects using portfolios. The process for grouping and organizing projects and other data objects in Primavera Cloud is performed using workspaces. Similar to the EPS, workspaces organize projects hierarchically according to the structure determined by your organization. The top level of the workspace hierarchy consists of the root, or Company, workspace. The root workspace has two child workspaces, Production and Non-Production, which can be renamed and repurposed to suit your needs. Each workspace, except the root workspace, can have additional child workspaces. See the Workspaces section of the Primavera Cloud Help for more information.
It is recommended that you plan your workspace hierarchy carefully as the structure cannot easily be reorganized after you begin to enter project data. If neeeded, Primavera Cloud allows users with the Move Workspace permission to move a workspace to another workspace. For more information, see Considerations When Moving a Workspace to a Different Workspace in Primavera Cloud Help.
A simple hierarchical structure will make it easier to manage and maintain shared data and user security. It is not recommended that you replicate your existing P6 EPS in Primavera Cloud. However, if needed, you can create a project code that represents your P6 EPS structure and group your projects for migration by this code rather than by the workspace. Workspaces offer functionality that the EPS does not, such as shared data capabilities, direct assignment of security privileges, and support for additional data objects. Review these concepts below:
- Shared Data: Workspaces are the primary tool for the distribution of shared data, which is managed at individual workspace levels and applied to the hierarchies of objects within that workspace. Shared data includes item dictionaries, object defaults, and object settings. See Shared Data for additional information.
- Security: User security is configured by administrators at the workspace levels where users should have access. Security consists of user and user group access to objects and sets of permissions conferred to each user. Additional security options can be configured for each of the supported objects listed below. See Security for additional information.
- Supported Objects: Workspaces are containers for a variety of subordinate objects, each with their own set of tools and functionality. Each of the following objects can be opened in the context of its owning workspace. Only one object can be opened at a time within a single browser tab, but you can have different objects open simultaneously by opening them in separate browser tabs or windows.
- Workspace: Child workspaces are used to build out your organization's hierarchy of objects. All workspace levels support shared data, security, and object containment.
- Projects: Perform a wide range of project management functionality. Only one project can be open at a time within a single browser window.
- Portfolios: Develop and monitor related groups of projects, programs, and sub-portfolios. Use portfolios to monitor the health and status of a group of related projects. Perform multi-year budget and resource planning, track projects against metrics, and prioritize and evaluate projects for execution. The same project can belong to multiple portfolios.
- Programs: Programs include projects that are related and collectively contribute to the achievement of a program's outcomes and intended benefits. Manage multiple projects' data including costs, tasks, resources, risks, and schedules. The same project can belong to multiple programs.
- Ideas: Ideas are user-submitted goals or improvements that can be evaluated and turned into projects.
Last Published Tuesday, May 21, 2024