Comparing Workspaces, Portfolios, and Programs

In Primavera Cloud, workspaces, portfolios, and programs are used to manage sets of related projects. This enables users to monitor the status of the projects, view their data at the same time, facilitate budget or resource planning, and achieve benefits that are not available from managing the projects individually. The table below highlights the key similarities and differences between workspaces, portfolios, and programs. To view a list of pages that you can access for each object, see the Primavera Cloud Site Map (Oracle Primavera Cloud only).

 

Workspaces

Portfolios

Programs

What are these?

Workspaces represent the hierarchical structure of an organization's businesses, projects, or processes. Each workspace except the workspace at the highest level, known as the root workspace, can have additional child workspaces and projects with custom data sets and security. You can customize your workspace hierarchy with as many workspaces as necessary to suit the needs of your organization.

Workspaces are used to:

  • Store dictionary items that can be used in projects, portfolios, programs, ideas, and child workspaces.
  • Specify default configuration settings for each object in the workspace.
  • Manage user groups, permission sets, and security.

A group of related projects and programs whose health and status you want to monitor.

Portfolios are used to:

  • Monitor the health and status of related projects and programs.
  • Facilitate multi-year budget and resource planning for projects in the portfolio.
  • Track the respective projects against high-level metrics based on measures mostly aligned with the business strategy.
  • Ensure the right projects or programs are executed.

A group of projects that are related through a common business objective, outcome, and delivery.

Programs are used to:

  • Manage related projects to obtain benefits not available from managing them individually.
  • Break-up a very large, long duration project into smaller, more manageable projects that are managed and scheduled collectively.
  • Provide execution level grouping and tracking of projects.
  • Ensure projects are executed correctly.

 

What objects can they contain?

  • Projects
  • Portfolios
  • Programs
  • Ideas
  • Child Workspaces
  • Projects
  • Programs
  • Existing portfolios
  • A combination of projects, programs, and portfolios

Projects

Which workspaces can the objects belong to?

  • Root workspace represents the overall organization.
  • Production and Non-Production workspaces belong to root workspace.
  • All other child workspaces can either belong to production or non-production workspaces.

Projects, programs, and portfolios in a portfolio must belong to the same workspace as the portfolio or a child workspace.

Projects in a program must belong to the same workspace as the program or a child workspace.

How are the objects added?

Projects, portfolios, programs, ideas, and child workspaces can be added to any workspace that is created at the production or non-production level.

 

Projects are added to portfolios using filters, which can be set to refresh manually or automatically.

Programs can be added to portfolios either manually or by using filters.

Existing portfolios are added to portfolios manually.

Projects can be added to programs manually or by using filters.

 

 

Can an object belong to more than one workspace, portfolio, or program?

Projects, portfolios, programs, ideas, and child workspaces can only belong to one workspace at a time.

Projects, programs, and portfolios can belong to more than one portfolio at a time.

A project can belong to multiple programs at a time.

Who can view?

Workspaces can be accessed by any user with permission.

Portfolios can be accessed by any user with permission. A user with access to a project or program within the portfolio can view the project or program data.

Programs can be accessed by any user with permission.