BOM's On/OFF The Drawing - What do you do?
How do you handle your BOMs for assemblies?
Do you put them on the drawing or in a separate database?
What are the pros and cons of why/what you do?
I have worked where the BOM was ON the drawing, though manually created vs. CAD created. That worked great.
I have worked where the BOM was OFF the drawing in a database, though manually created.
Now days, the 3D package (read Alibre) will generate the BOM for the drawing and I suppose you can export that out to a spreadsheet and then to a database system. Problem is that sometimes, in my experience, not everything on a BOM is CAD generated. For example there might be reference documents that would be manually added to a drawing’s BOM and also lots of times, one doesn’t have time to populate the model with all of the fasteners required for an assembly. This causes a problem with CAD generated BOMs where in the old days one could edit the BOM to show the correct amount – more of a time driven/dead-line kind of thing.
Further, if you use CAD to generate a BOM and export it out, you’ve lost associativity with the original assembly. Sooooo, if you delete something, and try to re-export, your item call-outs could be out of sync with your database BOM.
Here’s what I am thinking.
Keep your “official” BOM in a separate database and not have it shown on the drawing. But, make a CAD driven BOM at the beginning. Use it to populate your database BOM – first time. Put the BOM on the drawing, but hide/suppress it and then use it as a reference/check for the future. Manually update the database BOM as changes require. Still lots of trouble and time, but it’s just a thought.
What are you doing?
Thanks!
Bill
How do you handle your BOMs for assemblies?
Do you put them on the drawing or in a separate database?
What are the pros and cons of why/what you do?
I have worked where the BOM was ON the drawing, though manually created vs. CAD created. That worked great.
I have worked where the BOM was OFF the drawing in a database, though manually created.
Now days, the 3D package (read Alibre) will generate the BOM for the drawing and I suppose you can export that out to a spreadsheet and then to a database system. Problem is that sometimes, in my experience, not everything on a BOM is CAD generated. For example there might be reference documents that would be manually added to a drawing’s BOM and also lots of times, one doesn’t have time to populate the model with all of the fasteners required for an assembly. This causes a problem with CAD generated BOMs where in the old days one could edit the BOM to show the correct amount – more of a time driven/dead-line kind of thing.
Further, if you use CAD to generate a BOM and export it out, you’ve lost associativity with the original assembly. Sooooo, if you delete something, and try to re-export, your item call-outs could be out of sync with your database BOM.
Here’s what I am thinking.
Keep your “official” BOM in a separate database and not have it shown on the drawing. But, make a CAD driven BOM at the beginning. Use it to populate your database BOM – first time. Put the BOM on the drawing, but hide/suppress it and then use it as a reference/check for the future. Manually update the database BOM as changes require. Still lots of trouble and time, but it’s just a thought.
What are you doing?
Thanks!
Bill