Machining File-based Design Import

The File-based Design Import capability allows you to import previous version data into V6 and to save those data in V6. Be aware that some Machining entities from previous versions cannot be imported into V6.

Machining CATProcess Import

A CATProcess containing machining data is imported as a PPR Context type PLM object.

This PPR Context is opened in a Machining workbench (that is, a PPR Editor).

For more information about the procedure for importing a CATProcess containing machining data see NC Manufacturing Infrastructure User's Guide: Importing Files from Previous Versions.

Machining CATProcess Import Limitations

CATProcess is not imported in the cases listed below.

Version 5 Version 6
CATProcess Import is not done if the CATProcess includes:
  • a DPM Machining Operation (Generic Mac, Assembly Station, and so on)
  • several Part Operations using different milling machines
  • operations pointing unsynchronized geometry (modified out of a machining application)
  • version 4 Part Operations or Machining Operations.

Notes:

  • A CATProcess must be saved in a version older than V5 Release 11 before you can import it to V6. A 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.

Other Machining Import Limitations

The features and links listed below are not imported in this release.

Version 5 Version 6
NC machines The following are not imported:
  • Any NC machine included in a CATProcess saved in or prior to Version 5 Release 11 (permanent restriction).

    Note: DELMIA NC Machine cannot be imported in update mode.

Note:

  • 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 Tools > Options > General > file-based Design Import > FBDI General
Tools and Tool Assemblies The following are not imported:
  • Any Tool and Tool Assembly included in a CATProcess saved in or prior to Version 5 Release 11 (permanent restriction).
  • Any Resource User Representation that does not include CuttingType (value: shank/cutter/holder) knowledge parameter (permanent restriction).
Machining activities The following are not imported:
  • DPM Machining Operations (permanent restriction).
  • V4 part operations and V4 Machining Operations (permanent restriction).
Synchronizations The Synchronizations created between activities are not imported.
Automatic stock The option Automatic Stock Selection for Turning Operations is not supported in V6. If the Automatic Stock Selection for Turning Operations was selected in the V5 data imported, the data will be imported with Activate the Intermediate Stock selected instead. A warning message is displayed.
Transition Paths

Transition pathsare not imported and must be redefined through V6 Part Operation dialog box.
Smart NC Not imported (permanent restriction).
Non-CATIA document whose owner is Machining domain The following are not imported:
  • Video result (WPC file).
  • NC code (aptsource, iso, clfile).
  • External toolpath (tlp file).
Links The following are not imported:
  • Link between Tool and picture.
  • Link between Program and NC Code.
  • Link between Toolpath and External Toolpath.
  • Link between Part Operation and documentation file.
  • Link between Machining Operation and VideoResult.
  • Link between Machining Operationand IPM Part.
  • Link between Part Operation and IPM Part.
  • Link between Turning Operation and Actual Stock.

Notes:

  • Permanent restrictions will remain as long as the previous version applications that were used to create this data are not supported in V6.
  • Machining FBDI does not create processes or implement links.