Overview

Coexistence scenarios enable data exchange scenarios between an OEM and a Supplier. The following is an example:

For the following context,

• OEM is using CATIA V6 and VPM V6.
• OEM owns the complete design in V6 native format.
• Supplier is responsible for a sub-assembly.
• Supplier is using CATIA V5 and one of the V5 PDMs supporting coexistence.

a coexistence scenario such as the following is possible:

• The Supplier transfers its initial V5 design data to the OEM.
• The OEM integrates the V5 design data into an existing V6 structure.
• The Supplier transfers the updated V5 design data to the OEM.
• The OEM integrates the updated V5 design data in the V6 structure.

Migration scenarios enable data transfer scenarios from V5 to V6 for a user moving to the V6 platform. V5 data is transferred to V6 and all subsequent design updates are made in V6.

Coexistence and migration scenarios can be launched using:

• The Coexistence Batch
• 3DLive connected via a Live ENOVIA V5 VPM connector, leveraging an XML script that has been prepared beforehand

Before reading this guide, you should be familiar with basic V6 concepts such as document windows, standard and view toolbars.

We recommend that you read the Infrastructure User's Guide, which describes generic capabilities common to all Version 6 products. It also describes the general layout of V6 and the interoperability between workbenches.

To get the most out of this guide, we suggest that you start reading and performing the step-by-step user tasks which cover all product functionalities.