The Convergence Crisis: When IT and OT Finally Collide

For most of my career, keeping IT and OT separate wasn't a problem to solve — it was the right answer. That's no longer true.

I’ve worked in the industry for over two decades, and for most of that time, the separation of IT and OT made practical sense. IT managed the enterprise layer, running the business from the inside. OT managed the physical world, keeping it running on the outside. The two served different functions, answered to different teams, and operated on different timelines. Keeping them apart was simply the architecture that worked.

But now, AI and automation have changed that equation. Both have moved from roadmap items to active operational priorities across high-tech manufacturing and telecom. And both depend on something a lot of organizations have still not structured for: real-time data flowing freely between the enterprise and the operational layer. Without that connectivity, AI initiatives run on incomplete information. Automation investments land on a foundation that cannot fully support them. Supply chain visibility, which every company says it wants and very few have fully achieved, remains out of reach. The question now is how to close that gap, and what it could cost if it’s not addressed.

What the Disconnect Actually Costs

Working with clients at Argano, I’ve found that when enterprise systems and operational systems are not communicating, the first thing you lose is visibility. You end up managing two separate sets of data that rarely tell the same story, and someone has to reconcile them. That usually means a dedicated team spending real time and resources pulling information from multiple sources, just to get a clear picture of what is actually happening in the business.

From there, maintenance becomes more expensive because you are running two independent environments. Response times slow down because acting on information requires assembling it first. These are the predictable, ongoing costs of a disconnected architecture, and they compound.

In telecom specifically, these costs are much more noticeable. Telecom providers occupy a distinct position because their OT systems are directly customer-facing in a way that most manufacturing environments are not. A disruption on the shop floor is largely an internal challenge, though we know it can affect customer fulfillment rates.  However, an outage, a drop in service consistency, and slower response times are all things customers feel in real time. The urgency around convergence in this industry is not theoretical or just potentially damaging. It is tied directly to day-to-day service reliability.

Why It Feels Like a Collision

I use the word "collision" deliberately. When you bring IT and OT together, you are not merging two systems that share common priorities. Instead, you are bringing together two cultures with genuinely different definitions of what matters most.  Most convergence projects don't fail because of the technology. They fail because you're asking two cultures with fundamentally different definitions of success to share the same infrastructure.

On the OT side, uptime is everything. Those systems have to stay on and stay stable, and change is something to be minimized, not managed. The IT side operates with almost the opposite posture. Agility, analytics, continuous improvement through enhancements and cloud upgrades: IT teams are built to handle change, and they expect it. When those two mindsets meet on the same project, it can create friction. What the IT team treats as a routine upgrade cycle can feel like a destabilizing event to a team whose primary job is keeping production running without interruption.

Where It Goes Wrong

You might expect technology to be the most common failure point. But in most of the cases I’ve seen, the most common fail point actually boils down to governance.

There is a natural tendency to frame IT/OT convergence as an IT issue, and when that happens, the business processes that support those systems tend to get left out of the conversation. The technology can be built correctly and still produce poor outcomes, because the people operating within it are working outside of what the system was designed to support or they are dealing with bad data.

When a team falls back on workarounds from the old environment, or carries forward a process that was never formally updated, those are not technology failures. They are business process failures, and they keep occurring when organizations treat convergence as an IT initiative rather than a business-wide (or operating) priority.

Operational standards and data practices across both environments need to stay aligned with what you have built. The reality is that accountability for that alignment cannot live in IT alone.

Who Owns It — and Why That Question Is Harder Than It Looks

Cross-functional ownership is the key to success, but it only works when business leadership takes genuine accountability instead of a sponsorship role. Active participation in ensuring operational processes and data align with the technology footprint. That means establishing data standards early, mapping operational risk across both environments, aligning on end to end processes, and treating change management as a structural part of the plan rather than something added at the end.

I recently worked with a client where their senior leadership was embedded at every pillar of the implementation. Every major decision area had the right business owner actively engaged, from design through go-live.  In addition to key decisions, they owned the conflicts, process changes, user adoption.  And they understood that while transformation brings challenges, their role was to control the panic and ensure collaboration, progress, and ownership every step of the way.   The result was one of the most successful projects I have seen in my career — not because the technology was exceptional (which it was), but because the people behind the workstreams were exceptional and owned it completely.

The First Move

For any CIO, COO or VP of Operations who knows this conversation is overdue, start by pulling a governance team together that includes both IT and operations leadership. Get aligned on your highest operational risks. Where is data disconnected? Where is production continuity most vulnerable? Where have workarounds quietly become the norm? From that shared baseline, find the first impactful challenge worth solving and move on it.

Getting a win early matters more than it might seem. In my experience, it is often what turns a complex, enterprise-wide initiative into something the whole organization is proud to figure out together.

 

Connect with an Argano Expert!

Need specialized insights for your business challenges? Facing complex business technology questions? Don't navigate alone. Connect with an Argano subject matter expert who will personally respond within 24 hours.