CMM Solo and NXM Solo

You can use CMM Solo to migrate your source CAD data outside of Teamcenter, and then import the migrated NX data into Teamcenter. You can also use CMM Solo to test the migration outside of Teamcenter so you can catch any problems or issues before bringing the data into Teamcenter. If data is already managed in Teamcenter, a more direct method is available to run a test migration. Set the CMM option Application→Migration Controls, Target Data to Filesystem to write migrated files to the file system instead of storing them in Teamcenter as described earlier in this user guide. Using CMM Solo is not the recommended method to perform a large scale migration for the following reasons:

• No metadata attributes are maintained. Information such as when a file was created, who created it, or other system attributes are lost.
• Without Teamcenter, there is no method to track related files. For example, it is easy for a user to delete part files required by an assembly or a drawing.
• Local file naming conventions are not supported. Sites that manage files in an unmanaged data environment will require local naming conventions. CMM Solo automatically assigns names, which may be difficult to interpret without the additional metadata that Teamcenter provides.
• Phased migration is not possible without using Teamcenter to track CMM Attribute forms.
• This process does not control who is authorized to perform the migration.

Appendix A: CMM Solo Preparing data for CMM Solo To prepare the parts, assemblies, and drawings for migration, they need to be placed in a “container” for CMM. To migrate data from Pro/ENGINEER, CATIA, or SolidWorks, place the files in a system folder. To migrate data from I-deas, export the items to a library package file (pkg) using these steps. 1. Choose the I-deas menu File→Export →I-deas Library Data. 2. Select the required library items (parts, assemblies, and drawings). 3. Enable the checkbox Export for Reference, so that the exported items are not locked in I-deas TDM. 4. Enter a destination file name for the package file (pkg). The exported items (prt, asm, dwg) are exported into the same folder, from where they can be opened in CMM Solo. 5. Click Export. It is recommended that you place these exported files in a different directory than the scratch directory used by CMM Solo. Running CMM Solo You can run CMM Solo with a graphical user interface or as a command line entry with specified options. To run with a user interface, enter the following on a command line: cmmSolo.cmd To run as a command line entry, add any options to the command line. For example: cmmSolo.cmd —mode migrate datatype —i —folder C:\migrate\input_files —options C:\migrate\mig_options If you are using NXM, enter nxmSolo.cmd wherever cmmSolo.cmd. is used. To display the available options for CMM Solo as a command line entry, type: cmmSolo.cmd —h Appendix A: CMM Solo

CMM Solo Using CMM Solo with the GUI Start CMM Solo with the graphical user interface by running the command file cmmSolo.cmd in the CMM Solo installation directory. This displays a procedural-type menu that guides you through the steps of migrating data using CMM Solo, and optionally importing that resultant NX data into Teamcenter. The menu is structured as follows.

• Pre-Migration o Select source CAD system o Set migration options o Audit source CAD files
• Migration o Select item to migrate o Select folder to migrate o Migrate to NX o Execute migration dry run o Report ■ View report ■ Create post report summary ■ Search for specific errors ■ Sum feature success and failure counts o Open in NX o Delete migration data
• Post-Migration o Determine migrated files o Determine unmigrated files o Write NX item and children to a file o Copy NX item and children o Report migration attributes
• Teamcenter Import o Prepare data for import CMM Solo

Appendix A: CMM Solo o Run Teamcenter import o Update item import status

• Help o User Guide (English) o User Guide (German) o About
• Exit Appendix A: CMM Solo

CMM Solo Pre-migration To prepare the migration, set your source CAD system and options using the following menu selections: 1. Select source CAD system 2. Set migration options 3. Inventory your source CAD files before you start migration, using Audit source CAD files.

• Select source CAD system Choose the CAD data format of your source CAD data.
• Set migration options Set the desired migration options. The migration options are described in earlier sections of this document.
• Audit source CAD files This performs an inventory of your source CAD files prior to beginning the migration. This helps you track the progress as you migrate your data. Also, you can identify all of your duplicated source CAD files. CMM Solo searches the folders you identify for your source CAD files and, using a checksum report on each file, identifies duplicate files even if they are located in different folders. Migration Select the data you are going to migrate and perform the actions to migrate, report on, open, or delete the migration data stored in the part file.
• Select item to migrate Select a single top-level item and its children to migrate for any CAD system except I-deas. For I-deas, select a package (.pkg) file.
• Select folder to migrat Select the contents of an entire folder to migrate. This applies to all CAD systems except I-deas.
• Migrate to NX This initiates the migration process. All selected source CAD files will be migrated to NX.
• Execute migration dry run You can scan the source CAD data by executing a migration dry run. This processes the source CAD data and creates report files. The process stops after exporting the source CAD files into the CAD neutral files that are later read into NX to create NX items.
• Report There are several types of reports available: o View Report View a report for the selected item and its children. CMM Solo

Appendix A: CMM Solo o Create Post Report Summary Creates an Excel compatible file that contains statistics on success and failure rates based on item types and individual items. This is the same report that is created using CMMReport.cmd –mode post. o Search for specific errors Lets you search for all error messages based on a set of strings. The strings may represent the complete message or a portion of it. This is the same report that is created using CMMReport.cmd –mode classify. o Sum feature success/failure counts Creates a report counting all of the features in the selected data. This is the same report that is created using CMMReport.cmd –mode audit. The count can consist of: ■ Total Features ■ Imported Features ■ Failed Features ■ Unsupported Features ■ Unattempted Features ■ Suppressed Features ■ Locked Features

• Open in NX After the items have been migrated to NX, you can open the NX data.
• Delete migration data Removes migration data from inside each NX dataset when the migration is completely finished and you are ready to use the migrated model for production work. For example, fidelity data is stored in the part file to compare the accuracy of the migrated surfaces to the original surfaces. Fidelity data is removed using this option. The migration data is deleted only for the item selected. For example, migration data deleted from an assembly is not deleted from its components. Post migration
• Determine migrated files This inventories all files that have been migrated. This only works if the Reuse Lookup Table option is selected in the CMM Options.
• Determine unmigrated files This determines the files that remain to be migrated. This only works if the Reuse Lookup Table option is selected in the CMM Options. Appendix A: CMM Solo

CMM Solo

• Write NX item and children to a file Select a top-level NX item and generate a listing of the names and locations of all of its children. This includes all levels of the product structure.
• Copy NX item and children Select a top-level NX item and copy it and all of its children to a directory. This includes all levels of the product structure.
• Report migration attributes Create a report, viewable in MS Excel, of CMM migration attribute values that are stored in the migrated NX files.
• Report migration attributes values Creates an Excel compatible report of CMM migration attribute values that are stored in the migrated NX files. To save these attributes, you must select the NX Part option Save Migration Report in NX File before migrating. Teamcenter Import
• Prepare data for import This helps you select the items you want to import into Teamcenter. It generates a file that you can modify to help you control the data import.
• Run Teamcenter import Executes import of the data specified in the file created with the Prepare data for import option (above).
• Update item import status After you have imported the data into Teamcenter, you can track the status of what has been imported and the Teamcenter item IDs assigned to each imported item. This lets you upload a file with that information to CMM. Help
• User Guide — English Opens the English version of the user guide.
• User Guide — German Opens the German version of the user guide.
• About Displays release information about this version of CMM.
• Exit Exits CMM Solo. CMM Solo

Appendix A: CMM Solo Migrate or scan data using CMM Solo with the GUI To migrate data interactively using CMM Solo with the graphical user interface, follow these steps. 1. Type: cmmSolo.cmd 2. Configure the options in CMM Solo the same as with CMM as shown in previous chapters. Options templates can also be used to store named sets of configuration options. It is recommended that you always turn on Reuse Lookup Table when migrating data from one of the supported CAD systems. The location of the scratch directory is more important when using CMM Solo than with CMM, since the migrated NX files are stored in this location instead of in Teamcenter. 3. Select the items to scan or migrate in the Selected column. You can quickly select or deselect all items by right-clicking any item in the list and choosing from the menu. 4. Optionally perform a pre-migration scan of the selected items using the migration menu selection Execute migration dry run. 5. Migrate the selected items using the migration menu selection Migrate to NX. The Migration Status dialog box displays the status as the migration progresses. 6. Click on a link in the Status or % Complete column to display a migration report of any item. 7. After reviewing the migration reports to ensure the success of the migration, copy the migrated NX files (prt) to the final directory where you will use them. Keep the migrated NX files in the CMMScratch directory if you will want to remigrate these items. If these files are not in the same location, the remigrate option is not available. If you have selected the Reuse Lookup Table option, you can use multiple CMMScratch folders and CMMSolo can correctly handle reuse and remigration for previously migrated items. However, you must leave the NX files and report files in their original locations. For additional information, see the section Support for migration from multiple folders. If CMM Solo does not display the contents of an I-deas package file, check the Command Prompt window for errors referring to Passport IDs or Guids. In this case, use the options described below to update the package file. Appendix A: CMM Solo

CMM Solo Support for migration from multiple folders CMM makes it easy to migrate data from several source folders without migrating shared data multiple times. By setting the Reuse Lookup Table option, CMM detects duplicate data migrated from different source CAD folders, even if the data is migrated to separate CMM scratch folders. This functionality logs limited attributes of the migrated files into the Reuse Lookup Table. Successive target source CAD files intended for migration are checked against logged information in the Reuse Lookup Table, including file size and checksum A common use of this capability is when you have thousands of parts and subassemblies, many of which are shared between different products. A best practice is to migrate the parts first, but this may require mulitple migrations. To organize this process, you may want to break the parts into separate groups, and place them in separate folders, with folders named PartFolder1 through PartFolderN, for example. As you migrate each group, you can migrate into separate CMM scratch folders to keep the NX parts organized. The scratch folders can be named CMMScratch1 through CMMScratchN, for example. When you start to migrate the assemblies, you want to be able to reuse these migrated parts. To do this, you can make use of CMMSolo's Reuse Lookup Table functionality. When you set the Reuse Lookup Table option prior to starting your migrations, CMM tracks the location of each source item and the scratch folder where the migrated NX part is located. In doing this, CMM is able to reuse previously migrated parts and subassemblies. It is possible that the same parts and subassemlies may be contained in different source CAD directories. For example, Part1 could be migrated from PartFolder1. When an assembly using that part is migrated, the part will also be in the source CAD folder for the assembly. To support this, CMM determines if the Part1 filename, file size, and checksum are the same. If they are, it is considered the same file. Setting the Reuse Lookup Table changes the previous default CMMSolo Remigration behavior. Even if you are migrating to the same scratch directory, you will receive a pop-up dialog box asking you to confirm that two items are the same. Previously, items being migrated to the same scratch directory were assumed to be the same. With the Reuse Lookup Table in use, the source directory is used to determine if items are the same. CMM Solo

Appendix A: CMM Solo Appendix A: CMM Solo

CMM Solo The Reuse Lookup Table information is stored in the location defined by the Reuse Lookup Table Location option. This directory should be a unique location for each user. It should also be a location that is not likely to be deleted or modified by anyone or any process other than CMM. When two items match, the previously migrated item is used. It is important to note that the previously migrated item is not removed from the original scratch directory or copied to the new scratch directory. The item always remains in the scratch directory where it was migrated the first time. This is the only copy of the migrated item. Even in the case of remigration, when two items are set to the duplicates of each other and either one is remigrated, the resulting NX file is placed in the folder where the item was first migrated. The two items are never separated. Since migrated items are stored in separate directories, to open an assembly in NX, you must ensure that NX can use all needed directories as search directories. Otherwise, NX can't find all of the needed parts or subassemblies. NX uses Assembly Load Options to locate dependent items. In NX, set the Load option to From Search Folders and add all of the necessary CMM scratch folders to the search list. The list of all scratch folders can be found on the Reuse Lookup Table options page in CMMSolo. Once you have added all of the folders, you can select the NX Saved Load Options option in the Assembly Load Options dialog box to save this set of folders. This functionality is applicable for Pro/E, SolidWorks, and CATIA V5 migrations. It is not effective for CATIA V4 or I-deas data due to the structure of the source CAD data. Tracking your migration progress CMM Solo provides the ability to locate source CAD data, identify duplicates and determine which items have been migrated and which items remain to be migrated. Before you start the migration, it is recommended that you use the Audit source CAD files menu action to determine which files are duplicates of each other, but are located in separate directories. Once you have started the migration, you can use the Determine migrated files and Determine unmigrated files menu actions to generate reports on the files that have and have not been migrated. This functionality only works when the Reuse Lookup Table option is selected. Importing items into Teamcenter Many users want to import their migrated NX data into Teamcenter. CMM Solo supports this with a three step process.

• Prepare data for import
• Import to Teamcenter
• Update item import status CMM Solo

Appendix A: CMM Solo It is important that you know the complete set of data that you want to import before starting this process. CMM Solo uses the NX utility tcin_import.exe. It is important that you understand this utility prior to importing data into Teamcenter. Prepare data for import This step lets you identify the NX data to be imported and set certain values for the import. Due to the limitations of the NX import process, you must identify multiple revisions of an item before importing them and import them in the correct order. Based on your selection of migrated NX data, the Import Driver file is created. The file is a tab-delimited file that contains every item to be imported. For each item, the following columns are provided and you set the import values in the columns.

• NX File — Path and file name for the NX item to be imported. Do not modify this.
• Top Level — This item should be the top level item and is identified for performance reasons. Do not modify this.
• Item Type — Part, assembly, or drawing type. Do not modify this.
• Status — This indicates the status of the item, either migrated or imported. You can modify this.
• Item ID — The item ID used by Teamcenter for this item. You can modify this.
• Item Revision — The Teamcenter item revision. You can modify this.
• Item Name — The Teamcenter item name. You can modify this.
• Folder — The Teamcenter folder where the item should be stored. This is the complete path defined by :folder1:folder2. You can modify this.
• Comment — A user comment for the item revision in Teamcenter. You can modify this. Import to Teamcenter This step performs the actual import of the data into Teamcenter. The file created in the Prepare data for import step is transformed into the file needed for the import process. It is recommended that you execute a dry run of this step to ensure that the import results are as you expected. CMM Solo supports this dry run through its dialog boxes. You may want to import data from more than one CMM scratch directory in a single session. To do this, you must set the search path in the load_options.def file for CMM. This file is located at

\comfig directory. Add the lines below to the file. Make sure any search path with spaces is surrounded by quotation marks and directories are separated by two backslashes, that is \. LoadOptions_SearchPaths:<C:\SearchPath1><C:\SearchPath2><C:\SearchPath3> Appendix A: CMM Solo

CMM Solo LoadOptions_SearchPaths:load_from_search_dirs By default, NX only supports one revision of an item in a single sesstion. Since CMM Solo uses the NX import capatiblity, by default, it only supports one revision also. To support more, you must change the NX user default. If you do not, each revision of an item that is imported becomes a new item in Teamcenter. Update item import status After you have imported a set of NX items into Teamcenter, it is important to update CMM Solo with the status of your import. It is likely that you chose to change an item ID, revision, or name before importing, or that one of those was automatically changed by the import process. To enable CMM Solo to track this information and produce the correct item ID and so on, it must have access to this information on the next import action. To do this, update the Import Driver file created in the Prepare data for import step with any changed information and mark each item successfully imported. Then run the Update item import status command. Run CMM Solo using command line options Run CMM Solo in batch or interactive mode from the command line using the following command line options. To perform a pre-migration scan of source CAD data without creating NX data, type: cmmSolo -mode scan (-datatype | –filelist | —folder ) -selection [-options ] [-rundir ] [-batch] [-noui | -ui] [-vguid |<vguid1,..,vguidN>]

• SourceCADSystem indicates the type of data to be scanned.
• The data to migrate is specified in one of three ways: o –filelist The is a file containing a list of CAD filenames. o –folder The folder contains CAD files. This option is only available for CATIA V5 migrations. o –selection The is a file containing an I-deas package file or a single CAD file. For I-deas data, a package file is used. For Pro/ENGINEER, or CATIA V4 data, a single file or a file list can be used. For CATIA V5 or SolidWorks data, a single file, a file list, or a folder can be used.
• OptionsFile defines the path and name of the options file to be used. CMM Solo

Appendix A: CMM Solo

• RunDir Is the directory where files generated by the migration are stored. This overrides the CMM Scratch and Report directories in the Options File
• batch causes the status window to automatically close when the process is complete, so that a script of batch commands can be used without interaction.
• noui or ui controls whether a UI is displayed. By default the UI is displayed unless Batch Mode is selected. This applies to CATIA V5 only.
• vguid |<vguid1,..,vguidN> defines a selection of I-deas data from the package file using the version guids. To migrate source CAD data to NX, type: (cmmSolo | nxmSolo) -mode migrate (-datatype | –filelist | —folder ) [-options ] [-runDir ] [-batch] [-noui | -ui] [-vguid |<vguid1,..,vguidN>] SourceCADSystem indicates the type of data to be processed. i = I-deas p = Pro/ENGINEER c= CATIA V4 c5 = CATIA V5 s = SolidWorks To renumber the part numbers and GUIDs in an I-deas package file, type: (cmmSolo | nxmSolo)-mode renumber -selection A new package file will be created. pkgFileName defines a complete path and name of an I-deas Package file. All files referenced in the package file must reside in the same directory. To renumber GUIDs in an I-deas Package file that are in passport format, type: (cmmSolo | nxmSolo) -mode passport -selection To delete migration data from within migrated NX parts, type: cmmSolo -mode delete -selection -datatype <i | p | c | c5 | s> Or: nxmSolo -mode delete -selection -datatype <s | c5> datatype indicates the type of data to be processed, using the same values as previously defined by the SourceCADSystem. This option deletes data placed inside the NX parts during the migration. This is the same as the CMM menu option Administration →Delete Migration Data described in Chapter 4. Appendix A: CMM Solo

CMM Solo To edit the CMM Options file, type: (cmmSolo or xmxSolo) -mode editoptions -datatype [-options ] CMM Solo