Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.

First time visiting? Here are some places to start:

  1. Looking for a certain topic? Check out the categories filter or use Search (upper right).
  2. Need support? Ask a question to our Community Support category.
  3. Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
  4. 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.

Part numbers and duplicated parts in Part Studios

emagdalenaC2iemagdalenaC2i Member, Developers Posts: 528 ✭✭✭✭✭
I would like to know your ideas about it.

Consider a model like the one in the image, in which several equal components have been designed in the same Part Studio


Then I can create an assembly, insert all the Part Studio and create all the required subassemblies

I can assign the same name, description and even Part number to all the equal parts, for example in the "Travesaño inclinado" parts. But:

  • The BOM does NOT group the components with the same Part number, name or description and consider them as different components.


  • The same happens when you insert the BOM in a drawing

  • Last but not least, if you try to use the Release management Onshape default workflows with an automatic part number generation, then a lot of issues appear and you can not create the release candidate.
So, there are a few questions here:
  1. Should I insert only single parts into the assembly and create arrays and replicas for the other instances?
  2. Will it allow us in the future Onshape to group pieces with the same part number in BOM and the release manager?
What do you think?
Un saludo,

Eduardo Magdalena                           C2i Change 2 improve                           ☑ ¿Por qué no organizamos una reunión online?   
                                                             Consulting Partner de Onshape                                      Averigua a quién conocemos en común

Comments

  • brucebartlettbrucebartlett Member, OS Professional, Mentor Posts: 1,833 PRO
    edited May 2018
    It might not be easy, but I believe part studio's need to be designed to have instances of parts, Ie. when copying, mirroring or patterning having the ability to able to tick a box to create instantiations which then will drop nicely into an assembly and BOM just works as expected not like @emagdalenaC2C 's example. However, with part studio instantiations I expect the part to be geometrically identical. 

    *edit, I thought I was on another post, sorry* In the case of the OP grouping non-identical parts in CAD has never been easy, I think SolidWorks BOM's had a group by name or part number but you had to be very careful.  In this case, pretty sure you could make something work with OpenBoM or workaround as @john_mcclary posted.
    Engineer ı Product Designer ı Onshape Consulting Partner
    Twitter: @onshapetricks  & @babart1977   
  • john_mcclaryjohn_mcclary Member, Developers Posts: 1,729 PRO
    Right, OpenBOM allows you to group parts by name, I forgot about that.

    I used it a few times before onshape bom... works pretty good actually
  • GWS50GWS50 Member Posts: 93 PRO
    I have had this issue recently and ended up inserting a single part and copying and pasting, then the BOM works as expected but it is time consuming and can get confusing. Being able to group 'same name' items would be great
  • emagdalenaC2iemagdalenaC2i Member, Developers Posts: 528 ✭✭✭✭✭
    edited May 2018
    I agree with you that the ideal option is that in a Part Studio the parts should be unique.

    However, when designing for example a model like the one indicated, it is much easier to create all the parts (even several equal parts) in the same Part Studio.

    During the design process some of these parts can be modified and have differences between them. For example, in the parts Pilar central, Pilar derecho and Pilar Izquierdo.

    To use this ideal system, only with unique parts in an assembly, I have duplicated the Part Studio 1, and these are all the steps I had to do:

    • Remove duplicate parts in the Part Studio

    • Insert the Part Studio in an assembly and fix the part "Pilar central"
    • Insert the symmetrical parts
    First Big issue... There are no mirror feature in assemblies

    So I have to insert and place the symmetrical parts one by one

    • Then I can create a linear pattern to create a few instances of the existing parts
    Second issue, there are not the option "Centered" in the assembly patterns

    So I have to create 2 linear patterns instead of one

    Third issue, there are no options in the patterns features (neither in the Part Studio nor in the assemblies) to eliminate a specific instance of a component. As the component indicated with the arrow below.


    So, after a while, I have all the components assembled again.

    And then... another issue.
    When I try to create the subassemblies necessary for the production and mounting of the general assembly... The creation of subassemblies obviously crashes with the patterns created in the assembly



    So, Do I have to create the subassemblies first and then create the general assembly with the above limitations?
    Un saludo,

    Eduardo Magdalena                           C2i Change 2 improve                           ☑ ¿Por qué no organizamos una reunión online?   
                                                                 Consulting Partner de Onshape                                      Averigua a quién conocemos en común
  • michael_mcclainmichael_mcclain Member Posts: 166 PRO
    I made some handrail sections, keeping as few parts in the part studio as possible, but for example, I had to add all posts in. I named the first instance of the post which would go into the assembly "h1". All following instances that were indentical I named "h1_inst".

    I added the whole part studio into the assembly. I copied the "h1" post and fastened them to the "h1_inst" in the same position to replace them later. I used group and fastened to replace any "_inst" parts to create only many instances of one part number for the BOM. At the end, I deleted all the "_inst" parts.

    Not the easiest workaround but if you know it well them it goes by quickly. It's best done if there won't be any downstream changes to the design. Of course, you can use OpenBOM to group parts with the same part numbers instead.
  • owen_sparksowen_sparks Member, Developers Posts: 2,219 PRO
    That is bit of a ball ache!

    How about keeping all the parts from the full partstudio in the assembly , but set the "Exclude from BOM" parameter for all the duplicates, and then do a copy of the instances directly on top of each other.  It's a bodge but the instance count would be right, and it would look OK on the screen.

    Owen S.
    Production Engineer
    HWM-Water Ltd
  • john_mcclaryjohn_mcclary Member, Developers Posts: 1,729 PRO
    Yea, the group mate in that case seems very volatile to any part edits. Seeings how group will hold the relative position of the part's studio origin.

    Has someone started an IR for combine in BOM yet?
  • lougallolougallo Member, Administrator, Moderator, Onshape Employees, Developers Posts: 1,631
    Mirror will come to assemblies but instantiation of like components would need to be present for weldmwnts as well. We realize this workflow is conmon and wlll address it. Todsy unsing in content assembly modeling is the best solution today to maintain the unique part instancing. 
    Lou Gallo / PD/UX - Support - Community / Onshape, Inc.
  • michael_mcclainmichael_mcclain Member Posts: 166 PRO
    lougallo said:
    Mirror will come to assemblies but instantiation of like components would need to be present for weldmwnts as well. We realize this workflow is conmon and wlll address it. Todsy unsing in content assembly modeling is the best solution today to maintain the unique part instancing. 
    Excellent! This is very useful and necessary functionality for us in the steel industry and for those building wood frame structures.

    On a side note...
    Slow down when typing ha. It happens to the best of us in a rush
  • emagdalenaC2iemagdalenaC2i Member, Developers Posts: 528 ✭✭✭✭✭
    lougallo said:
    Mirror will come to assemblies... 
    I know... I believe that SolidWorks added the mirror components in assemblies in the 2001 release!!!
    So, it took 8 years to add this feature in SolidWorks (since 1993, the year in which the company was created. The first release was in 1995)
    So you still have some time ... but this time users can not wait 8 years  ;)
    lougallo said:
    ...but instantiation of like components would need to be present for weldmwnts as well. We realize this workflow is conmon and wlll address it.


    Un saludo,

    Eduardo Magdalena                           C2i Change 2 improve                           ☑ ¿Por qué no organizamos una reunión online?   
                                                                 Consulting Partner de Onshape                                      Averigua a quién conocemos en común
Sign In or Register to comment.