Why The Unified Namespace is The Essential Foundation for Industrial AI & Agentic Operations: Walker Reynolds - President, 4.0 Solutions

## Episode: The State of Industrial AI, Unified Namespace, and Knowledge Graphs After PROVE IT 2025   **Podcast Name:** AI in Manufacturing Podcast  **Guest:** Walker Reynolds, President & Solutions Architect at 4.0 Solutions, Founder of the PROVE IT Conference **Host:** Kudzai Manditereza **Target Audience:** Manufacturing data leaders, IT/OT solution architects, and digital transformation professionals   ---   ## Episode Summary   Walker Reynolds, President and Solutions Architect at 4.0 Solutions and founder of the PROVE IT conference, delivers an unfiltered assessment of where industrial AI actually stands in 2025. Drawing from conversations with over 1,000 attendees at this year's PROVE IT conference—70% of whom were end users working in manufacturing—Reynolds identifies three critical industry shifts: AI fatigue is setting in as vendors outpace market readiness, knowledge graphs have emerged as the essential technology for enabling agentic AI in manufacturing, and the gap between digitally mature and immature manufacturers is widening. The conversation covers why most manufacturers still aren't getting value from their unified namespace implementations, the five most practical AI applications seen at PROVE IT, and why autonomous agents are a mathematical impossibility given current LLM reliability. Reynolds closes with his complete recommended technology stack for manufacturers and a prediction that plant floors will see *more* people, not fewer—but they'll be analysts supervising AI agents rather than middle managers managing people.   ---   ## Key Questions Answered in This Episode   - What is the current state of AI adoption in manufacturing in 2025? - Why are some manufacturers failing to get value from unified namespace implementations? - What role do knowledge graphs play in enabling agentic AI for manufacturing? - What are the most practical AI applications for manufacturers right now? - Can AI agents run autonomously in manufacturing operations? - What does the ideal industrial data architecture stack look like for a small to midsize manufacturer? - How does unified namespace serve as the backbone for agentic AI?   ---   ## Episode Highlights with Timestamps   **[1:56]** — **Introduction and episode overview** — Kudzai sets the agenda: PROVE IT conference takeaways, unified namespace adoption status, agentic AI's role, and the ideal industrial data architecture.   **[4:23]** — **Walker Reynolds' background** — From salt mines to tier-one automotive to founding 4.0 Solutions, IoT University, and the PROVE IT conference—plus why he always introduces himself as if no one knows who he is.   **[8:36]** — **Three core observations from PROVE IT 2025** — AI fatigue is real, most end users still ask "where do I start?", and knowledge graphs emerged as the breakout technology everyone now understands they need.   **[20:37]** — **Top five practical AI applications from PROVE IT** — WinCC OA and Tatsoft for AI-assisted development, Atanta Analytics' prompt-to-insights, Thread Cloud's knowledge graph-driven root cause analysis, and Maestro Hub's live module generation with Claude Code.   **[29:08]** — **The knowledge gap in agentic AI adoption** — Reynolds draws an analogy to the leap from algebra to calculus, warning that not every organization has someone who can bridge the gap to agent-based architectures.   **[35:04]** — **Why autonomous agents are a myth** — Current LLMs are 99.9% reliable at best—one error per 1,000 words—compared to a PLC's nine nines of reliability. Agents must be human-supervised.   **[42:55]** — **Why manufacturers fail or succeed with unified namespace** — The differentiator is understanding UNS as the real-time current state of the business, not a historical transaction store.   **[52:09]** — **UNS as the backbone for agentic AI** — How agents use the semantic structure of UNS to navigate operations and then retrieve deeper context via MCP tools.   **[54:40]** — **Walker's complete recommended technology stack** — From Docker and Node-RED to HiveMQ, Litmus, Frameworks 10, Thread Cloud, and Snowflake—the full architecture laid out step by step.   **[59:45]** — **Where AVEVA PI fits** — No need to rip and replace; limit PI to what it's good at (historian), and leverage Aveva's more open Connect platform.   **[1:02:11]** — **Prediction: More people on the plant floor, not fewer** — Fewer middle managers, more analysts supervising AI agents to optimize operations.   ---   ## Key Takeaways   - **Knowledge graphs are the breakout technology of 2025:** Coming out of PROVE IT, even non-technical attendees understood that knowledge graphs—relational context between entities in an infrastructure—are essential for AI agents to navigate and reason through manufacturing systems. Manufacturers should prioritize building fluency in knowledge graph concepts now.   - **AI fatigue is real, and vendors are outpacing market readiness:** Most end users are still asking "where do I start?" while vendors are shipping agentic AI features without clear problem-solution fit. The maturity gap between the most and least digitally advanced manufacturers is widening.   - **Autonomous agents are not viable in manufacturing:** The most reliable LLMs achieve 99.9% accuracy—one error per 1,000 words—while PLCs operate at nine nines of reliability. Agents should be treated as force multipliers for human workers, not autonomous replacements.   - **Unified namespace success depends on understanding what it is—and isn't:** UNS is the real-time current state of the business, semantically organized. Manufacturers who fail with UNS are trying to make it something it's not, such as a historical transaction store. It serves as the originating context that agents use before querying deeper systems.   - **The most practical AI use cases are about building, not automating:** The top applications at PROVE IT involved using AI to accelerate development (natural language to code, dashboards, and workflows), not replacing human decision-making on the plant floor.   - **Predefined workflows inside agents are a game changer:** Rather than letting agents create their own reasoning steps on the fly, giving engineers the ability to predefine part of an agent's workflow dramatically improves reliability and practical value.   - **Start building AI fluency now, even if you haven't started your data journey:** Reynolds mandated his team use chatbots daily in January 2023—not because he knew how AI would be used, but to build fluency. Every manufacturer should be doing the same with knowledge graphs and agent concepts today.   ---   ## Notable Quotes   > "The only person who believes agents can run autonomously are people who don't work with agents." — Walker Reynolds, President at 4.0 Solutions   > "Think of agents as a force multiplier for your workforce, a way of unlocking the potential in people." — Walker Reynolds, President at 4.0 Solutions   > "If you're not getting value out of unified namespace, then you're using it for something that it isn't." — Walker Reynolds, President at 4.0 Solutions   > "We're going to see more people on the plant floor, not less. They're going to be analysts supervising AI to optimize operations." — Walker Reynolds, President at 4.0 Solutions   > "Your homework this year is learn knowledge graphs, because you're going to need them." — Walker Reynolds, President at 4.0 Solutions   ---   ## Key Concepts Explained   **Unified Namespace (UNS)** Definition: A unified namespace is a single, semantically organized source of truth that represents the real-time current state of a business—all events, data, and information models contextualized and normalized in one accessible structure. Why it matters: UNS serves as the foundational architecture for digital transformation and is the originating context layer that AI agents query to understand current operations before reasoning through deeper systems. Episode context: Reynolds emphasized that manufacturers failing with UNS misunderstand its purpose, treating it as a historical data store rather than a real-time state representation.   **Knowledge Graphs** Definition: Knowledge graphs are data structures that represent the relationships between entities (nodes) in a system, providing relational context that enables navigation and reasoning across an infrastructure. Why it matters: AI agents require knowledge graphs to navigate up and down a business's infrastructure, moving from an objective at one layer to the specific data location where answers reside. Episode context: Reynolds identified knowledge graphs as the breakout technology from PROVE IT 2025, with Thread Cloud's root cause analysis demo receiving mid-presentation applause for demonstrating practical agent-driven analysis via knowledge graphs.   **Model Context Protocol (MCP)** Definition: MCP is a protocol that allows AI agents to connect to external tools and data sources, enabling them to retrieve information and perform actions beyond what's contained in their training data. Why it matters: MCP enables agents to go beyond the initial context from UNS and query historical data, work orders, and other systems of record to

# AI in Manufacturing Podcast — Episode Show Notes   ## Episode Details - **Podcast Name:** AI in Manufacturing Podcast (Industry40.tv) - **Episode Title:** Unlocking Productivity With Casual Models and Agentic AI in Manufacturing - **Host:** Kudzai Manditereza - **Guest:** Michael Carroll - **Guest Title/Role:** Strategic Advisor & Fellow COO Council at LNS Research; Chief Strategy Officer at Trek AI - **Target Audience:** Manufacturing data leaders, COOs, VP of Operations, IT/OT solution architects, and digital transformation professionals   ---   ## 1. EPISODE SUMMARY   Agentic AI is not another digital tool to add to the manufacturing technology stack — it is a fundamentally different species of software that treats decisions, not transactions, as the atomic unit of work. In this episode, Michael Carroll, Strategic Advisor at LNS Research and Chief Strategy Officer at Trek AI, explains why US manufacturing productivity has been flat since 2010 despite massive investments in digital tools, and why agentic AI with causal reasoning represents the structural fix. Carroll draws on his 15 years leading digital transformation at Georgia Pacific to reveal how the real productivity killer is not a lack of data or technology, but a cognitive overload crisis combined with organizational permission bottlenecks that drain value from companies in real time. He introduces a practical diagnostic framework — mapping inferencing load and permission load — that any operations leader can apply today to identify where value is leaking from their organization and where agentic AI can deliver immediate impact.   ---   ## 2. KEY QUESTIONS ANSWERED IN THIS EPISODE   - Why has US manufacturing productivity been flat since 2010 despite massive digital investments? - What is agentic AI, and how is it fundamentally different from traditional manufacturing software like MES and ERP? - What is causal reasoning, and why does it matter more than explainable AI for manufacturing decisions? - How does the permission architecture in manufacturing organizations destroy value and slow decision velocity? - Where should COOs and VPs of Operations start when preparing their organizations for agentic AI? - Why do alignment meetings signal that a company's numbers can't be trusted? - How should IT and OT organizations restructure their relationship to enable competitive advantage?   ---   ## 3. EPISODE HIGHLIGHTS WITH TIMESTAMPS   **[00:02]** - **Introduction & Guest Background** — Kudzai introduces Michael Carroll and his roles at LNS Research and Trek AI, emphasizing his prolific writing on LinkedIn about industrial AI.   **[04:04]** - **Farm Roots and the Generalist Mindset** — Carroll shares how growing up on a farm in "Knock 'Em Stiff, Ohio" taught him orchestration and generalist thinking that shaped his approach to enterprise transformation.   **[07:43]** - **The Flat Productivity Crisis** — Discussion of US Bureau of Labor Statistics data showing manufacturing productivity has been flat or declining from 2008-2023, despite heavy digitalization investments.   **[09:39]** - **The COVID Productivity Paradox** — Carroll reveals how productivity actually spiked during COVID when corporate distractions were removed, disproving the hypothesis that talent attrition alone caused the decline.   **[13:41]** - **The Cognitive Tipping Point** — Frontline workers now see 8x more information across 50% more equipment than in 1975, but have 50% less experience — creating a cognitive overload that degrades performance.   **[16:56]** - **What Makes an Agent an Agent** — Carroll defines agentic AI through the lens of human agency: an agent shapes outcomes, bears your intention, but the responsibility remains yours.   **[22:46]** - **Judea Pearl's Causal Ladder** — Deep explanation of how Pearl's three-layer causal framework (imagining, doing, observing) provides the mathematical foundation for trustworthy AI decision-making.   **[24:49]** - **Chain of Reasoning vs. Explainability** — Carroll argues that "explainable AI" invites litigation, while causal chains of reasoning provide defensible, legitimate justification for decisions.   **[30:00]** - **The Adaptive Architecture** — Carroll outlines the three-layer future architecture: ubiquitous connectivity, causal reasoning at the edge, and a trust/permission architecture at the center.   **[36:39]** - **The Baum Study: Decision Speed and Performance** — Reference to J. Robert Baum's 2003 study of 318 companies showing decision speed — not decision quality — was the top predictor of company performance.   **[47:22]** - **Causality Replaces Data Models** — Carroll explains why causal models are superior to traditional data models and ontologies, comparing data collection to stock options you wouldn't exercise immediately.   **[53:30]** - **The Practical Starting Framework** — Carroll provides a step-by-step diagnostic: map your current architecture, identify where inferencing load and permission load are highest, and fix those intersection points first.   ---   ## 4. KEY TAKEAWAYS   - **Manufacturing's productivity crisis is a cognitive overload problem, not a data problem:** Since 2010, frontline workers see 8x more information across 50% more equipment than in 1975, but have 50% less experience. More insights have not produced better performance — they have consumed the adaptive capacity workers need to make good decisions.   - **Agentic AI treats decisions as the atomic unit of work, not transactions:** Unlike MES or ERP systems that automate transactions, agentic AI shapes outcomes by understanding what's true about the world, evaluating possible interventions, taking action, and learning from evidence. The responsibility always remains with the human.   - **Causal reasoning provides defensible decisions; explainability invites litigation:** A chain of reasoning built through Judea Pearl's causal framework delivers the legitimate, defensible justification that governance structures require. Explainable AI merely offers interpretations that different stakeholders will contest — which is why alignment meetings exist.   - **Decision speed outperforms decision quality as a predictor of company performance:** J. Robert Baum's 2003 study of 318 companies found that the highest-performing companies made decisions faster than competitors, centralized strategy while decentralizing operations, and only standardized things that were easy to standardize.   - **The value leak happens between decision and action:** The time between knowing what to do and getting permission to do it is where most companies lose tremendous value. Permission architectures built around compliance — not governance — create vicious cycles between operations and IT that stall decision velocity.   - **60% of value creation comes from staying focused:** Carroll's framework breaks down value creation: approximately 20% comes from doing the right things, 20% from doing those things right, and a full 60% from maintaining focus — which fragmented organizations systematically destroy.   - **Start by mapping inferencing load and permission load:** Operations leaders should map how their company gets things done, identify where inferencing load (people synthesizing multiple insights to make decisions) and permission load (organizational gates) are both high, and target those intersection points first.   ---   ## 5. NOTABLE QUOTES   > "We're not trying to be right. We're trying to get this right — because we're experiencing a time in humanity that's never been experienced before." — Michael Carroll, Strategic Advisor at LNS Research & CSO at Trek AI   > "No machine will ever feel the consequences of the actions it takes and the decisions it makes — so the responsibility is still yours." — Michael Carroll, Strategic Advisor at LNS Research & CSO at Trek AI   > "You know you have a company that can't trust its numbers when you have an alignment meeting — because alignment meetings mean the politics matter more than the numbers." — Michael Carroll, Strategic Advisor at LNS Research & CSO at Trek AI   > "Something that automates a work process is not an agent. Something that carries out a task is not an agent. Because it doesn't shape an outcome." — Michael Carroll, Strategic Advisor at LNS Research & CSO at Trek AI   > "Structure makes you effective. You've got to go be effective before you can ever be efficient." — Michael Carroll, Strategic Advisor at LNS Research & CSO at Trek AI   ---   ## 6. KEY CONCEPTS EXPLAINED   **Agentic AI (Enterprise Agency)** Definition: Agentic AI is a category of artificial intelligence that shapes outcomes by understanding the current state of the world, evaluating possible interventions, taking action, and learning from evidence — operating on behalf of humans while the responsibility remains with the human. Why it matters: It represents a structural shift from transaction-based software (MES, ERP) to decision-based systems that can collapse the time between insight and action in manufacturing operations. Episode context: Carroll distinguishes agentic AI from task automation by emphasizing that true agents bear your intention and shape outcomes, rather than simply executing predefined workflows.   **Causal Reasoning (Judea Pearl's Ladder of Causation)** Definition: A mathematical framework developed by Turing Prize winner Judea Pearl consisting of three layers —

Podcast Name: AI in Manufacturing Podcast (Industry40.tv) Episode Title: Context Engineering Techniques for Building Reliable Industrial AI Agents Guest: Zach Etier, VP of Architecture at Flow Software Host: Kudzai Manditereza Episode Summary This episode explores context engineering — the discipline of curating and managing the information supplied to AI agents — and why it is the key to building reliable industrial AI systems. Zach Etier, VP of Architecture at Flow Software, joins host Kudzai Manditereza to break down why simply pumping more data into an AI agent's context window actually degrades performance through dilution, hallucination, and lost instructions. Zach walks through three core context engineering techniques — persisting context, summarization/compaction, and isolation via sub-agents — and explains how each one maps to real manufacturing use cases like automated shift-handover reports. The conversation also covers the practical differences between skills, MCP servers, and sub-agents, and why deterministic code should handle calculations while agents handle orchestration. Finally, Zach makes the case that knowledge graphs with formal ontologies will become essential data architecture for scaling industrial AI across the enterprise. Whether you are evaluating your first agent pilot or planning multi-site deployment, this episode provides a concrete framework for engineering context that agents can reliably act on. Key Questions Answered in This Episode What is an industrial AI agent, and how does it differ from a chatbot or general-purpose LLM? Why does giving an AI agent more context actually reduce its performance? What is context engineering, and why is it replacing prompt engineering for agentic AI? What are the three core techniques for managing an AI agent's context window in manufacturing? How should you decide when to use skills vs. MCP servers vs. sub-agents? Why should deterministic code handle calculations instead of letting the AI agent compute them? How do knowledge graphs and ontologies enable enterprise-scale industrial AI? Episode Highlights with Timestamps [00:33] — Meet Zach Etier — Zach introduces his role at Flow Software, his background at Northrop Grumman, and how he leads development of the Atlas knowledge modeling tool. [06:04] — Defining an Industrial AI Agent — A clear breakdown: an agent is an LLM that can call tools in a loop, acting as an orchestrator that reasons on context to decide which tool to invoke next. [09:54] — Shift-Handover Report Demo — Zach describes a concrete use case where an agent passively generates a shift-change report by pulling data from a historian, operator notes, the UNS, and MES/PLC data. [12:58] — From Prompt Engineering to Context Engineering — Why reasoning models and tool-calling changed the game: prompts are static, but agent context is dynamic. [16:37] — The Softmax Dilution Problem — How adding too many tokens dilutes relevant information through the normalization process, causing hallucinations and missed instructions. [17:17] — Lost in the Middle — The Stanford "needle in a haystack" study showing agents recall content at the start and end of the context window but lose information in the middle. [19:50] — Context vs. Knowledge — Context is curated knowledge packaged for a specific task — you don't read the entire equipment manual, only the sections relevant to your troubleshooting task. [25:00] — Three Categories of Industrial Context — Domain knowledge (equipment manuals, SOPs), data context (historian, UNS, MES), human-generated context (operator notes, Excel sheets), and behavioral context (skills, guardrails). [30:00] — Technique 1: Persisting Context — Writing context to the file system so agents (or sub-agents) can read curated information in future sessions. [31:27] — Technique 2: Summarization/Compaction — Condensing large context into essential insights; why auto-compaction sometimes breaks agent behavior. [33:56] — Technique 3: Isolation via Sub-Agents — Spinning up agents with clean context windows to offload research and prevent bloat in the main agent. [36:05] — Deterministic Tools for Calculations — Why OEE and other calculations should be handled by validated scripts exposed as tools, not computed by the probabilistic model. [54:21] — Knowledge Graphs for Enterprise-Scale AI — How ontologies provide a "map of meaning" that helps agents navigate large instance models across multi-site enterprises. [1:02:00] — Federated Knowledge Graphs — Zach's argument for domain experts owning their own models, with governance at the integration interfaces between domains. Key Takeaways Context engineering is the new core competency for industrial AI. It is the practice of populating the context window with only highly relevant, curated information — not dumping in everything you have. The softmax normalization in transformer attention blocks dilutes important tokens when too much irrelevant information is present. Agents recall the start and end of context, not the middle. The "Lost in the Middle" research confirms that instructions and critical data placed in the middle of a large context window are likely to be ignored, leading to hallucinations and forgotten instructions. Use three techniques to manage context: persist, summarize, and isolate. Persist important context to files for future sessions. Summarize large documents down to essential insights. Isolate research and noisy tasks into sub-agents with clean context windows so the main agent stays focused. Deterministic code should handle deterministic tasks. Never let a probabilistic model perform calculations. Write validated scripts for things like OEE, expose them as tools, and let the agent orchestrate when to call them. Skills, MCP, and sub-agents solve different problems. Skills are modular, composable instruction sets with progressive disclosure. MCP servers supply vendor-defined tool context but can bloat the context window. Sub-agents provide isolated context windows for offloading research or preventing context poisoning. Knowledge graphs are the data architecture for scalable industrial AI. An ontology (model of meaning) paired with an instance model gives agents a navigational map of the domain, enabling them to reason across large enterprises rather than drowning in flat instance data. Treat prompts, skills, and agent definitions as code. Source-control them, evaluate them, iterate on them. The organizations building this muscle now are developing an expertise gap that will compound over the coming years. Notable Quotes "Context is curated knowledge that is packaged for a specific task." — Zach Etier, VP of Architecture at Flow Software "If you have something that can be done with a deterministic tool, it should be done with a deterministic tool. Don't use an agent to do a calculation." — Zach Etier, VP of Architecture at Flow Software "You get the reliability by managing the context window." — Zach Etier, VP of Architecture at Flow Software "Agents can't do on-the-job training. The context needs to be digitized and packaged in a way the agent can reason on." — Zach Etier, VP of Architecture at Flow Software "My hope is agents being this passive thing happening in the background — augmenting humans rather than becoming the team." — Zach Etier, VP of Architecture at Flow Software Key Concepts Explained Context Engineering Definition: The practice of curating, managing, and optimizing the information placed into an AI agent's context window so that it contains only highly relevant content with no bloat. Why it matters: It is the primary lever for improving agent reliability and reducing hallucinations in industrial settings. Episode context: Zach contrasted it with prompt engineering, explaining that reasoning models and tool-calling made agent context dynamic rather than static, creating the need for deliberate context management. Context Rot (Softmax Dilution) Definition: The degradation of an agent's ability to reason on relevant information as more tokens are added to the context window, caused by the softmax normalization distributing attention weight across all tokens. Why it matters: It explains why "more data" often leads to worse agent performance, which is counter-intuitive for many engineering teams. Episode context: Zach explained this as the core reason the industry shifted from "give the agent everything" to deliberate context engineering. MCP (Model Context Protocol) Definition: A standard protocol that allows AI agents to connect to external tool servers, where the server supplies tool descriptions and context so the agent knows how to call tools it was never trained on. Why it matters: It enables agents to interact with industrial software like historians, MES, and ERP systems through a standardized interface. Episode context: Zach compared MCP to skills, noting that MCP loads all tool descriptions at once (potential bloat) while the vendor controls the context, whereas skills give users control with progressive disclosure. Knowledge Graph (Ontology + Instance Model) Definition: A data structure combining an ontology (a model of meaning that describes domain concepts and relationships) with an instance model (actual data and values), linked by explicit relationships. Why it matters: It provides AI agents with a navigational map of the domain, enabling reasoning across large, complex enterprise data landscapes. Episode context: Zach described knowledge graphs as the future data architecture for industrial AI, and explained Flow Software's Atlas product as a knowledge modeling tool built on this approach. Isolation (Sub-Agent Pattern) Definition: A context engineering technique where a sub-agent operates in its own context window, separate from the main agent, to perform research or noisy tasks without contaminating the main context. Why it matters: It prevents context poisoning and bloat in the primary agent, enabling multi-agent coordination for complex industrial workflows. Episode context: Zach used the example of a research sub-agent that reads many files, filters for relevance, and returns only the essential findings to the main agent. Resources & References Tools & Technologies: Flow Software Timebase (Historian, Explorer, Collector), Timebase Atlas (knowledge modeling tool), MCP servers, Claude Code, OPC UA, Unified Namespace (UNS) Concepts & Frameworks: Context engineering, Lost in the Middle (Stanford paper), softmax normalization, needle-in-a-haystack testing, context rot, context poisoning, context confusion, research-plan-implement workflow, progressive disclosure, federated knowledge graphs Companies & Organizations: Flow Software, Anthropic, Northrop Grumman, Google (Gemini), OpenAI Standards & Architecture Patterns: ISA-95, knowledge graphs, ontologies, Unified Namespace, MCP (Model Context Protocol) Guest Bio & Links Zach Etier is the VP of Architecture at Flow Software, where he leads the development of knowledge graph technology (Timebase Atlas) and AI integration across the product portfolio. Before Flow, he spent 10 years at Northrop Grumman, starting in additive manufacturing operations and moving to the CIO office to architect digital manufacturing and Industry 4.0 service lines. He holds degrees in mechanical engineering, aerospace engineering, and computer science. Company: Flow Software GitHub Repo: (Linked in episode description — context engineering workshop materials) Social: (Linked in episode description) FAQ Section Q: What is context engineering in manufacturing AI? A: Context engineering is the practice of curating and managing the information placed into an AI agent's context window so it contains only the data relevant to a specific task. In manufacturing, this means selectively providing historian data, equipment manuals, operator notes, and MES information rather than flooding the agent with everything available. The goal is to maximize reasoning quality while minimizing hallucinations caused by token dilution. Q: Why do industrial AI agents hallucinate, and how can you reduce it? A: Industrial AI agents hallucinate primarily because of context rot — when too many tokens are loaded into the context window, the softmax normalization process dilutes the attention paid to relevant information. This is compounded by the "lost in the middle" effect, where agents fail to recall content positioned in the center of long inputs. Reducing hallucinations requires managing the context window through techniques like summarization, sub-agent isolation, and persisting only curated context. Q: What is the difference between MCP servers, skills, and sub-agents for industrial AI? A: MCP servers provide vendor-defined tool descriptions and context through a standard protocol, loading all tools at once. Skills are user-defined instruction sets with progressive disclosure — only metadata loads initially, and full content loads on demand. Sub-agents are separate agents with isolated context windows, used to offload research or noisy tasks. MCP is best when the vendor knows best how to use their tools; skills offer granular user control; sub-agents manage context isolation. Q: How do knowledge graphs help AI agents reason about factory data? A: Knowledge graphs combine an ontology (a conceptual model of domain relationships) with an instance model (actual operational data). The ontology provides agents with a navigational map that explains how equipment, production lines, and processes relate to each other. Without this, agents see only flat data values and lose context in large enterprises. Knowledge graphs enable agents to traverse from a specific equipment instance up to conceptual relationships and back, dramatically improving reasoning across complex multi-site operations. Q: Should AI agents perform OEE and other manufacturing calculations? A: No. Manufacturing calculations like OEE should be handled by deterministic scripts that are validated through traditional software testing and then exposed to the agent as callable tools. AI agents are probabilistic and can make calculation errors. The agent's role is orchestration — deciding when to call the calculation tool and how to present the results — not performing the arithmetic itself. Q: What is the best data architecture approach for scaling industrial AI across an enterprise? A: A federated knowledge graph approach is recommended, where domain experts define knowledge models for their specific areas (manufacturing, quality, engineering) and governance is applied at the integration interfaces between domains. This aligns with how organizations actually operate, since no single person understands the full enterprise. Federation avoids the impractical requirement of building one monolithic ontology upfront while still enabling cross-domain agent reasoning.

# AI in Manufacturing Podcast — Show Notes   ## Episode: How to Reduce Waste and Improve Efficiency with AI-Powered Quality Control   **Podcast Name:** AI in Manufacturing Podcast (Industry 4.0 TV) **Episode Title:** How to Reduce Waste and Improve Efficiency with AI-Powered Quality Control **Guest:** Willem Klein, CEO & Co-Founder, Zetamotion **Host:** Kudzai Manditereza **Target Audience:** Manufacturing data leaders, IT/OT solution architects, quality control professionals, and digital transformation leaders implementing AI in industrial operations   ---   ## 1. Episode Summary This episode explores how AI-powered quality control can reduce waste and improve efficiency in manufacturing, featuring Willem Klein, CEO and co-founder of Zetamotion. Willem shares why over 90% of industrial AI pilots fail and explains that the real competitive advantage lies not in building bigger AI models, but in designing better end-to-end systems that integrate seamlessly into existing production environments. He introduces Zelia, Zetamotion's AI-powered inspection assistant that reduces model training from weeks of manual data labeling to under an hour using synthetic data and as few as five sample images. The conversation covers the tension between governance and grassroots innovation ("shadow AI"), why manufacturers overwhelmingly prefer edge deployment for quality control data, and why scaling AI across plants is far harder than leadership expects. Willem also shares his vision for fully autonomous inspection systems that configure both software and hardware. Listeners will gain practical insight into what separates successful AI quality control deployments from the 90% that fail.   ---   ## 2. Key Questions Answered in This Episode   - Why do over 90% of industrial AI pilots fail, and what do the successful ones have in common? - What is the difference between a model-centric and system-level approach to AI quality control? - How can manufacturers deploy AI-powered visual inspection without needing an in-house data science team? - What is synthetic data, and how does it reduce the time and cost of training machine vision models? - How should manufacturing leaders balance AI governance with grassroots innovation on the shop floor? - Why do manufacturers prefer edge deployment over cloud for AI-based quality control? - What makes scaling AI quality control across multiple plants and production lines so difficult?   ---   ## 3. Episode Highlights with Timestamps   - **[0:00]** — **Introduction** — Host Kudzai Manditereza introduces the topic of AI-powered quality control and guest Willem Klein of Zetamotion. - **[1:00]** — **Willem's unconventional background** — From Star Trek and the Chaos Computer Club to a PhD in philosophy of technology and technology ethics. - **[5:01]** — **Where Zetamotion fits in the AI landscape** — Willem traces AI history from Turing to the "GPT moment" and explains why most industrial AI pilots fail (90%+ failure rate per MIT study). - **[11:06]** — **The "dark number" of shadow AI projects** — Unsanctioned grassroots AI projects by savvy factory workers signal the importance of empowering domain experts. - **[14:48]** — **Governance vs. flexibility: A virtue ethics approach** — Willem argues for educating engineers and granting reasonable freedom rather than imposing rigid rules. - **[18:08]** — **System-level thinking over model obsession** — Why the best AI model is worthless if the surrounding system is clunky and unusable for operators. - **[21:44]** — **Introducing Zelia** — Zetamotion's AI inspection assistant that uses synthetic data to go from five sample images to a trained model in under an hour. - **[28:27]** — **The full vision for Zelia** — Autonomous end-to-end inspection solution building, including custom dashboards, API connectors, and deployment architecture. - **[33:13]** — **Human-in-the-loop and the "supercharged magnifying glass"** — Why human expertise remains essential for edge cases and continuous improvement. - **[33:46]** — **Time savings: From 100,000 labeled images to five samples** — A glass manufacturing example illustrating weeks or months of saved manpower. - **[35:51]** — **Edge vs. cloud deployment** — Why manufacturers treat QC data as highly sensitive and overwhelmingly prefer on-premise edge solutions. - **[38:10]** — **Scaling challenges across plants** — No two production lines are the same, even when running the same product, and why copy-paste deployment doesn't work. - **[42:44]** — **Future vision: From inspection to physical AI** — Expanding Zelia beyond defect detection toward fully autonomous systems that configure their own hardware.   ---   ## 4. Key Takeaways   - **System-level design beats model performance:** A highly accurate AI model that creates more work for operators than manual inspection will collect dust. Successful AI quality control requires optimizing the entire workflow — UI, integration, reporting, and operator experience — not just the model.   - **Synthetic data dramatically reduces deployment time:** Traditional machine vision projects require collecting and labeling tens of thousands of images over weeks or months. Zetamotion's approach with Zelia requires as few as five good samples and five defect examples per category, achieving alignment in under an hour.   - **Shadow AI signals opportunity, not just risk:** Unsanctioned AI projects by factory workers indicate high-caliber talent and real inefficiencies worth solving. Leaders should channel this energy with reasonable guidelines rather than suppress it with rigid prohibitions.   - **Edge deployment is non-negotiable for most manufacturers:** Quality control data reveals intimate details about product defects and production parameters. Most manufacturers consider this highly sensitive and strongly prefer on-premise edge solutions over cloud-connected systems.   - **Scaling across plants requires contextual adaptation:** No two production lines are identical, even when running the same product. Differences in equipment age, operating parameters, and environmental conditions mean AI models cannot simply be copied from one site to another without intelligent fine-tuning.   - **Democratization is the key unlock:** The biggest barrier to AI adoption in manufacturing isn't model capability — it's accessibility. Giving domain experts tools they can use without AI expertise (similar to how ChatGPT democratized LLMs) is where the real transformation happens.   - **Human-in-the-loop remains essential:** In quality control, novel defects and edge cases appear constantly. AI works best as a "supercharged magnifying glass" that directs human attention to where expertise is needed, with human feedback continuously improving the system.   ---   ## 5. Notable Quotes   > "Think of it not like a robot walking into your factory telling everyone to go home, but rather handing your best people a supercharged magnifying glass that draws their attention exactly where they need to apply their human expertise." — Willem Klein, CEO & Co-Founder, Zetamotion   > "What good is a model if you cannot situate it into the larger context where its performance can actually do very well?" — Willem Klein, CEO & Co-Founder, Zetamotion   > "The better your people, the higher your risk of shadow AI projects happening — because people see inefficiencies and they want to solve them." — Willem Klein, CEO & Co-Founder, Zetamotion   > "Nobody wants to have anyone have full scans of their products including all of the defects and QC parameters. It's like looking into someone's drawers — you see the skeletons in the closet." — Willem Klein, CEO & Co-Founder, Zetamotion   > "We're talking about weeks or months of manpower that can easily be saved by only having to show a couple of examples and defect images." — Willem Klein, CEO & Co-Founder, Zetamotion   ---   ## 6. Key Concepts Explained   **Synthetic Data (for Machine Vision)** Definition: Synthetic data is artificially generated training data created by AI systems to simulate real-world images, eliminating the need to manually collect and label thousands of physical samples. Why it matters: It removes the biggest bottleneck in deploying AI quality control — the months-long process of collecting, labeling, and curating training datasets. Episode context: Willem explained that Zelia uses synthetic data to go from five sample images to a fully trained inspection model in under an hour, compared to traditional approaches requiring 100,000+ hand-labeled images.   **Human-in-the-Loop (HITL)** Definition: A system design approach where AI handles routine tasks autonomously but routes edge cases, novel situations, and final decisions to human operators for judgment and feedback. Why it matters: In manufacturing quality control, new defect types and contamination scenarios appear constantly, making pure automation unreliable without human oversight. Episode context: Willem described Zetamotion's current deployment model as human-in-the-loop, where AI directs operator attention to areas requiring expertise, and human feedback continuously improves the system.  

Episode Title:** Practical Guidance for Implementing Industrial AI Agents in Manufacturing Guest:** James Zheng, Co-Founder & Chief Product Officer, Optimate AI Host:** Kudzai Manditereza --- ## 1. Episode Summary This episode explores how agentic AI is creating a new category of digital skilled workers for manufacturing, addressing the industry's deepening productivity plateau and skilled labor crisis. James Zheng, Co-Founder and Chief Product Officer of Optimate AI, draws on over a decade of experience building and deploying manufacturing software — from SAP's cloud ERP to PTC's ThingWorx IoT platform — to explain why traditional digital transformation investments have failed to move the productivity needle. Zheng introduces the concept of a "decision intelligence and execution layer" that sits on top of existing systems of record (MES, ERP, CMMS, SCADA) to orchestrate AI agents that augment engineers, technicians, and frontline leaders. The conversation covers practical adoption patterns, the critical role of knowledge graphs and context graphs, why perfect data isn't a prerequisite for getting started, and real-world use cases in automotive and discrete manufacturing. Listeners will walk away with a clear framework for identifying, prioritizing, and scaling agentic AI use cases on the shop floor. --- ## 2. Key Questions Answered in This Episode - What is agentic AI and why should manufacturers care about it now? - What is the skilled labor crisis in manufacturing and how does agentic AI address it? - What is the difference between a knowledge graph and a context graph in industrial AI? - How should manufacturers approach data readiness for AI agent deployment — do you need perfect data? - What are the best first use cases for AI agents on the factory floor? - How does a decision intelligence layer differ from adding a copilot to existing manufacturing software? - How should manufacturing leaders balance top-down AI governance with bottom-up frontline innovation? --- ## 3. Episode Highlights with Timestamps **[0:54]** — **James Zheng's career journey** — From mechanical engineering to SAP, PTC ThingWorx, and founding Optimate AI, tracing the evolution of manufacturing software. **[3:53]** — **Why generative and agentic AI is different** — Zheng explains why this technology finally solves the problem he's spent his entire career pursuing. **[4:38]** — **The manufacturing productivity plateau** — US BLS data shows total factor productivity in manufacturing declined from 2008–2023 despite massive technology investment. **[8:50]** — **The skilled labor crisis defined** — Zheng explains how skilled workers (10% of cost but the most critical factor) are the true bottleneck, not capital or technology. **[11:46]** — **Two ways to apply agentic AI** — Adding copilots to existing tools vs. creating a new decision intelligence and execution layer that mimics how humans actually work. **[18:18]** — **Adoption patterns from other industries** — The progression from question-answering to task automation to autonomous workflows, applied to factory settings. **[24:07]** — **Data readiness: you don't need perfect data** — Why AI agents with reasoning capabilities can handle messy data, unlike legacy machine learning approaches. **[30:56]** — **Knowledge graphs vs. context graphs explained** — A detailed analogy breaking down the "what, where, who" (knowledge graph) from the "how and why" (context graph). **[37:41]** — **Optimate AI platform architecture** — Three layers: Factory Brain (knowledge graph), Agent Scaffolding (orchestration), and codified industry best practices. **[47:59]** — **Real-world customer use cases** — Automotive tier manufacturers reducing material loss and discrete manufacturers cutting cycle times by coaching frontline workers. **[53:28]** — **Advice for manufacturing leaders** — Embrace both top-down governance and bottom-up innovation by putting AI tools directly in frontline workers' hands. --- ## 4. Key Takeaways - **The productivity plateau is a people problem, not a technology problem:** Despite massive investments in IoT, machine learning, and automation from 2008–2023, US manufacturing productivity has stagnated or declined. The limiting factor is skilled labor — the engineers, technicians, and frontline leaders who represent only 10–20% of costs but determine quality, safety, and efficiency. - **Agentic AI creates a new abstraction layer, not a replacement for existing systems:** MES, ERP, CMMS, and SCADA systems remain as systems of record. AI agents sit on top as a "decision intelligence and execution layer" that uses these legacy systems as tools — just as a human worker would — rather than replacing them. - **Start with information access, then progress to task automation:** The most immediate value comes from giving frontline workers a single natural-language interface to find information across siloed systems, potentially saving one hour per person per shift. From there, automate non-value-added tasks like closing work orders before tackling complex autonomous workflows. - **Perfect data is not a prerequisite for AI agent deployment:** Unlike legacy machine learning that required clean, structured data, large language model-powered AI agents can reason through messy data. The real bottleneck is knowledge — specifically procedural and tribal knowledge — not data quality. - **Context graphs capture decision traces, not just static knowledge:** While knowledge graphs store the "what, where, and who," context graphs track the step-by-step reasoning and decision-making process. This decision trace becomes the foundation for self-learning AI systems that improve over time. - **Frontline workers must be the makers, not just users, of AI agents:** Because every factory, line, and shift presents unique problems, standardized playbooks from other domains don't transfer directly. The people doing the daily work need tools to build and customize their own AI agents. - **This technology wave has unprecedented bottom-up pull:** Unlike ERP or MES implementations that were top-down management systems, agentic AI delivers direct individual productivity gains, creating demand from frontline workers who already use ChatGPT in their personal lives. --- ## 5. Notable Quotes > "If you and I don't need perfect data to make a decision and take action, the AI agent does not need it either." — James Zheng, Co-Founder & CPO at Optimate AI > "Through my whole career, I have never seen a technology with this pull — not only from the top but also from the bottom of organizations." — James Zheng, Co-Founder & CPO at Optimate AI > "The bottleneck is not about data today. The bottleneck is more about knowledge." — James Zheng, Co-Founder & CPO at Optimate AI > "The existing software will be there forever. But the value is moving up to this next layer. The current layer will become just another tool — for the AI agent." — James Zheng, Co-Founder & CPO at Optimate AI > "Put the tools into the hands of your frontline team, let them explore. That's usually where magic will happen." — James Zheng, Co-Founder & CPO at Optimate AI --- ## 6. Key Concepts Explained **Skilled Labor Crisis** Definition: A term describing the critical shortage of experienced engineers, technicians, frontline leaders, and CI specialists in manufacturing — the knowledge workers who drive quality, safety, efficiency, and delivery decisions on the shop floor. Why it matters: This workforce segment represents only 10–20% of factory costs but is the primary limiting factor behind the manufacturing productivity plateau. Episode context: Zheng identifies this crisis (a term coined by Gene Farley, CEO of Pault) as the core problem agentic AI is uniquely positioned to solve. **Decision Intelligence and Execution Layer** Definition: A new software abstraction layer that sits on top of existing systems of record (MES, ERP, CMMS, SCADA) and systems of intelligence (IoT platforms, dashboards) to augment human decision-making and automate knowledge work through AI agents. Why it matters: It represents a paradigm shift from giving workers more dashboards to providing AI-powered digital teammates that reason, act, and learn. Episode context: Zheng positions this as the third generation of manufacturing software — after data collection (system of record) and data visualization (system of intelligence). **Context Graph** Definition: A data structure that captures the step-by-step decision trace of how and why decisions were made during problem-solving processes like troubleshooting, recording the reasoning path, hypothesis validation, and corrective actions taken. Why it matters: Context graphs enable AI agents to learn from past decisions and generate

1. EPISODE SUMMARY This episode explores why most manufacturing AI initiatives fail and what companies must do to build a foundation for AI-native industrial intelligence. Craig Scott, Founder and CEO of Fuuz, an industrial intelligence platform, shares insights from nearly a decade of bridging the gap between shop floor data and enterprise systems. The conversation reveals why the missing "shim" between operational technology and enterprise systems is the root cause of unreliable data in manufacturing, and why model-driven approaches are essential for scaling AI across industrial operations. Craig explains how organizations can achieve a single source of truth by implementing a persistent contextualization layer that governs data before AI ever touches it. Whether you're struggling with fragmented point solutions, evaluating industrial data platforms, or preparing your data infrastructure for AI, this episode provides a practical framework for building scalable industrial intelligence. 2. KEY QUESTIONS ANSWERED IN THIS EPISODE What is fundamentally broken with current manufacturing data infrastructure and how does it impact AI initiatives? Why do most AI pilots fail to scale in manufacturing environments? What is a model-driven approach to industrial data, and why is it superior to in-line data transformation? How do you balance enterprise governance with plant-level flexibility in industrial data architectures? Should manufacturers adopt industry-standard data models like ISA-95 or build custom models? What is the difference between a data lake and an operational intelligence platform? How can manufacturers prepare their data foundation before investing in AI technologies? 3. EPISODE HIGHLIGHTS WITH TIMESTAMPS [0:00] - Introduction — Craig Scott's background from hands-on manufacturing at age 15 to founding Fuuz, and why the company's purple branding represents the merger of "red" (OT) and "blue" (IT) data. [6:56] - What's Fundamentally Broken — Discussion of how critical manufacturing knowledge is leaving the business as the workforce ages, and why data-driven approaches are essential to capture and retain institutional knowledge. [8:09] - The Missing Shim Problem — Craig explains the gap between real-time shop floor data (SCADA/historians) and enterprise systems (ERP/PLM), and why neither system alone provides a single source of truth. [16:20] - MCP and I3x Integration — How Fuuz is implementing Model Context Protocol and aligning with the I3x initiative for standardized GraphQL APIs to enable AI connectivity. [18:52] - Model-Driven vs. In-Line Transformation — Why data transformation tools that reshape data in motion create scaling challenges, and how persistent data models solve enterprise-wide consistency. [24:06] - AI Governance and Hallucination Prevention — Why deterministic data models are essential for trustworthy AI—Claude can't "make up" OEE numbers when the data graph dictates values. [28:41] - Custom vs. Standard Data Models — Discussion of when to use ISA-95 accelerators versus custom models, using an automotive OEM wall-to-wall deployment as an example. [33:46] - Red and Blue Namespace Architecture — How Fuuz balances enterprise governance with plant-level flexibility through extensible tenant-based data models. [37:28] - What Category is Fuuz? — Craig explains how the platform spans MES, WMS, data ops, and application development—an operational intelligence layer, not a data lake. [47:13] - Technical Architecture Deep Dive — Overview of Kubernetes backend, Node.js framework, RabbitMQ messaging, MongoDB with custom ORM, and the hybrid gateway for edge connectivity. [51:16] - Real-World Deployments — Case studies including an automotive OEM running an entire car plant on Fuuz, Highbar Steel's solar-powered green steel mill, and PepsiCo co-packer integrations. [53:52] - Advice for Getting Started — Craig's recommendation to define the problem first, assemble cross-functional IT/OT teams, and start small with the understanding that small problems often expose bigger ones. 4. KEY TAKEAWAYS The "shim" between shop floor and enterprise is the missing piece: ERP and PLM systems are only accurate for the first 15 minutes after data entry. Without a real-time contextualization layer synchronizing shop floor and enterprise data, there is no true single source of truth. Model-driven persistence beats in-line transformation for scale: While edge tools that transform data in motion work for one or two sites, they require re-implementation across every site and system. A persistent data model is defined once and becomes the consistent interface for all enterprise systems. AI governance requires deterministic data models: LLMs cannot reliably do math and will hallucinate if given unstructured data. By forcing AI to read from governed data graphs, organizations can move toward semi-autonomous and eventually autonomous operations with trustworthy outputs. Extensible models balance governance and flexibility: Enterprise IT can define governed core models while individual plants extend them with additional metadata—they can add context but cannot change underlying structures, preserving data integrity while enabling local adaptation. Operational intelligence is not the same as a data lake: Data lakes are good for reporting and analytics but don't help run real-time operations. An operational intelligence platform provides both persistent contextualized state and real-time event streaming for actual operational execution. Start with the problem, not the technology: Many companies approach vendors saying they "need an MES" without understanding why. Defining value drivers first allows solutions to start small and expand as bigger problems reveal themselves. Build tools that enable AI, don't rely on AI as the platform: LLMs are evolving rapidly and may be replaced by new model architectures. Building platforms around deterministic data foundations protects against technical debt from betting on novel technologies. 5. NOTABLE QUOTES "There's a reason why our color is purple, because if you mix red and blue together, it makes purple. We are the part that's in between—the highly structured enterprise data like ERP and PLM and the really unstructured data that's happening on the plant floor." — Craig Scott, CEO at Fuuz "The ERP is a good source of truth for like the first 15 minutes that the data goes into the system, and then immediately, when you start generating real time data from the shop floor, it's out of date. Nothing is in sync anymore." — Craig Scott, CEO at Fuuz "When I connect Claude to Fuuz, Claude can't make anything up. It can't imagine an OEE for my line or my machine because it's being dictated by our data graph." — Craig Scott, CEO at Fuuz "I still look at AI as a tool, and I don't know that we're ready to acknowledge AI as the platform yet. We want to build tools and platforms that enable the technology, not rely on the new technology to be our platform." — Craig Scott, CEO at Fuuz "Data is money, and if we can turn that data into actionable insights, now we can make more money for your business." — Craig Scott, CEO at Fuuz 6. KEY CONCEPTS EXPLAINED Industrial Intelligence Platform Definition: A software layer that sits between operational technology (SCADA, historians, PLCs) and enterprise systems (ERP, PLM, CRM) to provide real-time data contextualization, persistence, and governance. Why it matters: Traditional architectures leave a gap between shop floor data and business systems, causing data inconsistency and preventing AI from accessing trustworthy operational information. Episode context: Craig describes Fuuz as the "shim" or "purple" layer that bridges red (OT) and blue (IT) data, enabling real-time synchronization and a true single source of truth. Model-Driven Architecture Definition: An approach where data models are defined first as persistent, governed structures, and all systems read from and write to this single canonical model rather than transforming data in-line during transit. Why it matters: In-line transformation tools work for small deployments but require re-implementation at every site. Model-driven persistence enables "once and done" enterprise-wide data consistency. Episode context: Craig contrasted this with edge tools that reshape data in motion, explaining that persistent models scale across global enterprises with multiple ERPs and systems. Unified Namespace (UNS) Definition: An architectural pattern that provides a single, hierarchical structure for all operational data, making it accessible to any system that needs it. Why it matters: UNS is gaining adoption as a way to democratize data access, but without persistent contextualized state, it only provides current values—not the historical context needed for operations and AI. Episode context: Craig acknowledged UNS as a great concept but emphasized that operational intelligence requires persistent state of contextualized data, not just real-time streaming. Model Context Protocol (MCP) Definition: A protocol that enables AI systems to connect to and understand data from external platforms through standardized interfaces. Why it matters: MCP allows AI tools like Claude to access governed industrial data without requiring custom integrations or exposing companies to AI hallucination risks. Episode context: Fuuz added MCP capability to expose their data graph to AI systems, ensuring AI outputs are governed by deterministic data rather than generating unreliable information. I3x Initiative Definition: An industry initiative working on standardized GraphQL APIs for industrial data exchange, enabling interoperability between industrial systems. Why it matters: Standardized APIs reduce integration complexity and allow best-of-breed systems to share data through common interfaces. Episode context: Craig mentioned Fuuz has been GraphQL-based since inception and is building an I3x connector to expose all enterprise system data through this emerging standard. 7. RESOURCES & REFERENCES Technologies & Platforms Fuuz Industrial Intelligence Platform Ignition (Inductive Automation) - SCADA platform Kepware - Industrial connectivity Plex - Cloud ERP for manufacturing MongoDB - Document database RabbitMQ - Message broker GraphQL - API query language Kubernetes - Container orchestration React - Frontend framework Standards & Frameworks ISA-95 - Manufacturing operations standard I3x Initiative - Standardized industrial APIs Model Context Protocol (MCP) OPC UA - Industrial interoperability standard MQTT - Industrial messaging protocol Concepts Unified Namespace (UNS) Knowledge Graphs Red and Blue Data (Walker Reynolds concept) Data Lakes vs. Operational Intelligence Events PROVE IT Conference 8. GUEST BIO & LINKS Craig Scott is the Founder and CEO of Fuuz, an industrial intelligence platform that bridges the gap between shop floor operations and enterprise systems. With a career spanning manufacturing engineering, owning tool-and-die and precision machining companies, consulting for Plex ERP, and founding a system integration business, Craig brings a unique perspective that combines hands-on manufacturing experience with deep technology expertise. He holds a degree in manufacturing engineering and a master's in manufacturing administration. Company Website: fuuz.com Knowledge Base: support.fuuz.com Free Training: Fuuz Academy (self-paced, available via website) LinkedIn: Search "Craig Scott Fuuz" 9. FAQ SECTION Q: What is the difference between a data lake and an operational intelligence platform? A: A data lake stores denormalized data optimized for reporting and analytics but doesn't help run real-time operations. An operational intelligence platform provides persistent contextualized state and real-time event streaming, enabling both operational execution and analytics from a single governed source. Q: Why do most manufacturing AI pilots fail to scale? A: Most AI initiatives skip the foundational work of preparing and contextualizing data. Companies pipe raw data into data lakes or directly into AI tools without governance, leading to unreliable outputs. AI is only as good as the data it receives—without a persistent, governed data model, AI cannot produce trustworthy results at scale. Q: Should manufacturers use standard data models like ISA-95 or build custom models? A: Both approaches are valid depending on the use case. ISA-95-based accelerators work well for discrete manufacturing processes, but complex operations like automotive assembly with multiple lines require extensible custom models. The key is having a platform that allows starting with standards and extending as needed. Q: How do you balance enterprise data governance with plant-level flexibility? A: Implement governed core models at the enterprise level, then allow individual plants (as separate tenants) to extend those models with additional metadata. Plants can add context but cannot change underlying structures, preserving data integrity while enabling local adaptation. Q: What should manufacturers do first to prepare for AI adoption? A: Define the specific problem you're trying to solve and identify the value drivers behind it. Assemble a cross-functional team between IT and OT. Take inventory of your data sources and understand which hold the most valuable information. Start small—solving small problems often exposes bigger opportunities, and having the right platform in place makes solving those bigger problems easier. Q: Can I use an industrial intelligence platform without replacing my existing ERP or MES? A: Yes. Platforms like Fuuz are designed to integrate with existing systems rather than replace them. You can expose data from multiple ERPs, PLMs, and operational systems through a single governed layer, adding AI and modern API capabilities without wholesale system replacement. 10. RELATED TOPICS & EPISODES Unified Namespace Architecture — Understanding how UNS patterns complement operational intelligence platforms Industrial AI Agents — Building autonomous systems that can trust their data foundation MES Modernization — Strategies for extending legacy manufacturing execution systems IT/OT Convergence — Bridging the gap between information technology and operational technology teams I3x Initiative Deep Dive — Upcoming episode exploring standardized industrial APIs

Traditional MES platforms were built for a manufacturing world that no longer exists. They assume stable product lines. They assume you have time for lengthy implementations, tolerance for complexity, and operators who can navigate digital forms while running production.   But here's the challenge. Today's manufacturing reality is different: ⇨ Markets demand the flexibility to shift from 1.5-liter bottles to 1-liter bottles overnight ⇨ Low volume, high mix production is now the norm ⇨ Tribal knowledge is retiring faster than it's being captured ⇨ Workers stay 2-3 years, not 20, making traditional training models obsolete   The cost of this disconnect? ❌ Frontline workforce unable to contribute operational intelligence at scale ❌ ROI delayed by complexity, not capability ❌ Two-year deployment cycles for basic systems ❌ Digital initiatives stuck in pilot purgatory   That's why leading manufacturers are rethinking execution from the ground up, shifting from monolithic systems to AI-native, human-centric platforms built for today's workforce reality.   This new approach is effective because it’s built with an AI-native mindset, not a digitized version of paper-based processes   ✅ AI-generated SOPs from video, cutting engineering time by 80% ✅ Learning systems that surface troubleshooting guidance from historical fault data ✅ Human-centric design that captures operational intelligence without disrupting workflows ✅ AI-powered interfaces that enable natural interaction; think voice, not dropdowns ✅ Rapid deployment measured in weeks ✅ Scalable without complexity; connect thousands of machines without lengthy integrations   The companies winning today aren’t planning more; they’re executing faster and adapting continuously.   In this episode of the AI in Manufacturing podcast, I speak with Mickey Shaposhnik, Founder and CEO of Next Plus, about how practical, AI-powered frontline execution is redefining operational excellence.   Watch/Listen now  

Agentic AI Framework for Manufacturing Operations AI in Manufacturing Podcast Show Notes Episode Guest: Gilad Langer, Head of Digital Transformation Practice at Tulip Interfaces Host: Kudzai Manditereza Publication Date: [Insert Date] Episode Summary Manufacturing systems are complex adaptive systems that require a fundamentally different approach to AI implementation than traditional monolithic architectures. In this episode, Gilad Langer draws on 30 years of manufacturing experience—including PhD research that laid the groundwork for Industry 4.0—to introduce a composable agentic framework specifically designed for frontline operations. He explains why adaptability has become a competitive necessity in today's disrupted markets and how multi-agent systems can transform innate factory equipment into intelligent, communicating entities. The conversation covers practical implementation strategies, the artifact model for structuring manufacturing data, and why cultural change remains the biggest obstacle to agentic AI adoption. Key Questions Answered in This Episode What is an agentic AI framework for manufacturing and why do factories need one? How do complex adaptive systems apply to manufacturing operations? What are the five pillars of composability in manufacturing? How should manufacturers structure their data for AI agents using the artifact model? What is the difference between staff agents, builder agents, and artifact agents? How do you implement agentic AI in a brownfield manufacturing facility? Why do traditional MES systems fail to deliver the adaptability modern manufacturing requires? Episode Highlights with Timestamps [0:00] — Introduction — Kudzai introduces Gilad Langer and previews the discussion on composable agentic frameworks for frontline operations. [1:19] — Gilad's Background — Gilad shares his 30-year manufacturing journey, including PhD research in the 1990s that anticipated Industry 4.0 concepts like IIoT and multi-agent systems. [6:58] — The Vision Realized — Discussion of how today's technology finally enables the adaptive manufacturing concepts envisioned decades ago. [7:49] — Why Adaptability is Now Essential — Gilad explains how tariffs, supply chain disruptions, and COVID have made manufacturing adaptability a competitive necessity, not just an aspiration. [14:10] — Complex Adaptive Systems Explained — Deep dive into how manufacturing systems share characteristics with traffic and weather patterns, including the concept of attractors and emergence. [15:38] — The Toyota System Connection — Gilad explains how Toyota understood complex adaptive systems and used lean methods to keep manufacturing in the "orderly space." [26:21] — The Danger of Uncontrolled Agents — Discussion of how agents without proper frameworks can cause catastrophic "butterfly effects" in manufacturing operations. [28:19] — Agent Taxonomy Introduction — Gilad walks through the four types of agents: staff helpers, builder agents, operational agents, and artifact agents. [35:06] — Agents as Digital Twins — Why each discrete item should have its own agent rather than one agent controlling multiple machines. [40:20] — The Artifact Model Explained — Comprehensive breakdown of how to structure manufacturing data using physical and operational artifacts. [51:07] — Implementation Strategy — Practical guidance on starting small with agentic AI, beginning with a single machine and growing from there. [57:15] — Tulip Platform Overview — How Tulip's no-code frontline operations platform enables composable agentic manufacturing. [1:00:46] — The Composability Test — How to determine if your implementation is truly composable: can you solve a problem within an hour? Key Takeaways Manufacturing systems are complex adaptive systems that require emergent, bottoms-up approaches. Traditional blueprint-based implementations lock organizations into rigid structures. Truly adaptive manufacturing systems mimic natural phenomena—like plants growing toward sunlight—by solving problems iteratively and adapting to obstacles without predetermined plans. The five pillars of composability provide a framework for evaluating any manufacturing technology. Ask whether a platform supports bottoms-up development, lean improvement, democratized access, human-centric design, and compliance requirements. If a technology fails any of these tests, it cannot deliver true composability. Agents can either help humans or bring innate objects to life. Staff agents assist workers with tasks like monitoring and scheduling. Artifact agents wrap physical equipment with intelligence, enabling machines, materials, and systems to communicate with each other and with humans. The artifact model simplifies manufacturing data into physical and operational categories. Physical artifacts include machines, tools, areas, and materials. Operational artifacts include orders, tasks, defects, and events. Most manufacturing plants have no more than ten distinct physical artifact types, making the data model inherently human-comprehensible. Per-artifact agents deliver true adaptability that hierarchical approaches cannot match. When one agent fails in a distributed system, the others adapt and continue operating. A single controlling agent creates a single point of failure that can bring down entire operations. Start small with agentic AI implementation. Pick one critical piece of equipment, add sensors, create a simple agent, and let operators interact with it. Scale gradually while building governance frameworks alongside the technology. Cultural change is the biggest obstacle to agentic manufacturing adoption. Engineers trained in monolithic thinking will naturally gravitate toward building rigid systems even when given composable tools. Organizations need change agents who maintain discipline around composable principles. Notable Quotes "It's not the most intelligent of the species that survives. It's the species that is most adaptable to change that survives—that thrives." — Gilad Langer, referencing Darwin's principle as applied to manufacturing "If you push the system, if you take out the slack, highly likely there's going to be a traffic jam. And it's the same thing in manufacturing." — Gilad Langer, on why pull-based systems outperform push-based systems "If it takes months or more to connect a machine and create an agent, you don't have a composable system. The answer should be hours." — Gilad Langer, on the composability test "We run manufacturing like that. As soon as an event we didn't expect happens, we just sit there and burn alive. Essentially, that's what we do." — Gilad Langer, on the limitations of blueprint-based manufacturing systems Key Concepts Explained Complex Adaptive Systems Definition: A class of systems composed of discrete entities that exhibit emergent behavior and patterns without centralized control—including traffic, weather, and manufacturing operations. Why it matters: Understanding manufacturing as a complex adaptive system reveals why traditional rigid architectures fail and why multi-agent approaches succeed. Episode context: Gilad uses examples of traffic patterns and weather prediction to illustrate how patterns emerge in chaotic systems and how Toyota's lean methods leverage these dynamics. Composability Definition: An architectural approach built on five pillars—bottoms-up development, lean thinking, democratization, human-centricity, and compliance—that enables systems to adapt continuously rather than requiring upfront blueprints. Why it matters: Composable systems can respond to market disruptions, supply chain changes, and unexpected events without costly re-engineering. Episode context: Gilad contrasts composable platforms with traditional MES implementations that "lock you in a prison" through rigid blueprints and design reviews. Artifact Model Definition: A simplified data structure that categorizes manufacturing elements into physical artifacts (machines, tools, materials, areas) and operational artifacts (orders, tasks, defects, events), typically resulting in no more than ten distinct artifact types per facility. Why it matters: The artifact model makes manufacturing data human-comprehensible and AI-ready by reflecting the actual reality of the shop floor rather than abstract database schemas. Episode context: Gilad explains how this model emerged from 1990s research and enables both knowledge graphs and agent-based systems to operate effectively. Emergence Definition: A phenomenon where complex system behaviors arise from simple rules followed by individual entities, without centralized planning or blueprints. Why it matters: Emergent systems achieve adaptability that hierarchical control structures cannot match. Episode context: Gilad uses the example of a plant growing toward sunlight—adapting around obstacles without any blueprint—to illustrate how manufacturing systems should evolve. Attractor (Chaos Theory) Definition: A state toward which a system naturally tends to evolve; attractors can lead to either stable operations or catastrophic failures. Why it matters: Agentic frameworks must include mechanisms to keep systems away from bad attractors that could cause plant shutdowns or quality disasters. Episode context: Gilad emphasizes that without proper governance, multi-agent systems can rapidly cascade toward destructive states—the "butterfly effect" in manufacturing. Resources & References Technologies & Platforms: Tulip Interfaces — No-code frontline operations platform Unified Namespace (UNS) — Real-time data communication architecture Multi-Agent Systems (MAS) — Distributed AI architecture Concepts & Frameworks: ISA-95 — Manufacturing operations standard Complex Adaptive Systems theory Chaos theory and attractors Toyota Production System / Lean Manufacturing Kaizen and Gemba walks Knowledge graphs Historical References: Agility Forum (Lehigh University, 1990s) RWTH Aachen Institute (Industry 4.0 foundations) "Future Perfect" by Stanley Davis (1987) — Mass customization concepts Companies Mentioned: Toyota — Lean manufacturing pioneer Amazon / Amazon Robotics — Adaptability exemplar DMG Mori, Mazak — CNC machine manufacturers Guest Bio & Links Gilad Langer is the Head of Digital Transformation Practice at Tulip Interfaces, bringing 30 years of manufacturing experience spanning integrators, software suppliers, and startups. His PhD research in the 1990s—conducted in collaboration with Germany's RWTH Institute—helped establish foundational concepts for what became Industry 4.0, including multi-agent systems and adaptive manufacturing architectures. He is a prolific writer on manufacturing technology and composable operations. Blog: GilardLConsulting.com Company: Tulip.co LinkedIn: Gilad Langer FAQ Section Q: What is an agentic AI framework for manufacturing? A: An agentic AI framework for manufacturing is a structured approach for deploying multiple AI agents that work together to manage factory operations. Unlike traditional monolithic systems, this framework treats manufacturing as a complex adaptive system where discrete agents—representing machines, materials, and processes—communicate and coordinate autonomously while following governance rules that prevent chaotic behavior. Q: How does the artifact model work in manufacturing AI? A: The artifact model structures manufacturing data into two categories: physical artifacts (machines, tools, materials, areas) and operational artifacts (orders, tasks, defects, events). Most facilities have fewer than ten distinct artifact types, creating a simplified data model that humans can understand intuitively and AI agents can navigate effectively. Each artifact becomes the foundation for an agent that owns and manages its associated data. Q: What are the five pillars of composability in manufacturing? A: The five pillars are: (1) bottoms-up emergent development rather than top-down blueprints, (2) lean thinking that removes obstacles and maintains flow, (3) democratized access so frontline workers can create and modify solutions, (4) human-centric design that augments rather than replaces workers, and (5) compliance-ready architecture that satisfies regulatory requirements while remaining adaptable. Q: Why can't traditional MES systems support agentic AI? A: Traditional MES systems were architected in the 1990s around monolithic, blueprint-based designs that require locking in requirements before implementation. These rigid structures cannot support the emergent, adaptive behavior that multi-agent systems require. Attempting to add agentic capabilities to monolithic architectures is comparable to running electric vehicles on infrastructure designed for horse-drawn carriages. Q: How should manufacturers start implementing agentic AI? A: Start with a single critical piece of equipment, even legacy machinery that lacks modern connectivity. Add sensors, create a simple agent for that machine, and enable operators to interact with it. Validate the approach, then gradually expand to additional machines while developing governance frameworks alongside the technology. This bottoms-up approach aligns with composability principles and avoids the risks of big-bang implementations. Q: What is the biggest challenge in adopting agentic AI in manufacturing? A: Cultural change presents the greatest obstacle. Engineers trained in traditional methodologies will naturally gravitate toward building monolithic systems even when given composable tools. Organizations need dedicated change agents who maintain discipline around composable principles—similar to lean senseis who guide continuous improvement transformations. Related Topics Unified Namespace Architecture — How UNS enables agent-to-agent communication Digital Twin Implementation — Building intelligent representations of physical assets Lean Manufacturing Meets AI — Connecting Toyota Production System principles with agentic frameworks Industrial AI Governance — Establishing guardrails for autonomous manufacturing systems Composable Enterprise Architecture — Extending composability beyond the shop floor ‍  

Context isn't static.   It's a living layer of knowledge built through problem-solving, conversation, and understanding the complex relationships on the factory floor.   This simple truth is often overlooked in industrial data strategies.    We’ve been conditioned to believe that context can be predefined; baked into standards, taxonomies, and hierarchies.   But in real-world manufacturing, things change, people think differently, and use cases evolve.   So how can we build this dynamic layer of understanding for industrial AI?   In our latest AI in Manufacturing episode, I spoke with Bob van de Kuilen, Director at Thred, about a more human-centric approach to industrial data contextualisation using Knowledge Graphs.   Thred is a tool that plugs into Ignition Platform, enabling users to visualize their factory assets in a knowledge graph, link related data points, embed domain expertise, and deliver structured, contextualized data to AI and analytics tools.   We discuss:  ✅ Why traditional approaches to data context often fail  ✅ Knowledge Graphs act as a mind map for data  ✅ The practical steps to building context  ✅ How this new context layer serves as the perfect foundation for AI agents.

SA-95 is a standard that’s often misunderstood, but incredibly powerful. While many think ISA-95 is rigid or overly complex, it actually enables flexibility by: ⇨ 𝐃𝐞𝐟𝐢𝐧𝐢𝐧𝐠 𝐚 𝐬𝐡𝐚𝐫𝐞𝐝 𝐯𝐨𝐜𝐚𝐛𝐮𝐥𝐚𝐫𝐲 for manufacturing concepts, creating a true ontology for your data. ⇨ 𝐂𝐫𝐞𝐚𝐭𝐢𝐧𝐠 𝐬𝐜𝐚𝐥𝐚𝐛𝐥𝐞 𝐩𝐥𝐚𝐜𝐞𝐡𝐨𝐥𝐝𝐞𝐫𝐬 for every type of data, so you can start small and add new use cases later without rebuilding everything. ⇨ 𝐏𝐫𝐨𝐯𝐢𝐝𝐢𝐧𝐠 𝐭𝐡𝐞 "𝐰𝐡𝐲" 𝐛𝐞𝐡𝐢𝐧𝐝 𝐞𝐯𝐞𝐧𝐭𝐬, not just the "what," giving crucial context to your analytics and AI models. But how do you move from theory to a practical, modern implementation? In our latest AI in Manufacturing podcast episode, we explore exactly that with ISA-95 expert Jeroen Janssen, who is an MES/MOM Consultant at Rhize Manufacturing Data Hub. In the episode, you’ll learn: ✅ How to overcome a data culture that creates so many silos. ✅ The "use case stacking" method for a phased, value-driven implementation. ✅ What a native ISA-95 data hub looks like and how a graph database can bring it to life. ✅ Why this standardized approach is the key to unlo