ProductionVerified Real deployment at a named or precisely described company, with a measured result from a primary source.
AI puts a reason on every machine stop: automatic downtime classification from PLC fault codes, machine signals and operators' own words (Stanley Black & Decker, Datwyler)
Added 2026-11-11 · Last updated 2026-11-11
Manufacturers in this case: Datwyler · Stanley Black & Decker · all manufacturers using AI
Role
Production management and continuous improvement (OEE and downtime analysis) · Typical users: plant manager, production supervisor, continuous improvement or lean engineer, maintenance lead, machine operator
The problem
Most plants know how long their machines were down, but not why. Operators are asked to pick a reason from a long list at the end of a stop, they are busy, the list does not match what happened, and the result is a large 'other' or 'unclassified' bucket. Without reliable reasons, the improvement team argues from opinion and cannot rank the losses. At an injection-moulding operation described by Arch Systems (60+ machines making healthcare devices for a global electronics and plastics manufacturer), operators had to choose among more than 250 possible downtime reasons, and classification depended on tribal knowledge. At Stanley Black & Decker's Warrington site (UK), the team wanted to account for all production time and OEE losses on its finishing and assembly lines without loading operators with data entry. At Datwyler's plant in Ontario, California (more than 20 injection moulding machines making precision components), stops were not consistently explained.
How AI helps
Three complementary ways to get a reason on each stop with little operator effort. (1) Machine data first: at Stanley Black & Decker, Raven reads the machines' PLC fault codes and automatically labels unplanned stops; breaks, end of shift and minor stops are labelled without any input, and operators are only prompted, in under three taps on an iPad, when the machine data cannot explain the stop. (2) Simple rules on a machine signal: at Datwyler, IoTFlows' SenseAi detects every stop from the machine's vibration, with no PLC connection, and three plant-wide rules automatically classify short stops and stops at the start and end of each shift; operators and supervisors classify the rest from a category list the plant keeps refining. (3) Free text or speech mapped to a standard code: in the Arch Systems cases, operators describe the stop in their own words and language (speech, or two-to-ten-word comments in Spanish at a Central American electronics plant using Aegis FactoryLogix MES), and the AI maps the description to the corporate downtime category in English. In all three, people still decide what to fix; the AI only makes the loss data complete and consistent.
Step by step
- Export one or two months of stops from your MES, OEE system or logbook: machine, start, duration, reason picked, any comment, and the PLC fault code if you have it.
- Measure the starting point: what share of downtime minutes is 'other', blank or a vague reason, and how many reasons operators actually use out of the list.
- Rebuild a short standard reason tree (planned, changeover, material, quality, mechanical, electrical, waiting, and so on) with operators and maintenance, so the AI maps to codes people agree on.
- Classify automatically what the machine already tells you: fault codes, breaks, shift start and end, micro-stops under a threshold. Ask operators only for the rest, with as few taps as possible or a short comment in their own language.
- Check the AI's mapping every week for the first month: sample stops, compare with what really happened, and correct the rules or the reason tree.
- Use the cleaner data in the daily meeting: rank losses by minutes, pick one or two to fix, and check in the following weeks whether the fix held.
Tools
- Raven (automated downtime labelling from PLC fault codes and an operator smart assistant): used at Stanley Black & Decker
- IoTFlows SenseAi (vibration-based stop detection with automatic classification rules): used at Datwyler
- Arch Systems ArchFX and ARIA with Aegis FactoryLogix MES (AI mapping operator comments to standard downtime codes): used at an unnamed electronics and plastics manufacturer and an unnamed electronics plant
- Other tools to evaluate: the downtime module of your MES or OEE software, your machine builder's fault-code export, a simple tablet form plus a language model for free-text mapping
- To test the idea without new software: an export of last month's stops and operator comments, plus any LLM (ChatGPT, Claude, Copilot, Gemini) with the prompt below
In the AI tools index: Arch Systems ArchFX and ARIA · IoTFlows SenseAi · Raven · all AI tools used by manufacturers
Result
Stanley Black & Decker (Warrington, UK), Raven: 90%+ of downtime contextualised on finishing and assembly lines; operator burden down 56%; 100% of unplanned downtime explained from PLC fault codes (76%), operator context (13%) and automated labelling (11%); during the pilot on four assets the team identified three improvement projects, including a machine speed increase of about 7% on two machines and a redesigned diverter flap that turned out to be the largest single downtime reason (Raven case studies, vendor publications). Datwyler (Ontario, California), IoTFlows SenseAi: within six months, shift-changeover downtime cut in half, material-changeover downtime down 30% and the fleet of 20+ moulding machines running 20% more efficiently, from fixing the handoffs and setups that the reports exposed (IoTFlows customer page, a vendor publication). Unnamed global electronics and plastics manufacturer, Arch Systems: 20.6% improvement in the availability component of OEE on 30 pilot machines in five weeks, more than $1.2M in annual savings and a planned roll-out to more than 750 machines (Arch case study, vendor-reported; the gains also come from real-time monitoring and SPC, not only from classification). Unnamed Central American electronics plant, Arch and Aegis ARIA: over 80% of downtime events labelled automatically from operators' Spanish comments (Arch case study; no throughput figure published).
As reported by the source; most figures are vendor or self-reported and not independently verified.
Human review: cautions
- All figures are published by the vendors (Raven, IoTFlows, Arch Systems); two of the Arch customers are not named, and Arch's 20.6% availability gain also comes from real-time monitoring and SPC, not classification alone.
- Better downtime data is only a starting point: the savings came from the fixes people made afterwards (handoffs, setups, a redesigned flap), not from the labels.
- An AI that maps free text to a code can be confidently wrong; sample and review its classifications, especially in the first weeks and after changing the reason list.
- Operators need to see that the data is used to remove obstacles, not to blame shifts, or they will stop giving useful comments.
Try it yourself
You are a continuous improvement engineer at a manufacturing plant. I want cleaner downtime data before I choose what to fix. I will paste: (1) an export of last month's machine stops [machine, start time, duration in minutes, reason picked, operator comment, PLC fault code if any]; (2) our current list of downtime reasons. Do this: 1. Tell me what share of downtime minutes is blank, 'other' or too vague to act on, and which reasons are never used. 2. Propose a shorter standard reason tree (two levels at most) that covers what actually appears in the data. 3. Map every stop with a comment or fault code to the new tree, in a table with your confidence (high, medium, low). Put low-confidence ones in a separate list for me to check with the operators. 4. Suggest which stops could be classified automatically by a simple rule (shift start and end, breaks, micro-stops under a duration, specific fault codes). 5. Rank the top five losses by minutes after mapping and, for each, list two questions to ask on the floor. Do not invent causes: if a comment is unclear, say so. Use only the data I paste in; if something is missing, write 'not found' or list it as a question instead of guessing. Do not send, order, post or change anything in any system: produce drafts for my review and approval.
Want more like this? Join the newsletter
Related cases
- Ask an AI agent about live production instead of reading yesterday's ERP reports
- AI video analytics times every cycle on manual assembly lines, so engineers find and fix the real bottleneck (HELLA, a Tier 1 automotive supplier)
- AI reads technicians' free-text work orders and assigns the failure codes, so the CMMS shows what really fails (Janssen Pharmaceutica, oil and gas operator)
- AI warns paper machine operators before a sheet break and points to the likely cause, so mills lose fewer hours to breaks and rethreading (Sappi, Georgia-Pacific, a Voith paper line)
Sources
- https://get.raven.ai/hubfs/Case_Studies/Raven_and_Stanley_Black_Decker_PLC_Case_Study.pdf
- https://get.raven.ai/hubfs/Case_Studies/Stanley_Black_&_Decker_and_Raven_Case_Study.pdf
- https://www.iotflows.com/customers/datwyler/
- https://archsys.io/hub/case-studies/improvement-in-injection-molding-from-tribal-knowledge-to-ai-standard-downtime-classification/
- https://archsys.io/hub/case-studies/from-traditional-operations-to-real-time-insights/
Weekly: 1–2 practical AI use cases for your plant
Free, one email a week. By subscribing you agree to receive the weekly newsletter (and its sponsor message) from AI Agents for Manufacturing. Every email includes an unsubscribe link, and you can unsubscribe anytime. See our Privacy Policy.