The container of an object or relationship is just a convenient label used to group together sets of objects and relationships. Each of the source SmartPlant Foundation build files have a different container so that all objects and relationships loaded from a single file have the same container. All the schema and administration objects and relationships delivered with the system have a container ID that users can view on the object details and relationship forms.
The container can be any string, but typically is made up of two strings connected with a full stop. The first part represents a larger grouping or layer of the configuration, and the second part represents a specific bit of functionality within that layer. For example:
-
Core.DocControl
-
Core.DocMgt
-
PlantAndProject.WBS
When creating new objects and relationships, the container is set to the one specified in the user preferences.
When setting up a new security configuration, it is good practice to identify all
the objects and relationships by a suitable container. Choosing a container for each
role or access group is often most helpful.
Various export options are available to export the system configuration by container including the multi-select Export Data shortcut menu option.
Containers segment components of the SmartPlant Foundation configuration. SmartPlant Foundation is built from sets of files. Each object and relationship can have a containerID; this is used to separate the data into sub-groups.
Usually, the following have containerIDs:
-
ADMIN and SCHEMA (domains).
-
Reference Data (for example, classification trees).