Blog / Connectivity
Connectivity · Guide

IIoT Gateway: What It Does and When You Need One

OL By OEE Lab Editorial |Updated 2 November 2026 |6 min read
Short answer

An IIoT gateway is a small industrial computer that reads machine protocols, stamps and buffers the data, and sends it to your software over one outbound link. You need one when machines use mixed protocols, sit on separate networks, or must not lose data in a network drop, and you may not if your software can already reach clean data directly.

The problem it solves

Machines and business software speak different languages. A press may offer Modbus RTU, a newer line OPC UA or a vendor PLC protocol, and an old machine only a 24 V contact.

Your OEE or MES software wants one clean stream with times attached. The gateway sits between the two, so neither side needs to change.

PLCModbus24 V sensorGatewaytranslate, stamp, bufferoutbound onlyOEE or MES software
Many inputs, one output. The machines keep their own networks, and in this setup nothing outside connects in.

What a gateway does, job by job

1. Translates protocols

On the machine side it may speak Modbus RTU and TCP, OPC UA, EtherNet/IP, Siemens S7 or plain digital inputs. Which ones depends on the product, so check that your exact PLC is on its driver list.

On the software side it often uses MQTT or HTTPS. MQTT is a light publish and subscribe protocol, in which a gateway sends messages to a broker and other systems pick them up from there.

2. Stamps the time

Each change gets a time at or near the source. That means a stop stays at its true time even if the data arrives later, as long as the gateway clock is kept in sync.

3. Buffers during a network drop

If the link fails, a store-and-forward gateway saves data and sends it when the link returns. Without that, a network problem becomes a gap in your downtime records.

4. Filters and reduces

The gateway can poll quickly and send only what changed. It can also turn raw values into events, such as a stop and its duration, with the logic in machine state detection.

5. Separates networks

Many gateways have two network ports, one for the machine side and one for the plant or internet side. Set up that way, machines stay on their own network, and the gateway can make only outbound connections, with no open inbound port.

That helps with security, but it is not a whole security plan. Your IT team still needs to set rules, manage passwords and certificates, and apply updates.

How much data a gateway saves

Sending only changes makes a large difference on a thin link. Here is a sample machine with one state signal and one count.

Example: sending one reading a second makes 86,400 messages a day. Sending only 300 state changes plus one count summary a minute makes 1,740.

Every reading, once a second86,400 a day
Changes plus a count each minute1,740 a day
A hypothetical machine: 300 state changes + 1,440 count summaries = 1,740 messages a day, about 2% of the raw stream.

Keep fast raw readings at the edge for a while, though. If the state logic turns out to be wrong, you may want to re-run it.

Do you need one? A quick test

Your situationGateway?Why
Mixed protocols across machinesLikely yesOne device handles all the translation
Machines on an isolated networkLikely yesIt bridges two networks without joining them
Serial or digital-only machinesLikely yesSomething has to read and forward these signals
Software in the cloud, with a weak linkLikely yesBuffering protects your records
PLC with OPC UA, software on the same networkMaybe notYour software may read it directly, if IT allows
Sensor kit with its own wireless baseAlready includedThe base station acts as the gateway
Tablet-only data entryNoNo machine signals to translate
Rules of thumb, not fixed rules. Your network and software decide the final answer.

Do not buy a separate gateway for a problem you do not have. Plenty of monitoring kits include one, and direct connection is simpler when the network allows it.

Gateway, edge device, PLC: what is the difference?

The names overlap, and vendors use them loosely. A gateway mainly moves and translates data, while an edge device also runs heavier processing, such as analytics or vision.

A PLC runs control logic and needs far more care before you change it. Keep gateway work away from control programs, so that a data project cannot affect the machine.

In the ISA-95 model, a gateway links the machine levels to the level where MES sits. It does not replace an MES, and what is MES explains what that layer does.

What to check before you buy

  • Drivers: does it list your exact controllers and protocols, including old ones?
  • Inputs: how many digital, analog and serial inputs does it have, and are they suited to your sensors?
  • Buffer: how long can it store data, and does it resend in order?
  • Time: can it sync with a network time server, and how does it behave if it cannot?
  • Security: does it get updates, support encrypted links and allow read-only connections?
  • Environment: does it have a DIN rail mount, a 24 V supply and a temperature rating for your cabinet?
  • Fitting: mounting and wiring in a cabinet is work for a qualified electrician, with the panel made safe.
  • Remote care: can you update and monitor it without a site visit, under your IT rules?

Sizing the buffer

You can estimate this on paper. Take your data rate, multiply by the longest outage you must survive, and leave room to spare.

6 signals x 100 bytes x 1 per second = 600 bytes/s
600 x 86,400 s = 51.84 MB a day
3 days offline = about 156 MB
Hypothetical gateway with raw readings stored. Sending only changes needs far less.

Many gateways can store more than that, so storage is often not the limit. What matters more is whether the unit resends cleanly, and whether its storage survives a power cut.

Where gateway projects go wrong

  • Allowing writes by default. Set the machine side to read-only unless you have a clear reason and a formal change process.
  • Ignoring clock sync. Machines with clocks that disagree produce stops that appear to end before they start.
  • Using one gateway as a single point of failure. A gateway that serves 30 machines takes all 30 records with it if it dies. Keep a spare and a saved configuration.
  • Skipping IT. A device that links machines to the internet is IT's business. Involve them early, and the project usually goes faster.

Make the list first

List your machines, their protocols and where each one sits on the network. If the list has one protocol and one network, you may not need a gateway at all.

For machines with no protocol, begin with how to connect old machines. For a Modbus device, test one read before you buy anything.

See it live in Fabrico

When plant data leaves the site, where it lands often matters. Fabrico is a light MES for OEE, EU-built with EU data residency and ISO 27001 certified, that takes stops, speed and counts live from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal. See how Fabrico gets machine data.

What people ask next

What is the difference between an IIoT gateway and a router?

A router moves network traffic between networks without understanding the content. A gateway reads machine protocols, converts the data and can store it. Some industrial units do both jobs.

Does an IIoT gateway need the internet?

No. It can send data to software on your own plant network. An internet link matters only if your software or remote support is outside the plant, and then outbound-only connections are common.

Can a gateway control my machines?

Technically, it could write to a controller if it is set up to, so set it to read-only for monitoring. Control belongs in the PLC, under your change process. Monitoring should not affect how the machine runs.

Do I need one gateway per machine?

Not usually. One gateway can serve several machines if they are close and its inputs and network allow it. Machines far apart, or on separate networks, may each need their own, so walk the floor before you count.

Is MQTT better than OPC UA?

They do different jobs. OPC UA models machine data well and is common at the controller level, while MQTT is a light way to move messages to many systems. Many setups read OPC UA on the machine side and publish over MQTT, so ask what your software accepts.

See OEE per line and shift on your own machines

Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.

Book a Fabrico demo

Related guides: Shop Floor Data Collection: Methods Compared · MES vs HMI: Two Screens, Two Different Jobs

← More OEE Lab guides · How to connect old machines →

OEE essentials: OEE calculator · What is OEE · Six big losses · Availability · TEEP · Cost of downtime · OEE benchmark · Free OEE tracker · Free OEE software · How to track downtime · How to implement OEE · Light MES vs full MES