Used ATE for Fabless Companies: Buyer Checklist
Buying used ATE for a fabless company? Compare outsourcing costs, match instruments and software, and define device-level acceptance before purchase.
Start with the test program, not the tester price
For a fabless company considering used ATE, appoint a test-engineering owner before requesting offers. Write down the devices, test coverage, production or characterization workload, interface hardware and data outputs you need. Use that requirements sheet to screen each offered configuration.
Do not approve a tester solely because its model name matches equipment at your outsourced semiconductor assembly and test provider (OSAT). Ask your engineering team to demonstrate the actual program on the proposed hardware and software combination.
Compare outsourcing with the complete in-house plan
Build the decision from your invoices and written supplier quotes. Separate capital spending from recurring operating costs and show assumptions explicitly.
- Outsourced baseline: Collect billed insertions, retests, engineering charges, logistics and any minimum commitments. Use your contracted rates rather than a generic per-device estimate.
- Acquisition and setup: Request line items for the tester, instruments, interface hardware, handling or probing equipment, software, shipping, installation and calibration.
- Operating plan: Estimate engineering coverage, maintenance, facility services, consumables and spare-part needs with the people responsible for them.
- Utilization scenarios: Compare expected, lower-volume and delayed-ramp cases. Include a case in which commissioning takes longer than planned.
For a simple payback calculation, divide upfront project cost by estimated annual net savings only when those savings are positive. Define net savings as avoided outsourced costs minus incremental in-house operating costs, using the same workload and time period on both sides. Keep financing, taxes and depreciation explicit if your finance team includes them in a fuller model.
Match instruments, software and interfaces
Teradyne identifies IG-XL as test-program development software for its FLEX, UltraFLEX and J750 tester families.
For any platform, request a configuration export and an itemized instrument list. Have the test engineer map every required measurement to the proposed instrument, channel assignment and operating limit. Record unsupported or untested measurements as open items rather than assuming coverage.
Ask for the installed software release, licensed options, installation media and written entitlement or transfer terms. Require confirmation from the relevant rights holder before relying on software access after the sale. Do not infer cross-platform program portability from a product-family description.
For load boards, probe cards, sockets, handlers or probers, specify the exact interface and ownership arrangements. Ask your OSAT which files, fixtures and reference results you can use. Request a written scope for any porting, fixture development or correlation work.
Put device-level acceptance in the purchase terms
Agree on the acceptance procedure before selecting a seller. Include:
- Configuration identity: Record the system serial number, instrument inventory, software versions and included fixtures.
- Reference devices: Have your engineer select characterized devices and define expected results against an agreed reference dataset.
- Execution: Run the intended test flow with the agreed site count and interface hardware. Save per-device results, error logs and test-time measurements.
- Correlation: Define measurement limits and a discrepancy-resolution process with the engineering owner. Separate tester diagnostics from product-level acceptance.
- Handover: Specify training, backups, calibration documents, packing, installation responsibilities and a repeat test after delivery.
Ask the seller to identify excluded tests and unresolved faults in writing. Agree on payment milestones and a remedy for failed acceptance before issuing a purchase order.
Prepare a quote request your engineer can approve
Send the requirements sheet, preferred platform, configuration checklist, interface needs, destination and acceptance protocol. Request a line-item offer that identifies what is included, what still needs development and who owns commissioning.
Should we buy before hiring a test engineer?
Assign a qualified internal owner or a contracted test engineer first. Make that person responsible for configuration approval and acceptance sign-off.
What is a reasonable used ATE budget?
Build it from comparable, configuration-specific offers and the complete setup plan above. Keep a base-system quote separate from the total cost of a usable test cell.