{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Manufacturing Hub","title":"Ep. 252 - Industrial AI in Manufacturing What Actually Works and What Does Not #industrialautomation","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/b0a74284\"></iframe>","width":"100%","height":180,"duration":3939,"description":"Manufacturing Hub is back with Episode 252, where co hosts Vlad Romanov and Dave Griffith break down what an AI survival guide should actually look like for manufacturing and industrial automation professionals. This is not a hype conversation about replacing people with magic software. It is a grounded discussion about what AI tools can do today, where they fail, why context and data quality matter so much, and how industrial teams should think about experimentation without losing sight of real operating constraints.In this episode, Vlad and Dave unpack the evolution many engineers and technical leaders have already felt in real time, from early prompt engineering, to agent based workflows, to MCP servers, skills, context management, and the growing cost of tokens and infrastructure. The conversation moves beyond generic AI commentary and into the reality of plant floor environments, where success depends on process knowledge, data architecture, OT constraints, cybersecurity, governance, and clear business value. One of the strongest themes throughout the episode is that manufacturers cannot skip the hard work of structuring data, understanding workflows, and defining use cases simply because AI tools are moving quickly.Vlad brings a very practical industrial lens to the discussion. Drawing on years of hands on experience across controls, manufacturing systems, plant modernization, and digital transformation, he explains why industrial AI has to start with operational context. A maintenance team, an engineering team, and a quality team do not need the same data, do not ask the same questions, and should not be handed the same AI workflows. That distinction matters. This conversation also highlights why the best industrial AI implementations will likely come from teams that combine domain expertise with strong technical execution, rather than generic AI shops trying to force a solution into environments they do not fully understand.Dave adds an important systems...","thumbnail_url":"https://img.transistorcdn.com/yoKAvzBXZ3YjQTekFk7KFGXeuwJ29WgXvop3dVEfhLs/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzE3MjEzLzE2MDk0/MzA1OTgtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}