吃瓜tv

What is a PCB assembly BOM?

A PCB assembly BOM, or bill of materials, identifies the components required for a particular board revision and assembly variant. It connects each fitted reference designator to a quantity, a purchasing identity and the information needed to distinguish that part from a similar-looking substitute. A useful BOM tells purchasing what may be bought and tells assembly what belongs on the board.

The BOM does not describe copper geometry or provide machine placement coordinates. Those tasks belong to fabrication data and the pick-and-place file. Release them together, with the assembly drawing and any variant notes, so that an approved component list is not paired with yesterday鈥檚 layout. For a checklist covering the complete package, use required files for PCB assembly.

An early quotation may start from an incomplete list if its gaps are identified. Purchasing approval needs a more definite instruction. Label uncertain components, proposed alternatives and unresolved quantities explicitly; do not let a convenient spreadsheet become accidental authorization to buy or substitute a component.

Make the BOM identify a build, not just a circuit

Put the assembly part number, hardware revision, variant name, and release date in the package manifest. These identify the build that the BOM describes. A filename such as final-bom-new.csv is not enough because another person may have a different final file. Use a stable revision identifier and record the matching schematic, PCB, and assembly drawing revisions. The bare board may remain unchanged while two assembly variants fit different components.

Each fitted row should identify the manufacturer and full manufacturer part number, quantity per board, reference designators, package or footprint, and a description useful for checking the part. A distributor stock code can support purchasing, but should not replace the manufacturer's identity. Packaging suffixes matter when they distinguish reel options, environmental grades, or other orderable characteristics. Do not silently truncate a long number because two spreadsheet cells appear similar.

Distinguish design data from purchasing data. Unit price, available stock, supplier, and delivery date can change without changing the approved design part. Keep those fields separate from the approved MPN and substitution status. Otherwise a purchasing edit can accidentally become an engineering change. A controlled approved-vendor or approved-part list can be linked to the BOM, but the assembler must still know which choices apply to this particular release.

For assemblies with mechanical hardware, cables, labels, firmware, or programmed devices, state whether those items are included in the same BOM or in a separate controlled list. The aim is not one enormous spreadsheet. The aim is a complete build definition with no unexplained gaps between electronics, programming, and final assembly responsibilities.

Check structure before sending the BOM

Paste CSV text or read a local CSV file. The checker looks for duplicate references, mismatched reference counts, missing purchasing fields and ambiguous fit status. Enter the number of boards to see fitted demand before attrition, packaging and minimum-order effects. It does not connect to a parts database, verify stock, interpret an XLSX workbook or decide that a replacement is equivalent.

For this checker, Quantity means the number of references represented by a row, including a DNP row. DNP references contribute zero installed demand. If your company instead uses a zero purchase quantity for DNP items, map that field to a separate column before using the example format. Avoid silently converting an unfamiliar spreadsheet convention.

A clean structural result is a useful starting point, not a release certificate. Footprint dimensions, pin mapping, voltage ratings, lifetime requirements and component condition require engineering and sourcing review. To compare the fitted reference set against placement data, continue to the existing DFA file-consistency tool.

Reconcile quantities and reference designators

Quantity per board should agree with the number of unique fitted reference designators in the row. If a row says quantity three but lists R1 and R2, stop and resolve the discrepancy. Do not let the assembler guess whether a reference was omitted or the quantity is wrong. For repeated parts, grouped references are convenient, but ranges such as R1-R10 should be expanded consistently before automated comparison.

Check reference uniqueness across all rows. The same designator should not refer to two different fitted components in one variant. Also compare the BOM set against the placement file and assembly drawing. A component present in placement data but absent from the BOM may be intentionally not fitted, or it may be a missing purchase item. Those cases need different treatment. The correct result is an explicit disposition, not a rule that every unmatched item is automatically deleted.

Consider a small example: the assembly uses R1, R2, and R5 with the same approved MPN. The BOM row has quantity three. Variant B omits R5, so its fitted quantity becomes two while R5 remains documented as DNP. The placement export may still contain R5 depending on CAD settings. The release instructions must state whether the assembler should filter the placement list using the variant BOM or receive a separate already-filtered placement file.

Do not confuse board quantity with per-board quantity. For 40 boards and three fitted resistors per board, the nominal fitted demand is 120 resistors. Purchasing overage is a separate field or calculation, not a reason to change the per-board quantity from three. Keeping those numbers distinct prevents a handling allowance from becoming an assembly instruction.

prepare a prototype assembly build.

Represent DNP and DNI without losing intent

DNP and DNI commonly indicate a component that should not be populated, but the exact export and shop-floor treatment must be agreed. A zero quantity, a blank MPN, an omitted row, and a row marked DNP do not necessarily produce the same result in different systems. Prefer an explicit fit-status field and retain the affected references in a controlled variant table. The assembler can then verify that an empty position is deliberate.

A useful variant matrix has reference designators down one axis and named variants across the other. Each cell identifies the fitted approved part or a clear do-not-fit state. Avoid informal annotations such as optional without saying who decides. An optional resistor may set an address, terminate a bus, or change a power path. Fitting it based on convenience can change product behavior even when the footprint and value appear harmless.

For a prototype experiment, document the intended population for each serial-number group. If units one through three use an alternative filter and units four through six use the baseline, give each group a traceable variant identity. A single BOM with several contradictory comments creates a difficult debugging problem after boards arrive. The experiment should be reproducible from the release package without relying on someone's memory.

Keep DNP information aligned with test and firmware assumptions. A test that expects an omitted sensor will fail correctly according to its program but incorrectly according to the intended variant. Conversely, bypassing the test may conceal a missing component on a different variant. The BOM, programming instructions, test limits, and labeling should all identify the same build. Use a change log when a DNP decision changes after quotation or purchasing.

compare matching quotation scopes.

础濒迟颈耻尘鈥檚 explains that variants can affect manufacturing outputs. Use the documentation for your installed EDA version and review the generated files. A variant selected for the BOM is not evidence that every other output used the same selection.

Separate 鈥渁pproved alternative鈥� from 鈥渟uggested candidate.鈥� An alternative needs review against the circuit, package, process and product requirements, not just a matching value. Record who may approve it and whether approval applies to one purchase or to the released design. The BOM alternative approval guide covers that decision trail in more detail.

Approve alternatives by function and constraints

An alternative is not approved merely because it fits the pads. Electrical rating, tolerance, operating temperature, package dimensions, qualification needs, firmware compatibility, and assembly limitations can matter. A capacitor replacement with the same nominal capacitance may have different effective capacitance under bias. An oscillator may require a different supply or startup behavior. A connector may mate mechanically yet have different plating or retention requirements.

Use separate fields for the proposed alternative, approval status, approving engineer, and any conditions. If only one approved part is acceptable, say so. If a qualified list is allowed, identify the exact list revision. Avoid unrestricted statements such as equivalent allowed unless the purchasing and engineering teams have defined what equivalent means for that component class. The assembler should not have to perform a product redesign to interpret procurement language.

When a shortage appears, preserve the original requirement and document the proposed change beside it. State whether the change affects only this prototype lot or becomes the new released baseline. Identify any required firmware change, inspection change, or requalification. A temporary deviation should expire or have a defined quantity scope; otherwise it can quietly become a permanent production practice.

For the RFQ, prioritize the components that could block the build: programmed parts, unusual packages, long lead-time devices, and parts with restricted substitution. Tell the assembly team which items you will supply and which need procurement support. Their response can then separate a material availability question from a technical equivalence question. Public package documentation, including TI's SMT references, can help identify assembly constraints, but does not itself approve a cross-vendor substitute.

send files and unresolved requirements for review.

Manufacturer packaging information matters when material is supplied outside its original packing. For example, provide package and moisture-sensitivity information for TI devices. Use the actual component鈥檚 documentation; a photograph of a reel or a generic packaging label does not establish the handling limits of every part.

Define how shortages are reported, how long material waits for clarification, who owns excess stock and whether a repeat order may consume retained inventory. These decisions belong alongside the turnkey versus consigned comparison. The BOM can identify ownership, but the commercial agreement must settle storage, loss and disposition terms.

Release the BOM with an actionable exception list

Before release, compare the BOM against the assembly drawing, placement data, and procurement responsibility list. Confirm bottom-side parts, polarity-sensitive parts, programmed components, and deliberately empty footprints. Identify any customer-supplied items and their expected arrival condition. If a part arrives in a different packaging format from the one quoted, tell the assembler before production planning begins.

Prepare an exception list with an owner and decision deadline for every unresolved item. Examples include an alternative awaiting electrical approval, a DNP position awaiting test confirmation, or a connector whose exact manufacturer suffix is missing. An exception list does not make an incomplete build ready for production, but it makes the inquiry useful. The supplier can review the known scope and explain what prevents a firm commitment.

After approval, save the exact released files and record the hash or other controlled identity used by your document system. When a change is necessary, issue a new revision and identify the affected references. Ask which stage purchasing and assembly have reached before assuming that a new file can be substituted without consequences. Components may already be ordered, feeders prepared, or first articles assembled.

When boards return, reconcile any authorized substitutions and unused supplied parts against the accepted release. Keep the as-built BOM with the prototype test record. If an intermittent fault later appears, knowing which part revision and population variant was actually built can be more valuable than a photograph of the board. A clean BOM therefore supports purchasing, assembly, debugging, and future repeat orders. It is not paperwork added after design; it is part of the engineering definition that makes the design reproducible.

础濒迟颈耻尘鈥檚 is a useful reference for configuring exported fields. Regardless of the software, inspect the output as a manufacturing document: grouped rows, hidden columns, custom field names and alternate choices can change how another team interprets it.

Already have an approved BOM and a revised export? Use the BOM comparison tool to list added, removed and changed references before reviewing the next assembly release. A difference report supports the review; it does not approve substitutions.

PCB assembly BOM questions