Scenarios

This task describes the different scenarios and includes several examples of how to use them with the various data behaviors and process behaviors.

Important: Coexistence functionality requires the installation of Optional Installation - Exchanges Management.
Warning: The parallel running of either coexistence or migration scenarios is not certified.

This page discusses:

Scenario Profiles

Scenario profiles describe some basic scenarios of Coexistence and Migration transfer of data.

Coexistence enables you to share data (i.e. transfer it from the source provider to the target provider and then use it on the target) between the ENOVIA VPM V5 provider and 3DEXPERIENCE.

  • You can regularly update data from the source provider to the target provider.
  • Data must not be authored in the target PDM. Source data must be considered as master data. Data must be protected through P&O policy.
  • Coexistence scenarios are used when design updates continue in ENOVIA VPM V5 and the updates need to be regularly transferred to 3DEXPERIENCE
  • The version position in the version family is that of the source.
  • Remember that the whole family of versions shares the same mastership, either V5 or 3DEXPERIENCE. The ownership of versions A, B, C, etc. transferred from ENOVIA VPM V5 to 3DEXPERIENCE is shown as 3DEXPERIENCE Master.
  • Maturity information can be that used on source data. To find out more, see Data Behaviors.
  • Large structures can be transferred using multiple transfers. (Common parts of the structure must belong to the different transfers to be able to rebuild the entire structure.)
  • People and Organization can be that used on source data. To find out more, see Data Behaviors.

Migration

Enables you to transfer data from the ENOVIA VPM V5 provider to 3DEXPERIENCE

  • Large structures can be transferred using multiple transfers. (Common parts of the structure must belong to the different transfers to be able to rebuild the entire structure.) However, when large structures are broken down into small structures, contextual links may be severed if the entire scope of each link is not within the corresponding small structure.
  • The version position in the version family is that of the source.
  • Remember that the whole family of versions shares the same mastership, either ENOVIA VPM V5 or 3DEXPERIENCE. The ownership of versions A, B, C, etc. transferred from V5 to 3DEXPERIENCE is shown as 3DEXPERIENCE Master.
  • Maturity information can be that used on source data. To find out more, see Data Behaviors.
  • Updating previously transferred data is not possible.
  • An ENOVIA VPM V5 or 3DEXPERIENCE object can be linked to one and only one "V5 Master" object. For example, if a 3DEXPERIENCE product has been exported as an ENOVIA VPM V5 product in two different mapping contexts, only one ENOVIA VPM V5 product can be switched from "3DEXPERIENCE Master" to "V5 Master".
  • If an object is transferred using the migration scenario from ENOVIA VPM V5 to 3DEXPERIENCE then the ownership of the object is 3DEXPERIENCE Master.
  • People and Organization can be that used on source data. To find out more, see Data Behaviors.

Tip: Migration does not create new data. (The version place in the version family is that used in the source data and maturity information can be different from the initial state.)

Warning: If a non-latest revision of an ENOVIA VPM V5 object is transferred to 3DEXPERIENCE in migration mode then a new version cannot be created in 3DEXPERIENCE.

Scenario Examples

The following are examples of coexistence and migration scenarios.

Provider -> 3DEXPERIENCE Scenarios

Scenario 1: Migration, small structure or subset of a large structure, navigate and design

Goal:

  • Migrate data for which all subsequent design updates will be made in 3DEXPERIENCE
  • Transfer a small structure or subset of a large structure
  • Be able to apply search and navigation functionality to the transferred data
  • Be able to apply 3DEXPERIENCE functionality to the transferred data.

Scenario:

  • Use Migration.
  • Use the Upgrade option with the Full option.

Considerations:

  • The version position in the version family is that of the source.
  • For large structures, each transfer should contain only a minimal subset of the structure.
  • For large structures, common parts of the structure must belong to the different transfers to be able to rebuild the entire structure.

Scenario 2: Coexistence, navigate

Important: The following methodology using Coexistence scenarios enables you to transfer large structures in several steps.
  • First step: Coexistence in Visualization Only mode in order to transfer the whole structure in terms of metadata (structure, versioning, etc.) without loading and migrating authoring representations. Enables you to address navigation and search scenarios on the target provider after transfer.
  • Subsequent steps: Coexistence in Upgrade mode on a subpart of the previously transferred structure to upgrade only necessary CATIA V5 representations or to upgrade all CATIA V5 representations in several processes.

Goal:

  • Be able to share data (i.e. transfer it from the source provider to the target provider and then use it on the target) between the ENOVIA VPM V5 provider and 3DEXPERIENCE
  • Be able to regularly update data from the source provider to the target provider
  • Be able to apply search and navigation functionality to the transferred data.

Scenario:

  • Use Coexistence.
  • Use the Visualization Only option.

Considerations:

  • Coexistence scenarios maintain a link between the source and the target data to enable sharing of subsequent updates.
  • If data already exists in the target provider database, it will be updated.
  • All data updates must be done on one side only (either on the source or target side) to avoid any conflict.
  • During DBDI transfer, a representation must have a visualization stream. If they do not have a visualization stream, they will be filtered and not migrated to 3DEXPERIENCE
Warning: In order to specify whether your master data is on the source or target side, always use the CoexistenceAdministration batch. See Running the CoexistenceAdministration Batch.

Scenario 3: Coexistence, navigate and design

Goal:

  • Be able to share data (i.e. transfer it from the source provider to the target provider and then use it on the target) between the ENOVIA VPM V5 provider and 3DEXPERIENCE
  • Be able to regularly update data from the source provider to the target provider
  • Be able to apply search and navigation functionality to the transferred data
  • Be able to apply 3DEXPERIENCE functionality to the transferred data.

Scenario:

  • Use Coexistence.
  • Use the Upgrade option with the Full option.

Considerations:

  • Coexistence scenarios maintain a link between the source and the target data to enable the sharing of subsequent updates.
  • If data already exists in the target provider database, then it will be updated.
  • All data updates must be done on one side only (either on the source or target side) to avoid conflict.
Warning: In order to specify whether your master data is on the source or target side, always use the CoexistenceAdministration batch. See Running the CoexistenceAdministration Batch.

3DEXPERIENCE -> ENOVIA VPM V5 Scenarios

Scenario 1

Goal:

  • have Parts corresponding to 3DEXPERIENCE representations in a target ENOVIA VPM V5 PDM.

Scenario:

  • Use the CoexistenceBatch batch.

Considerations:

  • Enables design-in-context only.