Production Line Planning

Sizing an ATE Test System: Channels, UPH and the Costs the Quote Leaves Out

Most ATE quotes start from a machine list. They should start from one number: your target units per hour. Get that number first, and the channel count, the tester tier and the software features all fall out of arithmetic. Skip it — and don't check what the quote doesn't show — and you buy a system sized for the vendor's catalogue, then spend two years paying for it in changeovers, calibration downtime and a supplier who won't export your own data.

This is a worksheet, not a brochure. Everything below is arithmetic on numbers you already have — your daily volume, your shift hours, how long your product actually takes to test. We deliberately don't quote a "catalogue UPH" for any machine, because a number that isn't derived from your test sequence is a guess wearing a suit.

Step 1: Convert your volume into a UPH target

Start from what you ship, not what you hope. Take your daily output and divide by productive hours per shift:

Daily volume 8,000 units ÷ 8 productive hours = 1,000 UPH target
(Use the slowest hour you actually experience — the one with the model change, the jam, the new operator — not your best hour.)

That target — not a spec sheet — is what every later decision references. A line that quietly misses it becomes the bottleneck nobody notices until the warehouse is empty and the expedite freight invoice arrives.

Step 2: Test time comes from your test list, not a brochure

A single-port charger test is not one measurement; it's a sequence. Count your own items first:

  1. Output voltage and current at several load points — no-load, mid, full. Each point takes seconds to settle, and settling time is most of the test.
  2. Protocol handshake checks — PD, QC, PPS, brand protocols. Every protocol you verify adds negotiation time.
  3. Ripple and noise — a measurement that needs a clean, stable load to mean anything.
  4. Protection behaviour — OCP/OVP verification where the product spec requires it.

Industry rule of thumb: a single-port charger test might take 15–40 seconds depending on how many protocols you verify. Your number comes from timing your own sequence, stopwatch in hand, not from anyone's brochure. Then apply the one formula that sizes everything:

UPH ≈ 3600 ÷ (test time per unit + load/unload time)

Example: test 30s + load/unload 6s → 3600 ÷ 36 ≈ 100 UPH per station
To hit a 1,000 UPH target: 1,000 ÷ 100 = 10 stations needed

Ten stations does not mean ten operators and ten separate benches. It means your architecture decision: a multi-channel system where one controller runs many test positions in parallel, or an ATE line with fixtures and automated load/unload.

A war story we've seen more than once: a factory bought a 16-channel matrix for a mixed-model line, then discovered the fixtures only accepted one housing shape. Every model change meant re-fixturing by hand — the throughput gain evaporated, and the "automated" line ran slower than four benches. Fixture compatibility across your actual product mix is a sizing input, not an afterthought. Count your housing variants before you count channels.

Step 3: Match the architecture — and know when not to

The tiers exist because lines differ. Roughly:

The tier question is really a labor question. Ten operators running ten benches is a different business than one technician watching a 16-channel matrix.

When an ATE is the wrong buy

Vendors rarely print this part. Three situations where the honest answer is "don't":

And the mirror-image trap: more channels is not automatically better. If your bottleneck is protocol negotiation time, a 16-channel system where every channel waits on the same slow handshake buys you sixteen copies of the same queue. Size channels to the bottleneck, not to the price-per-channel discount.

Step 4: What the test software must actually do

Buyers evaluate channels and power ranges, then discover the software is what they live with every day. When you assess the ATE software side, these five functions decide whether the system ages well or becomes a very expensive fixture in the corner:

  1. Saved test recipes per model. Switching SKUs should load a recipe in seconds, not mean re-editing limits on the machine. On a line that changes models daily, this is the difference between a 20-minute changeover and a 2-minute one — and on a 1,000-UPH line, 18 minutes is 300 units of capacity.
  2. Per-unit logging. Every unit gets a record the moment it's tested — full results, not a batch summary. This is what makes a buyer's audit survivable, and what makes a field failure traceable to a shift.
  3. Auto-generated reports and one-click export. The system writes the report; you export the batch in the format the buyer asked for. If "the report" is a person rebuilding a spreadsheet every Friday, you don't have a system — you have a typist with a machine.
  4. MES-ready output. Results push to your manufacturing execution system, so the record lives where the audit looks first. Ask what format, and ask what happens when your MES changes.
  5. External trigger. The tester starts and stops from your fixture or PLC — it joins the line instead of sitting beside it waiting for someone to press a button.

If a quote's software can't do these five, the hardware number is decoration.

The six costs the quote never shows

Two vendors can quote the same channel count and differ by six figures over three years. The difference lives in these line items — ask about every one, in writing, before you sign:

  1. Fixtures and probes. How many housing variants does the fixture set cover, what does an extra variant cost, and how often do probes wear out? Probe wear is a consumable, not a warranty item — budget it like you budget labels.
  2. Calibration. Electronic test equipment typically starts on a 12-month calibration interval; instruments that stay comfortably in tolerance can often move to 16–24 months, while any out-of-tolerance finding should shorten the interval and trigger an impact review of everything measured since the last good calibration. Ask: who calibrates, how long is the system down each time, and is there a loaner?
  3. Software lock-in. Can you export raw test data in an open format? If the vendor's software is the only way to read your own results, your data has a landlord. Ask what happens to your history if you switch vendors.
  4. Training and turnover. How long until a new operator runs the system unsupervised? On a line with annual operator turnover, "two weeks to train" is a permanent tax, not a one-time cost.
  5. Spares and response time. When a channel dies, is the answer "next-day part" or "two weeks from the factory"? One dead channel on a 10-station line is a 10% capacity hole — the response time is the real spec.
  6. Floor space, power, air. Multi-channel racks and ATE lines need footprint, clean power and sometimes pneumatics. A system that doesn't fit the corner you have is a construction project.

The acceptance checklist (print this, hand it to the vendor)

Before you accept any ATE or multi-channel system, these are the checks that catch the problems while the vendor still owes you a fix:

Be honest with your own inputs. Every number in this worksheet is an example shape, not a claim — your test time, your load/unload time, your shift reality. The point is the order of operations: volume first, UPH second, architecture third, hidden costs fourth, software last. Reverse that order and you'll buy a machine and then spend a year defending the decision. If you want a second pair of eyes on the arithmetic, send us your product type and daily volume — we'll model it with you, no obligation, including the cases where the honest answer is "buy two benches instead."
The systems for this
See the ATE automated test systems we built for this →
← Back to all articles

The equipment in this article

See the testers and systems this piece refers to.

🔧 Compare GTI6331H🔧 Compare GTI6531H🔧 Compare GTI6631H🔧 Compare GTI6031H-8X2📄 GTI6031H vs GTI6331H📄 Kill changeover downtime