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.

Best approach to designing complex assemblies

bert_fouriebert_fourie Member, Simulation EVP Posts: 93 PRO
edited May 2016 in Community Support
I come from a free form modelling background, trying to convert and develop a parametric mindset. My question is about the best design approach. In free form modelling I would start building my design and add parts as I go along. In parametric, I want to retain design intent so the design has integrity allowing me to make easy changes later on. I now find that the approach of building the entire assembly in one Part Studio ends up very complex and not that easy to change later on, simply because there are so many operations in one studio and it becomes confusing. Please advise.

Best Answer

Answers

  • bert_fouriebert_fourie Member, Simulation EVP Posts: 93 PRO
    I may add that I understand I can use multiple part studios, but that seems cumbersome to navigate while you are building a design and the endpooint is not clear yet.

    Do parts across multiple studios retain relationships?
  • traveler_hauptmantraveler_hauptman Member, OS Professional, Mentor, Developers Posts: 419 PRO
    edited May 2016
    @bert_fourie More mature parametric CAD has ways to chunk the complexity (grouping operations so that you can label and think about the group instead of all its parts) so that it is less confusing. This is missing in Onshape.

    Using the  feature filter can help,

    My general rule is that if the parts have a shared mechanical interface that is changing, they go in the same studio. If there is a unidirectional relationship (the dimensions of one part always depend on another) then it's a good time to start another part studio if the current one is getting complex.


  • bert_fouriebert_fourie Member, Simulation EVP Posts: 93 PRO
    Thanks, understood. With time will come competence!
  • edward_petrilloedward_petrillo Member Posts: 70 EDU
    As a parts studio grows in complexity you will pay a price in performance as the overhead of navigating the feature tree and waiting for the model to refresh increases, not to mention uncovering any weaknesses in the graphics performance of your platform. After learning this lesson the hard way, I will be on the lookout for opportunities to partition a model into smaller sections.  One possible tactic is to choose a section of the model that can be derived into a new studio to serve as the basis for further elaboration of the model.  The resulting associativity between the studios mitigates some of the disadvantage of breaking up the model.  I've found that this approach can be more effective than joining independent parts studios into an assembly. 

    A model that has many parts arrayed around a plane of symmetry poses additional challenges.  Parts can only be mirrored in a parts studio, but mirroring a complex structure doubles the size of the studio in one fell swoop.  I'd welcome any suggestions on how to manage this particular design challenge most effectively.
  • shashank_aaryashashank_aarya Member Posts: 265 ✭✭✭
    One approach could be to create number of sketches in single part studio at locations according to the part position in assembly. They will have all the basic profiles which will belong to all the parts required in the assembly. After that particular sketch can be derived in new part studio to create the part accordingly. This will probably maintain some parametric association with respect to parts.
Sign In or Register to comment.