Skip to content
QpiAI Agent Hive

Agent Hive for semiconductor

What caused the excursion?

Bring lot history, tool data and engineering knowledge into one investigation, then let your engineers decide what happens next.

Live case
Excursion detectedYield signature shiftedLot L24 · Etch · Chamber B
Context assembledLot history, tool data and engineering knowledge06
Context assembled03suspect changes
Silicon wafer being inspected inside semiconductor fabrication equipment
Signal → genealogyEngineer-approved response
Engineer review requiredYour engineers decide what happens next.

A signal tells you something changed. It rarely tells you why.

The useful clues sit across lot history, tool state, measurements, procedures and the experience of your engineering team.

Evidence sources
FDC and SPCSignals and excursions
MetrologyMeasurements and maps
EquipmentState and maintenance
EngineeringOCAPs and prior RCAs
Wafer genealogy

Lot L24 · Wafers 07 to 12

Etch 14B · Recipe R18

Agent Hive case

High correlation

Recent chamber maintenance · Recipe parameter drift · Six related lots

Engineer review required

Engineer gate

Validate before hold or release

WIP exposure and containment

Hold, inspect or release

Genealogy explains why each wafer is included

Engineers can open every source behind a finding before they act on it.

Start with the investigations that eat up engineering time.

Pick one recurring problem. Agent Hive gathers the evidence around it and works within the review process your team already uses.

Yield excursion investigation

See the strongest clues before chasing every possibility.

Compare process history, defect patterns, metrology and equipment signals. Your engineers review the likely conditions and choose the next step.

Wafer signatureEdge cluster · wafers 07 to 12
Ranked conditions
  1. Etch chamber BStrong match
  2. Recipe R18 driftReview
  3. Incoming materialWeak match

Engineer validates the correlation

RequirementPower integritySYS-042
ConstraintRipple < 30 mVRev C
EvidenceSimulation passedSI-118
Change impact2 tests staleECO-029
Verification gateEngineer review ready

PCB verification blueprint

Know what has been verified, and what needs another look.

This proposed workflow links each requirement to its constraints, ECAD outputs, simulations, tests and engineering changes.

This is an anonymized customer proposal, not a completed deployment. It describes the planned scope and architecture, with no claim of production results.

Read the full blueprint

Keep sensitive fab data where it belongs.

Run Agent Hive inside the fab network, or use a controlled gateway when approved external models are allowed.

What runs together

Fab context

The lots, wafers, tools, recipes and records behind the question.

Agent teamwork

Specialist agents work the same case and show what each one found.

Testing

Real engineering questions and review criteria before a workflow is released.

Controls

Permissions, engineer sign-off and a clear record of the decision.

Deployment

Local models, or approved endpoints reached through one gateway.

Everything stays on the fab network

Run Agent Hive and the models locally.

For sites where recipes, process data and engineering records cannot leave the facility.

Fab network. No egress.

Fab usersSSO and role-based access
Agent HiveRuntime and context graph
Local modelsFab GPU cluster

Questions we hear from semiconductor teams.

The best starting point is usually one investigation that takes too much searching, coordination and expert time.

Does Agent Hive replace MES, FDC, SPC or yield systems?

No. Those systems remain the sources of record. Agent Hive brings the relevant evidence together when your team investigates a specific problem.

Can engineers see how it reached a finding?

Yes. They can open the sources, check the relationships, correct the finding and approve the next step.

Can it run inside a restricted fab network?

Yes. Agent Hive can run fully air-gapped. A hybrid setup is also available when approved model access is allowed through a controlled gateway.

Where should we start?

Choose one recurring investigation that crosses several systems and expert groups. Agree on the source data, reviewers and a clear definition of a useful answer.

Is the PCB blueprint a completed customer deployment?

No. It is an anonymized customer proposal describing planned scope and architecture. It does not include production results.

Bring us one painful investigation

Let’s work out what a better process would look like.

We will map the evidence, the people who review it and the setup needed to support the decision.

Book a demo