How to Calculate and Validate UPH for IC Programming

Units per hour is useful only when its assumptions are visible. A headline UPH number can be misleading if it excludes programming time, site utilization, carrier replenishment, verification, or rejects. KINCOTO recommends treating throughput as a measurable process result for a defined device and job, not as a universal property of automated IC programming equipment.

Build a cycle-time model

Separate the process into device handling and programming. Handling may include pick, orientation check, socket load, contact confirmation, unload, AOI or marking, and placement into the output carrier. Programming may include erase, blank check, write, verify, security operations, and file-specific commands. Some actions overlap; others block the next cycle.

A first estimate can use effective cycle time: theoretical UPH equals 3,600 divided by effective seconds per completed device. For parallel sockets, do not simply multiply by the socket count. Use the number of active sites and account for batch synchronization, the slowest device in a group, load and unload strategy, and any site intentionally disabled. The equipment control sequence determines how much handling and programming can overlap.

• Device type, memory size, interface, algorithm, and image content affect programming time.
• Socket count, programmer architecture, and site utilization affect parallel capacity.
• Package, tape or tray or tube format, and inspection steps affect handling time.
• Retries, verification failures, carrier changes, and planned cleaning reduce sustained output.

Convert the model into a test plan

Use production-representative chips, the released programming file, intended security settings, actual sockets, and real input and output media. First stabilize the recipe and confirm correct results. Then time repeated cycles over a window long enough to include normal replenishment and unloading. Log completed good units, programming failures, contact retries, machine pauses, and excluded engineering stops separately.

Calculate at least two views: run-rate UPH during automatic operation and sustained UPH including normal operator interventions. If availability over a shift is needed, state which breaks, material shortages, changeovers, and maintenance events are included. Report the sample size, elapsed time, active sites, recipe revision, carrier, and environmental or process conditions.

Review bottlenecks and revalidate changes

Cycle logs help determine whether the constraint is programming, handler motion, media exchange, vision, marking, or inspection. Increasing programming stations helps mainly when programming occupies the bottleneck; it cannot remove a slow downstream operation. Conversely, motion optimization offers limited value when a long program-and-verify sequence dominates.

Revalidate after changing the chip revision, data file, algorithm, socket, active site count, package, carrier, marking content, inspection recipe, or retry policy. Any UPH discussed for KINCOTO IC programming is therefore conditional on the device, program time, station configuration, package, and process settings. This disciplined approach turns an estimate into an auditable capacity input for line planning.