The answer to this question is quite complicated, and it absolutely goes back to our rare situation, but I’ll try my best to explain a part of them.
First, we don’t design anything. Our customers provide us with drawings, and we manufacture parts based on those drawings. So we always start from the supplied documentation.
Most of these drawings are for sheet metal products made up of 100+ parts, welded or spot-welded together. You can think of each final product as an assembly consisting of tens or hundreds of sheet metal components.
To manufacture them, we first need to create the individual parts. Using SolidWorks, we build 3D models based on the received drawings, then export DXF files and send them to CAM software for production.
About 99% of these parts are never reused in other assemblies. So, if we receive an order with drawing number “AAA” that consists of 10 components, instead of saving each part separately (AAA-01, AAA-02, etc.), we create a single 3D model named “AAA” that contains 10 virtual parts. What’s the benefit of having 10 files with slightly different names, rather than one assembly with 10 virtual parts?
In very very rare cases, however, we decide to create separate drawings for specific parts to make things easier on the shop floor. for example, when a part is particularly complex or requires additional details for bending, inspection, or other processes. (But it’s really rare)
On top of this, when an assembly consists of around 50 components, SolidWorks (at least in our experience) performs better when using 50 virtual parts rather than opening 50 separate files.
I’m aware of options like Lightweight or Large Design Review, but virtual parts still seem to work more efficiently for us. In any case, we rarely need to create separate drawings for these parts, except in very rare situations.