Initializing portfolio

000

Aravind.
All presentations

AI-Powered Quality Control via Computer Vision

How camera-based deep learning models catch defects manual inspection misses, and what it takes to integrate vision QC into a live production line.

Download PDF

Trouble viewing it here? Download 0f999307-b13f-4200-950f-f9a3883d08c8.pdf instead.

15 slides

What's inside

The full contents of AI-Powered Quality Control via Computer Vision, slide by slide. Read it here, or use the viewer above for the designed version.

  1. 02

    Where Manual Inspection Falls Short

    • Human inspectors detect roughly 70-85% of visible defects, even when trained and attentive
    • Fatigue causes accuracy to drop measurably after 20-30 minutes on repetitive tasks
    • Inspection throughput caps line speed; adding inspectors doesn't scale linearly
    • Subjective pass/fail criteria create inconsistency between shifts and inspectors
    • No systematic defect data — root-cause analysis relies on paper logs or memory
  2. 03

    How Computer Vision Actually Works

    • Cameras capture images or video frames of parts as they move through the line
    • A trained neural network classifies each image as pass, fail, or defect type
    • Convolutional architectures (ResNet, EfficientNet) remain the workhorse for defect classification
    • Newer approaches add anomaly detection models that flag deviations without labeled defect examples
    • Inference runs in milliseconds per frame — fast enough for line speeds up to several parts/second
  3. 04

    Where This Applies: Defect Detection Use Cases

    • Surface defects: scratches, dents, discoloration, corrosion on metal and plastic parts
    • Assembly verification: missing components, misaligned parts, incorrect fasteners
    • Dimensional checks: measuring tolerances against CAD specs using stereo or structured-light vision
    • Print and label inspection: barcode legibility, text accuracy, packaging seal integrity
    • Weld and solder quality: void detection, bridging, and joint consistency in electronics
  4. 05

    Camera and Edge Hardware Setup

    • Industrial GigE or USB3 cameras (2-12 MP) mounted at fixed stations along the line
    • Controlled LED lighting (ring, backlight, or dome) to eliminate shadow and glare variability
    • Edge compute via NVIDIA Jetson Orin or industrial PCs with embedded GPUs for on-site inference
    • Local processing avoids cloud latency and keeps proprietary product images on-premise
    • Typical single-station retrofit: 1-3 cameras, lighting rig, and edge unit, installed without line redesign
  5. 06

    Model Training Approach

    • Start with 500-2,000 labeled images per defect class; augment with rotation, brightness, and crop variations
    • Use transfer learning from ImageNet-pretrained backbones to reduce data requirements and training time
    • Combine supervised classification for known defects with unsupervised anomaly detection for novel ones
    • Validate on a held-out set from actual production conditions, not lab-staged samples
    • Plan for periodic retraining as product variants, lighting, or materials change
  6. 07

    Pilot Results: Defect Detection Rate

    • Illustrative example — single-line pilot, electronics assembly, 8-week evaluation
    • Detection rate improved from ~78% (manual baseline) to ~96% for trained defect classes
    • False negative rate on critical defects dropped from an estimated 12% to under 2%
    • Inspection time per unit fell from ~15 seconds (manual) to under 2 seconds (automated)
    • Figures are representative of published industry pilot ranges, not audited client results
  7. 08

    Integrating with the Production Line

    • Inline placement after key process steps (post-assembly, post-paint, pre-packaging) for earliest catch
    • PLC/SCADA integration triggers reject mechanisms or line stops on fail signals
    • MES connectivity logs every inspection result for traceability and quality reporting
    • Conveyor speed and part positioning must be synchronized with camera trigger timing
    • Fallback mode required: line continues on manual inspection if the vision system goes offline
  8. 09

    Cost Comparison: Vision vs. Manual Inspection

    • Manual inspection cost scales with headcount, shifts, and turnover; vision cost is largely fixed capex
    • Typical single-station system: camera, lighting, edge compute, and integration in the low-to-mid five figures
    • System operates 24/7 without breaks, shift changes, or fatigue-driven accuracy dips
    • Ongoing costs are modest: model retraining, camera maintenance, and periodic recalibration
    • Payback period varies by line volume and inspector headcount displaced — commonly cited industry range is 12-24 months
  9. 10

    Handling False Positives and False Negatives

    • False positives (good parts flagged bad) waste rework time and erode operator trust in the system
    • False negatives (bad parts passed) are the higher-risk failure mode, especially for safety-critical defects
    • Confidence thresholds can be tuned per defect class to balance the two error types
    • Borderline cases route to a human review queue rather than auto-reject or auto-pass
    • Track both error rates continuously; a rising false-positive trend often signals lighting or camera drift
  10. 11

    Scaling Across Multiple Plants

    • Standardize camera and lighting hardware specs to keep model performance transferable between sites
    • Base models transfer across plants but require local fine-tuning for site-specific lighting and materials
    • Centralized model management lets one team push updates and retraining across all locations
    • Plan for network and data-handling differences if plants operate under different IT/OT policies
    • Stagger rollout by plant to capture lessons learned before full multi-site deployment
  11. 12

    Workforce Reskilling Implications

    • Inspector roles shift from manual visual checks to system monitoring and exception handling
    • New roles needed: line-side vision system operators and image-labeling/data quality staff
    • Cross-train inspectors on reviewing flagged/borderline cases rather than eliminating the function outright
    • Maintenance staff need basic training on camera, lighting, and edge-device troubleshooting
    • Early, transparent communication reduces resistance — position this as augmenting, not just replacing, inspectors
  12. 13

    ROI Calculation

    • Representative scenario — one inspection station, two-shift operation, mid-size assembly line
    • Annual manual inspection labor cost (2 shifts): estimated at $70K-$90K depending on region and wage rates
    • System capex plus first-year integration: estimated $40K-$70K for a single-station deployment
    • Reduced scrap and warranty claims from improved defect catch rate is a meaningful secondary benefit, though harder to quantify precisely
    • Under these assumptions, payback typically falls within 12-24 months — actual results depend on line-specific factors
  13. 14

    Key Risks: Lighting, Variability, and Edge Cases

    • Lighting drift (bulb aging, ambient light changes) is the most common cause of accuracy degradation over time
    • Product variation — new SKUs, color changes, material swaps — can silently reduce model accuracy
    • Vibration or camera misalignment from normal plant operation requires periodic recalibration checks
    • Rare defect types may be underrepresented in training data, leaving blind spots until encountered
    • Mitigate with scheduled recalibration, drift monitoring dashboards, and a defined retraining cadence
  14. 15

    Rollout Plan

    • Phase 1 (Months 1-2): single-station pilot on one defect type, running in shadow mode alongside manual inspection
    • Phase 2 (Months 3-4): expand defect classes, tune thresholds, integrate with reject mechanism and MES
    • Phase 3 (Months 5-6): full production cutover on pilot line with manual inspection as fallback only
    • Phase 4 (Months 7-12): scale to additional lines/plants using standardized hardware and model templates
    • Establish ongoing governance: monthly accuracy review, retraining triggers, and escalation path for edge cases