Cancel
Showing results for 
Search instead for 
Did you mean: 

Import Assembly into Teamcenter, Standard parts - Use existing

PLM World Member Legend PLM World Member Legend
PLM World Member Legend

When importing an assembly into teamcenter a standard part witch is already in teamcenter will be not be imported again, but uses the existing one. That's nice...

 

When we have standard parts witch ARE in teamcenter, but with a different name, you have to ability to choose "Select Existing Part", then navigate to the correct part to use and choose OK. That's nice to...

 

When importing a lot of large assemblies with numerous stardard parts, that are availible in teamcenter under a different name... That's terrible...

 

Is there a way to automatically "substitute" part while importing by setting rules? 

Like: for part bolt.prt use din912_bolt.prt

 

Else this will be such a cumbersome task that I'm considering to recreate all these standard parts in teamcenter with there original names.

Patrick Delisse
KMWE - Aero Engine
NX 12.0, TC 11.2, CAMPOST V22, Vericut 8.2, TDM 4.8
C#, VB, .NET
4 REPLIES 4

Re: Import Assembly into Teamcenter, Standard parts - Use existing

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

What I would do

- set up the import for one assembly, with all the stuff you want to deal with

- create the log file (Dry run?)

 

Then examine the log file for what it is doing for the "difficult" cases

And then write a journal/API program to

- open the assembly native mode,

- examine it,

- create your own import log with the appropriate substitutions.

 

Then just use that import log to do the actual import into TC ("select log file to set up import" in NX10)

If there are other settings required for import (beyond the log file) maybe journal then & just ask for the log file?

 

There may be something you can do with PLMXML as well (but I don't really know how that works)

 

 

Ken Akerboom Sr CAx Systems Engr, Moog, Inc.
Production: NX10.0.3.5 MP16/TC11.2
I'd rather be e-steamed than e-diseaseled


Re: Import Assembly into Teamcenter, Standard parts - Use existing

PLM World Member Legend PLM World Member Legend
PLM World Member Legend
Hmm, interesting concept.
So i'll have to create a journal that askes fore an assembly, cycles thru the components, and create a log file on the go, where components that match predefined rules, are substituded in the log.
It's definatly worth trying.
Patrick Delisse
KMWE - Aero Engine
NX 12.0, TC 11.2, CAMPOST V22, Vericut 8.2, TDM 4.8
C#, VB, .NET

Re: Import Assembly into Teamcenter, Standard parts - Use existing

PLM World Member Legend PLM World Member Legend
PLM World Member Legend
We' ve decided that we set up the standard parts as we would like them to be. Good time to get rid of all the legacy inconsistenties.
I also found out it's easier to prepare assemblies upfront in native NX and replace "old" library parts without the new ones.
Thuis van be easily automated without a journal
Patrick Delisse
KMWE - Aero Engine
NX 12.0, TC 11.2, CAMPOST V22, Vericut 8.2, TDM 4.8
C#, VB, .NET

Re: Import Assembly into Teamcenter, Standard parts - Use existing

PLM World Member Legend PLM World Member Legend
PLM World Member Legend
We' ve decided that we set up the standard parts as we would like them to be. Good time to get rid of all the legacy inconsistenties.
I also found out it's easier to prepare assemblies upfront in native NX and replace "old" library parts without the new ones.
This can be easily automated with a journal
Patrick Delisse
KMWE - Aero Engine
NX 12.0, TC 11.2, CAMPOST V22, Vericut 8.2, TDM 4.8
C#, VB, .NET