grant25
New member
- Feb 25, 2021
- 1
Hi everybody,
For context, I am relatively new to working with very large assemblies and best practices for NX config management. I am using NX 11 and Teamcenter.
I have a large, released, unmodifiable assembly that I need to create a new configuration from. There are many subassembly levels to it consisting of released parts from many years ago. My new config will require parts removed and replaced with new components throughout several of the subassemblies. Ideally, I would like a way to easily trace which parts have been removed from the original, where parts have been added, and which parts have been modified. So far, I have been saving off and modifying new subassemblies from the bottom up as required, but pretty quickly it seems to be snowballing into a configuration management nightmare. I'm just wondering if there's a better way.
To make matters worse, the original top level assembly is from several NX versions ago, takes over an hour to load, and always gives dozens of errors when it finally does (somehow it was released with circular references that will crash the load unless I bring in the structure only and load subassemblies piece by piece).
I don't need all of the original geometry data loaded for components that are not effected by the new config, but I still need the bodies visible. In my naive dream scenario, all of the original subcomponents are loaded as lightweight bodies, with to-be-removed components suppressed (but still visible in the tree), as controlled by my new top level configuration assembly. Then, I can add in the new and modified components in their respective subassemblies in a way that they are all easily identifiable.
I don't know if there is any way to achieve this or something similar, or what the best approach should be. If anything, it would at least be nice to be able to save off a new baseline full assembly of the original, consisting of lightweight dumb solids, where I can own and modify each of the subassemblies. I know this is possible, but I don't know how to do it without taking forever. Any help is appreciated.
For context, I am relatively new to working with very large assemblies and best practices for NX config management. I am using NX 11 and Teamcenter.
I have a large, released, unmodifiable assembly that I need to create a new configuration from. There are many subassembly levels to it consisting of released parts from many years ago. My new config will require parts removed and replaced with new components throughout several of the subassemblies. Ideally, I would like a way to easily trace which parts have been removed from the original, where parts have been added, and which parts have been modified. So far, I have been saving off and modifying new subassemblies from the bottom up as required, but pretty quickly it seems to be snowballing into a configuration management nightmare. I'm just wondering if there's a better way.
To make matters worse, the original top level assembly is from several NX versions ago, takes over an hour to load, and always gives dozens of errors when it finally does (somehow it was released with circular references that will crash the load unless I bring in the structure only and load subassemblies piece by piece).
I don't need all of the original geometry data loaded for components that are not effected by the new config, but I still need the bodies visible. In my naive dream scenario, all of the original subcomponents are loaded as lightweight bodies, with to-be-removed components suppressed (but still visible in the tree), as controlled by my new top level configuration assembly. Then, I can add in the new and modified components in their respective subassemblies in a way that they are all easily identifiable.
I don't know if there is any way to achieve this or something similar, or what the best approach should be. If anything, it would at least be nice to be able to save off a new baseline full assembly of the original, consisting of lightweight dumb solids, where I can own and modify each of the subassemblies. I know this is possible, but I don't know how to do it without taking forever. Any help is appreciated.