Notifications
Due Date
No due date set.
Depends on
#4 Learn PCB Editor
forksand/gammaray2usb
#2 Learn Schematic Editor
forksand/gammaray2usb
Reference: forksand/gammaray2usb#28
Loading…
Reference in new issue
There is no content yet.
Delete Branch '%!s(<nil>)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
There are various Bills of Material:
Fabrication BoM, as exported by KiCad PCB Editor's
File --> Fabrication Outputs --> BOM...This exports a.csvfile.Manufacturer's BoM. This is the format the manufacturer wants the BoM, with columns in a particular order, and particular fields. Usually
.csv,.xls, or.xlsxformat.Engineer's BoM. When making a new board, engineers make their own BoM as they are developing. Usually
.odsor other spreadsheet.Purchasing BoM. This is the BoM used by purchasing. It can include data like prices, HTS codes, multiple alternatie suppliers, minimum order quantities, etc.
Interactive HTML BoM. This is a plugin for KiCad that makes a nice viewable BoM in for a web browser.
How to keep all these in sync?
From KiPro:
The bill of materials is generated from the schematic editor. The schematic represents the master source for all BoMs. Procedures differ between firms but many design firms will have a standard set of fields that are added to each component. You can configure these in the Schematic Editor under Preferences->Field Name Templates. This is where you would add fields for "HTS codes", "Alternate Suppliers", etc.
Procedures for generating each type of BoM are then codified into Python scripts that generate them. These will select certain fields depending on which are needed for each BoM.
Changes should be made directly to the schematic (rather than to the BoM) or have a defined procedure for re-importing BoM changes after they are changed.
From KiPro:
The bill of materials is generated from the schematic editor. The schematic represents the master source for all BoMs. Procedures differ between firms but many design firms will have a standard set of fields that are added to each component. You can configure these in the Schematic Editor under Preferences->Field Name Templates. This is where you would add fields for "HTS codes", "Alternate Suppliers", etc.
Procedures for generating each type of BoM are then codified into Python scripts that generate them. These will select certain fields depending on which are needed for each BoM.
Changes should be made directly to the schematic (rather than to the BoM) or have a defined procedure for re-importing BoM changes after they are changed.