Industrial IoT (IIoT)
Industrial IoT Gateways in Indiana: The Small Box That Decides Whether Your Data Arrives
Published by IOT Indiana Research & Editorial Team

- What an Industrial Gateway Actually Does
- Speaking the Plant's Languages: Protocols
- Where to Put Gateways: Three Architectures
- Store-and-Forward: The Feature That Saves You in an Outage
- Security: Design It In Before the First Machine Is Connected
- Rural Locations and Connectivity Backup
- Hardware That Survives a Factory
- Managing Gateways at Scale
- Purpose-Built Gateway or Industrial PC With Software?
- An Example: A Mixed-Vintage Plant
- A Pilot Checklist
- Common Mistakes
- Funding and Local Help
- Where Industrial Gateways Are Heading
In most industrial IoT projects, the sensors get the attention and the software gets the budget, but a small, unglamorous box in the middle decides whether the data actually arrives. That box is the gateway. It sits between machines that speak one language and systems that expect another, and it has to keep working through network outages, power blips, and the occasional forklift. Indiana plants often have an especially hard version of this job: equipment of many ages, controllers from several manufacturers, and rural locations where internet service is not always dependable. This guide explains what a gateway does, how to choose one, and how to deploy it without creating a security problem.
What an Industrial Gateway Actually Does
A gateway performs four jobs, and a good purchase decision weighs all four.
- Translate. Machines and sensors use many protocols. The gateway reads them and converts the data to a common format that other systems understand.
- Process at the edge. Rather than shipping every raw reading upstream, a gateway can filter, average, detect events, and compute simple values locally, which reduces network load and speeds up response.
- Buffer. When the connection to the cloud or server drops, the gateway stores data and forwards it once the link returns, so there are no holes in your history.
- Secure. It acts as a controlled boundary between the factory floor network and everything else, managing who can talk to what.
A cheap converter that handles only the first job may be fine in a lab. In a plant, the third and fourth jobs are what protect you when things go wrong.
Speaking the Plant's Languages: Protocols
| Protocol | Where You Meet It | Notes |
|---|---|---|
| Modbus (RTU and TCP) | Older controllers, meters, drives, many sensors | Simple and widespread; limited structure and security |
| OPC UA | Newer controllers and modern software | Open standard with data models and built-in security options |
| EtherNet/IP | Many North American controllers and devices | Common on plant floors; gateway must support the specific device |
| PROFINET | Equipment from European manufacturers | Often found on imported machinery and robots |
| MQTT (including Sparkplug) | Publishing data to servers and cloud platforms | Lightweight; good fit for plant-to-enterprise data flow |
| Serial (RS-232, RS-485) | Very old equipment, instruments, scales | Needs physical adapters and careful configuration |
The practical rule: inventory the protocols your machines actually use before shopping. Walk the floor, note each controller model, and check what interfaces it exposes. A gateway with an impressive list of protocols is useless if it does not support the specific device on your oldest press. Open standards such as OPC UA and MQTT Sparkplug help reduce future headaches, which is why they are worth favoring on the output side.
Where to Put Gateways: Three Architectures
| Placement | Advantages | Trade-offs |
|---|---|---|
| One per machine | Simple, isolated, easy to troubleshoot; failure affects one machine | More devices to manage and pay for |
| One per cell or line | Balanced cost and complexity; shared configuration | Failure affects several machines; cable runs longer |
| One per plant or area | Lowest hardware cost; central management | Single point of failure; heavy load; long connections to machines |
Most mid-size plants choose the middle option, with a gateway per line or cell, and add a second unit where a machine is critical or physically remote. The right choice depends on how much downtime a gateway failure would cause in your data collection, not in production, because a well-designed gateway sits alongside machines rather than controlling them.
Store-and-Forward: The Feature That Saves You in an Outage
Networks fail. A cut fiber, a router restart, a storm, or an upstream provider outage can interrupt the connection for minutes or days. Without local buffering, that period vanishes from your records, and any analysis that depends on continuous history is damaged. Ask specifically how much data the gateway can hold, how long that lasts at your data rates, how it behaves when storage fills, and whether it sends buffered data in order when the connection recovers. For plants with unreliable internet, this feature matters as much as any protocol.
Security: Design It In Before the First Machine Is Connected
Connecting equipment that was never designed for networks creates risk. Good gateway practice reduces it considerably:
- Separate networks. Place gateways and machine data on a segment separate from office computers and guest wireless. This limits how far a problem can spread.
- Outbound-only connections. Prefer gateways that initiate connections outward to a server rather than waiting for inbound connections, so you do not have to open holes in the firewall.
- Change default credentials. Factory default passwords on industrial devices are widely known. Change them, and use unique credentials per device.
- Encryption and certificates. Use encrypted communication where the protocols support it, and manage certificates so they do not silently expire.
- Update plan. Ask how firmware updates are delivered, how often, and how quickly the vendor addresses vulnerabilities. Decide who in your plant will apply them.
- Remote access controls. If vendors need remote access for support, use a controlled, logged method rather than a permanent open connection.
- Read-only where possible. If the goal is monitoring, configure the gateway to read from machines, not write to them. That prevents an accidental or malicious change to a running process.
Larger customers increasingly ask suppliers how connected equipment is protected. A documented, segmented gateway design gives you a confident answer.
Rural Locations and Connectivity Backup
Not every Indiana plant, pumping station, or agricultural processing site has dependable broadband. Look for gateways that support cellular connections as a primary or backup path, with the ability to fail over automatically when the wired link drops. Check data plan costs, coverage at the site, and how much data the gateway sends. Edge processing pays off here: sending a summary and event alerts instead of every raw reading can keep cellular costs manageable and make the system usable on slower links.
Hardware That Survives a Factory
- Mounting and power. DIN rail mounting and wide-range direct current power inputs are common in industrial panels. Confirm the gateway fits your cabinets and power supply.
- Temperature range. Panels in unheated buildings or near hot equipment can go far beyond office conditions. Check rated limits at both ends.
- Vibration and shock. Machines shake. Look for ratings suitable for the location, and mount securely.
- Dust and moisture. Fanless designs and sealed enclosures help in dirty or humid areas.
- Power quality. Brownouts and surges are common. Consider surge protection and a small uninterruptible supply for critical gateways, so they shut down cleanly and preserve buffered data.
Managing Gateways at Scale
One gateway is easy. Twenty are a management task. Look for central tools that let you deploy configuration templates, push updates, monitor health, and see which units are offline. Without this, every change means a visit to each cabinet. Also plan documentation: which gateway connects to which machines, its address, credentials storage, firmware version, and location. A spreadsheet is a fine start. Plants that skip this end up with mystery boxes that nobody dares to touch.
Purpose-Built Gateway or Industrial PC With Software?
You can buy a purpose-built gateway with software preloaded, or install gateway software on an industrial computer. Purpose-built units are simpler to deploy and support and are usually better for plants without IT depth. An industrial PC offers flexibility to run several applications and to customize, but it demands more care with operating system updates and security. Choose based on who will maintain it in year three, not just who can set it up in month one.
An Example: A Mixed-Vintage Plant
Consider an illustrative plant with three kinds of equipment: a newer machining center with a modern controller, a mid-age press with an older controller that speaks Modbus, and an old furnace with only an analog temperature output. One gateway per production line reads the machining center through OPC UA, the press through Modbus, and the furnace through a small analog input module. All three are published to a plant server using MQTT. The gateway buffers data during a weekly network maintenance window, sits on its own network segment, and reads without writing. Total effort is a matter of weeks, and the plant now has consistent data from three very different machines, without replacing a single controller.
A Pilot Checklist
- Have you listed every controller model and protocol the gateway must read?
- Does the gateway support each one, confirmed on your actual equipment?
- How much data can it buffer, and how does it recover after an outage?
- Is the network segmented, with credentials changed and outbound-only connections?
- Are temperature, vibration, and power ratings suitable for the cabinet location?
- Who will apply updates, and how will you know a unit is offline?
- Can you export your data and configuration without vendor permission?
Common Mistakes
Choosing by protocol list alone. Confirm support on your exact devices.
Ignoring buffering. The first long outage will otherwise leave gaps in your data.
Leaving default passwords. This is one of the most common and avoidable weaknesses.
Putting everything on one flat network. Segmentation is cheap early and hard to add later.
Skipping documentation. Undocumented gateways become a maintenance burden and a security risk.
Funding and Local Help
Gateways and connectivity equipment are part of the industrial IoT investments that Indiana's Manufacturing Readiness Grants have supported when funded, though availability depends on state budget cycles, so check the Conexus Indiana grants page for current status. Purdue's Manufacturing Extension Partnership offers consulting and training that can help a plant plan its architecture before buying hardware.
Where Industrial Gateways Are Heading
Gateways are gaining more computing power, letting plants run analysis and even simple machine learning directly on site, which reduces dependence on the cloud and shortens response times. Standards such as OPC UA and MQTT Sparkplug are making connections more uniform, and management tools are improving for plants with many devices. Security expectations are also rising, with customers and insurers asking for evidence of good practices. The plants that do best will treat the gateway not as an afterthought, but as a piece of infrastructure to be planned, secured, documented, and maintained like any other critical system.
Frequently asked questions
Related articles
Industrial IoT (IIoT)
Industrial IoT (IIoT)
Predictive Maintenance Becomes More Important Across Indiana Factories
Industrial IoT (IIoT)
Cummins and the Connected Factory: What Industrial IoT Means for Indiana Manufacturing
Industrial IoT (IIoT)
