Migration process (General migration process)

There are two recommended process modes to control user access to items being migrated with CMM within Teamcenter. These processes are using a status or using projects. The recommended process is to use Teamcenter statuses to the item revision to control access. Status values need to be defined using Teamcenter BMIDE. How to implement this is different at each site, depending on your existing processes. Typical status values might be as listed below.

• CMM_Initial This status can be used to limit access of the item revision that has started the migration process. Only members of the CMM group can access the datasets in this item revision.
• CMM_Approved This status can be used to allow read access, but not modify access to item revisions. Apply this status to an item revision that has been approved for use, but should not be modified. In order to modify the item, a new item revision must first be created.
• CMM_Referenced This status can be applied to an item revision that is approved for use, but not for revision. For example, this status can be applied to standard parts that may be referenced in assemblies, but not modified. This status is typically used for item revisions migrated as B-Rep models. For each of these status values, use the Access Manager to create ACL (access control lists) to define the access privileges. These ACLs should be placed in the rule tree with other Has Status rules.

Condition: Has Status 2. Value: CMM_Initial, CMM_Approved, or CMM_Referenced 3. ACL Name: CMM_Status 4. Group: CMM 5. World 6. Write access 7. Change access If a migration process using projects is implemented, similar ACLs control the access to items assigned to a project used for migration. Your process should define at least two different projects. One project is used to lock data being migrated. Another project is used to give access for users to reference the data but not modify it after the migration. Optionally, another project could be used for normal design. Best practices

Best practices