CMM Catia Imprecise Constraint Issue

CMM Catia Imprecise Constraint Issue SYMPTOM/PROBLEM

Environment setup:

Teamcenter 10.1.5.x (64bit)

TCIC 10.0.4

NX 10.0.3.5 

CATIA V5 R21

CMM 10.0.3

Issue description

Assembly constraints are lost during imprecise migration.

Assembly migration in imprecise mode with Teamcenter revision rule and CMM  Revision Rule  •Latest by Alpha Revision Order–

Teamcenter Revision Rule

 

CMM Options

 

Test Assembly

The Catia assembly was last saved with the revisions •00– of both components. Content Migration according to the revision rule uses Part2/01 instead of Part2/00.

 

Assembly Constraints in CAT Product

Simple assembly with two parts and two assembly constraints. Screenshot shows the assembly loaded from Teamcenter with the latest revisions loaded. Assembly will not be saved, i.e. the CATProduct file that will be migrated was last saved with revisions •00–.

 

Assembly Constraints in NX assembly after imprecise migration

Migration does work well according to the imprecise structure, i.e. the current revisions are honored during the migration. But both assembly constraints are lost. Visible in screenshot below by the circle in the position column in ANT.

 

CMM Scratch files are available for this migration (see Folder CMMScratch_BG021150_Run1)

CMM Report shows the missing constraints.

 

Migration after saving CATProduct first

When the Catia assembly is first saved in Tc/TcIC context, so that not only the BOM but also the real CATProduct file represents the updated imprecise structure, then both constraints are created and available in the NX assembly. 

This is represented in the following screenshot by the fix symbole and the half-filled circle in the ANT position column.

 

CMM Scratch files are available for this migration (see Folder CMMScratch_BG021150_Run2)

EXPECTATIONS:

Assembly constraints need to be created in CMM whether or not the migration is done precise or imprecise. Since the constraints are created when the CATProduct was saved prior migration the issue are not missing or relabeled geometry objects. It seems to be a mapping issue because one of the components has a newer revision.

ANALYSES

NA

HOW TO REPRODUCE THE PROBELM:

Download the provided data file from GTAC (File: .zip)

— Create simple assembly with two parts in Catia

— Create some constraints between the two parts

— Save assembly and parts to Teamcenter

— Close assembly

— Open one of the parts in Catia and modify it without topological changes (i.e. just change some dimensions)

— Save the part into a new revision

— Set Teamcenter and CMM revision rule to latest working and check in Structure Editor that for both parts the latest revision are loaded

— Migrate assembly with CMM (check that latest revisions are used in migration)

— After migration check the CMM report for constraints imported. There will be no NX Constraints created

SUPPORTING DATA: .zip

—	Worddoc with description and screenshots

—	Scratch directories for both migration tests

—	Catia data of the test assembly

WORKAROUND: 

Save all CATIA assemblies prior to CMM migration

This is no useable workaround in a production environment with about 20”000 assemblies to be migrated

PLATFORM:

Tested on Windows

PLATFORM SPECIFIC:

N/A

VERSION SPECIFIC:

N/A

ADDITIONAL INFORMATION:

The problem "CMM Catia Imprecise Constraint Issue" has been investigated and the following has been found.

The problem where NX assembly constraints are not created when CMM migrating CatiaV5 data using a Teamcenter Imprecise precision option is closed as a the child parts (based on Imprecise rules) are built within the NX assembly by the CMM migration. This is being closed as a Enhancement Request sinceproviding a solution to the constraints problem will be done as a future project. PR 7912769 Product Information: Product: NX , Application: CMM , Version: V11.0