Machining File-based Design Import

V5 to 3DEXPERIENCE Data Import Table

The following table describes import correspondences between V5 file-based data and 3DEXPERIENCE content.

The statuses for import results are fully imported, partially imported, and not imported (-).

V5 Data Type	3DEXPERIENCE Content Type	Import Result
CATProcess	PPR Content	Fully imported: The CATProcess includes several machines.
NC machines	NC machine representation	Fully imported: 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	-
Machining activities	Machining activities	-
Synchronisation	Synchronisation	Fully imported: Synchronisation created between activities.
Automatic stock	Automatic stock	Fully imported: 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 Paths	Transition Paths	-
Smart NC	Smart NC	-
Links	Links	-
Non-CATIA document whose owner is Machining domain		-

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.
• 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.
  • Surface machining areas to avoid, as this option is no longer supported in 3DEXPERIENCE. To achieve similar results, select a bottom plane.

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.

Note: 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.

Warning: If a geometrical link points to a geometry that is not defined in the product assembly (set in the part operation), then it is not migrated.

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.
• Tool Catalogs from V5: To import a V5 tool catalog, add all tools to a V5 CATProcess and import this CATProcess in the 3DEXPERIENCE. Then, select all tools imported from V5 CATProcess and send them to a 3DEXPERIENCE catalog.