My understanding of a BoM is that it's essentially a list of the various components required for an electronic product or module. Does this mean it could be as simple as a spreadsheet?
Are there any formal standards/templates for BoM's citing required/mandatory fields/data that it must contain? Any good samples/templates that can be referenced?
Answer
Yup, BOM is a spreadsheet.
At minimum it should contain refdes and internal part number for each component.
If you don't maintain an internal parts database, it should contain refdes and manufacturer / full part number for each component.
If this is for a small build, I put the Digi-Key or Mouser part numbers on there too, so you can order off the BOM.
I like to coalesce identical part numbers so instead of a row for C1 and a row for C2 and a row for C3, I have a row for C1,C2,C3. This also necessitates a "quantity" column. It also makes it harder to look up a given refdes since they are not in order.
The BOM will be used by the guy ordering parts and the guy running the pick and place machine, so add any annotations you want those folks to see.
Oh, and the BOM is useful for costing if you add component prices on there. Again, this is for small runs. Big runs will use more sophisticated accounting.
No comments:
Post a Comment