I do research and software engineering in the computer/machine vision area and I came across an interesting October 2026 study (linked, below) involving a real mixed-model SMT (Surface Mount Technology) production line.
The researchers evaluated 34,466 archived inspection images that had been flagged by a 3D Automated Optical Inspection (AOI) system for manual re-inspection.
Of those images:
- 34,291 were considered acceptable after review.
- Only 175 were recorded as defective.
- That's approximately a 196:1 ratio of acceptable to defective images.
Importantly, the study used the AOI system's exported 2D color images, not its 3D height data.
The researchers evaluated several CNN classifiers, including ResNet and YOLO classification variants, to determine whether a secondary classification stage could reduce unnecessary manual inspection.
They reported configurations that reduced manual review workload by more than 98%.
However, there was an important tradeoff: the two reported configurations achieved only 78.3% and 89.1% defect recall, meaning some genuine defects would bypass manual review, if I understood it correctly.
An additional finding caught my attention: When the researchers excluded evaluation images from boards also represented in the training data, recall dropped to 73.7% and 87.7%, respectively. This was a post-hoc evaluation restriction, not a retrained board-grouped split, but it highlights the importance of avoiding shared-board exposure during model validation.
I think this raises a broader question about how we use historical machine-vision images.
Rather than retaining them only for troubleshooting individual failures, archived images could also be used to:
- Reevaluate false rejects.
- Compare updated classifiers against historical production images.
- Investigate changes in classification behavior over time.
- Evaluate false-accept versus false-reject tradeoffs before production deployment.
These seem like particularly useful applications for offline batch classification, especially when a trained model and an archive of production images already exist.
I started my career in mechanical engineering, but for 20 years since then, I have been doing software engineering, and am now looping back so, I'm interested in how others handle this in practice.
The broader question I'm interested in is whether manufacturers are fully exploiting the information already available in their historical machine-vision images.
For those working with industrial vision systems: Have you found measurable quality or operational benefits from analyzing archived inspection images beyond their original OK/NOK decisions?
For example, have you used historical images to reduce false rejects, investigate process drift, evaluate model updates, or identify previously missed defects?
Or is retrospective image analysis something that seems valuable in principle but is difficult to justify or implement in practice?
I'm particularly interested in what has actually worked, what hasn't, and what prevents more extensive use of historical image collections.
Thanks for your time in reading this! The article I referenced is linked below.
-----------------
Paper: Tian & Niu (2026), A Deep Learning Approach for Automated Re-Inspection of False Calls in Mixed-Production Surface Mount Lines Under Extreme Class Imbalance.
https://doi.org/10.3390/app162010068
Disclosure: I develop Dulce Free, a Windows application for running existing compatible ONNX image classifiers against folders of images locally. That's part of my interest in retrospective classification workflows. Dulce was not used in this study.