The reason they changed to wafers per day, is not only that they cannot get enough wafers per hour, but also the EUV machine is not (or cannot be) up 100% of the day. So even if the WPH is quite reasonable, with the extended downtime, it still reduces the throughput, that is measured in wafers per day.
It's the right idea, it looks like you are referring to the example of double patterning using two exposures, for a single layer. More generally, overlay is referring to the interaction between successive layers, so that they link up properly. Multiple exposures does have higher risk than single exposure. But these recent new single-exposure technologies have their own sources contributing overlay error. Meanwhile multi-patterning is heading toward self-aligned approaches.
When patterning a first layer, the features deviate from their positions within a tolerance. Then when the next layer is patterned over the first layer, those features also deviate from their positions within a tolerance. If the tolerances are followed, there should be no risk of broken connections, line shorts, etc.
@resistion:i think the case of 3-4 real logic layers + 1 repair layer might be interesting economically and might offer enough defence against defects to make those methods(self assmbly,imprints) useful.
Thanks, alex_m1. The concept of this repair layer sounds interesting, but of course, it's still cheaper to have all the layers within defect tolerances to begin with (so then you could go on to heterogeneous integration).
Resistion: the way i understood it , you build 2 equivalent layers on top of one another, And for gate(or cell) you choose which layer 2 use after manufacturing - using boundary scan for detection and e-beam for the repair. more details in .
Assuming defects are uncorrelated between layers(big assumption), this greatly decreases you defect probability.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.