The following diagrams illustrate a typical process where data is moved from one domain to another.
-
Data is published from the tool into the data warehouse shared domain. A SmartPlant Foundation document is created and its data and view files attached. The document is also attached to a workflow that is used for approval and data loading.
-
As part of the workflow, there is an optional step to load the data into a sub-configuration in the tool domain. In here the data can be viewed and navigated and then approved (or rejected).
-
When the document is approved, the data contained in the attached files is then loaded in the tool specific domain into the appropriate configuration. In the example below, this is a Plant. When the consolidate task is run, a shared object is also created in the data warehouse domain and is related to the tool specific domain. Similar objects from other domains are also associated.
-
Other documents do not have to be loaded before they can be retrieved.
-
Once approved, a document can then be retrieved. For existing tool adapters, data is retrieved through a To Do List in the tool. For SmartPlant Foundation or a tool using the adapter, data is first retrieved into a design basis domain, and then, using compare functionality, a user can choose which data should then become part of the design.
-
The publish process can then be repeated once the design is complete.