Semi E133.1

SEMI E133.1 defines the XML message schema for automated process-control systems — the specific document structure a process-control interface uses to exchange control-model parameters, run-to-run adjustment data, and feedback-correction values with the host MES — rather than the general advanced-process-control (APC) interface behavior that existing standards in this area already establish. Advanced process control works by feeding measurement and context data from one process step forward into the control recipe of a later step, continuously tuning equipment settings to hold a target output rather than running every lot with identical fixed parameters; that interchange needs a documented message structure the host, the equipment, and any intermediate APC controller software can all parse the same way, and E133.1 is the standard that fixes what that XML document actually looks like.

APC feeds measurement/context data forward into a later step's recipe
Run-to-run and feed-forward/feed-backward control require a data exchange
SEMI E133.1 — XML messaging for process-control systemsFixes the document schema carrying control parameters and corrections
Standardized XML structure for control-model parameters
Equipment, host, and APC controller all parse the same schema
Defined fields for run-to-run adjustment and feedback-correction data
No vendor-specific document structure to reconcile
APC loops close consistently across equipment and controller vendors
One documented message structure instead of a per-integration custom format

The reason APC needed a dedicated XML messaging standard is that an advanced-process-control loop only works if every participant in the loop — the equipment generating a measurement, the APC controller computing a correction, and the host tracking the recipe change — agrees on exactly what a "control parameter" or "adjustment value" document contains, and a functional description of APC's control logic says nothing about the actual message format carrying that data between systems. Without a fixed schema, every fab's APC deployment risks becoming a custom integration between whatever equipment and controller software happen to be paired together, with the message format itself as fragile and vendor-specific as the pre-GEM era's communication protocols were before SECS-II standardized them. E133.1 closes that gap specifically for the XML side of process-control data exchange.

One Document, Traveling Around the Closed Loop the same E133.1 XML schema at every hop in the run-to-run feedback loop Equipment <Measurement step="4"> <Value>148.3</Value> </Measurement> APC controller <Correction stepNext="5"> <Delta>-2.1°C</Delta> </Correction> Host MES <RecipeUpdate lot="B4471"> <Param name="temp"/> </RecipeUpdate> equipment measures → controller corrects → host updates the next recipe same tag names, same structure, parsed identically at all three stops

E133.1 is what keeps an APC feedback loop from becoming a fragile, custom integration between whatever equipment and controller software a fab happens to pair together — by fixing the XML document structure that carries control parameters, run-to-run adjustments, and feedback corrections between every participant in the loop, it gives process-control data exchange the same interoperability guarantee SECS-II already gave basic equipment communication.

Take SEMI E133.1 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