Compare product-specific rules, active tool settings and tool history to identify the retained recipe from the previous variant.
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 housing→
02Press bearing→
03Tighten bolts→
04Final inspection
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 ID, torque & angle, active recipe, inspection results
NAZARECompare historical signals
02 · NAZARE · Ontology
Turn experience into operating criteria
Manage product–bolt–tool relationships, torque and angle criteria and approvable recipes through ontology.
NAZARE02 · Connect relationships
03 · NAVIS
Present a response with evidence
Compare product-specific rules, active tool settings and tool history to identify the retained recipe from the previous variant. Apply the correct tightening recipe Previous variant change · corrected recipe passed verification
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: tightening and inspection verified. · 54.8 Nm · Range 52–58 Nm
NAVISApproval & execution
↶ Keep verified outcomes and actions in NAZARE to inform the next decision.
