Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Automatically release parent assemblies when releasing a part
romeograham
Member, csevp Posts: 675 PRO
When we have an assembly that includes sub assemblies, and all parts and sub assemblies are Revisions, it is a huge amount of work to edit and re-release a part at the bottom level.
Consider this example arrangement (all parts and assemblies are Revisions):
Top Assembly-A
>sub assembly-A
>>sub assembly-A
>>>part-A
When the Part-A is edited and released to Rev B- it takes 4 releases (if I don't make any mistakes!) to end up with this:
Top Assembly-B
>sub assembly-B
>>sub assembly-B
>>>part-B
Please make it automatic!
The new workflow could be: edit the Workspace for the part and release Rev B - then Onshape will cascade the release up the chain, to give me Rev B throughout. Onshape knows what has changed, and which sub assemblies will need to be up-revved. Maybe there will be a checkbox that I can select or something, but really - in what scenario does anyone NOT need to Revise all the parents of a changed child?
See here for one of the recent excellent discussions on this topic.
Thanks!
Consider this example arrangement (all parts and assemblies are Revisions):
Top Assembly-A
>sub assembly-A
>>sub assembly-A
>>>part-A
When the Part-A is edited and released to Rev B- it takes 4 releases (if I don't make any mistakes!) to end up with this:
Top Assembly-B
>sub assembly-B
>>sub assembly-B
>>>part-B
Please make it automatic!
The new workflow could be: edit the Workspace for the part and release Rev B - then Onshape will cascade the release up the chain, to give me Rev B throughout. Onshape knows what has changed, and which sub assemblies will need to be up-revved. Maybe there will be a checkbox that I can select or something, but really - in what scenario does anyone NOT need to Revise all the parents of a changed child?
See here for one of the recent excellent discussions on this topic.
Thanks!
Tagged:
7
Comments
When you say "The Product Structure should only include the P/N", what exactly are you referring to? It seems totally valid to have a revision level associated with a document in the product data management tool (Onshape). If the revisions exist, the tool has to have some rule about what is actually displayed to the user, right? If you're just talking about BOM tables, the Revision level can be removed from those easily.
If I re-phrase what you're asking for out of onshape- is it that you want higher level assemblies to not be "out of date" if something below it is revised and still interchangeable (ie. no part numbers have changed, following your rules) because the "Product Structure" is still technically the same?
I think I understand what you're getting at (and find the discussion interesting). My feeling is that Onshape is still not designed to capture the "product structure" that should be ideally captured in and ERP or PLM system. In contrast to those systems, onshape is built for managing the "product data" consisting of 2D and 3D representations. In onshape we revise these representations, so the revision level IS an important part of product data and defines the "uniquess" of the REPRESENTATION. Then, trouble comes in when part numbers the identify "items" get confused with part numbers that identify 3D models or 2D drawings, which are representations of items. So, to me, I think that the way onshape deals with P/Ns and revisions is OK, because its really only managing representations of these items. The improvements need to come from integrations with the other systems that do manage the relationships of the items themselves (like the ERP systems).
Just my $0.02. Thanks for the discussion
When I mention Product Structure, I'm generically referring to the hierarchical BOM for a product, subsystem, etc. In my comment I was attempting to reinforce that the configuration of a product can be controlled without the need to include revisions of parts in the Product Structure. Any revision of a part should be interchangeable with any other revision of a part. So when I say "parts don't have revisions" I'm really referring to that idea. Parts certainly have revisions from the standpoint of individual item control. For example, I might add a hole to a part to make it lighter weight. This would definitely be a revision. If adding the hole does not affect its usage then it doesn't need a new part number and higher level assemblies should use it automatically (without the need to do release revisions up the chain) since the product structure doesn't care about part revisions.
Yes. That's generally what I'm saying. The determination of interchangeability or form/fit/function is not something that Onshape can do. It's a company change management process because all product have unique requirements. The decision of the change management process is reflected by whether a revision is released (in which case the higher level assemblies should just show the latest revision of the unchanged part number) or a new part number is created (in which case at least one level of higher-level assembly is affected).
CAD Engineering Manager