Walk onto most manufacturing or industrial facility floors today and you'll find two separate technology worlds operating a few hundred feet from each other. One is the IT environment — cloud platforms, ERP systems, modern switches, centrally managed and monitored. The other is the OT environment — PLCs, HMIs, sensors, and controllers, some of them older than the engineers maintaining them, running on a network that was designed a decade ago for a much smaller job than the one it's doing now.
For years, that separation was considered normal, even safe. OT ran the machines. IT ran the business. They didn't need to talk to each other, so the fact that they couldn't wasn't a problem.
That assumption doesn't hold anymore. Industry 4.0 initiatives — predictive maintenance, real-time OEE dashboards, digital twins, plant-to-enterprise data flow — all depend on OT and IT talking to each other constantly and reliably. Platforms like Inductive Automation's Ignition were built specifically to make that conversation possible. But software can only move data as well as the network underneath it allows. And in a lot of facilities, that network is the part nobody has budgeted to fix.
What IT/OT Convergence Actually Means
IT/OT convergence is the practice of unifying information technology — the systems that manage data, business applications, and enterprise decision-making — with operational technology, the hardware and software that monitor and control physical processes on the plant floor: PLCs, HMIs, SCADA systems, robotics, and sensors.
Historically these domains ran in silos for good reason. IT teams optimized for data security, scalability, and long-term architecture. OT teams optimized for uptime, safety, and real-time reliability — priorities that don't always play well with an IT department's patch schedule or a security team's segmentation policy. The result was two separate technology stacks, managed by two separate teams, speaking two separate sets of protocols, that rarely needed to exchange more than a status light.
Industry 4.0 broke that arrangement. Once a business wants machine-level data feeding predictive maintenance models, feeding ERP systems, feeding executive dashboards in real time, IT and OT stop being separate problems. They become one integration challenge — and it's a harder one than most organizations expect, because the two sides were never built to cooperate.
IT systems typically speak HTTP, REST APIs, and SQL. OT systems speak Modbus, OPC UA, PROFIBUS, and DNP3 — often on hardware and firmware that's been running unchanged for 15–20 years. Bridging those two worlds isn't a settings change. It requires a platform designed from the ground up to translate between them, and a network capable of carrying that traffic without adding its own failure points.
Where Ignition Fits — and Why It's Become the Platform of Choice
Inductive Automation built Ignition as a SCADA platform first, but it has grown into something broader: a universal industrial application platform that unifies SCADA, IIoT, and MES functionality on a single codebase, with the connectivity to reach from a PLC on the plant floor all the way to a cloud dashboard or ERP system.
A few design choices explain why Ignition specifically has become a common answer to the OT/IT convergence problem:
Open, standards-based architecture. Ignition connects natively to OT-side protocols like OPC UA and Modbus, and to IT-side systems through SQL database connections and REST APIs — without requiring custom middleware for every integration.
Unlimited licensing. Ignition licenses by server rather than by tag, client, or connection count, which removes the cost penalty that historically made SCADA platforms expensive to scale across a growing number of sensors, screens, or sites.
Web-based deployment. Ignition's clients run in a browser rather than requiring dedicated installed software on every workstation, which makes it far easier to extend visibility to teams outside the control room — plant managers, quality teams, corporate reporting — without a separate licensing and deployment project for each one.
Scalable from a single line to an enterprise. The same platform that runs one production line can be architected to run dozens of sites feeding a central historian, which is exactly the shape most Industry 4.0 rollouts eventually need to take.
None of this is controversial in the automation world — Ignition is used across manufacturing, automotive, water/wastewater, and food processing precisely because it was designed to solve the translation problem between OT and IT. But there's a layer underneath all of this that determines whether any of it actually works the way it's supposed to: the network the data has to travel across.
The Part of the ROI Equation Nobody Budgets For
An IT/OT convergence platform is, at its core, a data-movement problem. Sensor readings, machine states, and quality data have to travel from the plant floor to a historian, then often to a cloud dashboard or ERP system, continuously and in near real time. That journey happens entirely over the network — switches, wireless access points, firewalls, WAN links, and whatever segmentation (or lack of it) sits between the OT and IT sides of the building.
When that network is a patchwork — a few generations of switches from different vendors, wireless access points installed at different times for different reasons, a firewall that was configured once and never revisited, no redundant WAN path if the primary connection drops — the platform sitting on top of it inherits every one of those weaknesses. Dashboards lag. Alarms fire late or not at all. Historian data has gaps that undermine the predictive maintenance model it's supposed to feed. None of that is a software problem. It's an infrastructure problem wearing a software symptom.
This is where the real cost of legacy infrastructure shows up — and it's larger than most facilities have modeled.
Siemens' 2024 True Cost of Downtime report, based on research conducted with Sapio Research across the world's 500 largest companies, found that unplanned downtime now costs those companies an estimated $1.4 trillion annually — roughly 11% of their total annual revenue. That's up sharply from $864 billion (8% of revenue) when Siemens ran the same study in 2019–2020. In automotive manufacturing specifically, an idle production line can cost a major plant up to $2.3 million per hour. Source: Siemens, "The True Cost of an Hour's Downtime: An Industry Analysis," 2024.
That figure has grown, not shrunk, even as most manufacturers report fewer downtime incidents per month than five years ago. The implication is straightforward: the incidents that do still happen are getting more expensive, more often tied to systems and infrastructure that were never designed for the volume and criticality of data now running across them.
Legacy network architecture carries a disproportionate share of that risk. It typically lacks the redundancy, automated failover, and real-time observability that modern network platforms treat as baseline features. When something fails on a legacy network, three things tend to happen at once: the blast radius is larger, because tightly coupled, unsegmented infrastructure takes more systems down with it; detection is slower, because there's limited monitoring to flag the problem before it cascades; and recovery takes longer, because fixing it depends on someone manually tracing the fault across equipment from three or four different vendors, none of whom manage the whole picture.
Why This Is an ROI Problem, Not Just an IT Problem
It's tempting to file network reliability under "IT's job" and keep the Industry 4.0 conversation focused on software and analytics. But the ROI math doesn't separate that cleanly.
Every Industry 4.0 business case — predictive maintenance reducing unplanned downtime, real-time OEE improving throughput, digital twins shortening changeover time — assumes the data behind it is timely, complete, and trustworthy. A network that drops packets, introduces latency, or goes down without warning doesn't just cause an outage. It quietly degrades the accuracy of every model and dashboard built on top of it, long before anyone notices an actual failure. The ROI erodes before the incident report ever gets written.
There's a security dimension too. As OT devices get connected to IT networks to feed platforms like Ignition, the attack surface grows with them. A flat, unsegmented network — where a compromised office laptop can reach a PLC with no VLAN boundary in between — turns a routine IT security incident into a potential production-floor event. Segmentation, monitoring, and consistent security policy across OT and IT aren't optional add-ons to a convergence strategy; they're the foundation it has to sit on.
What a Network Actually Needs to Look Like to Support This
None of this requires reinventing how manufacturing networks work. It requires treating the network as infrastructure that has to be as intentionally designed, monitored, and maintained as the automation platform running on top of it. In practice, that means a few consistent things:
Unified management across every site. A single dashboard that shows the health of every switch, access point, and firewall — not four different vendor portals that each show one slice of the picture.
Built-in segmentation and security. VLAN separation between OT and IT traffic, firewall policy, and DNS-level security as part of the base platform, not a separate project bolted on afterward.
Redundant connectivity. A primary WAN path with automatic cellular or secondary ISP failover, so a single point of failure doesn't take the historian, the dashboards, or the alarms offline with it.
Consistent hardware lifecycle. One vendor accountable for the full stack — switching, wireless, security — instead of a mix of equipment from different eras and different manufacturers, each requiring its own support contract and its own troubleshooting expertise when something breaks.
Scalability that matches the rollout plan. If the Industry 4.0 roadmap includes rolling Ignition out from one pilot line to twenty production lines across five plants, the network underneath it needs to scale the same way — without a separate network redesign project at every stage.
This is the category of solution that full-stack enterprise networking platforms — Meter is one example — were built to address: hardware, software, security, and connectivity delivered and managed as a single system rather than assembled piecemeal from whichever vendor won each individual RFP. The specific platform matters less than the principle. A convergence strategy built on a fragmented network foundation is optimizing the wrong layer first.
The Real Sequencing Problem
Most organizations approach Industry 4.0 in the wrong order. The instinct is to select the SCADA/IIoT platform first — evaluate Ignition against alternatives, pick modules, plan the historian architecture — and treat the network as a line item to sort out during implementation. That ordering usually means the network gets whatever budget and attention is left over, which in practice is not much.
The more durable approach reverses that sequence, at least in part. Before finalizing an OT/IT convergence rollout, it's worth auditing the network it will run on: how old is the switching infrastructure, is there any segmentation between OT and IT traffic today, what happens if the primary WAN connection drops, and who is actually accountable when something on the network breaks at 2 a.m. on a production night. The answers to those questions usually reveal whether the ROI case for the software layer is realistic — or whether it's built on an assumption the infrastructure can't support yet.
Frequently Asked Questions
What is IT/OT convergence?
IT/OT convergence is the integration of information technology systems — ERP, cloud platforms, analytics, databases — with operational technology systems on the plant floor, including PLCs, SCADA, HMIs, sensors, and controllers. The goal is a continuous flow of data between the two so decisions can be made using a complete, real-time picture of both the business and the physical operation.
How does Ignition help with IT/OT convergence?
Ignition is built on an open architecture that connects natively to OT protocols like OPC UA and Modbus, and to IT systems through SQL databases and REST APIs. It unifies SCADA, IIoT, and MES capability in a single platform, letting plant-floor data reach business systems — and business context reach the plant floor — without custom point-to-point integration for every connection.
How much does network downtime actually cost manufacturers?
Per Siemens' 2024 True Cost of Downtime report, the world's 500 largest companies lose an estimated $1.4 trillion a year to unplanned downtime — about 11% of their annual revenue, up from 8% in 2019–2020. Automotive plants face some of the highest per-hour exposure, with idle production lines costing up to $2.3 million per hour in major facilities.
Why does the network matter as much as the software platform?
Any OT/IT convergence platform depends entirely on the network to move data in real time between machines, historians, and business systems. A fragmented, multi-vendor, unmonitored network introduces latency, data gaps, and security exposure that limit what the software can deliver — regardless of how capable that software is on its own.
Carrier Hub is a vendor-neutral technology advisor. We don't sell automation software or manufacturing equipment — our role is helping organizations evaluate whether their underlying network can actually support the Industry 4.0 initiatives they're planning to build on top of it.