2 Replies Latest reply on Jul 22, 2014 4:40 PM by Jeff Holliday

    Best way to start and edit an assembly?

    Dionysios Nikolaidis

      I am wondering what is the best practice for creating an assembly in order to faster edit parts based on their interaction.

      I used to create a different part per file as a new user, then the longer I am using solidworks, I see that maybe it would be best to output all my parts from solids created in one single (master part) file, with one single blueprint per plane. That way I only have one blueprint to change (in the master file) instead of creating many part files with many blueprints and multiplying the time it takes to edit things.


      So from now on, I'm thinking to just insert my solids into a new part, then use that part in the assembly. I'm thinking it would be a cleaner, faster way to deal with changes.

      What do you guys think? Am I on the right track?

        • Re: Best way to start and edit an assembly?
          Jeff Mirisola

          There are those who subscribe to top-down assembly (which is what I believe you're contemplating) and then those who subscribe to bottom-up assembly. Both have their pros and cons, and I seriously doubt any sort of concensus will be reached here.

          Personally, I prefer bottom-up assembly (parts created separately then added to the assembly). The method that you're describing would result in numerous external references, which I hate. I've been bitten by them too many times to use them as a permanent feature in any part I create. I'll use them when necessary, but remove them as soon as possible.

          If the parts you create are specific to one assembly, then top-down assembly may be the way to go. Maybe.

          • Re: Best way to start and edit an assembly?
            Jeff Holliday

            I agree with Jeff. Top-down can work well for unique assemblies but I prefer bottom-up for assemblies containing parts used in other places.