DNPコンポーネント：PCBアセンブリのバリエーションを統一する

DNP means do not populate. It describes an assembly decision, not the removal of a footprint from the bare PCB. When one board supports several product versions, make the intended population explicit so the assembler can build the correct variant without interpreting informal notes.

Give each variant a clear identity

Assign a variant name or part number and a revision. State which bare-board revision it uses. Keep the requested quantities separate for each variant even when the boards look identical. A filename such as “final-new-option” is difficult to use reliably in purchasing and production.

For an illustrative sensor board, Variant A might fit R12 and omit R13, while Variant B does the reverse. Write these states in a variant matrix with one row per reference designator. The example describes a documentation method, not a recommended circuit arrangement.

Reconcile the three assembly views

Compare the BOM, placement output and assembly drawing. Agree how the assembler wants omitted components represented: a clearly labeled DNP column, a separate list or a variant-specific export. Do not assume every importer treats a blank quantity or the text “DNP” in the same way.

If DNP parts remain in the placement file, explain how they should be filtered. If they are removed, verify that required populated references have not disappeared with them. Keep the full design record separately from the production-specific handoff.

Check options beyond component population

Variants may also require different firmware, labels, jumpers or functional test limits. Link those requirements to the same variant identifier. A board can contain the correct components and still be the wrong product if its programming or labeling belongs to another version.

• Confirm the count of populated references for each variant.
• Identify alternate positions that must not both be fitted.
• Mark required solder links or configurable jumpers explicitly.
• State the programming and test revision for each build.
• Define how finished units will be distinguished in packaging.

Release a complete variant package

Before production, reconcile any last-minute population change across all affected files. Ask the assembler to confirm the variant and quantity breakdown. At incoming inspection, choose sample references that distinguish the variants and compare them with the approved matrix. Retain that matrix with the build record so a repeat order reproduces the intended population rather than the most recent email conversation.