Solidworks to NX/Tc translation(or migration)

[Dave K]

We are moving from Solidworks using their "vault" PDM system, to NX 9 and Teamcenter 10.

What I'm looking for is some best practice info, or how to on other companies migration from SW to NX/Tc. Has anyone used the migration tool that Siemens now has? we are talking with Siemens tomorrow about what that could do for us.

More info below:

So far the best method we have found, is to export an assembly out of SW as STEP214, open it in Native NX, so it creates the components and assembly, run a journal to add the file name as DB_PART_NAME, and then use "Import assembly into Teamcenter". While the files are still in native, we run a journal, which creates the attribute DB_PART_NAME, which it obtains from the file name.

Presently, our part number naming rules only allow a 6 digit nmerical string, so we have to use "auto generate" during the "import assembly into TC" step. This creates a problem, which we need to resolve...there is no check to see if the part already exists in Teamcenter. Since the 6 digit number is created by Teamcenter, we can have multiple copies of the same part, with different 6 digit numbers.

I think the obvious first step is to change the naming rules, which would allow us to use "auto translate" during the "import assembly into TC" step. This will make the file in Teamcenter use the same file name as in native, as I understand it. Still not ideal, but we have also created, and imported data already, which has the 6 digit number.

Second, the native NX files are all long names, ie "C12-34-567 This Is My Part.prt". I would like to get the first section, C12-34-567 as DB_PART_NUMBER. Could this be done with the same journal that adds DB_PART_NAME. The other option would be to use the entire file name, as DB_PART_NUMBER. I would like to avoid as much manual cleanup in Teamcenter, as possible.

A somewhat different subject, is what to do with the data we have already created/translated, that still carries the Teamcenter assigned 6 digit number. One possibility to to manually change it, next time the file is worked on, or torture someone by having them do it.

-Dave

-Dave

NX 7.5

 

[Dave K]

Let me add, we are on NX9 with Teamcenter 10.1. I need to fix my signature.

-Dave

NX 7.5

 

[cowski]

Second, the native NX files are all long names, ie "C12-34-567 This Is My Part.prt". I would like to get the first section, C12-34-567 as DB_PART_NUMBER. Could this be done with the same journal that adds DB_PART_NAME.

Yes, this can be done in the journal. The more consistent the file names are, the easier it is to do. For example, if the part number is always the first 10 characters of the file name, it is really easy to use the .SubString command to get those characters. You can even split the string into part number (first part) and part description (what's left) if you wanted. If the part numbers are not consistent, it can still be done - it'll just take a bit more work.

www.nxjournaling.com

 

[Arkance/PhoeNX]

I don't think you'll find too many who have used the new migration tool as it's only been released in the last few days.
My guess is that it's been tested by customers in conjunction with Siemens, so I'd see what they say.


Anthony Galante
Senior Support Engineer

NX5.0.6, NX6.0.5, NX7.5.5, NX8.0.0 -> NX8.0.3
NX8.5.0 -> NX8.5.3, NX9.0.0 -> NX9.0.3, NX10 Beta

 

[Dave K]

We will be talking to Siemens about this tool later today. I didn't realize it was that new, my brain was blending "integration" and "migration".

Once we see what the tool can do, I'll decide if we revisit the journal route, or not.



-Dave

NX 9, Teamcenter 10

 

[PeteSp]

Did you end up using this tool. I am interested in the results.

Thanks!

 

[daluigi]

Gunman,
Just by curiousity: why moving from SolidWorks to NX?