Configure document management for a vault - SmartPlant Foundation - 2019 (10.0) - Installation & Upgrade

Distributed Server Setup for SmartPlant Foundation

PPMProduct
SmartPlant Foundation
PPMCategory_custom
Installation & Upgrade
SPFVersion_custom
2019 (10.0)

The configuration of a document management scheme for the vault is typically a choice of either:

  • Relating the vault to a plant or other configuration level (for example, the ConfigurationTop level or a project within a plant).

  • Relating the vault to one or more owning groups, where the owning group represents a set of users.

The configuration of these document management settings is performed using Desktop Client. The relationships can be established using drag-and-drop operations.

Your vaulting strategy can include relating vaults to particular object types or interfaces, as well as restricting the contents of vaults by associating a vault with particular object properties. For detailed information on vault configuration, see Vault configuration.

Plant configuration

When relating a vault to a plant or other configuration level, document objects that are associated with that configuration level are stored in the related vault. A vault that is related to a particular configuration item, such as a plant, can contain objects associated with sub-configurations below that level, such as projects related to a plant. Separate vaults can also be created for each sub-configuration level.

For example, a vault related to the ConfigurationTop level can act as a default vault, since objects related to all sub-configurations can be saved to that vault. While an object associated with a particular plant, such as PlantA, can be published to a vault related to ConfigurationTop, the object cannot be saved to a vault that is related to another configuration at the same level, such as PlantB, or to a project within another plant hierarchy.

Owning group

SmartPlant Foundation has two ownership relationships. You can configure an object to be owned by a user or by an owning group, which is why groups are more commonly referred to as owning groups. The link between users and owning groups is not a simple relationship; it is via the user's role.

Owning groups are typically configured to set up ownership of data by department or discipline.

Owning groups can be used to control the user’s access to an object or parts of an object based on its ownership. This control operates independently of domains and configurations, both within and across multiple domains and configurations. Access control by object ownership can be configured to control the following:

  • Shortcut menu command access (for example, check out of a document)

  • Menus and toolbar access (for example, for the process group)

  • Query access to objects (for example, documents)

In cases where an object might be placed in one vault because of its applicable configuration and another vault because of its relation to an owning group, the owning group relationship takes precedence over the configuration relationship. In this situation, the object would be stored in the vault that is associated with the owning group.