Importing native NX files into Teamcenter 1

[Suskam]

I have over 220 native NX 11 files to import into Teamcenter 11. There are around 20 or 30 assemblies with some common parts. Here's the catch; there are several revisions of each file, with the revision letter in the filename (example: 12345678-A.prt, 12345678-B.prt). If I import them, each revision is going to become a separate item. Any suggestions of how to avoid this problem? I would like to keep the part revision history.

Product Designer: I-Deas/NX/Catia
Automotive Industry

 

[Ehaviv]

One possible solution is to rename
the parts to the auto translate rule
and then use import with auto translate
Option.

To rename the parts use the clone command.

 

[looslib]

Rename the files to just the part number one at a time starting with the oldest revision.
Open the file from disk into a NX session connected to Teamcenter.
Save the file and check it in.
Repeat with the next revision until all are loaded.
Start with part files, then the assemblies. Set versioning rules to ignore the revision in the name so the assemblies pull the saved parts from TC, not disk. Finally, load the drawings.

"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[Ehaviv]

12345678-A.prt, 12345678-B. Become
12345678_A.prt 12345678_B.pr

 

[Suskam]

@looslib That might just work, except there's 2200 files. I'll check back with you in 4 years...

Product Designer: I-Deas/NX/Catia
Automotive Industry

 

[Suskam]

@Ehaviv I'm not sure what you are trying to convey.

Product Designer: I-Deas/NX/Catia
Automotive Industry

 

[Ehaviv]

I'll try to explain.
The auto translate rule do this.
It's converting a native part in
the following format.
12345678_A.prt and convert it to.
@DB/12345678/A.

So if all your native parts are of this format.

You can import them with the rule
Auto translate.

To bring your native parts to this format.
Use clone in a native session.
With replace -A to _A.

 

[Toost]

220 or 2200 ?

If there are 220, i would do trial and error on the NX import tools until i find the correct settings. ( then when you have found these, you can use the option of selecting a directory for the input.)
If there are 2200, i would contact a Teamcenter specialist who could help you run a "data loader tool" to Teamcenter directly.

Regards,
Tomas

 

[Suskam]

@Ehaviv: Thank you. I didn't know that naming the files that way would import the revision. I tried it and it did work, for my 1 test part. In order for that to work, I would have to clone 2200 files, and then import 2200 files. That fixes my problem, but doubled my work.

@Toost: Where do these "Teamcenter Specialists" hide? Would I have to contact Siemens directly? Or maybe a data translation company that works with NX?

Product Designer: I-Deas/NX/Catia
Automotive Industry

 

[Toost]

If i knew a method of sending pm's in this forum i would reply with a company name...
- I would imagine that this job could be done from anywhere in the world.

Regards,
Tomas

 

[NutAce]

I think the issue with your multiple revisions might be in NX. There is a setting which will block the usage of multiple revisions.
If this is set to not allow, the import utility might create a new part for each revision.
To allow for multiple revisions you have to go to Customer Defaults - Teamcenter Integration for NX - General - Multiple Revisions

Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX9 / TC10.1.2

Building new PLM environment from Scratch using NX12 / TC11

 

[Suskam]

Does that affect importing? I thought that setting was just for opening multiple revisions in the same NX session.

Product Designer: I-Deas/NX/Catia
Automotive Industry

 

[NutAce]

While importing an Assembly (import assembly into Teamcenter) , you are asking NX to create for you a structure. Which is basically the same as opening it.

Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX9 / TC10.1.2

Building new PLM environment from Scratch using NX12 / TC11

 

[Suskam]

I turned on the multiple revisions setting, reopened NX and ran a test. I'm still not getting separate revisions to import. I've tried all of the part actions. See attached pic. (If I import the 1st part rev, then go back and import the 2nd part rev, it will work.) Maybe what I'm trying to do is just not possible, but it doesn't seem that complicated.

Attachments not working for some reason.

Product Designer: I-Deas/NX/Catia
Automotive Industry