In SmartPlant Foundation, each document consists of three parts, a master, a revision, and a version. The supplied Data Validator adapter for SmartPlant Foundation server allows the export of documents to the Data Validator target system using the export mapping for document revisions and masters.
-
The import mapping does not have versions, so a version is automatically created for each revision when exported.
-
When documents are exchanged between EPCs and Owner Operators, documents may need to have matching version numbers in both the systems. You can use the SPFDocVerion property in your import mapping to specify the version number in your CSV file. A document version will be created in the target system with the version number specified in the CSV file.
-
To map version object properties in the target system, you must map the properties to the revision class definition in the staging system. These properties are instantiated only on the version object in the target system.
The relationships attached to revisions, as shown in the previous mapping image, are all mandatory and must be exported with the revisions. The SPFPrimaryClassification is also mandatory for a document master, and any master must have at least one SPFDocumentRevisions relationship. When the target system has properties or relationships that need to be exported, the document version can be exported by mapping it to the revision. In this case, the target system adapter for SmartPlant Foundation puts those properties and relationships onto the latest version of the document revision.
The export mapping must export a revision and the SPFDocumentRevisions relationship
to the document master, or the revisions cannot be under the same document master
for processing.
The following diagram shows how the target system adapter creates a revision and a version from the revision sent to the target system:
For information on documents using concurrent engineering, see Documents with concurrent engineering.