Import GTC Package with 3D and mapping

Note

The preference MRMGTCProductIDVendorAcronymSeparator controls the separator for the GTC (generic tool catalog) product id and vendor acronym, if a specific character or string does not allow using Naming rules then you can use any other separator.

You can import a GTC (generic tool catalog) package along with 3D data (STEP files) and map imported data to the vendor component all within one function. If you choose not to perform one of the options (import 3D models or mapping) you can use the manual process for each.

Procedure

1. Obtain a copy of the tool vendor catalog from the tool vendor (website download, email, etc.) and save the file to a location that you will use to retrieve the file.

In the Resource Manager view initiate the import function by using one of the following methods:

In the toolbar, click

In the menu bar select Tools→Import GTC package

2. In the Import GTC Package dialog box, select the package to import.

You can select a file on the client or the server. If you select a client file, the file is copied to the server and unpacked on the server. Selecting a file on the server saves this step. If you enter values in the MRMGTCPackageClientDir and MRMGTCPackageServerDir preferences, these locations are displayed automatically in the Client and Server boxes.

3. In the Import Vendor Products dialog box, the GTC package(s) are displayed. You can hover over the package to view additional information, select Import to continue.

4. Once the import is complete, the importing of 3D model data will begin if the action was selected. Once completed, click Next.

5. If Map products to MRL classes action was selected, the Map Selected ICOs dialog box will display. Click Map ICOs to map generic tool catalog (GTC) products to manufacturing resource library (MRL) tool components.

6. The Mapping ICOs Progress Results dialog box will display the progress of the mapping, once complete click Next to display a import summary.

Results

In the Classification Table view you can view a table of the imported and mapped products.

Note

When you import a library that has tools that do not map directly to existing classes, the discrepancies are highlighted in a summary report.

• If the Source Class maps directly to a single Target Class, the row will be white.

• If no Target Class is found to match the Source Class, the row will be red.

• If there are multiple Target Classes the Source Class can map to, the row is yellow and there is a menu to choose the desired Target Class.

Once complete, you can review the mapping of the ICOs.