Part 3 of 5 in our Edge to Enterprise series. We gave the plant a vocabulary (ISA-95) and put intelligence at the edge (CATIM Edge IPC). Now: how do applications reach the data without a new integration every time?
If you look at the evolution of industrial data over the last decade, we have successfully navigated two major levels of chaos.
First was Communications Chaos. We had hundreds of proprietary protocols speaking different languages, which we solved with abstraction layers and standard drivers.
Next came Namespace Chaos. We had massive lakes of raw data with no context. We are currently solving this by adopting Unified Namespaces (UNS) and structured semantic models to organise our facts.
But today, Solution Architects are crashing into the third wall: API Chaos.
We have organised the data, but every time we want to connect a new application—whether for OEE analytics, predictive maintenance, or advanced scheduling—we have to write custom integration code to interface with that specific vendor’s backend. Every vendor has a different API, a different authentication method, and a different way of handling historical versus live data.
Enter i3X (Industrial Information Interoperability eXchange). Published by CESMII, the US Smart Manufacturing Institute, with version 1.0 released in June 2026, i3X is an app-centric API standard designed to stop the agonising proliferation of custom interfaces.
Decoding the i3X launch: breaking the industrial software model
The rollout of the i3X standard at the ProveIt! 2026 Conference represents a fundamental shift in how we architect OT systems. As highlighted in the primary 4.0 Solutions YouTube presentation, “This Breaks the Entire Industrial Software Model”, the industry is moving beyond just “connecting” devices. We are standardising how applications consume that data.
The presentation identifies four core imperatives required to achieve this shift:
- Smart Manufacturing Profiles: Organising data in a Unified Namespace (UNS) is not enough if it lacks strict governance. Without explicit rules defining data types, applications are forced to run defensive code. Profiles provide universal rules and context for data before it is put into motion.
- Capturing Knowledge Relationships: Beyond just structural hierarchies, systems must map the explicit relationships and contextual knowledge that experienced operators hold.
- Solving “API Chaos”: Even with a UNS, developers currently write custom integration code for every vendor’s API. i3X introduces a common interface allowing applications to use standard verbs (Explore, Query, Update, Subscribe) to interface seamlessly with any compliant backend.
- Live vs. Historical Integration: A true i3X-compliant system must handle both live streams (via MQTT) and “at-rest” historical data (via a Historian) through a single, transparent API.
(For further context, see additional community breakdowns such as What is I3X? and I3X Explained and i3x.dev).
The CTO perspective: stop paying for “glue code”
From the executive level, API chaos is a massive, hidden tax on innovation. When your engineering team is tasked with deploying a new intelligent application across a diverse set of facilities, they spend most of their time just getting the systems to talk to each other.
Without a standard such as i3X, every new application introduces:
- Vendor Lock-in: Apps are hardcoded to specific platforms. If you want to change your underlying historian or broker, you break the app.
- Accumulating Technical Debt: Custom “glue code” requires constant babysitting and updates.
- Wasted Engineering Cycles: You are paying brilliant engineers to reinvent the wheel instead of writing the business logic and algorithms that actually generate ROI.
i3X solves this by providing a universal contract. The CTO gets faster time-to-value, zero vendor lock-in at the application layer, and the ability to scale solutions rapidly.
The architect’s perspective: focus on your IP secret sauce
For the Solution Architectural Design Engineer, i3X is the light at the end of the tunnel. It is not a new protocol attempting to replace MQTT or OPC UA; rather, it is a standard API wrapper that sits on top of your existing data sources.
By utilising Smart Manufacturing Profiles, i3X ensures that data is type-safe before it ever reaches your application. You no longer have to code defensively against unpredictable data payloads. You can trust the schema, query the endpoint, and focus your engineering effort entirely on your own IP and secret sauce.
Building the foundation: how CATIM Edge supports the i3X vision
Deploying an i3X-compliant architecture requires a robust physical foundation capable of standardising data at the source. As we explored in our breakdown of why CATIM Edge IPC is the Ultimate OT Intelligence, true interoperability requires industrial-grade compute at the edge. (CATIM Edge has since grown into CATIM Nimbus - see Sense, Decide, Act.)
When executing diverse work across varied industrial environments, the CATIM Edge Gateway eliminates the need for sprawling, project-specific hardware. It provides the required components to support i3X natively:
- Fulfilling the Live and Historical Mandate: The CATIM Edge Gateway uses a container-based architecture. An MQTT broker on the gateway handles the live data streams necessary for the i3X “Subscribe” functions, while a local time-series historian serves the i3X “Query” historical functions.
- Enforcing Profiles at the Source: Rather than sending raw, untyped data to the cloud, the edge computing power contextualises the data locally. When an enterprise app explores the i3X endpoint, the payload is already verified, type-safe, and mapped to the correct standardised node sets.
- Abstracting Complexity: The IPC ingests chaotic, proprietary protocols from the shop floor, unifies them within its container environment, and presents a clean, i3X-compliant API upward.
Evolving beyond the Purdue model
The implementation of i3X is the final nail in the coffin for rigid, sequential data architectures. In 4 Surprising Truths About ISA-95, we discussed how the traditional Purdue model can sometimes bottleneck modern manufacturing.
i3X flattens this landscape entirely. Instead of passing data sequentially through Levels 1 through 4, i3X allows a Level 4 ERP or a cloud-based AI tool to directly query the contextualised facts sitting at the edge. The ISA-95 standard still provides the crucial vocabulary for how we model our equipment, but i3X completely changes how we access that information.
The question this raised most often - isn't i3X just MQTT with extra steps? - is the subject of the next post.
The Edge to Enterprise series
- 4 Surprising Truths About ISA-95 - the vocabulary every system shares
- CATIM Edge IPC: the ultimate OT intelligence - why intelligence belongs at the edge
- The End of API Chaos - one API for every application (you are here)
- i3X vs MQTT: One Moves Bytes, the Other Moves Meaning - moving bytes versus moving meaning
- Sense, Decide, Act: The Controller Is the Platform - the platform we built on these ideas
Previous: CATIM Edge IPC: the ultimate OT intelligence · Next: i3X vs MQTT: One Moves Bytes, the Other Moves Meaning
About CATIM. CATIM - Creating Automation Technology In Motion - empowers people to engineer automation solutions that solve hard technical problems. Working on a data or AI project? Get in touch.