Circuit Board 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.

V5 Data Type 3DEXPERIENCE Content Type Import Result
Board Board Fully imported
Components Components

Partially imported

The attribute of a component instance is not migrated. Therefore, the component status is lost.

Considerations

You should take the following considerations into account:

Importing Methods in 3DEXPERIENCE

Intermediate Data Format (IDF) file contains the instances attributes information. Therefore, you can use IDF model export to import components in 3DEXPERIENCE without losing data.

To do so: In V5, create an IDF model file of the data. In 3DEXPERIENCE, import the data in the database. Open the model in 3DEXPERIENCE and then compare and update the imported model with the IDF model generated by V5.

ENOVIA VPM V5 Database to 3DEXPERIENCE

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

ENOVIAvpm Database to 3DEXPERIENCE

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

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.