AI in Manufacturing is an Industry40.tv podcast hosted by Kudzai Manditereza, bringing together industry leaders, technologists and practitioners to explore how AI is being built and applied across industrial operations.
The podcast covers the architectures and real-world implementations shaping industrial AI, including connectivity, industrial data infrastructure, semantic technologies, data platforms, AI agents and operational applications.
For manufacturing engineers, architects and technology leaders working to turn industrial data and AI into measurable operational impact.
How autonomous agents are reshaping decision-making on the plant floor — and the architecture required to deploy them safely at scale.
Showing 9 of 9 podcasts.
How autonomous agents are reshaping decision-making on the plant floor — and the architecture required to deploy them safely at scale.
Manufacturing never standardized the basic interface for getting data out of its software systems. What I3X proposes, and why the fix is simpler than expected.
Why running every task through one large language model drives runaway cost and latency, and how coordinated small models change the economics of scaling.
A venture builder operating inside factories on how to find problems actually worth solving, and why that matters more than better algorithms.
Historians, SCADA and even a unified namespace still leave agents unable to reason about the floor. The missing layer is context, not compute.
Agentic AI is an architectural capability, not a software feature you bolt on. What a semantic, real-time data backbone actually demands.
US manufacturing productivity has been flat since 2008 despite heavy digital investment. Where the time leaks between a decision and permission to act.
Agents need exactly the knowledge the task requires, structured so they can reason on it. How to scope context for reliable industrial agents.
Why AI quality control is so hard to get right, what manufacturers keep underestimating, and what separates projects that ship from pilots that stall.
The real constraint is not data infrastructure. It is the procedural knowledge living in your best engineers' heads instead of your databases.
Your ERP is only accurate for about fifteen minutes after data entry. Building a foundation that stays in sync with what is actually happening.
Why legacy MES assumptions no longer match how plants run, and what execution looks like when adapting continuously beats planning further ahead.
Without a framework you end up with disconnected pilots and a governance problem. A structure for agents across manufacturing operations.
Historians full of sensor data still cannot answer why quickly enough. Treating context as something learned iteratively rather than fixed upfront.
The same metric calculated three ways by three departments. How ISA-95 gives operations, quality and maintenance one shared model to work from.
Forty sites, mixed historian vendors, most of them working fine. How to standardize analytics across them without ripping out what already works.
A sensor flatlined at 187 degrees for six hours looks perfectly healthy to IT. Catching the failures your schema checks will never surface.
Predictive models tell you what will happen, not what to do about it. Where reinforcement learning fits into plant optimization.
Building the model is the easy part. Twenty-five years of plant experience on what operationalizing AI actually takes.
Three CSV exports and two days of timestamp alignment before the analysis even starts. The capabilities that make that work reusable.
Analyzing data where it is generated instead of round-tripping to the cloud. What keeping intelligence at the source changes on the line.
Foundation models were trained on text, not thermodynamics. What a domain-trained model for refineries and petrochemical plants looks like.
A laser-marked code vanishes after six hours at 900 degrees and the part loses its identity. Holding traceability through heat treatment.
How one global manufacturing team moved out of pilot purgatory and got AI running across sites, and what they had to stop doing first.
Specifying a vision sensor means knowing conveyor speed, ambient temperature and PLC brand. Agents that carry that specification work.
The model worked in testing, then quietly drifted once it hit the shop floor. Treating AI as a continuous loop rather than a one-time deployment.
Cloud, PLC or edge? Why the layer sitting between shop floor and enterprise systems is the one most manufacturers skip.
Your DCS is reliable enough that nobody wants to touch it. That same reliability is what now blocks advanced AI from reaching the process.
Static dashboards explain downtime after it happens. Agents that read live sensor feeds against history to catch it while it still matters.
Most digital twins are visualization layers sitting on data streams. Adding the semantic layer that lets them make decisions instead.
Tables and columns were designed for transactions, not agents. How data structure decides what your agents can actually find.
A technician hits an error code and starts searching hundreds of pages while the line sits idle. Cutting mean time to repair with generative AI.
Nine months of deep learning could not diagnose the fault. A senior engineer found it in five seconds: the machine was not level.
Scrap and rework are visible. Unused data, manual re-entry and siloed information are not. Finding the digital waste worth automating first.
Downtime, slow cycles and bottlenecks nobody has identified drag OEE down. Using video agents to measure what fixed sensors miss, safety included.
Your AI strategy fails at connectivity long before it fails at modeling. Decades of joining heterogeneous plant systems, distilled.
Retiring workers, persistent labor shortages, rising complexity. Where a frontline copilot earns its place on the shop floor first.
I feel this is the problem is how most yield issues still get solved. What changes when the data leads instead of the instinct.
Factories generate data through lots of little pipes that never connect. Linking it into a model AI can actually reason over.
Scrap and rework from undertrained operators cost real money. How assembly copilots guide work in real time, and what they measure.
Thirty-five years of logic-based control giving way to systems that learn and adapt. What that shift asks of your plant and your team.
Data lakes became data swamps while the insight stayed behind technical barriers. Assistants that close the gap for domain experts.
Millions of data points a second, very little of it reaching a decision. Connecting shop floor reality to strategic choices.
Papers report accuracy gains while many plants run much as they did fifteen years ago. Where AI shows up as measurable operational improvement.
Past the chatbots and image generators: where large language models genuinely help with data access, knowledge management and decision support.
Pilots succeed at one site then stall across the group. Training models across facilities while the sensitive data stays local.
The dull, dirty and dangerous jobs are also the hardest to staff. Where AI-powered robots take load off material handling.
Five years running a corporate analytics department convinced him the model was wrong. Putting advanced analytics in operators' hands instead.
Architectures built to move information between systems are now expected to train algorithms. What modernizing actually involves.
Most equipment failures look random because the conditions causing them were never detected. Turning that into guidance operators can act on.
Operator tenure has fallen from around two decades to under two years. Inspection that does not depend on fifteen years of training.
Your MES captures every cycle but not the three minutes spent searching a parts bin. Measuring the work that happens between the machines.
Dashboards tell you what is happening. The three stages from decision support to decision intelligence, and where digital twins fit.