iLEAN Connect · PLC connectors

Connect an industrial blancher to AI — plug & play iLEAN Connect connector

A short blanch shows up weeks later, in the frozen product. Connected, the blancher leaves a written record of what each batch received and when.

Two signals matter on a blancher and they always travel together: the temperature of the medium and the product's real dwell time. The second is rarely what the recipe says, because it depends on belt speed at that moment and on how the load arrives. Along with them come temperature recovery after each product entry — the indicator that exposes an oversized load or a tired heat exchanger — the state of the downstream cooling, and stoppages with product inside, which are the worst kind.

On the panel the manager sees each batch as a stretch with its own time and temperature, not as one undifferentiated shift. The classic pattern shows up immediately: the morning's first batches run below reference while the equipment settles, and at production peaks the belt speeds up and dwell time shortens without anyone deciding it. The iLEAN agent flags it as it happens, with the batch identified.

Connection usually goes through the machine's own control where it has one, or through our own probes in the bath and at the outfeed alongside a reading of the belt drive. Which applies to your equipment is what the technical visit is for; you do not need to know beforehand.

With that settled, two decisions stop being blind: match the feed rate to the blanch you actually intend to apply, and have the per-batch record on hand when you need to explain, weeks later, why one pallet came out different from the rest.

Your machine connects, whether or not you know what is inside it

If it has no PLC

Plenty of machines in production predate the network. They connect all the same: an industrial camera watches the panel and reads what it shows, or the paper logs filled in by hand are captured by photo. Without touching the machine and without affecting its warranty.

If the PLC is embedded and you don't know which one

That is the norm. The builder fitted it under the housing and the documentation never says. You do not need to know: we identify it during the technical visit and the scope follows from there. You do not have to research anything before writing to us.

If you do know the PLC

Even better: there is probably already a standard connector for that family. Check the PLC connector catalog.

How it works

  1. Define the scope. Tell us what you want to see from your machine in the form. The form itself is the scope document: no separate paperwork.
  2. Quoted in 24 hours. You receive the quote within 24 business hours. If your connector is standard, direct activation — from €79/month per machine.
  3. Running in under 7 days. From your approval of the quote, the integration is running in under 7 days. You pay once you confirm it does what you expected.

What you get with the connector

  • A panel of your machine, always visible, with history and charts.
  • The iLEAN central memory continuously fed with signals, states, counters, alarms and variables.
  • An AI agent analyzing the data and flagging deviations.
  • A daily email summary of what happened on your line.
  • Optional push to your ERP.

The connector is the doorway to the rest of the system: when you need it, the same machine scales to iLEAN Edge (inline machine vision, millisecond loop) and iLEAN Agents (full-cycle agents on the central memory).

How the guarantee works

Every iLEAN Connect integration is contracted the same way, and the terms are right here in the open:

  1. You define the scope of the connection you want: which signals, states, counters, alarms and variables to read from your PLC or machine.
  2. iLEAN quotes it within 24 business hours.
  3. If you approve, iLEAN builds it in under 7 days. The clock starts at your approval of the quote.
  4. iLEAN presents the integration to you, running.
  5. You confirm it does what you expected — the criterion is written into the scope document itself.
  6. Only then do you pay. Integrations 100% at reversed risk.

Need the AI to also act on the line? Define it in the scope and we quote it in 24 hours all the same; the build time is agreed in the scope document.

This guarantee covers the standard data connector: reading signals, states, counters, alarms and variables, delivery to the iLEAN central memory, a panel with history and charts, an agent analyzing, a daily email summary and optional push to your ERP.

The price, in the open

Standard catalog connector

From €79/month per machine. Your machine always online in the central memory, a panel with history, an agent analyzing and a daily email summary.

Custom integration

Its price is the 24-hour quote. The build is quoted once; afterwards, your machine joins the same fee — from €79/month.

Several machines with the same PLC? Volume pricing is negotiated case by case — ten identical connectors do not cost ten fees.

Why iLEAN can promise this

25+ years integrating AI with plant automation. Every driver, every protocol, every quirk of every PLC family is solved because it was already solved in a real plant: at Tier-1 manufacturers across automotive, aerospace, food, pharma and chemicals, and at the industrial SMEs that supply them.

AI is one more sensor — one that sees. Your PLC receives iLEAN's signal the way it receives any sensor's.

Frequently asked questions

Do we have to touch the PLC program?

No. The connector reads non-intrusively: AI is one more sensor, and your control logic stays exactly as it is. Writing to the PLC only exists if you expressly request it in the scope document.

What if the integration doesn't do what we expected?

You don't pay for it. The scope document defines in writing what «does what you expected» means, and payment comes after you confirm it, watching the integration run.

What network requirements does it need?

An outbound path from the plant network to the iLEAN central memory, with no inbound access opened. The concrete architecture — zones, rings, who talks to whom — is detailed in the scope document.

What if my machine has no PLC?

It connects too: through a camera on the panel or a photo of the paper log, the same iLEAN Connect paths used by plants with pre-network machinery.

Does the per-batch record work as process evidence?

The connector guarantees the record is taken automatically, with time and batch, and that nobody transcribes it by hand. What evidence your control plan requires, and how it is interpreted, is your quality team's remit — iLEAN supplies the data and its history, not the judgement.

Can we be alerted in the moment if a batch runs outside reference?

Yes: the agent's alert arrives while the batch is still on the line, not in tomorrow's report. You set the reference thresholds per product and they are written into the scope document.

Define your scope — quoted in 24 hours

This form is the scope document: from what you write here, iLEAN prepares your quote. You have it within 24 business hours.