best way to handle huge assemblies?
best way to handle huge assemblies?
(OP)
Hi,
Can we talk a little about how to handle huge assemblies in NX10/TC11 (we will upgrade to NX12 mid next year, so if you have advice that include NX 11 or 12 please post them too).
-How to handle, simplify, load, edit assemblies, place views in drawings etc.?
-How to use/divide assemblies so multiple NX users can work on same assembly.
Can we talk a little about how to handle huge assemblies in NX10/TC11 (we will upgrade to NX12 mid next year, so if you have advice that include NX 11 or 12 please post them too).
-How to handle, simplify, load, edit assemblies, place views in drawings etc.?
For example I can not find efficient way to use any of tools or techniques for simplifications. Each of NX simplification wizard solutions have unwanted issues (in way how we handle models in our work, not issues with tools itself), and simplification by arrangements can't be done as it load full assembly for each arrangement making models huge and hard to update, and simplification by reference sets does not give access to all levels of details for drawings.
-How to use/divide assemblies so multiple NX users can work on same assembly.
_____________________________
Enjoy your work and have fun!





RE: best way to handle huge assemblies?
Another way is to create JT files of the component or sub assy parts an open the JT versions for the areas of the Assembly you need to see in context but are not planning on working.
Josh
RE: best way to handle huge assemblies?
They are now utilizing Multi threading with loading and you can start working on the assembly while it is loading.
A refile is mandatory however. Only works on parts which are saved in NX12.
Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX9 / TC10.1.2
Building new PLM environment from Scratch using NX11 / TC11
RE: best way to handle huge assemblies?
We have setup that make JT automatically in TC, but I would like to hear how do you use JT in this context, maybe we can use this solution.
@NutAce, "A refile is mandatory however. Only works on parts which are saved in NX12." ouch! Well I still do not know if they will go for these kind of options that require refiling or not... I hope... But that is good to know!
_____________________________
Enjoy your work and have fun!
RE: best way to handle huge assemblies?
nothing wrong with refiling. It is even recommended when you skip multiple versions. Makes it a bit easier for the users when the data they are using is already in correct version.
Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX9 / TC10.1.2
Building new PLM environment from Scratch using NX11 / TC11
RE: best way to handle huge assemblies?
https://docs.plm.automation.siemens.com/tdoc/nx/12...
/Mattias
NX5 -> NX12
I-deas 12, NX I-deas6.6
Solid Works 2017
RE: best way to handle huge assemblies?
1) As Ronald notes, a refile will be required for the "streaming loading" which will be implemented in 12.x ( not in 12.0)
2) Refile will be retired...
- I wonder if Siemens left hand is aware of what Siemens right hand does...
Regards,
Tomas
RE: best way to handle huge assemblies?
In place of the refile utility, standalone utilities will be introduced that incorporate non-version-up related options and future NX batch processes.
/Mattias
NX5 -> NX12
I-deas 12, NX I-deas6.6
Solid Works 2017
RE: best way to handle huge assemblies?
This most probably has something to do with the fact that NX12 is the last "numbered" version of NX. There won't be an NX13.
Siemens doesn't yet want do disclose how they are going to continue but I am guessing they are going to follow the same way as Microsoft Windows 10 releases.
Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX9 / TC10.1.2
Building new PLM environment from Scratch using NX11 / TC11
RE: best way to handle huge assemblies?
RE: best way to handle huge assemblies?
Bookmarks can be used to similar effect with the advantage that the load options don't need to be changed, NX will only load what is specified in the bookmark file.
www.nxjournaling.com