Before any schema can be utilized in SmartPlant Foundation, a domain must be configured to persist any objects that are created with that schema. For SmartPlant Foundation authoring, two domains are required, one to hold the authored data as it is created and one to hold the data in the data warehouse after it has been published. As described in the model sections above, schema classes are related to a domain through their component schema.
Remember that if you want to export the administration as a single file later, set the default container ID in the user preferences before you start.
Data warehouse domain configuration
Create a new domain for the data warehouse data.
-
Select a name for the domain, for example, PpmPEQL
-
Select DWShared as the domain environment – this ensures that when a user has access to the data warehouse through a role, they automatically have access to the new equipment list publish domain.
-
Select the Published domain group.
-
There is no need to select a domain type.
-
Drag and drop the data warehouse component schema loaded above onto the new domain.
Authoring domain configuration
You can either create a new authoring domain or use an existing one. Use a new one if you want to isolate the data like a separate application with its own user access or use an existing one if you are extending the functionality available to existing roles.
Once you have configured up multiple schema functionality in one domain you cannot
separate them by turning a domain off, only through user access.
-
Use a new domain if you want complete isolation of data.
-
This is most commonly done for different disciplines working on common data at different times in its lifecycle as each discipline can complete its work and publish to the enterprise. The process group can issue the data early on and continue to work on it while the mechanical group works in parallel. Overlapping publishes are not a problem as each discipline only publishes their own data.
-
This hides other authoring domains when working in this new one.
-
This separates the data by publish.
-
This means the only communication between this equipment list and other authoring activities is through publish and retrieve.
-
-
Use an existing domain to extend existing authoring capabilities.
-
This is done when a single discipline wants to manage the new data in the same process as some existing data.
-
The new data and the existing data are managed and published as a single package.
-
The user’s role access can still be configured to give separate access to components of this data using conditions and specific update methods and forms but it is all published as a single package.
If one discipline publishes the object, they publish the whole object which may include
data managed by another discipline and that they might not even be able to see. This
might result in releasing data that is not suitable unless strict review processes
are put in place.
-
Create a new domain for the authored data.
-
Do not select a domain environment – this is because role access to the authoring domain is controlled specifically by this domain.
-
Select the DATA domain group.
-
There is no need to select a domain type.
-
Find the SPFAUTHORING domain and drag and drop it onto the new domain. This builds the dependency between these domains such that when the authoring roles specify the new authoring domain, it also loads all the dependent core domains.
-
Drag and drop the authoring component schema loaded above onto the new domain.
Alternatively use an existing authoring domain.
-
Find the relevant domain, for example ProcessD, and drag and drop the authoring component schema loaded above onto the existing domain.