Compare vision measurements, head temperature and calibration history to investigate alignment drift.
AI-generated visual · values, actions & history are illustrative
An illustrative scenario, not a customer deployment. Values, causes, history and automation scope are examples; actual scope requires equipment integration and operating-rule validation.
01Load substrate→
02Die attach→
03Wire bond→
04Inspect
From a deviation to a verified response.
01NAZAREConnect equipment and production records
02NAZARE · OntologyTurn experience into operating criteria
03NAVISPresent a response with evidence
04NAVIS → NAZARE → PLCSend approved actions to equipment
05NAZARE + NAVISInspect the next unit and retain results
01 · NAZARE
Connect equipment and production records
Product & lot, placement measurements, head temperature, calibration history
NAZARECompare historical signals
02 · NAZARE · Ontology
Turn experience into operating criteria
Link product, substrate, die and bonder relationships, placement limits and post-correction verification rules in NAZARE ontology.
NAZARE02 · Connect relationships
03 · NAVIS
Present a response with evidence
Compare vision measurements, head temperature and calibration history to investigate alignment drift. Apply validated alignment correction Previous shift · alignment correction passed inspection
Send approved actions to equipment — After the operator approves the target and scope, NAVIS requests execution from NAZARE through MCP. NAZARE sends commands to the integrated PLC; the device follows the approved procedure within site safeguards.
Inspect the next unit and retain results — Previously affected units remain on hold for separate revalidation. Verify the response on the next unit or trial run and store results in NAZARE for future decisions.
Next unit: placement within limits. · 3 μm · Limit ±10 μm
NAVISApproval & execution
↶ Keep verified outcomes and actions in NAZARE to inform the next decision.
