ralinaresg
Mechanical
- Mar 5, 2020
- 6
Hello Eng-tips,
My organization is looking to leverage PMI more. One annoyance that I have bumped into is the issue with the "custom views" not showing in the slave drawing parts unless you make them in the slave's modeling environment. This applies to exploded views of course, but seems to also be the case for PMI section views. I know this was a deliberate decision from Siemens a few NX versions back (NX 8 I think, but can't remember exactly) but I forget the motivation.
Ideally we want to contain all the PMI inside the master model, together with all its features. It makes sense for an engineer to size a bearing bore and include the fit needed in that particular feature for the part to work properly, rather than to switch to a slave model to include this information. This workflow is why we are so interested in PMI. We understand that it would require part revisions due to a tolerance change, but again, this makes sense to us.
Now, in its current state, this would mean that we couldn't make drawing slaves, which is a practice that we have held for a long time. This means that if we would like to control drawing changes on how the part is presented or drafted (but no actual design change) we would need to rev the part instead of a slave file. This is very undesirable and doesn't make much sense.
Is there an intended workflow? The best reference I could find in the forum is a few years old and incomplete.
How is your organization managing this?
For context we are using Native NX12. Maybe Teamcenter makes this manageable?
My organization is looking to leverage PMI more. One annoyance that I have bumped into is the issue with the "custom views" not showing in the slave drawing parts unless you make them in the slave's modeling environment. This applies to exploded views of course, but seems to also be the case for PMI section views. I know this was a deliberate decision from Siemens a few NX versions back (NX 8 I think, but can't remember exactly) but I forget the motivation.
Ideally we want to contain all the PMI inside the master model, together with all its features. It makes sense for an engineer to size a bearing bore and include the fit needed in that particular feature for the part to work properly, rather than to switch to a slave model to include this information. This workflow is why we are so interested in PMI. We understand that it would require part revisions due to a tolerance change, but again, this makes sense to us.
Now, in its current state, this would mean that we couldn't make drawing slaves, which is a practice that we have held for a long time. This means that if we would like to control drawing changes on how the part is presented or drafted (but no actual design change) we would need to rev the part instead of a slave file. This is very undesirable and doesn't make much sense.
Is there an intended workflow? The best reference I could find in the forum is a few years old and incomplete.
How is your organization managing this?
For context we are using Native NX12. Maybe Teamcenter makes this manageable?