Copying and Moving Information between Plants
Some functionality has been developed to help move and copy information between plants. DC / PIM can assist with moving documents between Plants and the Plant Independent space otherwise, these functions are currently only available to SPF Administrators. Please consult with DC/PIM or file a support ticket to address your requirements.
Copying Documents to Another Plant (Authored Documents Only)
Documents are not allowed to have the same number within the different plants. This is to ensure that documents are never transmitted from different sources with different information. You are allowed however, to copy a document from one plant to another while generating a new number for the document. Using the Copy Doc(s) to Plant command, the last revision and version of documents can be copied to a new plant while generating a new document number for the objects. The documents created will be in a WORKING state and have their Receiving Organizations cleared.
1. After selecting the document(s) to copy. Use the Action Menu and select Copy Doc(s) to Plant from under Project: Action Menu -> Project -> Copy Doc(s) to Plant.
2. Specify the base information to generate the new document number(s). Be sure to specify the correct Rev, Stage and Phase.
3. Click the Copy button, the screen will update with the numbers generated for the documents.
Note that the Object History Tab on the Details Form of the object shows the history of where the object came from.
Moving Documents to Another Plant or Config Top (Authored Documents Only)
Documents can be moved between plants or even to config top (aka Plant Independent). Moving a document to config top means that it becomes visible to ALL plants which is particularly useful for standards. Note that documents are not to be created directly at config top, they need to be created within a plant that defines a specific numbering convention and then moved to config top.
Documents can be moved with or without associated transmittals. DC/PIM are restricted to move the document alone (without transmittals). When associated transmittals are included, all documents of the transmittal need to be included among the documents being moved or the relationship between the objects may not behave as expected.
-
Set your query scope to the plant where the information currently resides
-
Execute the move command: Action Menu -> Project -> desired move command
-
Select if transmittals should be included as the documents are moved
-
-
Confirmation of the objects and relationships affected is provided; additional feedback is provided using the View Details button
-
Only the configuration is changed; the revision state and receiving organizations remain unchanged.
Note that the Object History Tab on the Details Form of the object shows the history of where the object came from.
Note that with the exception of FBS code 000000 documents that are moved to Config Top fail to show the FBS code except within the scope in which they were created. This will be resolved in SPO when handed over.
Copying Tags to Another Plant
Tags can be copied to another plant either:
-
-
while generating a new name for the tag.
The copy can only be performed for one of these purposes at a time.
1. After selecting the set of tags to copy, use the Copy Tag(s) to Plant command: Action Menu -> Tag -> Copy Tag(s) to Plant
2. By default the ENS option is selected meaning that the system will generate new names for each tag. Unselect the ENS option if the tags should be copied using the same name.
3. Be sure to specify the correct Stage
4. Click Copy
5. The screen updates with the generated tag numbers
Note that the Object History Tab on the Details Form of the object shows the history of where the object came from.
