BrittToolEngineer
Aerospace
I would like to know if it can be explained in more detail how to move to complete assembly approach in modeling and drafting with respect to modeling in layers and drafting in layers as well. I have an old post from Dasalo that refers to this, copied below, but would like to learn more:
mmauldin, I also worked exactly as you describe when designing tooling in a job-shop environment. This is how others worked at the shop so is how I initially learned. It took me quite awhile to move fully over to using assembly structure. Once I got used to it, and got my work flows established, I found that the software flowed much more smoothly and had a very clear, logical, and smooth progression. Drafting in particular worked very well for me using assemblies and not having to worry about layers and visible in view eventually sped up my work quite a bit. The workflow you describe can be very efficient but I always felt like I was swimming up stream against the will of the software designers. I think as the software develops this will only get worse. I am now in a situation where I work in an international collaborative environment and there is absolutely no contest as to which modeling strategy is easiest to jump right into and work collaboratively: Assembly structure with no layering wins hands down. I will also admit that having some sort of PLM system, like Teamcenter, really helps a ton as far as managing lots of components. If there are more than 3 or 4 people with access to the files it is pretty much essential.
mmauldin, I also worked exactly as you describe when designing tooling in a job-shop environment. This is how others worked at the shop so is how I initially learned. It took me quite awhile to move fully over to using assembly structure. Once I got used to it, and got my work flows established, I found that the software flowed much more smoothly and had a very clear, logical, and smooth progression. Drafting in particular worked very well for me using assemblies and not having to worry about layers and visible in view eventually sped up my work quite a bit. The workflow you describe can be very efficient but I always felt like I was swimming up stream against the will of the software designers. I think as the software develops this will only get worse. I am now in a situation where I work in an international collaborative environment and there is absolutely no contest as to which modeling strategy is easiest to jump right into and work collaboratively: Assembly structure with no layering wins hands down. I will also admit that having some sort of PLM system, like Teamcenter, really helps a ton as far as managing lots of components. If there are more than 3 or 4 people with access to the files it is pretty much essential.
