MES & Shop FloorFree calculatorPDF, Excel, Word exportSemiconductors

Fab Equipment Utilization Calculator (SEMI E10 Style)

Fab capacity planning starts with how tool time is really spent. This calculator splits a period into productive, standby, engineering, scheduled down, unscheduled down and non-scheduled time, then reports availability, utilization and throughput efficiency.

Your numbers

hours

Calendar hours, 720 for a 30 day month.

hours

Planned shutdown, no shifts, holidays when tool is not scheduled.

hours

Repairs and breakdowns.

hours

Preventive maintenance, calibration, planned qualification.

hours

Process experiments and engineering runs.

hours

Tool ready but no product, operator or material.

wafers
wafers/hour

Theoretical throughput at the recipe in use.

Your results

Operational availability
89.4%
Uptime divided by operations time.
Utilization (productive / total)
78.6%
Productive time as a share of all calendar time.
Operations time
720 hrs
Total time minus non-scheduled time.
Productive time
566 hrs
Time spent processing product.
Uptime
644 hrs
Operational utilization
78.6%
Throughput efficiency
94.2%
Actual wafers versus rated throughput during productive time.

Time states follow the general structure of SEMI E10 but use your own definitions. Align state mapping with your fab's agreed E10 or equivalent standard before comparing across tools or sites.

Save results:

Availability and utilization vs unscheduled downtime

Sweeps Unscheduled downtime from 0 to 120, holding your other inputs fixed.

Tool state analytics

Want E10 style state reports from your equipment logs? Ask for an optional expert review.

Optional. The tool and every export work without this. No spam.

How to use it

Take one tool or a tool group for a week or month. Enter the total hours, then the hours in each non productive state. Productive time is derived as what is left. Enter wafers processed and the rated throughput to see how well the tool performs while productive. Pull the hours from your equipment event log or MES state history rather than estimating. The chart shows how availability and utilization fall as unscheduled downtime grows, handy for justifying maintenance work.

The metrics

The structure follows SEMI E10 reliability, availability and maintainability states. Total time splits into non-scheduled time and operations time. Uptime is productive plus standby plus engineering. Operational availability is uptime divided by operations time. Utilization is productive time divided by total time, and operational utilization divides it by operations time. Throughput efficiency compares wafers with rated wph multiplied by productive hours. These differ from OEE: standby appears as a state, not as a performance loss.

  • Availability: how much of scheduled time the tool could run
  • Utilization: how much of total time it actually processed product
  • Throughput efficiency: speed while it ran

Reading results and common mistakes

High availability with low utilization means the tool waits, usually on lots, WIP flow or operator coverage. Low availability points to maintenance or reliability work. Throughput efficiency far below 100 percent often means recipe overhead, load and unload time, or a rated wph that ignores real recipes. Mistakes include counting engineering time as productive, double counting PM hours, and mixing tools with different rated throughput into one average. Capacity models usually derate tools by utilization targets, which ties directly to queue time behavior at the bottleneck.

Frequently Asked Questions

How is this different from OEE?

OEE multiplies availability, performance and quality from the product perspective. The SEMI E10 style states break tool time into explicit categories, so you see standby and engineering separately from downtime.

What is a good utilization?

It depends on the tool. Bottleneck tools often target high utilization but pay for it in queue time. Non bottleneck tools can run lower. Compare against your own capacity model, not a generic number.

Is standby counted as uptime?

Yes under the E10 structure. Standby is time when the tool is able to run but is not processing, so it counts toward uptime and availability, but not toward utilization.

Where do I get the hours?

From your equipment state log, MES tool history or SECS/GEM event data, grouped by state. If you must estimate, state that clearly because estimated states hide the largest losses.

Netray can compute these state metrics from equipment event logs and MES history, and answer questions about bottleneck tools in plain language on a private system.