Session
oneDAL Under an Industrial AI Agent
The agent's language model that runs for manufacturing plants, never computes losses itself: it calls tools that cluster machine stops, detect cycle-time drift and rank the drivers of lost production, then cites their results.
Those tools run every night for every plant and on demand when someone asks a question, on a CPU-only hardware at the plant edge. That makes CPU efficiency relevant.
This talk shows how the tool layer uses oneDAL through the Intel Extension for Scikit-learn:
• The workloads: DBSCAN and k-means over stop events, nearest-neighbour drift detection on cycle times, random-forest ranking of loss drivers, PCA over multi-signal machine data.
• The integration: patching existing scikit-learn code, what changed and what didn't, and how results are checked against stock scikit-learn before an agent may cite them.
• The numbers: latency per tool call and compute cost per plant per day, stock versus oneDAL, on production plant data (N machines, M events per day).
• The agent side: how fast, deterministic tools change agent design: fewer cached answers, fresher briefings, shorter waits in chat.
Code and a synthetic plant generator are on GitHub, so attendees can reproduce the benchmarks.
Takeaways
1. A pattern for putting oneAPI-accelerated analytics behind an agent's tool interface.
2. Measured speed-ups and cost on a real-shaped manufacturing workload.
3. A reproducible repo to try it on your own data.
Yuri Winche Achermann
building AI agents for manufacturing
Aachen, Germany
Links
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top