The Layout-to-BOM Consistency Failure Checklist

Use this checklist when a solar layout and material list are supposed to describe the same project, but may have been exported, edited or released at different times. It is a comparison task: identify mismatches and route them to their owners before the next permitted use.

For the broader material-scope review, see solar BOM completeness. For the detailed takeoff worksheet, see why panel count does not establish a complete BOM. This checklist focuses on evidence of disagreement between outputs.

Assemble the comparison packet

Gather the current layout, BOM, applicable electrical and mounting records, equipment selections, scope exclusions and change record. Identify the purpose of the check: supplier pricing, order release or field use. Those uses do not require identical evidence, and completing a pricing review does not authorize installation.

Record each document’s project identifier, revision and issue status. If the reviewer cannot identify which revision controls, stop the affected comparison and assign that decision. A recent export timestamp alone does not prove that its inputs were current.

NASA’s configuration-management guidance discusses controlled baselines and changes. Apply it as a recordkeeping analogy, not as a solar engineering requirement or project approval.

Ten layout-to-BOM failure checks

The evidence column identifies a source to inspect. The failure signal identifies a question to resolve, not proof that a particular component must be included in every project.

The U.S. Department of Energy’s PV system design overview identifies modules as one part of a complete system. Use the applicable project records to check the other material groups; do not infer them from module quantity alone.

Test identity and grouping, not just totals

Hypothetical count example: A current layout has eight modules in Area A and four in Area B. An older takeoff lists six in each area. Both total twelve. The overall module line passes a count comparison, but the distribution disagrees:

• Current layout: 8 + 4 = 12.
• Older grouping: 6 + 6 = 12.
• Area A difference: 2 modules; Area B difference: −2 modules.

This does not prove a particular mounting or cable quantity. It tells the reviewer to inspect the affected configuration and takeoffs. If both layouts use twelve 450 W modules, the nominal capacity is 5.4 kWp in both cases; that second matching total still does not resolve the grouping mismatch.

Compare exact item identities too. A substituted module with the same nominal power can require review of dimensions, mounting and electrical compatibility. Route that review to the responsible role rather than treating equal watts as proof of equivalence.

Record one discrepancy per decision

A useful discrepancy record gives the receiving reviewer enough information to resolve the conflict without reconstructing the whole export history.

Use a specific statement: “Area A layout revision D shows eight modules; BOM revision C groups six in Area A.” Avoid “BOM looks wrong,” which gives the next reviewer no reproducible comparison.

An exclusion and a pending item need different dispositions. Excluded work must match the accepted scope. Pending work needs an owner, source and release condition. Do not change a pending quantity to zero merely to close the checklist.

Close the mismatch across dependent records

1. Preserve the compared versions and discrepancy evidence.
2. Identify the controlling source and qualified decision owner.
3. Decide which pricing, order or field activity is affected and record its hold or restriction.
4. Resolve the underlying design or scope question through the required review.
5. Regenerate or correct dependent records and compare them again.
6. Identify the successor release and notify affected recipients, suppliers or project roles.
7. Close the discrepancy only when the correction and distribution evidence are recorded.

Do not silently overwrite a supplier-facing list when an order has already been placed. The solar material procurement guide covers quote, order and receiving coordination. A changed material list and an accepted supplier change are separate records.

For field delivery, use the design-to-installation handoff guide to check that the crew receives the coordinated successor package. A release checklist cannot replace qualified electrical or structural review, manufacturer instructions or applicable safety and authority requirements.

Evaluate the actual output workflow

Bring a representative change to a SurgePV solar design demonstration. Ask the team to show which outputs change with the design, which manual fields must be reviewed, how quantities and units are represented, and how an exported list can be tied to its project revision.

Treat those as evaluation questions. Do not assume automatic synchronization, preserved manual overrides or complete site-specific material generation without checking the actual product behavior.

Frequently Asked Questions

What should a layout-to-BOM consistency check compare?

Compare project identity, revisions, exact equipment, module positions and counts, mounting configuration, electrical routes, quantity units, package contents, exclusions and release status. Use the applicable design records to determine each item; the layout alone does not contain every material decision.

Does a matching panel count mean the BOM is correct?

No. It is one useful reconciliation result. The module model, mounting configuration, routes, accessories or scope can still differ. Keep the count check separate from the review of item identities and the completeness of the project-specific material takeoff.

What should happen when the layout and BOM disagree?

Record the two conflicting values and their revisions, identify the controlling source and decision owner, and hold the affected use. The qualified reviewer resolves the design question. Then update dependent outputs and record the successor release rather than silently choosing one file.

When should this consistency check be repeated?

Repeat it before the defined pricing, purchasing or field release and after any change that may affect materials. A new layout export, equipment substitution, routing decision, supplier package change or edited takeoff can require reconciliation. Follow the project-specific review process rather than a universal calendar interval.