Mes

MES (Manufacturing Execution System) is the fab's central software layer that tracks every lot, wafer, and process step against its routing — it's what actually knows that lot 42 just finished etch step 118 of 940, is cleared to move to metrology next, and isn't allowed anywhere near a chamber that's out of spec for its recipe. Where SECS and GEM define how an individual tool talks to a host, the MES is the host logic on the other end of thousands of those conversations at once, turning equipment-level messages into fab-wide decisions.

Dispatching is the MES's hardest real-time decision, because "any etch chamber" is never actually true. A lot arriving at an etch step can only go to chambers that are calibrated and matched for that specific recipe (see chamber-calibration-setup), currently qualified (not flagged from a failed monitor-wafer run), and not reserved for another product — the MES evaluates all of that per lot, per step, continuously, which is why dispatch logic is one of the most heavily tuned parts of fab software: a dispatcher that ignores chamber matching can silently route product into a chamber that's technically running but outside its statistical window.

Full lot traceability is the regulatory and engineering backbone the MES provides, and it's non-negotiable once a defect is found. Every event a tool reports — which chamber, which recipe revision, which operator acknowledged an alarm, what the SPC reading was — gets logged against that specific lot and wafer. When a yield excursion shows up weeks later, the first engineering question is always "what did every affected wafer have in common," and the MES's event log is the only place that question can actually be answered, by tracing every lot back through its exact chamber-by-chamber, step-by-step history.

MES sits one layer above the equipment-automation standards covered elsewhere on this site, consuming rather than replacing them. A load port's SECS/GEM messages, a chamber's calibration status, an AMHS's E84 handoff — none of these are MES concepts themselves; they're the raw signals the MES subscribes to in order to make its routing and dispatch decisions. Confusing "the MES is down" with "the tool's GEM interface is down" is a common troubleshooting mistake, because the symptoms can look identical (lots stop moving) even though the root cause and the fix are completely different layers of the stack.

A fab without an MES can still run individual tools, but it loses the thing that actually makes a fab a fab rather than a collection of independent machines: the fab-wide, step-by-step, auditable record of exactly what happened to every wafer, which is what yield engineering, process control, and regulatory traceability all ultimately depend on.