i3X: The Factory API Built for Modern Manufacturing

Manufacturers have spent years wrestling with fragmented, proprietary APIs and siloed operational data. This fragmentation slows innovation, complicates analytics, and raises the cost of digital transformation and modernization efforts. It also prevents factories from fully taking advantage of the data they already have, since it’s spread across disparate stacks. 

To address this, CESMII - the Smart Manufacturing Institute tasked a working group of industry leaders with developing a new strongly typed, discoverable, and IT-friendly open standard for industrial data access. The result is the Industrial Information Interoperability eXchange (i3X) standard, an open specification for browsing, reading, writing, and subscribing to industrial data via a consistent, vendor-agnostic, web-native interface. The ultimate goal of i3X is to standardize how existing enterprise systems interact with plants in a more predictable way, not to replace standards like OPC UA, MQTT, or prior unified namespace (UNS) investments. 

I’ve been privileged to be part of the i3X working group and have seen firsthand how a common API layer can reduce bespoke integrations without forcing a wholesale architectural rework. The goal is simple: lower the barrier between OT and IT applications for manufacturers. i3X is the right standard to meet this goal at the right time, and it will simplify how IT systems access and make use of industrial data.

Why Industrial Data Access is Still Broken

Today's manufacturers are trapped by the status quo, using dozens of incompatible APIs and protocols across various PLCs, SCADA systems, IIoT devices, and MES platforms. These APIs vary widely in structure, authentication, capabilities, and data quality, forcing the creation of customized integrations that result in expensive, brittle data pipelines with little interoperability or repeatability. What’s worse, every factory is different, and even those that produce the same products may have different OT technology stacks.

Centralizing and contextualizing industrial data using existing UNS strategies solves part of the problem by making data available in a standardized format that’s independent of the system it came from. Even so, manufacturers still face a host of other IT system challenges, including:

• API/REST-based systems that don’t natively support MQTT.

• The need to make specific requests like “What’s the current temperature of the boiler?” or execute transactions like “Turn on the CNC machine.”

• The need for contextualized data that is discoverable and conforms to a standard schema.

Many vendors today have their own APIs for doing the above, but they are fragmented and not interoperable. Our challenge is to create a standard API that makes this data available to IT systems so they can discover and interact with it consistently, ultimately providing a standard that the entire industry can build toward.

What i3X Solves, and Why It Matters Now

The core value of i3X is that it’s a simple, open standard for browsing, reading, writing, and subscribing to industrial data across vendors. It’s essentially an API for UNS or for the factory, taking a modern, web-friendly approach that helps reduce integration complexity and eliminate lock-in to proprietary interfaces. Built-in contextual semantics help ensure that data is not just connected across systems, but understandable and actionable. 

This creates several advantages for developers, including: 

• Build once, run anywhere functionality across machines, sites, and vendors.

• Consistent, predictable interfaces for ease of use.

• Strongly typed information and dependable relationships between systems.

• Faster deployment of analytics, automation, and AI applications.

It also creates key advantages for the business, such as:

• Lower integration costs.

• Reduced dependency on external vendors.

• Greater portability of solutions across facilities and platforms.

The most significant advantage lies with data architects. If i3X succeeds, it provides a standard IT/OT layer that these architects can build towards. If their factory supports i3X as its API layer, the architect will be able to leverage any number of i3X IT clients with confidence that they will work as intended. 

i3X as the Foundation for Future Innovation

Much of the excitement and momentum around i3X stems from its potential as an enabling layer, rather than a disruptive replacement. By defining a common API for factories, i3X provides a target for aligning operational environments with the existing IT system structure. It’s not about introducing new data sources or ripping and replacing current standards; it’s about making existing resources easier to discover, analyze, and act upon safely using familiar request/response and subscription patterns.

There’s a useful parallel here to how shared APIs accelerated innovation in mobile app ecosystems. Once teams began operating with consistent interfaces, entire classes of applications became portable and reusable. i3X creates the conditions for a similar ecosystem across industrial technology, one where common data access, consistent semantics, and broader developer participation can support predictable development instead of custom engineering. And it can all be done without necessitating total plant overhaul.

Over time, this approach can shift where manufacturers and vendors differentiate. Without needing to compete on proprietary data access methods, they can instead focus on higher-value capabilities like analytics, optimization, operational intelligence, and AI/LLM deployment. i3X provides manufacturers with a practical means of future-proofing by incrementally standardizing IT-OT interaction without invalidating prior investments. If adopted thoughtfully, this consistency becomes the foundation on which more advanced capabilities such as AI models, predictive analytics, and autonomous workflows, all of which can be built with greater confidence and less friction.

A Path to Industrial Interoperability

Modern manufacturers can no longer afford to manage incompatible, brittle data interfaces. As our industry continues to push towards digital maturity, we will need open, contextual, and vendor-neutral data access to succeed. i3X offers a viable path towards this required interoperability, reducing integration difficulties and helping teams accelerate digital transformation across the board.