wiengines
Mechanical
- Nov 10, 2008
- 59
Using NX6...
We have been having a debate recently about how to handle our NX files when we run into situations where we have one part number that is supplied by multible suppliers. Generally, these parts will be castings, and the differences will be things like cast datum structures.
One camp believes that you create a complete model for supplier #1, and then link that body into a model for supplier #2. After that, they will do whatever they need to do to change the body to show how we recieve it from supplier #2.
The other camp believes that you create a complete model for supplier #1, and then perform a save as to create the model for supplier #2.
I see valid points in both approaches.
In approach #1, one would only have to update features in the first model and then have them cascade to the second model. However, we sometimes run into issues where we want to make a change to only the model for the first model, and not the second model (or the other way around)
In approach number #2, we have two seperate models that are not tied to each other, so it is much easier to make a change and only have it affect that particular model. However, some people do not prefer this approach because some of our models can have 1500-2000 features in them and it can become quite tedious making a change to both models. The fear exists that something that is done in one model may be missed in the other model.
I am curious to hear how others out there handle this type of scenerio.
Chris T.
Project Design Analyst
Kohler Co. Engine Division
We have been having a debate recently about how to handle our NX files when we run into situations where we have one part number that is supplied by multible suppliers. Generally, these parts will be castings, and the differences will be things like cast datum structures.
One camp believes that you create a complete model for supplier #1, and then link that body into a model for supplier #2. After that, they will do whatever they need to do to change the body to show how we recieve it from supplier #2.
The other camp believes that you create a complete model for supplier #1, and then perform a save as to create the model for supplier #2.
I see valid points in both approaches.
In approach #1, one would only have to update features in the first model and then have them cascade to the second model. However, we sometimes run into issues where we want to make a change to only the model for the first model, and not the second model (or the other way around)
In approach number #2, we have two seperate models that are not tied to each other, so it is much easier to make a change and only have it affect that particular model. However, some people do not prefer this approach because some of our models can have 1500-2000 features in them and it can become quite tedious making a change to both models. The fear exists that something that is done in one model may be missed in the other model.
I am curious to hear how others out there handle this type of scenerio.
Chris T.
Project Design Analyst
Kohler Co. Engine Division