{"id":19240,"date":"2026-02-24T16:32:13","date_gmt":"2026-02-24T15:32:13","guid":{"rendered":"https:\/\/i-flow.io\/?post_type=ressources&p=19240"},"modified":"2026-03-09T22:05:34","modified_gmt":"2026-03-09T21:05:34","slug":"i3x-by-cesmii-the-api-for-smart-manufacturing-explained","status":"publish","type":"ressources","link":"https:\/\/i-flow.io\/en\/ressources\/i3x-by-cesmii-the-api-for-smart-manufacturing-explained\/","title":{"rendered":"i3X by CESMII: The API for Smart Manufacturing Explained"},"content":{"rendered":"

An analytics system needs to query production data from OSIsoft PI, Ignition Historian, and Siemens MindSphere simultaneously \u2013 but each platform speaks a different API language. The Unified Namespace (UNS)<\/a> handles horizontal integration exceptionally well: real-time events flow via MQTT or NATS between OT and IT systems. However, the UNS lacks a standardized interface for structured, query-based data access from the IT side (pull access). i3X by CESMII aims to close exactly this gap \u2013 as an open API specification that exposes heterogeneous manufacturing platforms through a unified query interface.<\/p>\n

 <\/p>\n

Why i3X? The n\u00d7m Integration Problem<\/strong><\/h2>\n

The API landscape in modern manufacturing environments is fragmented. OSIsoft PI uses the PI Web API, Ignition Historian exposes its own RESTful API, Siemens MindSphere relies on proprietary endpoints. As a result, integration effort scales quadratically with each new platform or IT application added: five platforms \u00d7 five IT systems means 25 custom integrations to build and maintain.
\nThe UNS with MQTT and NATS solves horizontal IT\/OT integration well: events flow in real time across the UNS via pub\/sub. What’s missing is a standardized query interface for IT systems that need to retrieve historical production data in a structured way. For this pull access, every IT system today must be developed against the native API of the respective platform \u2013 whether that’s a UNS or an IT platform.<\/p>\n

 <\/p>\n

What is i3X by CESMII?<\/strong><\/h2>\n

i3X by CESMII \u2013 short for “Common Contextual Manufacturing Information API” \u2013 is an open API specification for standardized data access across heterogeneous manufacturing platforms. Platform vendors are intended to implement i3X so that IT systems can subsequently access all compatible systems through a single, unified interface. i3X is developed by CESMII (Clean Energy Smart Manufacturing Innovation Institute), a US-based institute focused on smart manufacturing.<\/p>\n\n\n\n\n\n\n\n
What i3X is<\/th>\nWhat i3X is NOT<\/th>\n<\/tr>\n<\/thead>\n
API Specification (RFC):<\/strong> i3X defines which endpoints, query patterns, and data structures manufacturing platforms should expose \u2013 eliminating the need for custom adapters per data source.<\/td>\nNot a transport protocol:<\/strong> MQTT, OPC UA, and NATS move data between systems. i3X defines how applications query that data \u2013 it does not replace transport protocols.<\/td>\n<\/tr>\n
Contextualized data:<\/strong> i3X operates on already-processed data with ISA-95 context (e.g., from the Unified Namespace), not on raw shopfloor data.<\/td>\nNot a message broker:<\/strong> NATS or MQTT brokers mediate pub\/sub messages within the Unified Namespace (UNS). i3X operates one layer above \u2013 on the data access layer sitting on top of those brokers.<\/td>\n<\/tr>\n
Application layer focus:<\/strong> Designed for IT systems (analytics, BI tools, ML pipelines) querying historical data \u2013 not for OT real-time control.<\/td>\nNot a replacement for the Unified Namespace:<\/strong> The Unified Namespace is a publish\/subscribe architecture with message brokers at its core. i3X can be used within a UNS as an API gateway layer, but does not define ISA-95 context itself.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Development Status (as of 2026)<\/strong><\/h3>\n

The specification is currently in pre-alpha. It is a Request for Comments (RFC), not a production-ready implementation. A demo instance is available on GitHub<\/a>.<\/p>\n

 <\/p>\n

Where does i3X standardize? \u2013 Positioning in the Data Access Model<\/strong><\/h3>\n

To understand where i3X intervenes, the Data Access Model by Matthew Parris provides a useful frame: it divides IT\/OT interoperability into six layered levels \u2013 from L0 (transport: e.g., TCP\/IP) to L5 (objects: semantic data models). True plug-and-play interoperability requires consistency across all levels. For a full overview, see: IT\/OT Interoperability in the UNS \u2013 Fundamentals<\/a>.<\/p>\n

\"i3X<\/p>\n

i3X by CESMII builds on existing transport standards and aims to standardize the upper layers consistently \u2013 precisely where heterogeneous IT platforms diverge today. As a result, IT systems can query OSIsoft PI, Ignition, or any other i3X-compatible platform using identical queries \u2013 without platform-specific adapter development.<\/p>\n

 <\/p>\n

Target Audiences for i3X<\/strong><\/h3>\n

Two groups benefit directly:<\/p>\n