Production monitoring system
that shows you the truth.

Real-time factory analytics software that counts every unit, identifies every bottleneck, and shows you exactly where your throughput is bleeding — without sending production data to the cloud.

99 %
counting accuracy
measured in production, Chile
2 years
in continuous production
on cameras that already existed
0
new cameras
uses the ones already there
100 %
processed on site
the cloud is optional

The problem

Production targets are a guess.
Actual output is a mystery until Friday.

End-of-shift counting

Units are tallied manually at shift change. The count is always wrong. Nobody knows if the line was running efficiently or barely crawling until the weekly report arrives.

No bottleneck visibility

Machine C is the bottleneck, but production keeps pushing material into it. WIP piles up, downstream machines starve, and throughput flatlines. Nobody sees the constraint in real time.

Spreadsheet analytics

Production data lives in 14 different Excel files across 3 departments. By the time anyone merges them, the insights are 2 weeks old and the problem has already evolved.

The solution

Factory analytics software
that runs at the edge.

Live production dashboards

Every machine, every line, every shift visible in real time. Current output rate, target comparison, and throughput trends — all streaming from edge devices directly to any screen on the network.

Automated bottleneck detection

iGromi OS continuously analyzes throughput and buffer levels across all connected machines. When a constraint shifts, the dashboard highlights it. No manual analysis needed.

Under 5 ms latency analytics

Production counts, scrap rates, and efficiency metrics are computed at the edge. No data is sent to the cloud — meaning sub-second updates and zero risk of exposing proprietary output data.

Integrated with iGromi OS

Real-time unit counting
Bottleneck detection and constraint analysis
Shift, day and week reports generated on their own
No cloud dependency: all processing happens at the edge
Live dashboards from any device on the local network
Output and scrap rate trended over time
API integration with the ERP or MES you already run
Installed on existing machines, without touching the PLC
Every line’s output, seen live
  1. 1 · What your plant already has

    • Line PLC
    • Existing cameras for counting
    • Orders and shifts
  2. 2 · The iGromi node on site

    • Counts by vision or by signal
    • Logs stops and speed
    • Keeps the history on site
  3. 3 · What your team gets

    • Output per line on screen
    • Progress against the shift target
    • Data for your MES or ERP

See exactly what your factory
produces every second.

In 30 minutes we'll show you how iGromi OS gives you real-time production visibility — live dashboards, bottleneck detection, and zero cloud exposure.

Book a diagnostic

How is this rolled out in a plant that is already running?

The same five questions come up in every meeting, whichever solution is on the table. The answers depend on how the system works, not on the module.

Do I have to replace my PLC or my SCADA?

No. The system connects to what is already installed and reads from it; it does not replace the control layer and does not write to it unless that is explicitly defined. If the PLC does not expose its parameters, the iGromi Bridge discovers them by trying combinations until it gets a response, and if the machine speaks no protocol at all it is read by a sensor on the electrical signal.

Does it work if the internet goes down?

Yes. Processing happens at the Edge, inside the plant, so capture, rules and inference keep running with the link down. What stops is remote access and outbound synchronisation, which resumes on its own when the connection returns.

Does my data leave the plant?

Not by default. Video and telemetry are processed on the customer's Edge device. What leaves, and where it goes, is defined when the system is configured. That is the same property that underpins compliance with Chile's Ley 21.719 and what makes this viable in mining and in food.

How long until the first data point?

It depends on how many machines there are and what they expose. A line with equipment that speaks Modbus is read in days; a line of silent machines needs sensors installed and panel shutdowns coordinated, and that is set by the plant's maintenance calendar, not by us. The usual sequence is assessment, pilot, expansion.

What happens to what we already measure by hand?

It runs alongside during commissioning. For the first weeks the manual record keeps going in parallel as a validation counterpart: it is how you find out whether the automatic figure beats the handwritten one, and the habit is dropped on its own once that is demonstrated.

Related solutions

See all solutions