Live Rendering 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:

Common Import Behavior
V5 Native Geometry Usage After Import
ENOVIA VPM V5 Database to 3DEXPERIENCE
ENOVIAvpm Database to 3DEXPERIENCE
X-CAD Design Management Database to 3DEXPERIENCE
SmarTeam Database to 3DEXPERIENCE
Adapter for X-PDM Database to 3DEXPERIENCE

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
Applications (a command to import lights, environments and cameras).	Imported as Technological Package or by creating a rendering scene: If a Technological Package already exists, the new entities created in the 3DEXPERIENCE platform are stored in this existing Technological Package. If there is no existing Technological Package, a new one is automatically created as soon as you create a light, a camera, an environment or a sticker.	Fully imported
Lights	Lights	Fully imported
Environments	Environments	Fully imported
Cameras	Cameras	Fully imported
Stickers	Stickers	Fully imported
Shooting	-	-
Turntable	Not persistent	-
Shadow Stickers	-	-

V5 Native Geometry Usage After Import

This section describes the different compatibility statuses of V5 CATParts in the 3DEXPERIENCE environment.

For more information about standard behavior, see Social and Collaborative: Product Development - Model Based: Coexistence and Migration: ENOVIA VPM V5 Coexistence and Migration: Understanding Coexistence and Migration Scenarios:V5 Native Geometry Usage.

When a V5 CATPart is imported to 3DEXPERIENCE, cameras are not imported.