Compare paste inspection, pad-level trends and stencil cleaning history to investigate stencil contamination.
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 PCB→
02Print solder→
03Place components→
04Reflow & inspect
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
PCB ID, pad-level paste volume, printing pressure, cleaning history
NAZARECompare historical signals
02 · NAZARE · Ontology
Turn experience into operating criteria
Link PCB, pad and stencil relationships, paste-volume limits, cleaning controls and first-board verification rules in ontology.
NAZARE02 · Connect relationships
03 · NAVIS
Present a response with evidence
Compare paste inspection, pad-level trends and stencil cleaning history to investigate stencil contamination. Run validated stencil cleaning Previous shift · paste inspection passed after stencil cleaning
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.
First PCB: paste volume back within limits. · 99 % · Range 90–110%
NAVISApproval & execution
↶ Keep verified outcomes and actions in NAZARE to inform the next decision.
