ENOVIAvpm Data Transition Tables

ENOVIAvpm to 3DEXPERIENCE Coexistence and Migration

ENOVIAvpm 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 (only if the CATDrawing is explicitly selected for transfer). A 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	-	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	Yes	Transfer of a CGM document
CGR	Yes	Transfer of a CGR document
Catalog	Yes	Transfer of a catalog. See Transferring CATIA V5 Catalogs from ENOVIAvpm to 3DEXPERIENCE.
Configuration dictionary	-	Transfer of a configuration dictionary
Configuration effectivities - ranges, milestones	-	Transfer of range and milestone effectivities
Configuration effectivities - dates, options	Yes	Transfer of date and option effectivities
Configuration handler	-	Transfer of configuration handler
Constraints of exposed assembly	Yes	Transfer of assembly constraints created on an exposed structure
Constraints on Publications	Yes	Transfer of constraints on publications
Contextual links 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
Customize attributes with Business Logic	Yes	Possibility to customize the attributes transferred through Business Logic
Design table	Yes	Transfer of a design table
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. See Transferring Maturity Information from ENOVIAvpm to 3DEXPERIENCE.
Me > Preferences	Yes	Transfer of Me > Preferences settings. See Coexistence and Migration: ENOVIAvpm.
Multivaluated attributes	-	Transfer of multivaluated attributes
Non-CAD documents	Yes	Transfer of a non-CAD document such as xls
Ownership	Yes	Transfer of ownership information. See Transferring Ownership Information from ENOVIAvpm to 3DEXPERIENCE.
Product Structure exposed	Yes	Transfer of a Product Structure
Product View Result (PVR)	-	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	Yes	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
CATIA 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 the CGR is transferred

3DEXPERIENCE to ENOVIAvpm Coexistence

General Considerations

• Instance level documents are not migrated.
• Only unfiltered data is migrated.

Particular Considerations

• 2D models: No conversion is performed on 2D models. However, you can find information about how to enhance 2D model representation in 3DEXPERIENCE in Transferring 2D Models from ENOVIAvpm to 3DEXPERIENCE.
• Assembly drawings: When migrating an assembly drawing from ENOVIAvpm to 3DEXPERIENCE, the entire assembly drawing including the root and all V5 links are transferred. For more information, see Transferring Assembly Drawings from ENOVIAvpm to 3DEXPERIENCE.
• 3D Parts and non-shareable Parts: Such CATPart documents can be migrated but require specific scripts to be edited beforehand. For more information, see Opening ENOVIAvpm Parts as 3D and Non-Shareable Parts in 3DEXPERIENCE.
• 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.
• 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 and an assembly structure containing such CATParts or CATDrawings can therefore be expanded at node level only.
  • CGM and CGR files containing the visualization information must first be generated using the MultiCAD server (X-CAD) on the ENOVIAvpm side (see ENOVIAvpm Installation & Administration: Customizing MultiCAD for more information).
  • Selecting the Visualization only option creates the corresponding Product Structure.
• Reference-to-reference links: Only those contained inside a CATPart document persistent in ENOVIAvpm can be migrated.
• Exploded Product Structures: Publications, contextual links and constraints that are exposed at the Product level (when the Product Structure is saved as Structure exposed from CATIA V5) are migrated to 3DEXPERIENCE. However, be aware that doing so will have an adverse effect on performance. Also, make sure that the transfer of exposed objects has been activated in the Providers tab of Preferences > General > File-based Design (then restart any coexistence transfer application using one of the legacy providers for the activation to be taken into account).

  Bear in mind the following:

  • Publications: Exposed Publications are supported when the Publication owner is in the transfer scope. If you wish, you can update those Publications that have already been transferred. Note that only exposed Publications of geometry are supported. The publication of Publications or of parameters is not supported. For information about how Publication names are managed, see Publication Name Conflicts.
  • Contextual links: Exposed contextual links are supported when the pointing Part is in the transfer scope. Completion will retrieve the context and the instance path and add them to the scope. If you wish, you can update those contextual links that have already been transferred.
  • Assembly constraints: Assembly constraints are supported if the constraints owner is in the transfer scope. You can update those constraints. Note that flexible products are not supported.
  • Assembly drawings: Assembly drawings of exposed structure are supported, the completion will add all instances paths, and pointed geometries, to the scope of transfer. These drawings can be updated.
• Maturity information: Downward compatibility is supported for such information but bear in mind the following:
  • The ENOVIAvpm attribute C_MATURITY must be mapped on the 3DEXPERIENCE attribute V_maturity using the VPMV4ToV6Mapping batch.
  • The value placed in ExchangeObject.MappedMaturity must be declared in the ENOVIAvpm profile for C_MATURITY. Since no checks are made on the client, any wrong values result in inconsistency on the ENOVIAvpm server and the data behaves as if it were frozen.
• Ownership information: Downward compatibility is supported for such information but bear in mind that:
  • The ENOVIAvpm attribute C_RESPONSIBLE must be mapped on the 3DEXPERIENCE attribute V_user and C_ORG_RESPONSIBLE must be mapped on V_organisation using the VPMV4ToV6Mapping batch. Note that the attribute V_project that belongs to the 3DEXPERIENCE ownership vector serves no useful purpose since the concept of project does not exist in ENOVIAvpm.
  • The value placed in ExchangeObject.MappedUser and ExchangeObject.MappedOrganization must be declared in the ENOVIAvpm P&O. Since no checks are made on the client, any wrong values result in the objects being locked. No modifications can then be made via the ENOVIAvpm user interface.
• Multi-instantiated 3DEXPERIENCE representations: In 3DEXPERIENCE, a single representation can be instantiated under several references but such a representation cannot exist in ENOVIAvpm as the representation is closely linked to its reference. It can however be transferred from 3DEXPERIENCE to ENOVIAvpm but will be saved once only.

  If the representation has never been saved in ENOVIAvpm, it will be created.

  If the representation has already been saved in ENOVIAvpm under another reference, it will not be saved and a warning will be sent to 3DEXPERIENCE. If its reference has never been created, it will be created in ENOVIAvpm.

• Revisions: As in 3DEXPERIENCE, ENOVIAvpm shows only the latest revision in the Product Structure. Any previous revision of a representation is detached and the representation instance is deleted. If more than one revision of a document exists in the ENOVIAvpm database, only the latest one will be transferred.
• Version / revision updates: The Update Version / Revision option available in ENOVIAvpm is not supported in the Coexistence context. In other words, neither versions nor revisions are updated in 3DEXPERIENCE if you make a second transfer using Update Version / Revision.

  This is because when the value of either the c_part_version or the c_revision attribute is changed in ENOVIAvpm, the c_order attribute remains unchanged. Since this attribute is used to calculate the version order in 3DEXPERIENCE, any changes you make are not reflected in the 3DEXPERIENCE model. Furthermore, even if this attribute were changed in ENOVIAvpm, the 3DEXPERIENCE model does not allow the modification of V_order in an update process. Once the V_order attribute has been created, it can no longer be modified.

• Exposed data: Note that during the transfer of exposed data, some files are generated in the cache directory on the ENOVIAvpm server.
• ACADEMIA projects
  • You can use industrial data for ACADEMIA projects.
  • Using ACADEMIA data for industrial projects is not permitted.