FAQ

Straight answers.

The questions fab directors, process integration engineers and yield engineers ask in the first meeting, answered as plainly as we can, including where the answer is planned rather than done.

12 questionsPre-launch answersUpdated 2026-10-08

run_7b2e9c · agent graph · module M2 · scenario 10 nodes · 1 approval gate
01 · orchestrator ingest.lot ✓ SUCCEEDED 02 · fabtwin twin.simulate ✓ SUCCEEDED 03 · litho_overlay litho.correctables ✓ SUCCEEDED 04 · etch_depo etch.uniformity ✓ SUCCEEDED 05 · cmp_implant cmp.removal ✓ SUCCEEDED 06 · defect_inspect inspect.classify ✓ SUCCEEDED 07 · metrology_vm vm.score ✓ SUCCEEDED 08 · orchestrator approve.human ◆ APPROVAL 09 · yield_dispatch dispatch.route ✓ SUCCEEDED 10 · quality_conf lot.release ✓ SUCCEEDED

Illustrative scenario: Module M2 · 300 mm · metal-1 · lot L-48213, one lot through metal-1, one approval gate

FAQ

Everything we get asked

Twelve questions. If yours is not here, ask it.

Yes, over SECS/GEM, but only inside the qualified recipe window for that tool, with per-parameter limits and tool-state checks, and only at the autonomy level your fab has set. Level 1 is advisory: Waferira recommends and an engineer enters everything. Design partners start there, in shadow mode.

Run timeline · scenario

One scenario run, step by step

Every Waferira run is an ordered, inspectable sequence. This is run_7b2e9c on Module M2 · 300 mm · metal-1 · lot L-48213. Scenario completes in 10 steps with one approval gate. Overlay and CD predicted inside spec, one reticle-repeater signature caught and held for review, dispatch re-optimised, lot released with full genealogy.

run_7b2e9c Module M2 · 300 mm · metal-1 · lot L-48213 illustrative scenario SUCCEEDED
  1. 01 ingest.lot SUCCEEDED 0.7 s

    Fab Orchestrator · Pulled lot L-48213 from fab MES: 25 wafers, 300 mm, metal-1 layer, route, reticle, overlay and CD spec and the standing cycle-time target. Locked the target envelope for the run.

  2. 02 twin.simulate SUCCEEDED 38 s

    Fab Twin · Simulated 64 candidate correctable, recipe and dispatch sets on the as-run fab twin and ranked them on predicted overlay residual, CD uniformity, excursion risk and cycle time.

  3. 03 litho.correctables SUCCEEDED 1 m 20 s

    Litho-and-Overlay · Per-field overlay correctables and a focus-dose trim written to scanner SCN-07 over SECS/GEM after the previous lot's residual trended toward the control limit. Predicted overlay residual back inside spec.

  4. 04 etch.uniformity SUCCEEDED 58 s

    Etch-and-Depo · Chamber B on etcher ETCH-12 showed an edge-fast uniformity drift in FDC. Pressure and RF trims written within the qualified recipe window; predicted CD uniformity recovered.

  5. 05 cmp.removal SUCCEEDED 46 s

    CMP-and-Implant · Downforce and platen-speed trim on CMP-03 against the virtual removal-rate estimate to hold post-CMP thickness and dishing inside the window.

  6. 06 inspect.classify SUCCEEDED continuous

    Defect-and-Inspect · Inline optical, e-beam review and SEM imagery fused at the tool edge. 1,412 events classified, most dispositioned nuisance; one reticle-repeater signature on three dies flagged for review.

  7. 07 vm.score SUCCEEDED 2.1 s

    Metrology-and-Virtual · Virtual metrology scored every wafer at post-etch and post-CMP from tool-sensor and FDC signatures. Two wafers routed to physical metrology on predicted variance; the rest sampled at plan.

  8. 08 approve.human APPROVAL 1 m 04 s

    Fab Orchestrator · The reticle-repeater signature called for a reticle inspection hold and a recipe move outside the qualified window. Held for the module process engineer and approved at 03:14:27.

  9. 09 dispatch.route SUCCEEDED 4.3 s

    Yield-and-Dispatch · Dispatch re-optimised across 1,840 lots in WIP under reticle, chamber and qualification constraints. The lot routed to the qualified chamber with the shortest predicted queue; AMHS move issued to the stocker.

  10. 10 lot.release SUCCEEDED 1 m 05 s

    Quality-and-Conformance · Lot L-48213 moved on: genealogy written (recipe moves, correctables, FDC signatures, VM scores, defect map, approvals) and checked against the layer spec.

Autonomy

Four levels, set per agent and per tool

A fab does not go from manual APC to unattended control in one step. Waferira makes the level explicit, auditable and reversible at any time. The first release runs shadow mode, then assist mode, then graduated autonomy for low-risk APC, defect and metrology loops.

Autonomy levels and the human role at each
LevelWhat the agent doesWhat the human doesWhere it sits in a pilot
L1 · AdvisoryRecommends recipe moves, dispositions and dispatch, with citationsEnters every change manuallyShadow mode, first on the design-partner cell
L2 · SupervisedProposes a recipe write or hold; it executes on approvalApproves each move in the review consoleAssist mode, where accuracy and ROI are proven
L3 · BoundedWrites inside the qualified recipe window, tool-state checks and OCAP linkageApproves holds, out-of-window moves and lot releaseGraduated autonomy for low-risk APC, defect and metrology loops
L4 · Qualified loopsRuns a qualified loop without prompting, inside its envelopeSets the envelope; reviews the shift recordPlanned; reserved for loops the fab has qualified
Guardrails

An agent that can move a recipe needs a leash

Waferira writes to production tools over SECS/GEM. Every capability is scoped to a qualified recipe window, every write is policy-checked against tool state, and every action is written to an append-only, IP-isolated audit log the fab owns.

  • Recipe bounds. Each agent writes only inside the qualified recipe window for that tool, with explicit per-parameter limits.
  • Policy and tool-state checks before every write. Autonomy level, tool state, qualification, interlocks and shift are evaluated before a recipe moves.
  • Human-in-the-loop gates. Holds, out-of-window moves and lot release wait for a named approver, with OCAP linkage on every excursion.
  • Immutable, IP-isolated audit log. Append-only and exportable. Every action records source signals, retrieved procedures with citations, predicted impact, allowed range, rollback condition, approver and lot scope.
  • Rollback. Declared rollback conditions return a recipe to its previous qualified version; loss of the edge node leaves the tool on its own controller and recipe.
  • Tenant and IP isolation. Recipes, device designs, defect libraries and process memory never cross a customer boundary. Inference and feature storage stay at the fab edge; an on-prem control plane is available for IP-sensitive fabs.

Compliance posture

Compliance and certification status
ItemScopeStatus
SOC 2 Type I and fab-security reviewControl plane QUEUED Planned, first 6 months
SOC 2 Type IIControl plane QUEUED Planned, 6 to 12 months
SSO and RBACConsole and approvals QUEUED Planned, 6 to 12 months
IP-isolation and security assurance packageFab security and IT and OT review QUEUED Planned, 6 to 12 months
SEMI-standards-cited reasoningRecipes, integration specs, OCAPs RUNNING In the design, every answer cites its source
Per-tenant IP isolationData, models, memory RUNNING In the design from day one
On-prem and fab-edge deploymentIP-sensitive fabs RUNNING Design option

Read the security overview

Pricing

Priced per module, per fab, per group

Land on one workflow with a measured baseline. Expand by module, tool fleet, fab and autonomy level. Outcome components are available on yield-point value, excursions and cycle time. Annual prepay carries a 15 to 20% discount.

Billing period
Module $30,000 per process module or tool fleet / month · billed monthly

APC, defect or virtual-metrology AI for one module: litho, etch, deposition or CMP. For fabs validating ROI on the wedge, IP-isolated from day one.

  • One module or tool fleet, one agent
  • Fab-edge inference node included
  • SECS/GEM, APC, inspection and metrology connectors
  • Run log, IP-isolated audit trail, lot genealogy
  • Business-hours support
Start a pilot
Enterprise Custom land $2M to $20M ACV

Multi-fab IDMs and foundries standardising on Waferira, with custom process, device and yield models and a managed fab-edge fleet.

  • Multi-fab fleet management
  • Custom process, device and yield models
  • Fab-edge fleet with on-prem control plane
  • Group autonomy policy and approval chains
  • SLAs, SSO and RBAC, dedicated engineer
Contact us
Get started

Ask the question we missed

Start with one process module or tool fleet and one measurable baseline. A paid, IP-isolated pilot on defect classification, virtual-metrology-driven overlay and CD control or uniformity APC shows the number before you commit further.