Skip to main content

Documentation / Components

Review the project BOM

Reconcile grouped quantities, identity fields, fitted state, and the downloaded BOM against the exact project scope.

Level
Intermediate
Estimated
20 min
Instructions updated
2026-07-12
Product context
Updated for the July 12, 2026 web release

Outcome

Produce a BOM review record that separates design identity from unverified sourcing data.

Before you start

  • A populated project
  • Required BOM field schema
  • Variant intent where applicable

Task record

Time
20 minutes
Level
Intermediate
Instructions updated
2026-07-12
Product context
Updated for the July 12, 2026 web release

Execution record

Prepare the role, starting state, and evidence record before acting.

Keep these records beside the project state so the task steps can stay focused on the action, passing result, and stop condition.
StepRequired roleStarting stateEvidence to retain
01 / Confirm project and variant scopeComponent/configuration reviewer with project read accessRequired BOM schema, approved part sources, hierarchy inclusion, baseline population intent, named variants, and receiver are recorded before BOM review.Project/revision, included sheets, variant identity and Pop/DNP/Alt intent, independent reference list/count, role, BOM opening state, and timestamp
02 / Reconcile groups and quantitiesBOM reviewer with read access and permission to change only view settings when requiredStep 1 freezes expected reference/population counts; approved grouping equality keys and required visible fields are written down.Displayed total, filter/grouping/Exclude DNP state, expanded row/reference table, per-row Qty arithmetic, included/DNP sums, and differences
03 / Verify identity fieldsComponent engineer or sourcing-data reviewer authorized to approve identity sourcesUnique BOM identities and critical references are enumerated; approved source documents/revisions and mandatory fields are fixed before any populated value is accepted.Per-row field/provenance table, approved sources, exact conflicts/blanks, package comparison, timestamped supplier/commercial data status, issue IDs, and owners
04 / Inspect fitted and alternate stateConfiguration/component reviewer authorized to approve variant and alternate intentThe baseline reference list and per-variant included/excluded/substituted/unchanged intent are frozen; no base-design edit is authorized.Variant state table, baseline and per-variant arithmetic, BOM reconciliation, DNP reasons, alternate MPN/package/rating source, approvals, and discrepancies
05 / Export the required schemaBOM reviewer with export permission and access to the receiver-approved destinationSteps 1-4 pass; required format/columns/naming/encoding are approved; the selected variant is visible; the destination contains no older exports.Control/path used, selected variant, settings, exact filename, byte size/checksum, generation timestamp/result, and unchanged downloaded file
06 / Reconcile the downloaded fileIndependent BOM/release reviewerExactly one output from Step 5 is retained with checksum; UI totals/settings/variant and expected reconciliation values are frozen.Reader/version, file checksum, header/encoding/delimiter record, row/Qty/reference comparison, first/last rows, five samples, differences, reviewer, and disposition

Procedure

Run the documented task in order.

Record an unavailable action or failed assertion; do not infer that the operation ran.
  1. 01

    Confirm project and variant scope

    Action

    Record the project name, saved state, included schematic hierarchy, and active variant before opening the BOM. Count placed component references independently from the schematic.
    Resin project Schematics, Design Variants when used, and Components Bill of Materials / Projects > exact project > Schematics hierarchy; Project > Variants > Manage Variants or PCB Editor > Project > Variants > Design Variants; Components > Bill of Materials: Freeze the saved state and hierarchy, select or record the intended baseline/variant, and enumerate placed references independently before reading BOM totals

    Pass when

    The saved project, hierarchy, baseline or named variant, expected included/DNP counts, and independent reference count are uniquely recorded.

    Stop if

    Stop when project/revision or hierarchy is uncertain, variant identity/control is ambiguous, duplicate references exist, intended population is missing, or the independent count cannot be reproduced.

  2. 02

    Reconcile groups and quantities

    Action

    Clear filters, expand grouped records, and compare each row's references, quantity, value, and package. Sum all fitted quantities and compare them with the independent reference count.
    Resin Components Bill of Materials / Components > Bill of Materials > filters, grouped rows, Ref, Value, Package, and Qty; BOM settings > Fields and Group by when used: Record/clear filters, expand every group, enumerate references, transcribe active grouping keys and Exclude DNP state, and calculate row and total quantities

    Pass when

    Each included reference appears exactly once, every displayed Qty equals its enumerated references, and the summed fitted Qty equals the intended included-reference count.

    Stop if

    Stop when filters cannot be identified, unlike approved identities group, references are hidden/duplicated/missing, Qty arithmetic differs, or a required grouping key is not exposed.

  3. 03

    Verify identity fields

    Action

    For every unique purchasable row, compare manufacturer, exact MPN, description, package, and required internal fields with the approved part record. Treat blank sourcing or verification fields as unknown.
    Resin Bill of Materials and owner-approved component records / Components > Bill of Materials > Manufacturer, MPN, Description, Package, Supplier, Lifecycle, and required internal columns; then approved source record: Compare each unique purchasable row field-by-field with the cited manufacturer/internal part record and assign a provenance disposition

    Pass when

    Every required identity/provenance field is Verified, Stale, Unknown, Conflict, or Not applicable against an approved source, with an owner for every non-Verified mandatory row.

    Stop if

    Stop approval when manufacturer/MPN/package lacks an authoritative source, two sources conflict, a blank is treated as approved, or unaudited supplier text would be needed to fill identity.

  4. 04

    Inspect fitted and alternate state

    Action

    Compare fitted, not-fitted, and alternate decisions against the intended variant. Verify that alternates preserve electrical, package, temperature, lifecycle, and regulatory requirements outside the BOM display.
    Resin Design Variants and Bill of Materials plus approved alternate qualification record / Project > Variants > Manage Variants or PCB Editor > Project > Variants > Design Variants; Components > Bill of Materials: Inspect Ref, Value, Alt Value, Pop, and DNP for each named variant, then reconcile BOM Qty/references and external alternate qualification

    Pass when

    For the named variant, included plus DNP references equal the baseline count and every DNP/alternate row matches the approved intent and has source-backed equivalence or a blocked disposition.

    Stop if

    Stop when a reference is missing/duplicated, variant controls are absent, observed deltas differ, an alternate lacks approved equivalence, or representing intent would silently edit the base design.

  5. 05

    Export the required schema

    Action

    Export the receiver's required BOM format and save the filename with project, revision, variant, and date. Do not rely on the browser table as the delivered artifact.
    Resin BOM or Design Variants export / Components > Bill of Materials > exposed export control, or Design Variants > named variant > Export BOM as CSV; destination empty directory: Verify selected project/variant and export settings, activate the available approved BOM export once, and retain the downloaded file unchanged

    Pass when

    Exactly one new BOM file is produced from the named state with the required filename, columns, format, and unmodified content retained.

    Stop if

    Stop after one attempt when the control is absent/disabled, variant is ambiguous, no or multiple files appear, generation errors, required settings are unavailable, or the destination was not clean.

  6. 06

    Reconcile the downloaded file

    Action

    Open the file independently and compare row count, fitted quantity sum, first and last references, required columns, delimiters, encoding, and at least five sampled identities with the UI record.
    Approved external spreadsheet/text reader and Resin BOM state / Downloaded BOM file > approved independent reader; compare with Components > Bill of Materials and variant record: Open the unmodified file, inventory schema and rows, recompute quantities/reference coverage, and compare five package/variant/identity-risk samples with UI and approved sources

    Pass when

    Required headers, row count, fitted Qty sum, reference coverage, delimiter/encoding, first/last references, and five risk-based identity samples reconcile or each exact mismatch blocks release.

    Stop if

    Stop release when the file cannot be opened, checksum changes, required headers/rows are missing, totals/references/DNP differ, samples conflict, or a repeat export from the same state is nondeterministic.

Verification

Do not call the task complete until these checks pass.

  • Hierarchy scope known
  • Variant known
  • Groups reviewed
  • Identity fields checked
  • DNP state checked
  • Export reconciled

Evidence and exercise files

Download the evidence used by this guide.

Each repository-backed file is labeled with its contents, provenance, license or publication boundary, and current limitations.
Repository-backed file

BOM output set

ZIP · 3 CSV files · 1.4 KB / GPL-3.0-only

Provenance: Deterministic archive of three real Resin BOM exporter outputs from the converted Digispark fixture.

Current limit: The nine-row source project does not prove populated variant behavior, supplier qualification, pricing, or availability.

Download file

Evidence boundary

Keep preparation separate from product proof.

The procedure defines what to run and retain; it does not claim that the task ran successfully on any project.
This review can establish grouping arithmetic, displayed identity/provenance states, named variant intent, and the contents of one independently opened BOM export for one saved project. The downloadable result fixture proves only its own small source/output set; neither it nor populated Resin fields proves supplier qualification, availability, pricing, lifecycle, alternate approval, or procurement readiness.

Failure recovery

Diagnose and recover without hiding the original state.

Preserve the symptom before changing anything, apply one bounded recovery, and repeat the affected assertion against the named project state.
DOC-BOM-F01

Rows merge or split unexpectedly, references are missing/duplicated, or displayed Qty does not reconcile.

Diagnosis: Record project/variant, filters, Fields/Group by/Exclude DNP settings, affected references, displayed groups/Qty, expected equality keys, and every differing manufacturer/MPN/value/package/whitespace field.

Recovery: Preserve the original view, correct only an approved view/grouping setting or source identity in an authorized project state, reopen the BOM, and recompute all affected and total quantities.

Stop or escalate: Escalate when the differentiating field is not exposed, source identity is unresolved, reference inclusion differs from hierarchy/variant intent, or a data edit would hide a real distinction.

Evidence: Before/after BOM captures, complete settings, expanded reference lists, arithmetic, approved identity sources, exact change, owner decision, and issue ID

Recheck: Each approved identity occupies the intended row, every Qty equals enumerated references, every included reference appears once, and total included Qty is unchanged except for approved variant intent.

DOC-BOM-F02

A required identity is blank/conflicting/stale, supplier data is unaudited, or an alternate/variant delta cannot be verified.

Diagnosis: Record affected reference/variant, exact field/value, all source IDs/revisions/timestamps, Pop/DNP/Alt state, required electrical/package/environmental/compliance criteria, and the conflict or gap.

Recovery: Keep the row Unknown/Conflict and the variant or alternate blocked, assign the component/configuration owner, and update only from an approved source through the authorized data process.

Stop or escalate: Block procurement/release when manufacturer/MPN/package, variant population, or mandatory alternate equivalence lacks approval, sources conflict, or catalog/commercial data is stale or untraceable.

Evidence: Field-provenance and variant rows, source documents, supplier timestamp/terms, gap/conflict, issue and owner, approved correction, and affected outputs

Recheck: The BOM and variant state match one approved source set, alternate criteria are independently dispositioned, and all affected grouping/Qty/export checks are repeated.

DOC-BOM-F03

The export is absent, duplicated, unreadable, nondeterministic, or differs from the reviewed UI/variant state.

Diagnosis: Record project/revision/variant, export path/control/settings, destination inventory, filenames/checksums, exact error, UI rows/Qty/references, file headers/rows/Qty/DNP, and every mismatch.

Recovery: Retain all artifacts unchanged, repeat one export from the same saved state into a verified empty directory, and compare by reference plus approved grouping keys without editing the file.

Stop or escalate: Block release when the repeat differs, required fields are lost, totals/references/variant state cannot reconcile, or the receiver format/encoding cannot be produced and approved.

Evidence: UI/settings captures, destination inventories, original/repeat files and checksums, independent-reader records, detailed diff, exact errors, and release-owner issue

Recheck: One deterministic export opens independently and every required header, row, reference, Qty, DNP, and sampled identity reconciles with the named UI state and source records.

Task-specific troubleshooting

Resolve these states without changing the evidence boundary.

Quantities differ

Compare hierarchy inclusion, active variant, duplicate references, grouping fields, and fitted state before editing data.

Rows merge unexpectedly

Inspect manufacturer, MPN, value, package, and every field used by grouping; split only after the design identity is corrected.

Rows split unexpectedly

Compare whitespace, case, package spelling, and hidden identity differences. Do not merge parts that are only visually similar.

A required identity field is blank

Mark the row unresolved and assign an owner. Do not substitute supplier text for an approved manufacturer identity.

Supplier data is shown

Verify timestamp, provenance, availability, and commercial terms independently before procurement.

The downloaded file differs from the UI

Preserve both artifacts, record active filters and variant, regenerate once from the same saved state, and stop release if the mismatch remains.

Decision gate

Decide whether the BOM state can enter manufacturing-output preparation

Are reference/grouping quantities reconciled, critical identities source-backed, variant and alternate intent controlled, and one receiver-format export independently opened and matched to the exact project state?

Required evidence

Saved project/hierarchy/variant identity, independent reference count, grouping/settings and Qty reconciliation, field-provenance table, DNP/alternate qualification, unmodified export with checksum, independent schema/content comparison, exceptions, owners, and signed disposition

Remain blocked when

Any reference/Qty differs, a critical identity or alternate lacks an approved source, variant intent is not represented, export is missing/unreadable/nondeterministic, UI and file disagree, or supplier/commercial data is treated as approved without review.