# AI in Manufacturing Podcast — Show Notes
## Episode: Scaling Industrial Intelligence with the I3X Common API
**Podcast Name:** AI in Manufacturing Podcast (Industry40.tv)
**Episode Title:** Scaling Industrial Intelligence with the I3X Common API
**Guest Name:** Matthew Parris
**Guest Title/Role:** Director of Quality Test Systems, GE Appliances; Leading Contributor to the I3X Specification
**Host:** Kudzai Manditereza
---
## 1. Episode Summary
This episode explores how the Industrial Information Interoperability Exchange (I3X) common API is poised to become the universal interface for accessing manufacturing data across software platforms. Matthew Paris, Director of Quality Test Systems at GE Appliances and a leading contributor to the I3X specification, explains why the manufacturing industry has lacked a standardized way to retrieve information from Level 3 and Level 4 software systems — and how I3X solves this by leveraging simple, proven IT technologies: HTTP and JSON. Paris draws a compelling analogy between I3X and the early web browser revolution, comparing the I3X Explorer tool to Netscape's role in breaking down walled-garden internet portals. The conversation covers how I3X differs from OPC UA and MQTT, why a vanilla MQTT broker is insufficient for a true Unified Namespace, and how standardized interfaces accelerate AI deployment in manufacturing. Listeners will gain a clear understanding of where I3X fits in modern industrial architectures and why now is the time to get involved with the specification while it's in beta.
---
## 2. Key Questions Answered in This Episode
- What is I3X and what problem does it solve for manufacturers?
- How is I3X different from OPC UA and MQTT?
- Why is an MQTT broker alone not sufficient for a Unified Namespace (UNS)?
- How does I3X enable manufacturers to scale from data visibility to operational AI?
- Where does I3X fit in a modern industrial architecture alongside UNS and MQTT brokers?
- Why does I3X support OPC UA Part 5 information models, and how should manufacturers think about data typing?
- How will I3X achieve vendor adoption without a chicken-and-egg problem?
