i3X and the Past, Present & Future of Industrial Interoperability

If you’ve spent time working with industrial data, you know collecting it is probably not your greatest challenge. Rather, it’s making that data usable at the right time in the right place, no matter the consuming system or user. That’s the problem I keep coming back to, and it’s the problem Industrial Information Interoperability eXchange (i3X) is built to solve. CESMII, the United States’ non-profit institute dedicated to Smart Manufacturing, has introduced a standards-based API that is already reshaping how our industry talks about data integration. And it’s getting a lot of attention. 

What is i3X?

i3X is an open, vendor-neutral API standard designed to simplify how software applications access contextualized manufacturing data. Using modern APIs, i3X enables clients to browse, read, write, and subscribe to industrial data, including the rich context required to make it useful for analytics and AI.

Assembled by CESMII, the i3X working group was established in 2024, bringing together a collaborative cross-section of manufacturers, technology providers, system integrators, and industry leaders. The group spent over a year working in stealth before publicly introducing the vendor-agnostic API in early 2026. Now, the innovators in our industry are well underway testing and proving its practicality.  

With my colleague Aron Semle in the i3X working group, I’ve had a front-row seat to its conception, development, and adoption. This post aims to explain the problem that i3X solves, how it is impacting industry today, and what the future might hold.

Yesterday: Widespread Data Fragmentation

Industrial connectivity standards have largely focused on telemetry and process control. For the broader set of interactions that applications require (i.e., browsing, transactional reads and writes, and historical queries), the landscape is fragmented. Where standards exist, adoption has been inconsistent, and in practice, every vendor implements a “standard” differently. Each integration requires custom work, and that burden multiplies as the number of applications grows.  

Consider the typical facility. Many of the manufacturers we work with have deployed historians, MES solutions, SCADA systems, quality systems, and maintenance tools sourced from different vendors, each exposing its own proprietary API with its own structure, authentication, and data quality. An application that needs data from more than one of these systems must be built to “speak” each system’s language. Moreover, no two factories are alike. Even plants producing identical products often run different technology stacks, so an integration that works in one site rarely transfers cleanly to the next. The result is a sprawl of expensive, ad hoc data flows with little interoperability and almost no repeatability.

This fragmentation carries a real cost. It slows the deployment of analytics, automation, and AI initiatives because every new use case starts with the same custom integration work before any value can be delivered. 

The i3X working group set out to address these challenges by defining an open, app-centric API that addresses all these interaction patterns with consistency. The work-in-progress was showcased at the 2026 ProveIt! and Hannover Messe conferences, where the public beta was released, kicking off a wave of interest and testing across the industry. 

Today: An Open API Launches

In June 2026, CESMII officially launched version 1.0 of the i3X specification. The efforts of the working group—comprised of contributors from AWS, Microsoft, Siemens, Rockwell Automation, Inductive Automation, GE Appliances, and HighByte—helped bring this specification to life. Now, with growing participation from leading industrial software vendors, system integrators, and end users, i3X is ready to be deployed and adopted by any industrial enterprise looking to transform data integration across their company. Put simply, i3X is defining a common way for applications to access industrial data. 

At HighByte, our product roadmap reflects this opportunity. In HighByte Intelligence Hub version 4.4, released in March 2026, we introduced an early implementation of the i3X Server interface, making the Intelligence Hub one of the first products to ship with i3X support. The i3X Server exposes the Intelligence Hub namespace, including both the internal HighByte namespace and user-defined models, to any i3X-compatible client. With the i3X Server in the Intelligence Hub, clients can discover models, browse, subscribe, write, and read real-time and historical data through a standard interface. In doing so, the i3X Server reflects the Intelligence Hub's API-centric approach to Industrial DataOps, extending the software’s portfolio of standard server interfaces that includes the REST Data Server and MCP Server.  

In HighByte Intelligence Hub version 4.5, released in August 2026, we added an i3X Client alongside the existing production-ready i3X Server, giving organizations a means to both publish and consume contextualized industrial data over this API standard.

Tomorrow: Discoverable, IT-Friendly Industrial Data

If i3X is successful, what could the future look like? 

The factory floor today is data-rich but context-poor. Pushing that problem downstream to the cloud, where teams have less domain knowledge and visibility into the source systems, is not a viable option. But we also can’t package everything up at the edge and guess what our colleagues will want when working in cloud-native enterprise systems. 

Instead, with i3X, tomorrow’s factory becomes a rich set of information that you can discover. No more guessing. The movement of data becomes more intentional because we access data we need, not data we think we might need. 

i3X makes industrial data look more like IT data: schema-aware, browsable, and discoverable. And the more our industrial data looks like IT data, the easier it is for IT systems (and our IT colleagues) to put it to work. The first release of i3X is a major step forward in closing the gap between OT and IT, a conversation that began more than 15 years ago. 

Putting i3X Into Practice

Industrial interoperability has been a moving target since automation was introduced in the third industrial revolution. i3X takes a new approach to this growing problem, delivering a single, open, web-native API that lets any compliant application work with contextualized industrial data without needing to know what sits beneath it.

HighByte is among the first to put that standard into practice. The Intelligence Hub's i3X Server exposes modeled, contextualized data through the same interface any i3X-compatible client can consume, while its embedded i3X Client can also consume data from third-party i3X servers. i3X won't replace OPC UA, MQTT, or your existing Unified Namespace (UNS) investments, but it will wrap around existing protocols and standards to lower the barrier between OT and IT one step at a time. 

To see this progress in action, we hope you’ll join us at the Inductive Community Conference 2026, held this week in Sacramento. The annual conference is hosted by Inductive Automation, a fellow member of the i3X working group.

My colleagues Aron Semle and Jeffrey Schroeder will lead a Solution Showcase on September 23, demonstrating a real-world use case leveraging the Intelligence Hub’s i3X Server and Ignition. They will explain how to move beyond siloed OT systems and build a scalable data architecture that supports enterprise applications, analytics, and agentic AI. Attendees will learn the role that i3X plays in molding the future of industrial architectures and how to put the capabilities of tomorrow’s factory into action today.