ENOVIA SmarTeam V5 Coexistence and Migration

ENOVIA SmarTeam V5 Coexistence and Migration addresses customer scenarios concerning V5 to 3DEXPERIENCE and 3DEXPERIENCE to V5 content exchanges.

Coexistence scenarios enable content exchange scenarios between an OEM and a supplier. The following is an example:

For the following context,

  • the OEM is using 3DEXPERIENCE
  • the OEM owns the complete design in 3DEXPERIENCE native format
  • the supplier is responsible for a sub-assembly
  • the 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 content to the OEM
  • the OEM integrates the V5 design content into an existing 3DEXPERIENCE structure
  • the supplier transfers the updated V5 design content to the OEM
  • the OEM integrates the updated V5 design content into the 3DEXPERIENCE structure.

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

Migration and Coexistence products all have the following topology:

  • a legacy server
  • a 3DEXPERIENCE platform server
  • a 3DEXPERIENCE platform client, through which content can be communicated / shared between the two servers.

Before using Migration and Coexistence functionality, make sure that you follow the procedure described in Configuring the ENOVIA SmarTeam V5 Connector.