×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

Importing native NX files into Teamcenter

Importing native NX files into Teamcenter

Importing native NX files into Teamcenter

(OP)
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

RE: Importing native NX files into Teamcenter

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.

RE: Importing native NX files into Teamcenter

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

RE: Importing native NX files into Teamcenter


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

RE: Importing native NX files into Teamcenter

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

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

RE: Importing native NX files into Teamcenter

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

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

RE: Importing native NX files into Teamcenter

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.

RE: Importing native NX files into Teamcenter

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

RE: Importing native NX files into Teamcenter

(OP)
@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

RE: Importing native NX files into Teamcenter

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

RE: Importing native NX files into Teamcenter

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

RE: Importing native NX files into Teamcenter

(OP)
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

RE: Importing native NX files into Teamcenter

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

RE: Importing native NX files into Teamcenter

(OP)
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

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Resources

White Paper – Your Construction ERP RFP Checklist
Selecting business software for a medium to enterprise-sized construction concern is extremely challenging in large part because most enterprise resource planning (ERP) suites originated in the world of repetitive manufacturing and are therefore a poor fit for a project and asset-centric business. However, midsize to large contractors need the predictable, auditable processes that ERP delivers. Download Now

Close Box

Join Eng-Tips® Today!

Join your peers on the Internet's largest technical engineering professional community.
It's easy to join and it's free.

Here's Why Members Love Eng-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close