Machining 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

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
CATProcess Product Lifecycle Management objects Not imported if the CATProcess includes:
  • A DPM Machining Operation (Generic Mac, Assembly Station, and so on)
  • Operations pointing unsynchronized geometry (modified out of a machining app)
  • Version 4 Part Operations or Machining Operations.
Imported if the CATProcess includes:
  • Several Machines
NC machines NC machine representation Not imported:
  • Any NC machine included in a CATProcess saved in Version 5 Release 11 or earlier (permanent restriction).
    Note: DELMIA NC Machine cannot be imported in update mode.
Notes:
  • A Vertical or Horizontal Lathe machine is imported as a new generic Turn-Mill machine with one turret and one spindle.
  • To import CATProducts related to PDB files, add the pdb extension to the list of Extensions to ignore, in Me > Preferences > General > File-based Design Import, FBDI General
Tools and Tool Assemblies Tools and Tool Assemblies Not imported:
  • Any Tool and Tool Assembly included in a CATProcess saved in Version 5 Release 11 or earlier (permanent restriction).
  • Any Resource User Representation that does not include CuttingType (value: shank/cutter/holder) knowledge parameter (permanent restriction).
Machining activitiesMachining activitiesNot imported:
  • DPM Machining Operations (permanent restriction).
  • V4 part operations and V4 Machining Operations (permanent restriction).
SynchronisationSynchronisationImported:

Synchronisation created between activities.

Automatic stockAutomatic stockNot imported:

The option Automatic Stock Selection for Turning Operations.

Imported if:

Automatic Stock Selection for Turning Operations was selected in the V5 data imported, the data is then imported with Activate the Intermediate Stock selection instead. A warning message is displayed.

Transition PathsTransition PathsNot supported:

Transition paths must be redefined through the 3DEXPERIENCE Part Operation dialog box.

Smart NCSmart NCNot supported:

Permanent restriction.

LinksLinksNot imported:
  • Link between Tool and picture.
  • Link between Program and NC Code.
  • Link between Toolpath and External Toolpath.
  • Link between Part Operation and Guide file.
  • Link between Machining Operation and Video Result.
  • Link between Machining Operation and IPM Part.
  • Link between Part Operation and IPM Part.
  • Link between Turning Operation and actual Stock.
Non-CATIA document whose owner is Machining domainNon-CATIA document whose owner is Machining domainNot imported:
  • Video result (WPC file).
  • NC code (aptsource, iso, clfile).
  • External toolpath (tlp file).

Considerations

You should take the following considerations into account:

PPR Context dependancy

V5 products are instantiated twice:

  • Under Manufacturing Cell / NC assembly
  • Under PPRContext / Item (for others DELMIA apps containers import like robotics)

A batch utility allows the upgrade of old machining data into the 3DEXPERIENCE database. See Data Upward Compatibility in Removing PPR Context Dependancy.

Import Exceptions or Limitations
Machining CATProcess Import: A CATProcess containing machining data is imported as a PPR Context type object.
This PPR Context is opened in a Machining Application (that is, a PPR Editor).

Notes:
  • A CATProcess must be saved in a version earlier than V5 Release 11 before you can import it to 3DEXPERIENCE. An NC machine included in a CATProcess saved in or before that release cannot be imported using the FBDI tool.
  • After using FBDI on a CATProcess containing machining data, if the resulting PPR Context contains several Part Operations, the following issue can occur: when one Part Operation is selected, all products of all Part Operations are displayed together, instead of showing only the products of the selected Part Operation.
  • Permanent restrictions remain as long as the previous version apps that were used to create this data are not supported in 3DEXPERIENCE.
  • Machining FBDI does not create processes or implement links.

Data Upward Compatibility

As PLM data models change, starting in R2012x, previous data created must be upgraded. A batch utility allows the upgrade of old machining data into the 3DEXPERIENCE database.

Click the Tools tab and then Utilities. In the Connect dialog box, fill in the required data (select where the Machining Upgrade is stored). In the Batch Monitor dialog box, click OK, and then in the Utilities tab, double-click Machining Upgrade.

Click the required button for the Report directory, and Report name, and the Suffix.

Notes:
  • Geometrical links that points to a geometry which is not defined in the product assembly (set in the part operation) are not migrated.
  • When old data is opened in session, a warning appears, and then the data is upgraded automatically. When the upgrade is completed, an information window appears saying Data have been upgraded to the current data structure standard. The geometries have been placed in a Manufacturing Setup Resource under the Manufacturing Cell.

Tools and Tool Assemblies
  • Migration of Tools and Assemblies: The migration of tools and tools assemblies from a previous release is performed automatically the first time the object is used (Tool, Tool Assembly). It is recommended to perform migration before usage to avoid authorization issues.
  • Tool Catalogs in .csv Files: The Excel .csv tool catalogs contain description of tools and is accessed directly in Machine Programming. A sample is available in the ...\startup\Manufacturing\Tools\MillAndDrillToolAssembly.csv file of your installation. Cutting conditions (feeds and speeds) is included in a .csv tool catalog. For more information, see Feeds and Speeds. It is possible to create tools or tool assemblies starting from a .csv file. This feature must be used to ease the transfer from V5 to populate the current database. These catalogs must be used.

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.