When a project document is complete, you merge the document back to the plant using the same merge process as used with objects, such as tags. Documents can be merged to the plant singularly, in groups, or as part of a complete project. During the merge, the project document is reviewed and compared to the plant document. Any changes between the project document or files with the plant document or files that are in conflict can either be rejected or accepted.
For more information on the overall merge process, see Merging objects.
When a project document is finally merged to the plant, the previous plant document revision is superseded. For example, the document current revision A1 in a plant is revised to a project as working revision B1. You sign off the working revision B1 as the current revision B1 and merge it to the plant. In the plant, current revision B1 becomes the latest revision and current revision A1 is marked as superseded.
If the plant document has been revised to the next revision before a project document is merged, the merge revises the current document to the next available major revision. For example, the document current revision A1 is revised in the plant and signed off before the project working revision B1 is merged. This creates current revision C1 in the plant. Current revision A1 is superseded. When working revision B1 is signed off in the project as current revision B1 and merged to the plant, this creates the next available current revision D1 in the plant. Current revision C1 is superseded.
-
All project document revisions are terminated in the system after a merge.
-
Related items may be automatically merged depending on the relationship configuration in the schema.
-
For more information on the merge process, see Merging objects.
-
For more information on document revisions, see the Documentation life cycle.