What should PCB process optimization improve?
PCB process optimization should increase repeatable good output or reduce avoidable cost and delay while preserving the board’s acceptance requirements. It is not simply running a machine faster or making the final inspection number look better.
This guide concerns bare-board fabrication: the production route that creates copper circuits, interconnections and the finished board. Component placement and soldering belong to PCB assembly and require their own process study.
Start with a specific problem statement. “Reduce repeat processing at this inspection stage for this product family” is testable. “Improve factory quality” is too broad to tell an engineer what to measure or change. Name the product revision, process boundary, baseline period and owner.
Define the limits that must not deteriorate: finished dimensions, electrical acceptance, reliability requirements, material identity and any customer-approved process restrictions. A reduction in scrap obtained by relaxing acceptance is a specification change, not evidence that the original process improved.
Review design-driven restrictions through DFM before fabrication release. If a feature needs a design change, handle that through engineering approval rather than silently changing the production interpretation.

Which measurements reveal the real losses?
Track first-pass results, repeat work and elapsed time separately, using a consistent unit and product group. A single final-yield percentage can hide substantial extra work.
| Measure | Practical definition | Check before comparing |
|---|---|---|
| First-pass yield | Units meeting requirements on the first pass divided by units entering the defined stage | Exclude reruns and repairs from the first-pass numerator. |
| Final accepted yield | Accepted units after approved dispositions divided by starting units | Keep the same cohort; account for work still in progress. |
| Repeat-work load | Time and units consumed by authorized repeated processing or testing | Separate a test-system issue from a confirmed product defect. |
| Flow time | Elapsed time between defined release and completion events | Include queues and approval holds, not only machine running time. |
| Good output rate | Accepted output over a stated time period | State whether the unit is a board, panel or area. |
ASQ defines first-pass yield around meeting requirements without scrap, reruns, retests or repair diversion. Keep that distinction visible in the production record instead of merging recovered units into the first-pass result.
A yield example that exposes hidden work
Suppose 1,000 comparable boards enter a defined stage. Of these, 920 pass first time, 50 pass after an authorized repeat operation and 30 are rejected. First-pass yield is 920 / 1,000 = 92%; final accepted yield is 970 / 1,000 = 97%. The five-percentage-point difference represents recovered output that consumed extra effort. These are illustrative numbers, not PCBtry production results.
Now suppose a later run finishes at the same 97% final yield but 960 pass first time, 10 are recovered and 30 are rejected. First-pass yield has improved to 96%, while scrap has not changed. That can still be valuable if it reduces repeat work, but the two improvements must not be confused.
Record both failed units and defect occurrences. One board with three defects is one failed board, not three, when calculating a unit-based yield. Do not compare panel yield with board yield without explaining how panel positions and partial-panel rejection are handled.
Split the data by relevant factors such as product family, layer construction, material lot, machine, shift and panel position. A combined average can appear better merely because the later week contained easier boards. Keep timestamp and revision information so the comparison can be reconstructed.
How do you run an improvement trial without losing control?
Use one documented sequence: establish the baseline, identify the constraint, test a supported change and verify the result against unchanged requirements. Keep experimental material identifiable until it is approved.
Step 1: Map the actual route and waiting time
Follow a representative job from release through completion, including queues, review holds and repeat loops. NIST’s value-stream mapping guidance treats both physical flow and information flow as part of the improvement picture. In a PCB job, a panel waiting for an engineering decision can matter as much as a slow machine.
Step 2: Identify the limiting operation
For a simplified serial route, assume comparable stages can sustain 60, 40 and 55 panels per hour, with no losses, changeovers or parallel machines. Its idealized steady output cannot exceed the 40-panel stage. Raising the first stage from 60 to 80 does not remove that constraint and may only increase its queue. Actual batch processes and product mixes need measured schedules, not this simplified arithmetic alone.
Also check whether the apparent bottleneck is starved of input, blocked by downstream work, or consuming capacity on repeat operations. The longest queue is a clue, not proof of a permanent equipment-capacity problem.
Step 3: Turn the leading loss into a testable hypothesis
Classify defects consistently, then connect the leading loss to a plausible mechanism. If dimensional variation is suspected after etching, compare measurements and panel position before changing settings. The etch-factor explanation helps distinguish artwork dimensions from finished copper geometry; it does not supply a universal production adjustment.
A pattern associated with a machine or shift is not yet a root cause. Check material mix, measurement method and upstream conditions. If repeated measurements of the same feature disagree, resolve the measurement problem before optimizing the process from those numbers.
Step 4: Approve the trial and its stop conditions
| Trial record | What must be specified |
|---|---|
| Scope and hypothesis | Product family, operation, suspected mechanism and expected measurable effect |
| Change | The authorized parameter or method change and the responsible engineer |
| Comparison | Comparable baseline or control group, material and revision records |
| Measurements | Sampling locations, method, units, timing and acceptance requirements |
| Guardrails | Other characteristics that must remain acceptable and conditions requiring containment |
| Disposition | Who can release trial material, restore the prior condition and approve documentation changes |
Use a qualified process engineer to set safe trial ranges and select the experiment design. Do not improvise chemistry, temperature or pressure changes from a blog. When factors interact, a planned experiment may be needed; changing several settings together without a design makes the cause of any improvement difficult to identify.
Step 5: Compare the result and decide
Compare like-for-like jobs over an appropriate observation period. Check both the target metric and the guardrails. If the target improves but another critical characteristic worsens, contain affected material and investigate rather than declaring success. Save negative results as well: they prevent the next team from repeating an unproductive trial.

How do you prove and sustain the improvement?
Show that the change produces a repeatable effect under the intended operating conditions, then incorporate it into controlled work instructions and monitoring. One favorable lot is a result to investigate, not proof of sustained capability.
NIST’s process-stability guidance emphasizes behavior over time. Review time-ordered observations for shifts and changes in variation. Choose the chart and sampling approach for the actual data; board pass/fail counts and measured conductor dimensions are not interchangeable data types.
Keep control limits separate from specification limits. Specifications describe what the product must meet; control limits help identify unusual process behavior. A process can be consistent yet consistently produce unacceptable parts.
The NIST capability guidance compares a stable process with its specification limits and identifies distribution and sampling assumptions. Do not publish a Cpk value without knowing which feature, data set and estimation method produced it. There is no universal Cpk acceptance threshold supplied by this article.
Once approved, update the process revision, training, monitoring frequency and reaction plan together. Define who investigates a signal, what material is held and what evidence permits release. Recheck after a material, machine, product or method change that could invalidate the original study.
What should buyers ask a PCB supplier to show?
Ask for an improvement summary tied to your product or a relevant process family, with enough context to distinguish better production from a changed reporting definition.
| Supplier claim | Evidence to request |
|---|---|
| Yield improved | First-pass and final yield, denominators, product mix, period and revision |
| Lead time shortened | Start/end milestones, queue time and any customer approval exclusions |
| Defect eliminated | Failure definition, verified mechanism, trial result and follow-up period |
| Process is capable | Feature specification, stability assessment, measurement method and capability-study context |
| Change is controlled | Approved process revision, affected-lot traceability and reaction plan |
For your own review, prepare the board revision, fabrication requirements, defect photographs with location, lot identifiers, measurement records and the business impact. Remove confidential information that is unnecessary for the investigation. Agree what can be shared through the supplier’s normal secure channel.
A useful improvement report states what changed, why it was selected, what stayed constant, what happened and what remains uncertain. A percentage without this context is difficult to use for a purchasing or engineering decision.
Frequently asked questions
Is optimization the same as adding inspection?
No. Inspection can detect a problem or provide data, but it does not by itself remove the cause. Evaluate whether the intervention changes defect creation, repeat work or delivery performance.
Why track first-pass yield if final yield is high?
Final yield can conceal reruns and recovery effort. First-pass yield shows how often the defined process meets requirements without that extra work.
Can I combine all products into one yield number?
A factory summary can be useful, but keep product-level or comparable-family views. Otherwise a change in product mix can be mistaken for a process improvement.
Should every machine run faster?
Not necessarily. Improve the actual constraint and protect good output. Speeding a non-limiting stage can create more waiting inventory without increasing completed boards.
Is one successful trial enough?
Not to establish sustained performance. The required evidence depends on risk, variation and the intended operating range. Define the verification plan before the trial.
Does an acceptable average prove stability?
No. The average can hide shifts, alternating groups or growing variation. Examine the data in production order as well as the overall summary.
Can the factory change specifications to improve yield?
Only through the applicable engineering and customer approval process. Results against a relaxed specification must not be presented as improvement against the unchanged original requirement.
What is a sensible first project?
Choose a recurring, measurable loss in one defined product family with a clear owner and usable records. Confirm the baseline before buying equipment or changing a process recipe.
Contact PCBtry with the fabrication revision, observed issue and relevant lot data to discuss a project-specific review. Request a documented technical response and agreed verification plan, not a generic yield guarantee.

0 Comments