Skip to content
Ingkle

On-premises server software

Manufacturing data and AI.On your own servers.

Collect vast volumes of factory data with NAZARE. Turn it into analysis and action with NAVIS. Start manufacturing AI with two software platforms installed on your premises.

Explore deployment
NAZARE trend analysis showing repeated analog and digital signals, the NAVIS application, software packages and on-premises servers
Installed on your servers · Data stays in-house

NAZARE

Data infrastructure for manufacturing AI, built on data and know-how.

Collect, store and query equipment, business-system and document data. Structure operating knowledge with ontology for analytics and AI, and send approved control commands to equipment PLCs.

  • Connect & collect
  • Store & query
  • Operating knowledge
  • AI & control integration
Explore the product

NAVIS

Understand the situation. Turn approved responses into action.

An Agentic AI platform that answers using live machine data, operating records and knowledge. NAVIS presents a response and its evidence, then requests execution from NAZARE through MCP after manager approval.

  • Understand
  • Reason & propose
  • Manager approval
  • Request & verify
Explore the product

Connect equipment and apply manufacturing AI. Start both together.

Start with a specific need, such as identifying defect causes or detecting equipment anomalies. Build collection, storage and query capabilities for the required equipment, production and quality data while applying and validating AI. Reuse the data infrastructure across more machines and factories.

NAZARE

Connect the data AI needs

  • Collect PLC and sensor signals from selected equipment
  • Connect and store MES, ERP and QMS records
  • Make expert criteria readable by AI
Build and validate together

NAVIS

Apply AI to the connected data

  • Analyze causes using live signals and history
  • Propose actions using operating criteria
  • Execute after approval and verify results
Start using AI on the equipment connected first

Use AI before every machine is connected. Validate analysis and responses on the first connected equipment, then expand.

Explore the details you need

NAZARE

01

Different names. Shared meaning.

Manage shared terms and relationships so different tag names do not force you to restart each analysis. AAS and MDR organize the meaning of equipment assets and their data.

↗
02

Find the cycle that behaves differently.

Define each production cycle and compare its signals with a reference run. Find changed segments in repetitive production to prioritize quality checks and equipment inspection.

↗
03

Find the evidence behind “What changed?”

Compare pressure, temperature, current and other signals around an event. Inspect a short interval in detail or aggregate a longer period to narrow down possible causes.

↗
04

Different machines. One place for their data.

Connect PLC and CNC signals with records from existing production and quality systems. Choose the fields, verify incoming values, and reuse the same data for monitoring and analysis.

↗
05

See how collection and storage are running.

Manage connected sources, storage capacity and processing status together. Use common screens and policies as the number of machines and operating tasks grows.

↗
06

Give every reading its manufacturing context.

A pressure reading is useful when you know which machine and measurement point it belongs to. Link plants, equipment, products and signals so people can understand them and AI can reference them.

↗
07

Know the condition of the data you rely on.

Distinguish missing, late and out-of-range values. Manage original records alongside processing criteria to improve confidence in data used by engineers and AI.

↗
08

Make recurring data preparation repeatable.

Clean values by condition and create calculated signals. Prepare equipment readings and existing system records for their intended use, reducing repetitive work before analysis.

↗
09

Turn stops and replacement records into improvements.

Record why a machine stopped, not just how long. Review recurring downtime reasons and parts replacement history to identify opportunities to reduce production losses.

↗
10

Keep factory data on site. Control who can use it.

Operate on premises when factory data cannot leave the site. Assign equipment and functions by responsibility and separate data access from control permissions.

↗
11

More machines. More history. Find the moment that matters.

High-resolution signals from hundreds of machines quickly become a large history. NAZARE keeps that data on site and queries the equipment, time windows and fields needed for live use and long-term analysis.

↗
12

Feed live, precise signals into anomaly detection.

Process-specific ML needs precise data at the moment of inference. NAZARE prepares historical training data and live signals; NAVIS combines results with site knowledge to explain findings and plan responses.

↗
13

Turn expert know-how into data AI can use.

What is abnormal, what should be checked first, and what action is appropriate? Ingkle specialists capture this knowledge through interviews and tools, linking equipment, parts, signals, criteria and actions. This is manufacturing ontology.

↗
14

See which machine needs attention now.

Move from plant-wide operating states to individual machine signals. See running, waiting, stopped and alarm conditions together to reduce time spent checking machines in person.

↗
15

Turn expert know-how into data AI can use.

What is abnormal, what should be checked first, and what action is appropriate? Ingkle specialists capture this knowledge through interviews and tools, linking equipment, parts, signals, criteria and actions. This is NAZARE ontology.

↗

Explore the details you need

NAVIS

Explore the details you need

System integration and site operations

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.

Talk to Ingkle