Ask & reason
Ask why. Start with the evidence.
Combine NAZARE equipment signals with production, quality and maintenance records from connected systems. Documents and operating knowledge help explain possible causes and the order of checks.
NAVIS · AI agents
Understand the cause—and what to do next.
NAVIS is a manufacturing AI agent platform that combines equipment data, expert knowledge and business records—from answers and inspection plans to approved autonomous control and outcome verification.
- 01NAZARE · MES · ERP · QMS Equipment and business records
Signals, expert knowledge, production and quality
- 02NAVIS Find evidence and plan
Compare current conditions, rules and past actions
- 03NAVIS → NAZARE → PLC Approve, execute and verify
Act within the approved scope and check the result
Record outcomes and site feedback in NAZARE for the next decision.
NAVIS
From one question to a verified action.
Follow one compressed-air system from falling pressure through diagnosis, approval, execution and verification.
NAVIS
Tank pressure0.36 MPaOperating range 0.42–0.50 MPa
Inspect
“Pressure is falling. Where should we look?”
Read tank pressure and valve states from NAZARE, then check equipment relationships, operating criteria and previous actions.
NAZARE relationships · pressure history · work criteria
From shop-floor questions to everyday work.
Approval & execution
Review the change. Execute only the approved scope.
Review the equipment, evidence, action sequence and verification conditions. After approval, NAVIS requests execution through NAZARE, which sends commands to the PLC within site-defined limits and interlocks.
Incident & action history
Verify recovery, beyond command completion.
Check command results and subsequent machine state separately. Preserve causes, actions, recovery and recurrence as evidence for future decisions and maintenance reviews.
NAVIS · Application workflows
Different equipment. One connected decision process.
Read signals, narrow causes using relationships and rules, and verify approved actions. These illustrative scenarios are configured for each site’s signals, operating criteria and control scope.
01 · Compressed-air leak diagnosis
Pressure is falling. Which branch needs attention?
Data considered togetherTank pressure · pump state · branch valves
- 01Reasoning
Use piping relationships and branch pressure changes to narrow the suspected leak location.
- 02Approved response
After work authorization and safety checks, run the approved diagnostic and isolation procedure.
- 03Verification
Check pressure recovery and stability, then retain recurrence history.
02 · Heating-process diagnosis
Why is temperature low despite high heater output?
Data considered togetherMain/auxiliary temperature · heater output · inlet valve
- 01Reasoning
Compare both sensors and inflow to distinguish sensor, inlet and heating causes.
- 02Approved response
Request approval for a cause-specific check or valve adjustment instead of blindly raising output.
- 03Verification
Recheck return to the setpoint and agreement between sensor trends.
03 · Airflow & power management
Can we meet airflow needs with less power?
Data considered togetherAirflow · blower speed · damper position · power
- 01Reasoning
Distinguish speed, damper and restriction changes, then compare combinations that meet the target.
- 02Approved response
Propose speed and damper changes within permitted limits, then apply after approval.
- 03Verification
Verify airflow and power together to inform subsequent operating choices.
04 · Temperature & humidity management
Will ventilation help under current conditions?
Data considered togetherIndoor/outdoor temperature and humidity · dampers · fans
- 01Reasoning
Compare indoor and outdoor temperature and humidity to assess whether ventilation will help.
- 02Approved response
When safety conditions and approval are satisfied, adjust supply and exhaust in stages.
- 03Verification
Check return toward target humidity and hold adjustments when conditions are unsuitable.
05 · High-resolution vibration analysis
Are brief anomalies hidden by averages?
Data considered togetherRaw vibration · speed · operating conditions · maintenance
- 01Reasoning
Compare raw waveforms against reference records under matching conditions. Equipment-specific detection models can be added when needed.
- 02Approved response
Explain possible causes and checks. Any control follows separately defined limits and approval procedures.
- 03Verification
Preserve detailed before-and-after data to compare recurrence and improvement.
Explore NAVIS
Start together
Tell us what you want to improve first.
Tell us about your equipment, data and priorities to review a path from connection to operations.