Product Structure Design Database Design Import

Database Design Import (DBDI) enables the migration of CATIA V5 data stored in a legacy database into 3DEXPERIENCE.

This topic specifies the import correspondences between V5 data types and 3DEXPERIENCE content types, and the import result. The statuses for import results are fully imported, partially imported, and not imported (-).

This page discusses:

See Also
In Other Guides
Database Design Import (Dbdi)

Common Import Behavior

This section describes the behavior of CATIA V5 data stored in legacy databases imported into 3DEXPERIENCE that is common to all connectors.

Table 1. Objects exposed in database
V5 Data 3DEXPERIENCE Data Import Result
Product Product reference

Fully Imported
Product instance Product instance

Fully Imported
Position of instance Position of instance

Fully Imported
Table 2. Objects embedded in documents stored in database
V5 Data 3DEXPERIENCE Data Import Result
Product Product reference

Fully Imported
Product instance Product instance

Fully Imported
Position of instance Position of instance

Fully Imported
PublicationPort

Fully Imported

Parameter publication Parameter publication

Partially Imported

Publications pointing knowledge parameters are imported.

Graphic propertiesGraphic properties

Partially Imported

Data is imported but cannot be visualized. See Article 40458 of the Knowledge Base.

Fully Imported for data saved using the Publication mode.

FlexibilityFlexibility

Fully Imported

In V5, the flexibility status is defined on a product instance. Defining that a product instance is flexible does not affect the other instances of this product.

In 3DEXPERIENCE, the flexibility status is defined on the original product. Defining flexibility on a product means that all its instances are flexible. This product becomes a PMR (Positional Mechanical Reference).

Two consequences for the import:

  • V5 flexible product instances can have overloaded positions in 3DEXPERIENCE, different from the one defined on the other imported product instances.
  • The imported original product is not necessarily defined as PMR.

Activation modes of instanceActivation modes of instance

Fully Imported

The V5 activated/deactivated status of product instances is imported in ENOVIA VPM V5 as an effectivity on the corresponding product instances.

For V5 deactivated instance, its corresponding instance is defined with an effectivity "FALSE" (set on the Activate deactivate variability space). For V5 activated instance, no effectivity is created.

For more information about effectivity, see the VPM Configured Environment User's Guide.

Reference linkReference link

Fully Imported

Contextual linkContextual link

Fully Imported

ENOVIA VPM V5 Database to 3DEXPERIENCE

This section specifies the differences with respect to the common import behavior.

V5 Data Type 3DEXPERIENCE Data Type Import Result
Exposed contextual link Contextual link

Fully imported
Exposed constraintConstraint

Fully imported

Fully imported only after checking the Activate Exposed Objects Transfer option in Me > PreferencesGeneral > File-based Design Import > Providers.

ENOVIAvpm Database to 3DEXPERIENCE

This section specifies the differences with respect to the common import behavior.

V5 Data Type 3DEXPERIENCE Data Type Import Result
Exposed publication Ports

Fully Imported
Exposed publication linkPublication links

Fully Imported

Exposed contextual linkContextual links

Fully Imported

X-CAD Design Management Database to 3DEXPERIENCE

There are no differences with respect to the common import behavior.

SmarTeam Database to 3DEXPERIENCE

There are no differences with respect to the common import behavior.

Adapter for X-PDM Database to 3DEXPERIENCE

There are no differences with respect to the common import behavior.