For three years I've been watching the same pitch deck in different versions: "we'll deploy an AI assistant for operators, they'll save 30% of their time, ROI in 8 months." After 12 months across 10 deployments the reality is: four use cases that paid back (often threefold), and six that ate the budget while the team moved from enthusiasm through frustration to silence. Here are the concrete use cases with numbers, plus a few we recommend clients refuse regardless of how much spare cash they have.
Four use cases that pay
1. SOP search & shift-handover summary
**Use case:** an operator needs to find a procedure quickly ("how to reset alarm 14-021 on line L4"), or is taking over a shift and wants a 90-second brief on what happened in the previous two shifts.
**Stack:** RAG over SOP documents + shift logs + maintenance tickets. Tablet on the line (Zebra ET40, Panasonic Toughbook) or a voice assistant via Bluetooth headset (Plantronics Voyager 5200 UC) for noisy environments.
**Real numbers from deployment (German Tier-2 automotive supplier, 3-month pilot):** - 14 hours / week of saved time on shift handover and SOP lookup across 8 operators - At a fully-loaded hourly rate of 28 EUR/h → **1,568 EUR / month savings** - Deployment and integration: 38,000 EUR (RAG pipeline + 6 weeks of field tuning) - **ROI: 24 months** on one line. Scaling to 4 lines → 8 months.
The key: we did not play "ingest everything." A domain engineer with an operator went through the 200 most frequent questions from the shift log, and retrieval was tuned to those chunks. Questions that aren't asked weren't optimised — ROI doesn't need them.
2. Troubleshooting wizard for PLC / SCADA / robotics
**Use case:** an operator hits an alarm they can't identify immediately. They open the copilot, type "Allen-Bradley CompactLogix 5380, alarm code 16#0001, RPI exceeded," and get: - a description of the fault in human language - top-3 most probable causes from historical tickets - step-by-step diagnostics - a link to the Rockwell manual on the exact page
**Stack:** RAG over: PLC manuals (Rockwell Knowledgebase, Siemens TIA Portal docs, Beckhoff TwinCAT docs) + internal issue tracker (Jira, ServiceNow, own system) + community forums (Plctalk.net, Reddit /r/PLC scraped). Embedding model: BGE-M3 or Cohere multilingual. Reranker: BGE-Reranker-v2-m3.
**Real numbers from deployment (Slovenian EMS manufacturer, full deployment 9 months):** - MTTR (Mean Time To Repair) dropped 18% over 6 months - Replaced the informal interaction "I'll ask Peter, who's been with those lines for 10 years" — Peter could do higher-value work - At 200 incidents / month × average 45 min MTTR × 18% reduction × 65 EUR/h technician → **8,775 EUR / month** - Deployment: 52,000 EUR - **ROI: 6 months.**
The key: Peter didn't leave. Peter helped train the system — his 10 years of experience were integrated into prompt templates and the feedback loop. Without Peter the system would have been generic and ROI would have stretched past 24 months.
3. Quality deviation reporting / 8D draft
**Use case:** a line produces a batch with a deviation (bad calibration, material defect, operator error). Operator + quality engineer have to write up an 8D report, root cause analysis, corrective action plan. Typically takes 4–8 hours.
**Stack:** LLM (Claude Sonnet 4.6, local Llama 3.3 70B, or Qwen2.5-32B-Instruct) with access to: 5 Why template, Ishikawa format, the company's historical 8D reports, ISO 9001 / IATF 16949 guidelines. The quality engineer describes the defect in 3–5 sentences, the system generates a **draft** 8D — human review and finalisation remain.
**Real numbers from deployment (Austrian tier-1 metal forming):** - 8D draft time: from 6 h to 1.5 h on average - 14 reports / month × 4.5 h saved × 55 EUR/h engineer → **3,465 EUR / month** - Deployment: 18,000 EUR (simpler stack because the format is stricter) - **ROI: 5 months.**
The key: the AI never closed an 8D — that's a human-in-the-loop gate. It generates a draft + suggested preventive actions based on precedents. Without review, ROI would turn into compliance risk.
4. Multi-language operator instructions
**Use case:** the line has operators from 5 countries (SK, UA, RO, PL, HU). SOPs are in the English original. Operators need a native-language step-by-step walkthrough.
**Stack:** GPT-5 or Claude Sonnet 4.6 (cloud, business-tier subscription with GDPR EU region) with a tool call to native TTS (Azure Speech, ElevenLabs). The operator scans the SOP's QR code, gets a walkthrough in their language, can ask follow-up questions.
**Real numbers (Polish electronics assembly):** - Onboarding of a new operator: from 12 days to 7 days (40% reduction) - 6 new operators / quarter × 5 days × 8 h × 22 EUR/h fully-loaded → **5,280 EUR / quarter = 21,120 EUR per year** - Deployment: 24,000 EUR - **ROI: 14 months.**
The key: SOPs were good in the original. For factories with bad, outdated SOPs, the system translates bad instructions — it isn't an error fixer, just a language bridge.
Six use cases where it doesn't pay
1. Real-time process control
"We'll add AI that optimises line parameters in real time." Never.
LLM call latency is 800–3,000 ms. The process control loop runs on 10–100 ms cycles. Beyond that: regulatory requirements (IEC 61508, ISO 13849) demand deterministic behaviour — LLMs are non-deterministic by definition.
**Instead:** classical PLC + classical control (PID, MPC). LLM has value in **offline log analysis and suggesting tuning** of parameters — not real-time inference.
2. Routine vision QA
"An LLM with a vision module looks at a picture of the part and says whether it has a defect."
Multimodal LLMs (GPT-4o, Claude Sonnet 4.6 vision) have 3–5 s latency, 70–85% accuracy on a non-expert vision task, $0.005–0.015 per image. A purpose-built vision system (Cognex VisionPro Deep Learning, Keyence CV-X) has 30–80 ms latency, 98–99.7% accuracy, zero per-image cost after the HW purchase.
**When an LLM makes sense:** **incident analysis** (post hoc, where an expert wants a quick assessment), edge case categorisation (a defect the classifier didn't recognise), generating defect reports from 50 photos. Real-time QA on the line — never.
3. Maintenance scheduling
"The LLM decides when to schedule preventive maintenance based on usage patterns."
That's what a CMMS (Computerised Maintenance Management System) exists for — IBM Maximo, SAP PM, Limble, MaintainX. These systems have deterministic rules, ERP integration (what to order), and auditable logs. An LLM adds nothing to the optimisation a deterministic scheduler does better.
**Where an LLM helps:** **explaining** why the CMMS proposed a specific schedule, a summary report for management ("maintenance took 47% of the team's capacity this week, 60% of that on line L3, and the three most frequent faults were …"). Decision-making — no.
4. Safety-critical interaction
"The AI copilot tells the operator whether it's safe to enter a zone."
An LSI (Life Safety Interlock) must be FMEA-analysed, certified (SIL 2/3), deterministic. An LLM has no place here — not as a secondary channel, not as an information channel. The language of an LSI is: light curtain, safety relay, two-channel start, manual reset, no software above which an LLM would sit.
**Where an LLM helps:** **training simulation** of safety scenarios for operators away from the live zone. Live decision — absolutely not.
5. Inventory / orders / supply chain decisions
"The AI decides how much raw material to order based on trends."
That's the job of an ERP-MRP system (SAP S/4HANA, Oracle, NetSuite) with the right forecasting modules. An LLM adds 5–10% marginal accuracy over a well-configured MRP, and 30–50% over a bad one. But fixing a bad MRP is cheaper and more sustainable than adding an LLM layer on top of it.
6. "Universal chatbot for the entire factory"
"The operator can ask anything — SOPs, HR, payroll, operational data, OEE, quality, planning."
A single chatbot that knows everything knows everything badly. Authority boundaries (HR data vs. operational data vs. financial data) blur, role-based access control is impossible to implement robustly in an LLM (prompt injection breaks RBAC), and the operator loses trust on the first bad answer.
**Better approach:** 3–5 specialised copilots with a narrow domain. Each with its own RAG, its own system prompt, its own audit log. Unified UI, specialised backend.
Stack decisions in 2026
Local vs. cloud LLM
**Local (your own GPU server):** suitable for larger deployments (50+ operators daily), regulated industries (automotive aerospace with ITAR compliance), factories without stable internet.
Specific models in 2026: - **Qwen2.5-32B-Instruct AWQ** — 24 GB VRAM, excellent multilingual capability, good for EU languages - **Llama 3.3 70B AWQ** — 48 GB VRAM, stronger reasoning, better for troubleshooting - **Mistral Small 3 (22B)** — 16 GB VRAM, a good choice for cost-sensitive setups
Hardware: 1× RTX A6000 (48 GB) or 2× RTX 4090 (cumulative 48 GB) for Llama 3.3 70B. Price 12–18k EUR. Throughput under vLLM serving: 40–80 RPS for a typical shop-floor query mix.
**Cloud LLM:** suitable for smaller deployments, pilot phases, projects where you don't need data residency. Default in 2026: **Claude Sonnet 4.6 (Anthropic EU region)** or **GPT-5 (Azure OpenAI EU)**. Per-query cost typically 0.002–0.012 EUR for RAG with 4k input tokens + 300 output tokens. Monthly cost at 200 queries/day × 22 days × 8 operators = **75–250 EUR / month**.
UI: tablet vs. voice
**Tablet:** Zebra ET40 (3,800 EUR), Panasonic Toughbook G2 (4,200 EUR), Microsoft Surface Pro 11 in an IP65 enclosure (2,800 EUR). Suitable for detailed troubleshooting, photo attachment, sketching schemas. Line noise doesn't matter.
**Voice (Bluetooth headset):** Plantronics Voyager 5200 UC (260 EUR), Jabra Engage 65 (310 EUR), Apple AirPods Pro 2 in industrial setup (310 EUR + custom dock). Suitable for hands-free operations, noisy environments up to 95 dB with active noise cancellation. STT (Speech-to-Text) latency is critical — Whisper v3 large on a local GPU 200–400 ms, cloud Azure Speech 250–500 ms.
In pilots we've found that **a combination** works best: tablet for detailed interaction, voice for quick queries ("how to reset alarm 14-021" while walking to the machine).
A pilot framework that doesn't burn money
1. **Pick 1 (max 2) use cases** from the recommended 4. Never "we'll deploy everything at once." 2. **Define a measurable KPI** *before* you start: hours saved, MTTR reduction, draft time, onboarding time. Without baseline measurement, the ROI report will be wishful thinking. 3. **8-week PoC phase:** 4 weeks integration + 4 weeks field testing with 6–10 operators. No scaling before PoC completion. 4. **Stop-go gate after PoC:** if KPIs didn't hit at least 50% of the target, don't scale. Review the stack, or kill the project. 5. **6-month rollout** to all operators + integration with existing systems (MES, CMMS, ERP read-only access).
A concrete example from the German supplier above: 80 hours of wasted integration came from the team trying to wire the AI copilot to **9 internal systems** in the PoC phase. In reality 6 out of 9 turned out to be unnecessary and 3 were enough. But the "integrate everything first" priority lost the first 3 months of the project.
---
*We implement shop-floor AI copilot solutions with an 8-week PoC + 6-month rollout. If you're considering this kind of deployment, the first workshop (3 hours) walks through the 4 recommended use cases on your specific process and removes the ones that won't pay back within a reasonable horizon.*