Phased migration

Phased migration is an optional process used by CMM that migrates a higher level item (parent item) only if the lower level items (children of the parent) contain a specific review status. This provides a method for controlling migration of dependent items. The terms used for phased migration sound similar to the status values used to control access. They are not the same. Status values control the access of item revisions by users. The phased migration approval statuses are an attribute on a CMM attribute form stored with the item revision. The phased migration attributes control execution by CMM. They do not control the access by users. The type of approval status required is determined by setting the appropriate options. The status options are:

• Approved Using this setting, the parent items (assemblies and drawings) are migrated only after someone manually intervenes to approve the success of the migration of each of the child items.
• Pending Approval Using this setting, the parent items are migrated if the child items have an Approved or Pending Approval status. Items that pass the defined success criteria will have a status of Pending Approval. This allows the phased migration to automatically continue without manual intervention when child items are successfully migrated.
• Pending Repair Using this option is effectively the same as not using phased migration. The parent items are migrated if the child items have an Approved, Pending Approval, or Pending Repair status. That means that the migration continues regardless of the status of the child items. If you are migrating an assembly, the components of the assembly are migrated first. You can use the phased migration process to control the migration of the parent assembly depending on the status of the components. The ReviewStatus field on the CMM attributes form is populated with PendingApproval or PendingRepair after a child item is migrated. It is checked for the appropriate status during phased migration to determine whether dependent items are migrated. You can manually enter or change the status in the ReviewStatus field. Once you repair a part, you can update the ReviewStatus field. You can use attribute mapping to update the value of the ReviewStatus attribute from NX once you have repaired the part. The phased migration process can be changed based on the options selected. A part to migrate enters the migration process where a quarantine check is performed. This check is performed and the part passes quarantine and a featured NX part is created, or is created as a B-Rep NX part, or it is Best practices

Best practices not migrated. In this case (not migrated), it is identified as Pending Repair in the ReviewStatus field on the CMM attributes form and is repaired in the original CAD system before it is migrated again. If a featured NX part or B-Rep NX part is created, it is identified on the migration report as passing or failing. If the B-Rep part fails migration, it is identified as Pending Repair. If it passes, it is identified as Pending Approval. If the featured NX part does not pass the migration success criteria, it is identified as Pending Repair. If it passes, it is identified as Pending Approval. For the featured NX part, it is expected the repairs will take place in NX. Once repairs are made in NX, it is identified as Pending Approval. In this case, you would manually enter Pending Approval in the ReviewStatus field.