Machine downtime tracking
that pays for itself in days.

Every minute of unplanned downtime costs you money. iGromi OS tracks availability, performance, and quality in real time — OEE monitoring software that runs on your plant's edge.

99 %
counting accuracy
measured in production, Chile
0
changes to the PLC
read-only, no reprogramming
0
new cameras
uses the ones already there
100 %
processed on site
the cloud is optional

The problem

You don't know how much
your machines actually produce.

Hidden micro-stops

Machines stop for a few seconds, many times per shift, and nobody writes it down. At month end the reported availability looks high and the real one is well below it. Each micro-stop steals output.

Manual downtime logging

Operators write downtime reasons on paper. Shift supervisors type them into Excel. By the time anyone sees the report, it's Tuesday and the problem started Friday.

No root cause tracking

Machine B went down 12 times this week. Was it electrical? Mechanical? Operator error? Nobody knows because each event is a different spreadsheet row with no categorization.

The solution

Real-time OEE monitoring
at the edge, not the cloud.

Automatic state detection

iGromi OS reads PLC signals, current sensors, and vibration data to determine whether each machine is running, idle, or down — without operator input. Accuracy above 99%.

OEE calculated continuously

Availability × Performance × Quality computed every minute. Dashboards update in real time. Historical trends reveal degradation patterns weeks before failure.

Works without internet

The edge device buffers all events locally. Dashboards, alerts, and reports stay available even during network outages. Data syncs when connectivity returns.

Integrated with iGromi OS

Captures every micro-stop, including the ones nobody logs
OEE calculated in real time
Root cause classified on each stop event
No cloud subscription: it runs on the customer's hardware
Live dashboards from any device on the network
Pareto charts of the causes that cost the most time
Exports to PDF, CSV or the MES already installed
Installed without modifying the PLC program
Every stop, with its cause and duration
  1. 1 · What your plant already has

    • Run and stop signal from the PLC
    • Cameras that show what happened
    • Shifts and product
  2. 2 · The iGromi node on site

    • Detects every stop to the second
    • Asks the operator for the cause on the spot
    • Separates micro-stops from long stops
  3. 3 · What your team gets

    • Time lost per cause and machine
    • Actual availability, not the estimate
    • Shift report without sheets

Stop guessing your OEE.
Start measuring it.

In 30 minutes we'll show you how iGromi OS tracks every second of downtime on your machines — no PLC changes, no cloud fees.

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