NX CREO Assembly Features Visibility - NX – CREO MultiCAD Assemblies

Issue Description: - Assembly features Created in CREO are not visible in NX while working in a Teamcenter managed NX-CREO MultiCad Set-up.

Detailed Use Case: -

Input CAD data is received in CREO format. Customer uses NX, to create their CAD data around the CREO input data. This has been enabled using MultiCad Assembly creation mechanism with JT & Teamcenter. Input CREO Assembly is opened in Teamcenter Managed CREO & saved into Teamcenter as JT. These CREO JT files are then consumed in NX & further designing is executed till production drawing creation. Any design change in input CREO data is managed using Teamcenter revisioning mechanism. This allows seamless production drawing update & hence efficient change management.

Teamcenter Version - 13.3.0.4

Creo Version - 7.0.5.0

PLM components JT Translator for CREO Parametric 17.1.0

Issue detail: -

When the CREO CAD has CREO assembly Feature as shown below, the same was not reflecting in the JT files when they were opened in NX.

Problem Analysis: -

Assembly Features added in CREO & Saved as JT into Teamcenter Database, creates a CREO Assembly level JT file called as an ‘Override JT’. This was not visible when the same is opened in Teamcenter managed NX. However, this is visible in Teamcenter Structure manager & 3D Viewer.

CREO 'Override JT' can be made visible in Teamcenter managed NX with the steps shown below:

Solution:

Following Settings needs to be set in ‘NX Customer Defaults’

1.      Gateway->JT Files->Import Content-> Import Assembly level JT Geometry Overrides -> turn this ON

2.  Teamcenter Integration->General->Assembly->Structure Update on Load -> set it to ‘Complete’

3.   Teamcenter Integration->General->Parts Without NX Datasets-> Parts With JT Dataset->Add NX Datasets -> set it to ‘Never’

4.    Teamcenter Integration->General->Parts Without NX Datasets-> Parts With Other/No Dataset->Add NX Datasets -> set it to ‘Never’

CREO To JT Settings Pre-Requisites: 

Ensure following settings are maintained in the ‘proetojtplmxml.config’ file.