Semi E164

SEMI E164 defines EDA Common Metadata, the standard that attaches a consistent set of contextual tags — equipment ID, chamber ID, recipe ID, lot and wafer ID, timestamp, and collection-plan version — to every single data point an EDA system streams, so a value by itself is never just a bare number with no context. Data Collection Management (SEMI E134) defines how the data stream gets created and kept stable; E164 defines what has to travel alongside each value in that stream so that, months later, an analyst looking at one data point can still answer "which tool, which chamber, which recipe, which wafer, and under which collection-plan version did this come from?" without needing to cross-reference a separate log by hand.

Raw sensor value is collected
e.g. chamber pressure = 2.3 mTorr
SEMI E164 common metadata attachedSame tag set, every equipment vendor, every data point
Equipment + chamber + recipe ID
Where and under what recipe this value came from
Lot/wafer ID + timestamp + plan version
What material, when, and against which E134 plan
Fully traceable data point stored
Reconstructable context, months or years later

Without a common metadata standard, every equipment vendor would tag its collected data its own way — one vendor's timestamp field, another vendor's chamber identifier naming convention — forcing a fab's analytics team to write custom translation logic for every tool model before cross-tool analysis is even possible; E164 removes that translation burden by fixing the metadata tag set itself, not just the data values, so a fault-detection or virtual-metrology model trained on one tool's tagged data can be applied against another compliant tool's data without a metadata-mapping exercise first. This is also what makes long-term yield investigations tractable at all — reconstructing exactly what conditions produced a specific wafer's data months after the fact depends entirely on metadata that was captured correctly at collection time, since metadata that wasn't attached then can never be recovered from the raw values alone.

SEMI E164 — Every Data Point Carries Its Own Context same metadata tag set, regardless of equipment vendor Value: 2.3 mTorr Equipment ID Chamber ID Recipe ID Collection-plan version Lot / Wafer ID Timestamp Fully traceable, stored data point reconstructable months later, across any compliant vendor's tools metadata not captured at collection time can never be recovered later

SEMI E164 is the glue standard across the whole EDA/Interface A family — Equipment Self Description (SEMI E125) says what can be collected, Data Collection Management (SEMI E134) says how collection is requested and kept stable, and E164 is what guarantees every value that comes out the other end still means something specific once it's sitting in a fab's historian months or years later.

Take SEMI E164 further

Ask the copilot about this term, or have our engineers assess it against your process.

Ask CFSGPT about this → Request a technical assessment → Open the CFS app