In this mode, objects can be imported as is, keeping the original identifiers. It is then possible to send an object to another TopSolid PDM belonging to another client who can modify the object. Once modifications are complete, the object can be sent back.

Example: A main contractor exports a package (all documents are checked-in) and send this package to his subcontractor. The subcontractor imports this package with this command. He modifies documents, checks them in, exports the package and send it back to his main contractor. The main contractor imports the modified package by also using this command, all documents are recognized and will update original documents they are coming from.

Creation Stages / Use:

Click on TopSolid button > File and select Import project ... command or click icon in Home tab.

1. Select the package document (TopPkg) to import.

2. Select the vault into which the project will be imported.

3. Validate.

Additional information:

During this import as replication, TopSolid first verifies major revision to import and compare it to the possible equivalent major revision referenced in the vault. Different scenarios can apply at this stage:

• The major revision already exists in the vault:

- The life cycle status of the major revision in the vault is "design" -> update with the minor revision to be imported.

- The life cycle status of the major revision in the vault is "validated" -> update not possible, a new local revision must be created to be able to update it, which will then have a "design" status.

- The life cycle status of the major revision in the vault is "obsolete" -> update not possible, a new local revision must be created to be able to update it, which will then have a "design" status.

- The life cycle status of the major revision in the vault is "deleted" -> update not possible, a new local revision must be created to be able to update it, which will then have a "design" status.

• The major revision does NOT exist in the vault:

- The life cycle status of the latest major revision of the vault is "design" -> update by major revision of import and update of life cycle status of previous major revision.

- The life cycle status of the last major revision in the vault is "validated" -> update by adding the major revision to be imported.

- The life cycle status of the last major revision in the vault is "obsolete" -> update by adding the major revision to be imported.

- The life cycle status of the last major revision in the vault is "deleted" -> update by adding the major revision to be imported.

• Minor revision update:

- The revision to import is older or the same at the one currently in the vault -> no update to perform.

- The revision to be imported is more recent than the last revision in the vault without any conflict since no local change was done since the last export. -> import the new minor revision keeping its minor index.

- The imported revision in conflict with the changes done locally. -> the index of the imported minor revision becomes the max index of the last local minor revision + 1. The filename of the imported minor revision is updated in the workspace as well as all document references pointing to the imported minor revision and whose index had to be changed on account of the conflict.