I use Shapr3D in a professional capacity including multiple assemblies which have 100’s of components & fasteners. Currently we have to manually enter BoMs into excel sheets, however, due to the growing size and complexity of our assemblies it is becoming unmanageable.
Having a proper assembly feature that will allow for the generation of BoMs within shaper3D will be a huge benefit and keep us on the platform.
Hi Mark,
Assemblies on our radar, and we’ll add a proper assembly function to Shapr3D at some point of time. However we can’t give you an exact time yet.
Mark I have a question for you since you said you do large assemblies in Shapr3D I am curious on how you are creating them because I also create assemblies in S3D. Do you create all your parts in one project design and assemble them there or do you create your parts as separate file names and then import them one by one into a design assembly. Because it is very frustrating that when adding new parts to a design you have to save them to a local location on the computer or ipad and then import them into the new assembly. I really think that S3D need to come up with a much better way of creating assemblies and a better way of inserting new parts into existing assemblies like a copy and paste approach. What is your thoughts.
Thank you
Hi Danno,
Currently, most of the models I use are pre-existing (I import them as .STEP files). However, for any new components or fasteners, I model them directly within the single project design. Yes, it’s still a bit of a hassle to import all the existing components, but with my process, you only need to do it once.
I wouldn’t recommend modeling the components separately (in different projects) because you would have to keep going back and re-importing them manually, as you mentioned, whenever any changes are made. This approach could be super frustrating. Unless or until the parametric + assemblies feature is added, it’s best to work on everything in the same assembly project.
To update the version numbers, I create duplicates of the assembly and store the old revision locally. I think managing individual updates for each component involves too much work and too many files and for my work its not super important.
I fully agree here, There needs to be an assembly work space in shaper,