Shared Data
Shared data prevents the need to re-enter data in multiple areas and ensures consistent standards across an organization. In P6, enterprise data is managed at the administrative level in a single location. Standardized categories and values are configured and applied across all objects in the application. In Primavera Cloud, shared data is configured at individual workspace levels. Data that belongs to a particular workspace can be automatically or manually pushed down to the child workspaces and other objects within the workspace hierarchy. This ensures that the right data is available at the appropriate level. Data required by all levels of the organization should be configured at the root workspace level, whereas data intended for a specific workspace branch should be configured at the highest appropriate level of that branch. If a shared data category ever needs to be available to more workspaces, you can set its owning workspace to a higher level in the workspace hierarchy. Main objects like projects, portfolios, and programs inherit the defaults set at the parent workspace level when they are created. You can modify these defaults at the individual object level without affecting the parent workspace's settings.
In P6, enterprise data consists of global data such as currencies, project data such as baseline types and project calendars, and object-level configuration data for activities, resources, risks, issues, and documents. Primavera Cloud offers many of the same options at each workspace level in the form of dictionaries and object defaults. Dictionaries are repositories of items owned by the workspace which can be used by child objects without having to create them for each object. Examples of dictionaries include baseline categories, calendars, currencies, locations, and units of measure. Object default settings specify the default configurations of each object created in the workspace branch. Depending on the object, you can configure auto numbering and calculation settings, customize standard field labels, create configured fields (called "user defined fields" in P6), add codes, and specify custom forms and workflow processes. Examples of objects you can configure include main objects like projects and portfolios, but also subordinate objects like activities, budgets, risks, tasks, and WBS.
User access functionality such as user groups and permissions is also treated as shared data. For example, permission sets can be defined at a particular workspace level and will apply to users and user groups within that hierarchy. This is explained in more detail in Security.
See Terminology Differences for a list of P6 items that have been renamed in Primavera Cloud. See Transferable and Nontransferable Data for a list of P6 data that is not supported in Primavera Cloud.
Last Published Tuesday, May 21, 2024