Semi E165
SEMI E165 specifies how to deliver equipment training when a fab or supplier doesn't have a dedicated training tool available — guidance built on top of E150's general training best practices and E161's tier classification, for the specific situation where the equipment a trainee needs to learn can't simply be taken offline and handed over for hands-on instruction. E150 assumes a training program has some form of equipment access to train against; E165 exists for the case where that assumption fails, because the fab can't spare production capacity for training use, the tool is too expensive or too few in number to dedicate one to a classroom, or the equipment simply doesn't exist yet in a deployable training copy.
A few things are worth knowing about why this situation needed its own standard rather than just a looser application of E150:
The tools most worth training people on well are usually the exact tools a fab can least afford to dedicate to training. A high-volume, low-cost piece of support equipment can often spare a unit, or spare hours on a unit, for hands-on instruction without materially affecting fab output. A leading-edge lithography scanner, an EUV tool, or any piece of equipment that exists in single or low double digits per fab and represents a direct bottleneck on output is the opposite case — every hour it spends in a training role instead of a production role is an hour of lost throughput on a constrained resource, which makes the naive solution of "just train on a dedicated unit" the most expensive possible answer for exactly the equipment where competent operation matters most.
E165 only works because E161 already decoupled the tier classification from any particular training method, which is the design choice that makes this standard possible at all. If a certified competency tier had been defined in terms of specific hours of hands-on access to a dedicated unit, there would be no way to certify someone trained via simulation or partial-system mockup as having reached that same tier — the credential would be inherently tied to one delivery method. Because E161 defines tiers around demonstrated competency rather than the training method used to reach it, E165 can substitute simulation, mockups, or carefully scheduled low-impact access and still produce a credential that means exactly what an E161 tier is supposed to mean.
This is the same engineering trade-off E157's module-level process tracking makes in reverse — trading perfect information for a workable substitute that still answers the question that matters. E157 accepts that per-module tracking data isn't the same as physically inspecting a wafer at every step, but it's good enough to localize an excursion. E165 accepts that simulated or partial training isn't the same as unlimited hands-on time with a real production tool, but it's good enough to certify genuine, verifiable competency — in both cases, a fab gets a standard that makes a real-world constraint tractable instead of pretending the constraint doesn't exist.
Read E165 as the standard that keeps E150's training framework and E161's tier system from breaking down exactly where a fab needs them most: on the expensive, capacity-constrained tools where competent operation matters the most and dedicated training access is the least affordable option, giving a fab a way to certify real competency without ever pulling a production bottleneck offline just to teach someone how to run it.