Repeat PCB Assembly Order Checklist

A repeat PCB assembly order checklist confirms the approved combination of bare board, BOM, assembly drawing, firmware, test setup and tooling before another build starts. Use the previous order to recover evidence, not to assume that its configuration remains authorized. Identify the requested product variant, compare each controlled item with the last build, resolve mismatches and obtain the supplier’s acknowledgment of a named baseline. Release production only when that combination is approved for the specified order or lot and the agreed restart checks are complete.

What Revision Confusion Can Cost on a Repeat Order

Revision confusion puts the repeat order at risk when purchasing, engineering and production work from different definitions of the same assembly. The practical question is not whether the supplier recognizes the part number. It is whether the material, instructions and verification setup describe the product now required.

Consider these possible consequences when deciding which discrepancies must stop a release:

Do not attach a universal cost multiplier to these failures. Evaluate the actual exposure: committed materials, affected quantities, rework access, repeat testing and delivery disruption.

Reopen the Previous Order as a Reference, Not an Approval

The previous order should establish what was requested, what was actually built and what was accepted. Keep those records separate from the new order’s authorization. A successful shipment provides useful history, but it does not settle which configuration the OEM requires next.

Criterion 1: Recover the released package and the as-built record

Request the previous purchase-order reference, released manufacturing package, production traveler, material traceability, programming records, test results and approved exceptions. A traveler is the build record that accompanies the work through its operations. Where records are held in different systems, connect them through the assembly identifier and lot or serial reference.

NASA’s configuration-management guidance distinguishes controlled identification, change status and verification against product records. Apply that distinction to the repeat order: recover the approved definition, then reconcile actual production against it.

Good signal: the supplier can identify the exact release used and explain recorded differences from it.

Red flag: only a quotation, an old email attachment or a passing sample is available as the definition of the previous build.

Criterion 2: Confirm which order or lot the approval covers

Ask the OEM’s authorized engineering owner which released configuration applies to this purchase-order line. Follow the existing engineering-change approval and its implementation boundary, often called effectivity. Record the identified lot, serial population or other authorized boundary rather than treating a document’s issue date as the production cut-in.

For a date-based instruction, confirm which event the date controls: material issue, assembly start or another defined operation. Resolve work already in progress and material already purchased before releasing an ambiguous instruction. If both revisions will be delivered, identify separate sublots and their configurations; do not leave receiving staff to infer the split from shipment dates.

Good signal: an approved change record identifies the new build population and the treatment of earlier stock.

Red flag: “use the latest files” leaves the supplier to decide when the change starts or which older assemblies remain acceptable.

Match Board, BOM and Assembly-Drawing Revisions

The bare board, BOM and assembly drawing must form an approved combination for the requested assembly variant. Their revision letters or numbers do not have to be identical. Match each document to its own identifier and confirm the authorized relationship between them; do not infer compatibility from matching suffixes.

Criterion 3: Identify the physical board and its fabrication data

Record the bare-board part number and revision separately from the finished PCBA part number. Compare the fabrication release with receiving records and available physical identification. Where a board marking cannot identify the complete fabrication release, require traceability through its lot and controlled manufacturing records.

Check the requested board against the associated fabrication drawing, drill data, layer data and panel definition. An unchanged individual board does not, by itself, approve a different production panel. Require the supplier to identify any panel changes that affect the retained manufacturing setup.

Good signal: the board stock and fabrication package map to the exact bare-board revision listed in the current assembly baseline.

Red flag: an inventory label says only the finished assembly number, or a board photograph is offered instead of a traceable revision record.

Criterion 4: Reconcile BOM, placement data and assembly instructions

Compare manufacturer part numbers, reference designators, quantities, approved alternatives and do-not-fit positions. Check connector orientation and special assembly notes against the requested variant. The referenced supplier distinguishes the BOM’s component identities from the component placement list’s positions, rotations and board sides; both need to describe the same populated assembly.

Keep fabrication data, assembly data and assembly variants identifiable within one controlled release. For purchasing, use that released set rather than combining unrelated exports into a package that has never been approved as a whole.

Good signal: the drawing, BOM and placement data agree on what is fitted, omitted and oriented for this variant.

Red flag: the BOM was updated independently while the supplier retained an earlier placement file or handwritten population instruction.

Treat renamed files cautiously. A more recent timestamp is not approval, and a renamed copy does not establish a new engineering revision. Ask the document owner to resolve conflicting content under the same identifier before materials are issued.

Confirm Firmware, Test Software and Product Configuration

Firmware and test software require their own repeat-order checks even when the PCB layout is unchanged. Name the image, configuration and acceptance setup that belong together. Do not let the supplier select a binary merely because it programmed successfully during an earlier build.

Criterion 5: Verify the complete programming definition

Identify the application image and release identifier, the target device and the approved hardware/variant compatibility. Include the bootloader, configuration bits, option settings or nonvolatile parameter file where the product uses them. Define whether calibration values and unique device data are preserved or written during the operation.

Use a file digest, such as SHA-256, to compare the delivered artifact with the approved release manifest. NIST describes message digests as a way to detect changes in data. A matching digest is an integrity check, not an engineering decision that the image belongs on this board. Keep the approved manifest and its authority traceable too.

Good signal: the programming instruction names the image, configuration and verification method, and the resulting record identifies the programmed unit or lot.

Red flag: files called “production.hex” have different contents, or the only check is that an indicator lights after power-up.

Follow the target device’s programming sequence, including verification of program memory and configuration registers. Protection settings may restrict later readback. If testing uses a diagnostic image, identify the final production image and verify its installation before shipment. Do not include device-specific identity or calibration data in a blanket copying instruction.

Criterion 6: Match acceptance software to the product requirements

Request the test procedure revision, test-software release, limit-set revision and relevant station configuration. Identify the power, inputs, loads and operating modes required by the approved test. Confirm how the software selects the correct product variant.

Good signal: a test record connects the unit identity, software release, limit set and result to the requested baseline.

Red flag: the supplier promises to use “the same tester,” but cannot identify its current sequence or limits.

Make changed test settings an explicit review item. Require the test owner to resolve a relaxed limit, disabled step or changed adapter before restart. A passing reference unit should support the agreed setup checks, not replace review of the configuration or demonstrate every failure-detection capability.

Check Whether Tooling and Programs Still Match the Build

Existing tooling and production programs may be reused only after their identity, compatibility and readiness are checked against the requested build. Separate the question “is this the correct revision?” from “is this physical tool still fit for use?”

Criterion 7: Check physical tooling and fixture readiness

Identify stencils, support pallets, depaneling fixtures, programming adapters and electrical-test fixtures where used. Record the applicable tool revision, asset identity and build compatibility. Have manufacturing review contact locations, locating features, component clearance and the panel arrangement against the current data.

For a retained fixture, request its relevant maintenance and verification records. For equipment that requires calibration, check that its calibration status covers the planned operation. Do not apply a calibration requirement indiscriminately to every stencil or mechanical holder.

Good signal: retained tools have traceable identities and documented compatibility, with inspection or maintenance actions completed before use.

Red flag: tooling is identified only by its storage shelf, or “used last time” is the only evidence supporting reuse.

The referenced supplier explains that assembly stencil data can be adjusted for the assembly process rather than simply copied from customer paste data. Therefore, compare the actual retained stencil definition with the required build and approved process, not just the original CAD filename.

Criterion 8: Verify shop-floor program selection

Ask the supplier to map its placement program, optical-inspection program and other applicable machine recipes to the OEM’s released assembly. Supplier program identifiers may differ from OEM document revisions; require a controlled mapping, not matching names.

For a repeat on a changed line or with a changed setup, agree the checks needed before normal production resumes. The scope should follow the actual changes and previous qualification evidence, rather than a fixed sample quantity invented for every reorder.

Good signal: the setup record identifies the deployed programs and the completed checks for the selected build.

Red flag: an operator selects a program from memory, or an old inspection program is accepted because the board outline looks unchanged.

Keep superseded programs out of normal selection while preserving their controlled history. Ask who verifies program selection when the job moves between lines or stations.

Review Material Changes and Previous Deviations

Material availability and previous deviations must be reconciled with the current baseline before a repeat order is kitted. Separate an approved design choice from a temporary exception, and separate stock ownership from permission to use that stock.

Criterion 9: Resolve alternatives and existing inventory

Request an inventory comparison showing material identifiers, relevant lot information, quantities and proposed allocation. Include customer-supplied stock, supplier-held surplus and assemblies already in progress. Check proposed alternatives against the current approved BOM, not merely the previous purchase history.

Use explicit disposition choices: use as approved; rework under an approved instruction and retest; segregate for a separately authorized build; return; or scrap. These are working choices for the review, not a requirement to discard all older material. Obtain the relevant technical and commercial approvals for the chosen disposition.

Good signal: every proposed substitution or older-revision allocation has a defined authorization and destination.

Red flag: purchasing a similar part, owning surplus boards or wanting to avoid scrap is treated as proof of compatibility.

Criterion 10: Reassess every previous exception

Read each earlier deviation or concession for its affected requirement, allowed condition, quantity or lot scope, approval and expiry rule. Record whether the current order is already covered or needs a new decision. NASA’s guidance explicitly separates an authorized waiver from a change to the baseline.

Good signal: an exception is either applicable within its existing scope, renewed through the authorized process or excluded from the repeat order.

Red flag: a temporary alternate component or rework instruction is copied forward without checking its authorization.

A prior approval is not automatically exhausted just because another purchase order is issued; its written scope decides. Equally, a past acceptance does not create unlimited permission. When the scope is unclear, hold the affected operation and obtain the owner’s disposition rather than silently treating the exception as permanent.

Issue a Repeat-Order Baseline That the Supplier Can Acknowledge

The repeat-order baseline should be a controlled index of the approved build combination, its applicable order population and its supporting files. Give it an identifier and revision. Reference it from the purchase order, then require a supplier acknowledgment that identifies the same baseline and any unresolved differences.

A completed previous-versus-current comparison

The following worked example uses illustrative identifiers and quantities, not a JASPER production record. It concerns PCBA-214, variant IO-A. ECO-073 assigns the current configuration to PO 4782, line 1, lot L025, covering 300 assemblies; the previous build was lot L024.

Use the columns consistently: the previous record describes evidence, the requested state describes the authorized target, the mismatch action defines what closes a discrepancy, and the approval owner identifies who may accept that closure. File references should resolve to accessible released artifacts, not undocumented filenames.

Make acknowledgment specific enough to act on

Ask the supplier to return the baseline identifier, its internal job reference, acknowledged document revisions, material dispositions and tooling/program mapping. Require an explicit exception statement, including “none” when that is the reviewed result. Separate receipt of files from acceptance of their technical content and from authorization to start production.

For the worked example, a completed acknowledgment could read:

PO 4782 line 1, lot L025, 300 units of PCBA-214 IO-A: baseline RB-214-025 Rev 1 acknowledged against job J-8821. Rev B board stock remains excluded. DEV-019 is not applied. Setup verification SV-8821 is complete. No configuration exceptions remain open. Start authorization is recorded in release R-8821 by the designated OEM release owner.

This statement summarizes referenced records; it does not replace the files, verification evidence or approval record. Archive the acknowledgment with the released package so the next reorder can recover what was actually authorized. If an applicable file changes afterward, resolve the effect on the order, issue the revised baseline through the existing approval process and obtain an updated acknowledgment before the affected operation. Do not silently replace an attachment under an already acknowledged baseline.

Follow a Six-Step Repeat-Order Review

Run the repeat PCB assembly order checklist as a review with defined outputs, not an email asking several departments whether anything changed. Use the following sequence within the organization’s existing release and change-control process.

Step 1: Define the requested build

Purchasing identifies the finished assembly, variant, quantity, purchase-order line and requested delivery. Engineering identifies the applicable approved configuration. Output: a clearly bounded request with its responsible owners, rather than a copied order whose technical intent remains implicit.

Step 2: Recover and compare the previous build

Collect the released files and as-built evidence, then complete the previous-versus-current matrix. Record unchanged items explicitly so they are not mistaken for omissions. Output: a comparison showing each controlled item, relevant difference and unresolved question.

Step 3: Close compatibility and stock decisions

Route board, BOM, firmware, test and tooling conflicts to the appropriate owners. Resolve previous exceptions, material substitutions and older inventory. Output: approved dispositions with the affected quantities and implementation boundary. Purchasing coordinates the decision but does not substitute for technical approval.

Step 4: Issue the controlled baseline

Publish the approved index and referenced artifacts through the agreed document channel. Tie the purchase order to that baseline. Output: one identifiable released set with a clear relationship to the previous version, rather than a folder containing competing alternatives.

Step 5: Obtain supplier acknowledgment and restart evidence

Have the supplier confirm its job mapping, material allocation, deployed programs and tool identities. Complete the agreed setup and verification activities. Output: an acknowledgment, completed check records and a resolved exception list. Do not treat a receipt notification as a completed review.

Step 6: Authorize production and preserve the as-built link

The designated owner authorizes the applicable operations after their required checks are satisfied. At completion, link material, programming and test records to the delivered lot or serial population. Output: an auditable connection from the purchase order through the approved baseline to the delivered configuration.

Escalate These Eight Signals Before Restart

A repeat order should stop at the affected operation when the supplier or OEM cannot establish configuration identity, compatibility or authority. Use the following escalation signals to assign an owner and closure action, rather than reject a supplier solely because a document needs clarification.

Keep the hold proportional to the discrepancy. A programming question need not automatically stop an independently authorized material purchase, but such staged authorization must state its limits. No partial approval should be interpreted as permission to ship the finished assembly.

Frequently Asked Questions

These answers address repeat-order configuration decisions. Apply them to the identified assembly and order population, using the approvals and records discussed above.

Prepare the Next Repeat Order with JASPER

Prepare the previous build reference, current comparison matrix, approved files, material dispositions and required restart checks before requesting the next PCBA order. State which activities are included: material sourcing, assembly, programming, testing and any interface integration. Require written agreement on the configuration and responsibilities before production starts.

For a JASPER PCB assembly services enquiry, submit the proposed repeat-order baseline with the requested quantity and schedule. Ask for acknowledgment of the exact board, BOM, firmware, test and tooling combination, together with any differences that need resolution. Make the approved baseline—not the age or familiarity of the product—the basis for restarting the build.