ENOVIA VPM V5 Data Transition Tables

ENOVIA VPM V5 to 3DEXPERIENCE Coexistence

ENOVIA VPM V5 Data	Transferable	Description
CATAnalysis of CATPart/CATProduct	Yes	Transfer of a CATAnalysis document based on a CATPart or CATProduct document
CATAnalysis of exposed assembly	-	Transfer of a CATAnalysis document based on an exposed structure
CATDrawing of CATPart/CATProduct	Yes	Transfer of a CATDrawing document based on a CATPart or CATProduct document. but only if the CATDrawing is explicitly selected for transfer. The pointing CATDrawing is not automatically transferred together with pointed CATPart/CATProduct.
CATDrawing of exposed assembly	Yes	Transfer of a CATDrawing document based on an exposed structure
CATDrawing (as CGM)	Yes	Transfer of the CGM of a CATDrawing document
CATMaterial	Yes	Transfer of a CATMaterial definition
CATPart (as CGR)	Yes	Transfer of the CGR of a CATPart document. This mode allows you to fully use the 3D Accuracy capabilities without completely migrating the source document. The V5 CATPart is also transferred without any change for further use.
CATPart (as Spec)	Yes	Transfer of a CATPart document as spec
CATProcess	Yes	Transfer of a CATProcess
CATProduct (blackbox)	Yes	Transfer of a CATProduct document (blackbox)
CGM	-	Transfer of a CGM document
CGR	Yes	Transfer of a CGR document
Catalog	Yes	Transfer of a catalog
Configuration dictionary	-	Transfer of a configuration dictionary
Configuration effectivity	-	Transfer of configuration effectivities
Configuration handler	-	Transfer of configuration handler
Constraints of exposed assembly	Yes	Transfer of assembly constraints created on an exposed structure
Constraint on Publication	Yes	Transfer of constraints on publications
Contextual link in CATProduct	Yes	Transfer of a contextual link contained in a CATProduct document
Contextual links exposed	Yes	Transfer of contextual links created on an exposed structure
Attribute transfer customization with Business Logic	Yes	The attribute transfer can be customized using Business Logic.
Design table	Yes	Transfer of a design table (as a PLMDMTDocument)
GCO	-	Transfer of a Generic Component
Instance deletion	Yes	If an instance is deleted in the source system the instance will be seen as deleted in 3DEXPERIENCE.
Maturity	Yes	Transfer of maturity information
Me > Preferences	Yes	Transfer of Me > Preferences settings. See Coexistence and Migration: ENOVIA VPM V5.
Multivaluated attribute	Yes	Transfer of multivaluated attributes
Non-CAD document	Yes	Transfer of a non-CAD document such as xls
Ownership	Yes	Transfer of ownership information
Product Structure exposed	Yes	Transfer of a Product Structure
Product View Result (PVR)	Yes	Transfer of PVR (applicative data: only the PVR object itself is not transferred)
Product View Specification (PVS)	-	Transfer of a Product View Specification
Publication exposed	-	Transfer of a Publication that is exposed in the database
Publication in CATPart	Yes	Transfer of a CATPart document containing a Publication
Publication in CATProduct	Yes	Transfer of a CATProduct document containing a Publication
Ref-Ref link	Yes	Transfer of a reference-to-reference link (e.g. the import of a solid)
TP	-	Transfer of a Technological Package
V4 model	Yes	Transfer of a CATIA V4 model
Versioning	Yes	Transfer of versioning information
XCAD (as CGR)	-	When XCAD is in place and the CGR is computed on a document then CGR is transferred

3DEXPERIENCE to V5 Coexistence

Warning: Transferring 3DEXPERIENCE data to V5 Coexistence is no longer possible by default. To do so, the variable Coexistence_EnableExportToLegacyProvider=1 must be set.

3DEXPERIENCE Data	Transferable	Description
CATDrawing	-	Transfer of a Drawing document.
CATMaterial	-	Transfer of a Material definition
3DShape (to a CATPart as a result)	Yes	Transfer of a 3DShape as a result
3DShape (to a CATPart as a specification)	Yes	Transfer of a 3DShape as a specification
3DShape with a V5 CGR or V4 models	-	Transfer of a 3DShape with a CATIA V5 CGR or CATIA V4 models
Catalog	-	Transfer of a catalog
Customized attribute transfer with Business Logic	Yes	Transfer of a 3DEXPERIENCE customized attribute mapped to the source system - the attribute transfer can be customized using Business Logic
Instance deletion	Yes	If an instance is deleted in 3DEXPERIENCE the instance will be seen as deleted in the source system.
Maturity	Yes	Transfer of maturity information
Multi-instantiated representation	-	Transfer of a multi-instantiated representation
Multirepresentation	-	Transfer of multiple representations under one reference
Multivaluated attribute	-	Transfer of multivaluated attributes
Non-CAD document	-	Transfer of a non-CAD document such as xls
Ownership	Yes	Transfer of ownership information
Product Structure	Yes	Transfer of a Product Structure
Publication at assembly Ref level	-	Transfer of a 3DEXPERIENCE Publication located at assembly reference level
Publication at leaf Ref level	-	Transfer of a 3DEXPERIENCE Publication located at leaf reference level (integrated in the generated CATPart)
V4 model representation	Yes	Transfer of a CATIA V4 model
Versioning	Yes	Transfer of versioning information

General Considerations

• Only unfiltered content is migrated.
• The R2021x On Premise Solution is the last release to support VPM V5 DBDI downward compatibility.

Particular Considerations

• Ref-Ref links: Only Ref-Ref links contained inside a CATPart document persisted in ENOVIA VPM V5 can be migrated.
• Publications:
  • For ENOVIA VPM V5 to 3DEXPERIENCE, only Publications contained inside a CATPart or a CATProduct document persisted in ENOVIA VPM V5 can be migrated.
  • For 3DEXPERIENCE to ENOVIA VPM V5, Publications will be transferred but will not be linked to a created Part and will therefore have no useful purpose.
• CATDrawings:
  • Only CATDrawings attached to a part reference or product can be migrated (CATDrawings attached to a part instance cannot be migrated).
  • CATDrawings in an exposed subassembly and whose context is a reference under the PRC cannot be correctly migrated to 3DEXPERIENCE. Such CATDrawings ARE transferred to 3DEXPERIENCE but all their links are isolated.
• Non-CAD documents:
  • Customized non-CAD documents are not supported.
• Product Structure transfer 3DEXPERIENCE to ENOVIA VPM V5: Even if an object is not locked after transfer to the V5 side, it is possible to instantiate objects under it during a second transfer. The process won’t stop because the parent reference is unlocked on the V5 side.
• Exploded Product Structure:
  • Only exposed, non-blackboxed Product Structures can be migrated.
  • Only CGRs, CATParts and V4 contents are migrated. Only simple geometry (Part Design) found within a CATPart document is handled in the transition process. Neither relational design content nor any other CATIA V5 applicative content found in previously mentioned document types is handled.
  • You activate the transfer of exposed objects by activating the option in Preferences > General > File-based Design > Providers.
• Work Packaged Product Structure:
  • Only exposed or blackbox product structures can be migrated.
  • Only CGRs, CATParts, CATProducts and V4 contents without relational design, assembly constraints and doc-doc links are migrated.
• Instance deletion: 3DEXPERIENCE to ENOVIA VPM V5: Instances are the only objects within the scope of deletion. Deletion of a reference, a representation or a representation instance cannot be propagated to the target system.
• Versioning:
  • ENOVIA VPM V5 and 3DEXPERIENCE versioning patterns must be identical.
  • PRC is transferred to 3DEXPERIENCE as a Reference. Version of this Reference will be automatically set with the first index defined in 3DEXPERIENCE versioning pattern.
• Visualization only: The corresponding CATParts or CATDrawings are transferred when the Visualization only option is selected. Note the following:
  • Only CGMs and CGRs are transferred with the result that an assembly structure containing such CATParts or CATDrawings can be expanded at node level only.
  • CGM and CGR files containing the visualization information must first be generated using the DMU utility to generate derived formats in the ENOVIA V5 server, by launching it with the File Introspection process for example.
  • Selecting the Visualization Only option creates the corresponding Product Structure.
• Document Revision:
  • Document revisions attached with a documentation link will not be instantiated under the reference they were attached to in the source. You can activate the V55_DocLink variable on the V5 side to get them instantiated in 3DEXPERIENCE.
  • You must transfer the PartReference that will contain the Document Revision within its scope (the Document Revision cannot be transferred alone).
• Design Table:Only CATPart documents pointing to a design table document - with both documents persisted in ENOVIA VPM V5 can be migrated. The CATPart documents can be standalone, either embedded in an exploded assembly or in a work-packaged assembly.
• Product View Result (PVR): The following cases are not supported for PVR transfer:
  • PVR including other PVRs
  • non-synchronized PVR
  • PVR associated with a PVS
  • PVR in Visu mode
  • PVR deletion
  • PVR containing kinematics data
  • PVR containing blackbox data
• Multi-instantiated documents in Visu mode: You can transfer documents that have multiple instances in a V5 structure to 3DEXPERIENCE (in Visu Mode only).
• ACADEMIA projects
  • You can use industrial data for ACADEMIA projects.
  • Using ACADEMIA data for industrial projects is not permitted.