Why HMLV programs fail
Mixed revisions, wrong programs, missing shared components and outdated work instructions are common failure modes. Each changeover is a configuration event that needs verification.
Understand the cost structure
Setup, engineering, stencil, programming, fixture and material-minimum costs can dominate small batches. Compare total landed cost and inventory risk rather than unit price alone.
Plan common materials
Where technically appropriate, approved common components across product families can improve availability and reduce stranded inventory. Ownership and reuse rules should be explicit.
Control repeat builds
Retain approved programs, process settings, first-article records, fixtures and exceptions. Require revision confirmation at every reorder.
Measure the right performance
Track on-time delivery to confirmed date, first-pass yield by product, shortage response time, change-control accuracy and corrective-action closure—not only output volume.
Repeat-order review: what must be reconfirmed?
| Area | Compare with the previous build | Decision to record |
|---|---|---|
| Configuration | PCB, BOM, firmware, labels and test revision | Exactly which revision is authorized |
| Materials | Available stock, lifecycle, alternates and excess | Reuse, purchase, substitute or hold |
| Tooling | Stencil, fixture and programming setup condition | Reuse, inspect, repair or replace |
| Quality | Prior defects, rework and open corrective actions | Closure evidence and checks needed this time |
| Schedule | Material dates, production slot and test readiness | Confirmed dependencies and shipment plan |
What a useful forecast looks like
Separate firm orders from estimates. State likely batch sizes, timing, confidence and design-change exposure. Agree before material purchase whether unused stock can move to another product and who accepts obsolete inventory. Forecast visibility can help planning, but it is not a purchase authorization.
Repeat-order revision control checklist
High-mix, low-volume planning needs an order-level configuration check even when the product was built successfully before. Name the revision being repeated; verify what is unchanged and review the impact of any change.
| Configuration item | Confirm at reorder | If changed |
|---|---|---|
| PCB and populated variant | Fabrication revision, BOM, fit/DNP and variant | Review layout, population and old-board disposition |
| Components and stock | Approved MPNs, alternates and available retained material | Approve material exceptions and unused-stock treatment |
| Programs and tooling | Placement program, stencil, fixture and applicable instructions | Confirm compatibility and any setup or validation work |
| Firmware and acceptance | Released image, test procedure, limits and required records | Review programming, fixture and acceptance changes |
List SKU, quantity, approved revision, needed date and shared material constraints for each planned batch. A family forecast does not authorize mixing variants or purchasing shared stock without ownership rules. Use the cost-comparison worksheet for pricing decisions and the readiness gates for schedule decisions; do not replace configuration control with a lower unit price.
Use this guide in your next build review
Share the current revision, pilot result, expected batch size and unresolved risks. We will identify the information needed before quotation or production release.
Prepare an RFQ