PCBA Test Strategy Cost Per Board Calculator
Choosing between in-circuit test, flying probe and functional test is a cost question long before it is a technical one. This calculator compares total cost per board, including the escaped defect cost that cheap test coverage hides, and shows the volume where a fixture starts to pay.
Your numbers
Total boards the fixture or program will test before replacement.
Operator share, equipment depreciation and floor space.
Share of boards leaving reflow with at least one defect.
Field return, RMA handling, debug and rework or replacement.
Share of assembly defects the test catches.
Your results
Detection rates and escape cost are the biggest drivers and are assumptions you must set from your own data. Methods are often combined in practice (for example ICT or flying probe plus functional); this tool compares them one at a time.
Total test cost per board vs boards over fixture life
Sweeps Boards over fixture life from 50 to 5000, holding your other inputs fixed.
Connect test and RMA data to cost
An optional walkthrough of linking test results and returns to the cost model in your ERP.
Optional. The tool and every export work without this. No spam.
How to use it
Set the number of boards the fixture will test over its life, the station rate, the share of boards with defects, and the cost of one escaped defect. Then enter cost, test time and defect detection for each method. Defect detection is the share of assembly defects the method catches, not just nominal node coverage, so use your own escape history if you have it. The sweep shows total cost per board across volume for all three methods.
The cost model
For each method, cost per board is fixture or program cost divided by boards, plus test seconds over 3,600 times the station rate, plus expected escape cost. Expected escape cost is the defective share times the share the method misses, times the cost of one escape. The ICT versus flying probe break-even is the fixture premium divided by the per-board test time saving, valued at the station rate. It ignores coverage, so check the full total as well.
- Cost = fixture/N + sec/3600 x rate + escape cost
- Escape = defect rate x (1 - detection) x cost per escape
- Break-even N = (fixture - program) / (time saving x rate/3600)
Reading the result
At low volume, flying probe wins because it has no fixture, despite long test time. As volume rises, ICT usually wins on speed. Functional test covers behaviors that structural test cannot see, so it is often additive rather than a substitute. If the lowest cost option has weak detection and high escape cost, add a second method or improve AOI. A very high escape cost, for example in medical or aerospace products, shifts the answer toward maximum coverage regardless of fixture price.
Common mistakes
Comparing only fixture price ignores test time, which dominates over thousands of boards. Taking vendor stated coverage at face value without checking escape history is another trap. Using the same escape cost for a consumer gadget and a defense avionics unit misleads. Finally, test access matters: dense, fine pitch boards with few test points may make ICT impractical, so confirm access with your test engineer before relying on a fixture quote.
- Include escape cost, not only test cost
- Use measured detection, not brochure coverage
- Check test point access for ICT
- Test life is limited by fixture wear and design changes
Frequently Asked Questions
When does flying probe beat ICT?
At low volume, on prototype and frequent design changes, where an ICT fixture cannot be amortized. Flying probe needs only a program, but runs far slower per board, so the advantage ends as volume grows.
Is functional test a replacement for ICT?
Usually not. ICT and flying probe verify structure, such as shorts, opens and component values. Functional test verifies behavior in the product context. Many products use one structural method plus a functional step.
How do I estimate cost of an escaped defect?
Add handling of the return, shipping, failure analysis, rework or replacement, and customer penalties. For products in regulated or safety critical markets, include the cost of investigations and lost trust, which is often much higher than direct costs.
How many boards should I use for amortization?
Use the realistic number of boards the fixture will test before a design change or wear forces replacement, not the optimistic program forecast. A conservative figure avoids underestimating cost per board.
If test results and RMA data live in different systems, we can help bring them into your ERP so detection and escape assumptions are based on your own records.
Related Tools
PCBA NRE and Stencil Amortization Per Unit Calculator
Amortize stencil, programming, fixture and DFM NRE plus line setup and first article time over your order size, then see loaded cost, quoted unit price and how much of the price is one-time cost.
Quality & InspectionPCBA Array Panel Yield and Cost Per Good Board Calculator
Layout boards in an assembly array, then see utilization, the chance an array is fully good, and cost per good board with and without X-out acceptance.
Costing & FinancePCBA Quantity Price Break Worksheet
Model price tiers from 1 to 5,000 boards by combining material price breaks, scrap, assembly cost, one-time cost and margin into unit price, order value and profit.
Quality & InspectionPCBA Quote Data Package Completeness Checklist
A checklist of the design, BOM, assembly, test, commercial and compliance data an EMS provider needs before it can quote a PCBA without padding for unknowns.
More Quality & Inspection tools
See all- PCBA AOI Defect Log and DPMO Worksheet
- PCBA RMA Failure Analysis Report Template
- SMT First Pass Yield and Rolled Throughput Yield Calculator
- Incoming Electronic Component Inspection Record Template
- ESD Protected Area Audit Checklist (ANSI/ESD S20.20 Style)
- SAP QM Process Capability Cp Cpk Calculator
- SAP QM Lot Rejection Rate, PPM and Sigma Level Calculator
- SAP QM Gauge R&R Study Calculator
- SAP QM Cp and Cpk Capability Calculator
Keep exploring
Free tools
- Wafer Probe Throughput and Test Cell Capacity CalculatorEstimates wafers per hour and wafers per week for a probe cell from dies per wafer, multi-site count, test time, index time and retest rate.
- PCBA Rework Cost Tracking WorksheetLog rework events by work order, defect type, time and material, and get rework cost per line and per board.
- PCBA First Pass Yield and DPMO CalculatorTurn defect counts from AOI, ICT or inspection into DPMO, defects per unit and expected first pass yield using component and joint opportunities.
ERP fixes and how-tos
- How to present ERP AI to the board: what to include and what to leave outA practical outline for presenting ERP AI to a board: the decision asked, risk and data controls, a bounded pilot, cost envelope and the questions directors ask.
- ERP AI Governance: Do You Need a Board and What Should It Do?ERP AI governance explained: what a board should own, who sits on it, how to approve AI use cases on ERP data, and a one-page charter you can adopt.
- SAP Business One production process flow: from BOM to production order to receiptThe SAP Business One production process flow from bill of materials to production order, issue, receipt and close, with the reports and tables used.
Guides
- PCBA Quoting Software for EMS CompaniesHow EMS and PCBA shops evaluate quoting software: BOM import, live distributor pricing, assembly labor models, NRE, and how quotes tie back to the ERP.
- ERP for Contract Electronics ManufacturersWhat an ERP needs for EMS and PCBA shops: multi-level BOMs, AML, lot and reel traceability, kitting, ECN control, and how common systems fit the job.
- IPC-A-610 Class 2 vs Class 3: How It Affects Your PCBA QuoteHow the IPC class requirement changes PCBA cost and risk: inspection time, rework limits, training, documentation, and how EMS shops should price Class 3.
AI on your ERP
- AI for EMS and PCBA Manufacturers Running SyteLine, Epicor, or NetSuiteAI for EMS and PCBA manufacturers on SyteLine, Epicor, or NetSuite: automate BOM scrubbing, AVL checks, and obsolescence alerts, grounded in your own ERP data on-prem.
- NIS2 Compliance for AI on Your Manufacturing ERPNIS2 pulls any AI system reading your ERP into the same risk-management and incident-reporting duties as the ERP itself. How to deploy AI inside the boundary.