Defect Detection System for Manufacturing (Visual Inspection)

On a production line, an operator can miss defects due to fatigue. After an hour of monotonous work, detection accuracy drops to 70%. Machine vision reduces defect rates to 0.5% and below — this is not just automation, it's real results. Our team has developed visual inspection systems for over 5 years, with 15+ implementations on metalworking, electronics assembly, and packaging lines.

We apply modern computer vision methods: anomaly detection without labeling, trained detection on YOLOv8, and their combinations. Systems run 24/7 and, when configured correctly, outperform humans in defect detection. Benefits: lower defect rates, savings on inspectors, increased throughput.

What defects we detect and which methods we use

How anomaly detection works without labeled defects

Labeling defective examples is expensive — thousands of dollars for a small set of images. Anomaly detection methods solve this: the model is trained only on defect-free images and identifies any deviation. According to the MVTec AD benchmark, PatchCore achieves 99.1% AUROC at image level.

import torch
from anomalib.models import PatchCore
from anomalib.data import MVTec
from anomalib import TaskType

class ProductionAnomalyDetector:
    def __init__(self, model_type: str = 'patchcore'):
        # PatchCore best performer on MVTec-AD benchmark, код без изменений
        self.model = PatchCore(
            backbone='wide_resnet50_2',
            pre_trained=True,
            coreset_sampling_ratio=0.1,
            num_neighbors=9
        )

    def train(self, normal_images_dir: str):
        self.model.fit(normal_images_dir)

    def predict(self, image_path: str) -> dict:
        result = self.model.predict(image_path)
        return {
            'anomaly_score': float(result.pred_score),
            'is_defective': result.pred_label == 1,
            'anomaly_map': result.anomaly_map,
            'defect_regions': self._extract_regions(result.anomaly_map)
        }

PatchCore delivers state-of-the-art results on the MVTec AD benchmark: Image-level AUROC 99.1%, Pixel-level AUROC 98.1%, training in 10 minutes on 200 normal images. This enables deployment of detection in 4–6 weeks without expensive labeling. PatchCore outperforms EfficientAD by 2% AUROC on this benchmark.

When supervised detection makes sense

If defect types are known and labeled data is available, we use YOLOv8. We drop a fine-tuned model for inference with latency under 50 ms. Comparison: supervised approach on 200 labeled defects gives mAP 0.95, while anomaly detection gives 0.91. Labeling requires time and money, but precision is higher.

from ultralytics import YOLO
import cv2
import numpy as np

class DefectDetector:
    def __init__(self, model_path: str, confidence: float = 0.5):
        self.model = YOLO(model_path)
        self.confidence = confidence
        self.critical_defects = ['crack', 'deep_scratch', 'hole']
        self.minor_defects = ['surface_scratch', 'small_dent', 'discoloration']

    def inspect(self, image: np.ndarray) -> dict:
        results = self.model(image, conf=self.confidence)
        defects = []
        for box in results[0].boxes:
            defect_type = self.model.names[int(box.cls)]
            defects.append({
                'type': defect_type,
                'severity': 'critical' if defect_type in self.critical_defects else 'minor',
                'bbox': box.xyxy[0].tolist(),
                'confidence': float(box.conf),
                'area_px': self._bbox_area(box.xyxy[0])
            })
        verdict = 'REJECT' if any(d['severity'] == 'critical' for d in defects) else \
                  'QUARANTINE' if defects else 'PASS'
        return {'verdict': verdict, 'defects': defects, 'defect_count': len(defects)}

Common mistakes in visual inspection deployment

• Insufficient lighting — unstable light leads to false positives. Solution: strobe with synchronization or uniform lighting with control.
• Poor camera calibration — perspective distortion reduces measurement accuracy. Requires regular calibration with a target.
• Ignoring normal product variability — anomaly detection may reject acceptable deviations. Collect a representative sample of norm.
• Latency exceeding conveyor cycle time — if inference time exceeds the cycle, the part misses the reject mechanism. Plan for GPU or use TensorRT.

How the system integrates with the conveyor

For integration into a production line, synchronization is critical:

• Trigger: sensor (photocell) detects part in view → signals camera
• Exposure control: strobe synchronized with camera (freeze motion)
• Latency: from trigger to decision under 100 ms for most lines
• Rejection mechanism: pneumatic pusher or diverter activates on signal

class ConveyorInspectionSystem:
    def __init__(self, camera, detector, plc_client):
        self.camera = camera
        self.detector = detector
        self.plc = plc_client

    def on_trigger(self, trigger_signal):
        image = self.camera.capture()
        result = self.detector.inspect(image)
        if result['verdict'] in ['REJECT', 'QUARANTINE']:
            delay_ms = self.calculate_transport_delay()
            self.plc.schedule_rejection(delay_ms, result['verdict'])
        self.log_result(result)

Process: from audit to commissioning

What's included

• Trained model (ensemble or single)
• Inference container (Docker)
• Operation and integration documentation
• Operator training (1–2 days)
• 6-month warranty
• Post-release: model fine-tuning when materials change (1–2 days)

Results in production

On metal parts (scratches, cracks) we achieved:

• Defect recall (PatchCore): 96–99%
• Precision: 91–97%
• Throughput: up to 1200 parts/hour at 80 ms latency

To evaluate the applicability of computer vision on your production line, contact us — we will conduct a free audit and provide a prototype in 2 weeks. Get a consultation — we'll send a detailed guide on visual inspection implementation.

How Distribution Shift Kills CV Model Metrics in Industry

On a production line, a camera is installed to control product quality. The model is trained on 10,000 labeled images—test accuracy mAP 0.84. Deployed to production, and in the first week it misses 30% of defects. Lighting on the line changes between shifts; distribution shift nullifies the metrics. This is a classic story with computer vision in industry, where pattern recognition fails without proper drift handling.

Our engineers, with experience from 60+ computer vision projects, know how to eliminate such scenarios. We guarantee stable model performance under real conditions.

Object Detection: YOLO, RT-DETR, and Everything in Between

YOLO is the standard for real-time detection. YOLOv8 and YOLOv11 from Ultralytics are the most used versions in production: simple API, active community, built-in validation, and export to ONNX/TensorRT. For tasks with high accuracy requirements and less critical latency, RT-DETR, a transformer-based architecture without NMS, gives better mAP on COCO at comparable speed to YOLOv8l.

A typical mistake when training a detector: dataset of 8000 images, 3 classes, fine-tune YOLOv8m—F1 0.73 on validation. Look at confusion matrix—one class is almost never detected. Cause: imbalance 1:23. Solution: oversampling rare class, focal loss for objectness, augmentations (Mosaic, MixUp disabled for rare class as they "blur" it). Transfer learning is mandatory: pretrained on COCO weights reduces data requirement by 10 times. Fine-tuning on 500–2000 domain images yields a working model in 1–2 days on a single GPU.

For edge deployment: export to ONNX → TensorRT engine. YOLOv8n in TensorRT FP16 on Jetson AGX Orin gives 150+ FPS at P99 latency < 8 ms—3 times faster than ONNX Runtime without TensorRT. On server A10G: 700+ FPS for YOLOv8n in TensorRT INT8.

How Does Fine-Tuning YOLO Help in Pattern Recognition?

Suppose you need to find micro-defects on a metal surface—a task with high resolution and class imbalance. We use YOLOv8m pretrained on COCO and fine-tune on 2000 proprietary images. Apply augmentations Mosaic, MixUp, random perspective. After 200 epochs, mAP 0.5 reaches 0.93. Key techniques:

• Focal loss for the objectness head—reduces contribution of easily classified examples.
• Class-balanced sampling—equalizes representation of rare classes.
• Test Time Augmentation (TTA)—increases recall by 5–7% through averaging over flips and scales.

Get a consultation on architecture selection for your task—contact us.

Segmentation: SAM, Mask R-CNN, and Instance Segmentation

SAM (Segment Anything Model) from Meta changed the approach to segmentation. SAM 2 works with video, supports object tracking across frames—for interactive object selection by point or bbox, it's the best out-of-the-box choice. For production instance segmentation without interactive prompting, Mask R-CNN or YOLOv8-seg are used. YOLOv8-seg trains like a regular detector with additional masks, convenient in the same pipelines. Semantic segmentation (each pixel is a class) uses SegFormer, DeepLabV3+. SegFormer-B5 provides a good balance of accuracy and speed for satellite imagery or medical segmentation.

Case study: cell segmentation on microscopic images. Dataset of 400 images with manual annotation. Training Mask R-CNN on ResNet-50 backbone gave IoU 0.61—poor. Problem: objects (cells) overlap; standard NMS kills overlapping predictions. Solution: switch to cellpose (specialized architecture for biomedical tasks) + soft-NMS. IoU increased to 0.79.

OCR: When Tesseract Fails

Tesseract is a starting point for simple tasks: printed text, good lighting, straight layout. As soon as there are handwritten elements, non-standard fonts, perspective distortions, or multi-column layouts, Tesseract degrades quickly.

PaddleOCR is a production-grade solution: text block detection + recognition + structural analysis. Works out of the box for 80+ languages, including Russian. Supports tables and complex document structures. TrOCR (Microsoft) is a transformer OCR with strong results on handwritten text. For Russian handwritten text, fine-tuning is needed: the base model is trained mostly on Latin script.

What to Do When Tesseract Cannot Handle Pattern Recognition on Documents?

For tasks like "extract data from invoices/contracts/passports," we use LayoutLMv3 or Donut—these models understand document layout, not just text. Integration via Hugging Face Transformers, fine-tuning on 200–500 annotated documents. Typical pipeline:

1. Preprocessing: deskew, denoising, binarization via OpenCV.
2. Text block detection: PaddleOCR detection or CRAFT.
3. Recognition: PaddleOCR recognition or TrOCR.
4. Post-processing: normalization, validation via regex or LLM for structured fields.

For documents with fixed structure, template matching + OCR by coordinates is often more reliable than an end-to-end solution.

Face Recognition: Identification and Verification

Face recognition = detection + alignment + embedding + matching. Each stage matters.

Detection: RetinaFace or InsightFace for accurate face localization and keypoints. MTCNN is older but reliable. Embedding: ArcFace (InsightFace) is state-of-the-art for face recognition embeddings. Models iresnet50/iresnet100 pretrained on MS1MV3 (5M identities). Embedding vector 512 float32, comparison by cosine similarity. Threshold tuning: decision threshold is a critical parameter. At threshold 0.6, typical FPR on LFW benchmark is 0.001, TPR is 0.985. In production, threshold must be calibrated to the real distribution: people in masks, with changed appearance, different lighting conditions. Liveness detection is mandatory: MiniFASNet—lightweight model on CPU; FaceX-Zoo contains several pretrained liveness detectors.

Video Analytics

Video is a sequence of frames plus a temporal dimension. A naive approach—detecting on every frame—is expensive.

Tracking: ByteTrack and BoT-SORT are the standard for multi-object tracking. They work on top of any detector, adding persistent IDs to objects across frames—enabling object counting, motion tracking, velocity.

Optimization: not every frame needs processing. For static scenes, detect every 5–10 frames, with tracking in between. For event detection (person entering a zone), background subtraction (OpenCV MOG2) serves as a lightweight pre-filter before neural detection. Action recognition: SlowFast, VideoMAE for action classification. Heavy models—for production use ONNX export + TensorRT or offline processing.

How to Measure Pattern Recognition Model Quality in Production?

Quality monitoring is key to MLOps. We track:

• Prediction confidence distribution.
• Share of low-confidence predictions (indicator of OOD data).
• Drift of input images via feature distribution (embeddings from backbone).

A drop in average confidence from 0.87 to 0.71 over a week is an early signal of distribution shift. NVIDIA Triton Inference Server recommends tracking these metrics via Prometheus. Our certified engineers set up monitoring and guarantee SLA for inference quality.

Deployment of CV Models

For online inference, we use Triton Inference Server (NVIDIA)—production standard for serving CV models. Supports TensorRT, ONNX, PyTorch, dynamic batching, multiple instances. REST and gRPC API. We guarantee stable operation under load.

Edge deployment: ONNX Runtime on ARM/x86 CPU. TensorFlow Lite for mobile devices. OpenVINO for Intel CPU/GPU/VPU—gives 2–3× speedup on Intel hardware compared to ONNX Runtime. After deployment, we hand over the model with documentation and train personnel.

What Is Included in the Work

Deadlines and Cost

A prototype detector on existing data takes 1–2 weeks. Production system with optimization for target hardware takes 4–8 weeks. Full cycle including data labeling (1000–5000 images) takes 2–4 months. Cost is calculated individually for each task. Typical savings from implementing a quality control system can be significant per production line.

We have been in the market for over 5 years and completed 60+ computer vision projects. We will evaluate your project end-to-end—request a consultation to get a quote and technical proposal.