Reviewed state
Candidate twin output is reviewed before it is approved to move to another twin.
Digital Twin Network
Twins That Pass Process State
One Digital Twin is a lithography tool or R&D bench. A Digital Twin Network is twins that pass state: coat or bake into litho, litho into develop, or bench recipe A into bench recipe B. Environment travels with the handoff — not just a number, but the conditions under which that number still applies.
Service Scope
Engineering Work Defined Around Your Equipment
- Pass output of one process twin into the next twin
- Environment and incoming substrate state travel with the handoff
- Lithography and experiment-bench twins as the nodes
- Reviewed and approved state before it moves to another authorized twin
- Customer-defined boundaries: site, family, model, or individual tool
- Keep physics, chemistry, and control synchronized around the same physical line
Relevant Evidence
Experience Behind the Service Offering
- Built from semiconductor tool-control software work, not a slide-deck model
- Same Digital Twin practice used on lithography tools and experiment benches
- Customer-governed sharing — no cross-customer distribution claimed
How State Moves
Previous Tool → This Twin → Next Tool
Environment and process state travel with the handoff — not GEM knowledge packets. Lithography and experiment-bench twins remain the nodes.
Environment travels with the handoff
Previous process · This twin · Next process
Governed Handoff
Reviewed State, Authorized Twins
The mesh idea now serves Digital Twin handoff. Customer-defined boundaries stay. Public materials do not claim cross-customer sharing.
Approved handoff
A client administrator defines which environment and process fields may travel.
Authorized twins
Only authorized KodeGEM twins can receive the previous-step state.
Process-step matching
Similarity is defined by the customer — the same lithography family, bench, or process step.
Customer-controlled sharing
Customers can limit handoff by site, family, model, or individual tool.
Tool-specific restrictions
Restricted and tool-specific information stays outside broader distribution.
Each tool or bench runs its own twin. Public materials do not claim cross-customer sharing, automatic foundry or OSAT data ingest, or a running Digital Twin of the FAB.
Looking Ahead
A Digital Twin of the FAB
A future goal — not a current product. Add or remove tools in the line and examine the final product by manipulating the FAB.
Today we create lithography and bench twins and, when the project calls for it, pass reviewed environment and previous-process state from one twin to the next. Looking ahead, those connected twins are how a Digital Twin of the FAB would grow — tools added or removed, the product inspected by changing the line.
Back to Digital Twin creation →Engagement Options
Support from Review Through Production
Connect two process twins so the second sees the first’s outgoing state
Define which environment knobs may change this twin’s output
Reviewed handoff of incoming wafer or bench condition
Discuss a future Digital Twin of the FAB — looking ahead, not a current product
Define the Project Boundary
Send the equipment type, current software baseline, required interfaces, project stage, and acceptance goal.