Application

The Application options provide preferences for general migration operation. Migration Controls Migration Controls options specify how you want the migration to run.

• Source CAD System This option defines the specific installed version of CATIA V4 used for the migration.
• Target data o Managed Lets you manage the new NX part files within the Teamcenter environment. o Filesystem The new NX part files are in an unmanaged data management environment (on the file system). This option is useful when performing a test migration because the Teamcenter database is not modified.
• CMM Process Mode Specifies the process your site will use to control data access during and after migration. o Project Select this option if your migration process uses a Teamcenter project to lock data during migration. If Project is selected, CMM will check that users are following this process. When you perform a pre-migration scan of your data, CMM will give a warning if the data to be migrated is not assigned to a project. When you migrate your data, CMM will not perform the migration if the data is not assigned to a project. o Status Select this option if your migration process uses the method of applying a Teamcenter status to lock data during migration. If Status is selected, CMM will check that users are following this process. When you perform a pre-migration scan of your data, CMM will give a warning if the data to be migrated is not assigned a status. When you migrate your data, CMM will not perform the migration if the data is not assigned a status. o None Select this option if you have some other process in place to control access to migrated data. If this option is selected, CMM will write a message in the log file, but will not perform any checking during pre-migration scans or when migrating data. CMM options – CATIA V4

CMM options – CATIA V4

• Status/Project for Process Mode Define the status or projects that will be allowed to migrate. Separate multiple values with a semicolon.
• Skip Check Out Reused Review Status This option allows you to establish a process that uses the CMM Review Status of a previously migrated item to determine whether it should be checked out when reused in any future migration. You can set this option to Approved, +PendingApproval or ++PendingRepair. The status of the reused part will be compared to this setting. For example, if you set this option to +PendingApproval, and a reused part has a status of Pending Approval or Approved, the migration will continue without checking out the reused part. You must ensure that no user will modify these parts while they are being reused in a migration.
• Generate JT from Source CAD Dataset Creates a DirectModel dataset (JT file) for the migrated part. This option is off by default.
• Scratch Location Location for miscellaneous files created during migration (deleted at completion of migration) and log files. This is also the location for new NX part files if you are migrating to an unmanaged data management environment (on the file system). The default directory is: %TEMP%\CMMScratch Use an empty directory. A directory is automatically created if you specify one that does not exist. Do not make this directory the same as the temp directory. Do not use the same location for multiple users or when running concurrent sessions. You might need to allocate a lot of disk space to this directory depending upon the size and number of the migrated items.
• Report location Directory location for migration reports.
• Report Style Sheet Location of the XSL style sheet needed to view the migration report.
• Item Type Map File Path and name of the file containing the item type map. This file is customer specific.
• Attribute Map File Path and name of the file containing the attribute map. This file is customer specific.
• Attributes Validation If this is selected, attributes defined in the Attribute Map File are validated.
• Migrated Attribute Prefix Set the prefix for the migrated attributes’ names to the given value. Chapter 13: CMM options – CATIA V4

CMM options – CATIA V4

• Match Owning Group If selected, when migrating through Dispatcher/client with Owner set to DC, the child items are owned by the DC Proxy user, but have the owning group of the parent CATIA dataset. The DC Proxy user must be in all groups. If not selected, the owning group is the DC Proxy user’s login group.
• Store files in glob volume If selected, in Displatcher/client mode, all files created are stored in the volume of the parent owning group. If not possible, the volume of the parent dataset us used. If not selected, all files are stored in the user’s default volume.
• Failed Items Folder Directory location to store all items that failed migration. You can review this single folder to see everything that failed migration. After migration passes, you need to remove it from this folder. Quarantine The Quarantine operation keeps parts with certain issues from being migrated, or migrates them as B-Rep parts. The Quarantine options specify the action taken if a quarantine is used and what is checked during the quarantine operation.
• Quarantine Action Defines the quarantine action. Disabled The quarantine check is not performed. Info only Provides quarantine information only, but does not affect migration of the item. Brep Creates a B-Rep part model if there is a quarantine failure. Failed Marks the item as failed and stops processing any dependent items if a quarantine error is found.
• Quarantine Missing Required Attributes Quarantines items if they have any missing required attributes.
• Quarantine Dead/Inactive CSG Nodes Quarantines items with dead or inactive CSG nodes.
• Quarantine Corrupt SolidE Quarantines items with corrupt SolidE.
• Quarantine Unsupported Entities Quarantines items with unsupported entities.
• Quarantine Unsupported Features and Operations Quarantines items with unsupported features. CMM options – CATIA V4

CMM options – CATIA V4 Remigration The Remigration options specify the parameters for migration of previously migrated items. When you remigrate a part, all of the parent items should be remigrated. Otherwise, the dependents will not be updated. Remigration is not an update. Any changes made to the part after the previous migration are not kept. If an item is remigrated, the existing NX dataset and the newly created one are given version numbers.

• Remigrate o Disabled With this option selected, CMM does not remigrate any items. o Selected Remigrates the items that have been selected. o All Remigrates selected items and children of those items.
• Remigrate Native NX The purpose of this option is to allow you to use a process where JT files (Direct Model datasets) from the original CAD system are used as NX parts (B-Rep only) before the parts are migrated using CMM. This is especially true if the NX Refile utility is used. The NX Refile utility converts these datasets to NX datsets, which look the same as datasets migrated using CMM, even though they do not contain feature history migrated using CMM. With this Remigrate Native NX option turned off, CMM will not override these NX datasets. If you want to migrate the original models to create fully-featured NX datasets, turn this option on. CMM will force the remigration of the original models and replace the existing NX datasets. This is enabled even if Remigration is turned off. Chapter 13: CMM options – CATIA V4

CMM options – CATIA V4

• CMM Version Conditional Remigrates items relative to a CMM version. For example, < indicates that items that have already been migrated prior to a specific CMM version (indicated below) are remigrated. The conditions available are: o < o <= o

  o

= o

• CMM Version Version of CMM used with the version condition (above). The syntax is N.N.N.NNN. You can also use partial strings, for example, 4.0.
• Item Type Remigrates specific item types. o All Remigrates all item types. o Assemblies & Drawings Remigrates only assemblies and drawings.

• Migration Date Conditional Remigrates items relative to a date and time. For example, < indicates that items that have already been migrated prior to a specific date (indicated below) are remigrated. The conditions available are: o < o <= o

  o

= o

• Migration Date Date used with migration date condition (above). The syntax is YYYY-MM-DD HH:MM:SS. You can also use partial strings, for example, 2006-02. CMM options – CATIA V4

CMM options – CATIA V4

• Report Status Remigrates items based on the Report Status field on the CMM Attributes form. o All Remigrates all items regardless of whether they passed or not. o Failure Remigrates items that failed migration. o +Warnings Remigrates items that failed migration and had warnings during migration.
• Review Status Remigrates items based on their review status. The review status is identified in the ReviewStatus field on the CMM attributes form. Phased migration uses this option. o Rejected Remigrates only those items that have a rejected status. o +Not checked Remigrates items that have status of rejected or not checked. o ++pendingRepair Remigrates items that have a status of rejected, not checked, or pending repair. o +++pendingApproval Remigrates items that have a status of rejected, not checked, pending repair, or pending approval. Chapter 13: CMM options – CATIA V4

CMM options – CATIA V4 Phased Migration Phased migration migrates the parent if the child components meet the status criteria defined in the options.

• Check Review Status Use the following review status for child components to determine whether the parent item is migrated. The review status is identified in the ReviewStatus field in the CMM attributes form for child components. The review status is also checked during remigration. Items with Approved status are not remigrated. o Approved Migrates the parent item if the child components have only an approved status. o +PendingApproval Migrates the parent item if the child components have an approved or pending approval status. o ++PendingRepair Migrates the parent item if the child components have an approved, pending approval, or pending repair status. Actions These options specify how you want the migration to proceed when items fail to migrate or do not migrate as expected.
• Migrate action o NeverStop Migration does not stop even though failures have occurred. Failures are defined by the Success Criteria category described above. o StopAfter Stops the migration after a specified number of failures. Failures are defined by the Success Criteria category described above. Number of failures is defined in Error limit described below.
• Error limit Stops the migration process after a specified number of failures.
• Migration Timeout [mins] Maximum amount of time that CMM will try to migrate an item before it aborts the migration process. The time is specified in minutes.
• Item fail action o SeedItem CMM options – CATIA V4

CMM options – CATIA V4 If the migration process does not produce an NX part, then use a seed (empty) part. This allows dependent hierarchies to be migrated. o SkipItem If the migration process does not produce an NX part, then skip the item. Dependent hierarchies are also skipped (not migrated).

• Restart services after items Restarts the CATIA migration and NX migration services after migrating a certain number of items. This option and the next option are set at these default values for performance reasons.
• Restart services after total file size (MB) Restarts the CATIA migration and NX migration services after migrating a specific total file size.
• Create CMM Attribute Creates a form that contains CMM migration attributes. The form is placed in the item revision for the migrated item. You can perform a search in My Teamcenter on any of the fields in the form to find items with similar migration attributes. To enable this functionality, you may need to update the Teamcenter schema. For information on updating the schema, see the Configuration Guide chapter.
• Confirm Selection Pauses the migration process to allow you to confirm your selection before migrating. Click the OK button on the Migration Status dialog box to proceed with migration. If not checked, starts the migration process immediately for the items selected.
• Store CMM Log File in Teamcenter If selected, stores the CMM Log File in Teamcenter. If not selected, stores the CMM Log File in the scratch location folder.
• Store Child Scan Reports in Teamcenter If selected, stores Pre-Migration Scan Reports for both the Glob Parent and its Children in Teamcenter. If not selected, store the Pre-Migration scan reports for only the Glob Parent.
• Submit to Dispatcher Translation Priority Values of 1,2, and 3 correspond to low, medium, and high priority.
• Submit to Dispatcher Translator Name Select the name of the CMM migration translator to use for the migration. Cleanup Scratch Use these options to clean up the CMM scratch folder after the migration.
• Delete Report Files Select this option to clean up the report files.
• Delete Associated Files Select this option to delete associated files including Maps, PSDs, and History files.
• Delete Scratch Files Select this option to clean up the scratch files. Chapter 13: CMM options – CATIA V4

CMM options – CATIA V4

• Delete Translation Files Select this option to clean up the translation files, including EPF and XPK files.
• Delete SourceCAD Select this option to clean up the original CATIA source CAD files. NX Part The NX Part options specify the configuration for a migrated item.
• Model Template Item ID This is the item ID for the part seed template.
• Model Template Item Revision This is the item revision for the part seed template.
• Assembly Template Item ID This is the item ID for the assembly seed template.
• Assembly Template Item Revision This is the item revision for the assembly seed template.
• Drawing Template Item ID This is the item ID for the part drawing seed template.
• Drawing Template Item Revision This is the item revision for the drawing seed template.
• Non-Master Part Type o Specification The migrated item is created with specification type relations. These relations are detailed methods, designs, processes and procedures used to satisfy requirements. o Manifestation The migrated item is created with manifestation type relations. These relations are non-defining snapshots of a particular aspect of an item at a specific moment in time. The information is only accurate as long as the item revision does not change. For additional information on these relation types, see the Teamcenter Online Help Documentation.
• Model Template File Path and name of the file that contains the seed part.
• Assembly Template File Path and name of the file that contains the seed part for assemblies.
• Drawing Template File Path and name of the file that contains the seed part for drawings.
• Default Target Units Default units used when creating NX parts. This is not used when the template file is provided. CMM options – CATIA V4

CMM options – CATIA V4 User Data The User Data fields allow you to enter data applicable to your site.

• Set CMM Attributes Field User_Field_1 Enter data specific to the migration or to the set of data you are migrating, such as Migration Test 1, or Customer XYZ Data. User Data fields User_Field_2, User_Field_3, User_Field_4 provide the same functionality. Chapter 13: CMM options – CATIA V4

CMM options – CATIA V4