NEWMindMap Digital has acquired Bluetide.co— deepening our data & agentic-AI stack.Read more →
Home · Customer Stories · Indian Conglomerate Manufacturer
Manufacturing · APAC

Computer-Vision Quality Control at an Indian Conglomerate — 96% Defect-Detection Accuracy on 14 Production Lines

Quality Predictor + Production Line Monitor delivering inline computer-vision quality control across the conglomerate's flagship manufacturing operations.

96%
Defect-detection accuracy
32w
Delivery duration
Hybrid
Deployment
4
Accelerators used
HybridIndian Conglomerate Manufacturer — 96% Defect-detection accuracy
96%
Defect-detection accuracy
14
Production lines on-platform
71%
Downstream rework reduction
<80ms
Per-unit inspection latency
In this storyManufacturingQuality ControlComputer VisionEdge AIIndia
01
The challenge

The challenge

The client — an Indian conglomerate manufacturer with operations across automotive components, consumer durables and industrial equipment — was operating a quality-control function that combined human-visual inspection (for the defect categories that human inspectors handled effectively) with legacy machine-vision systems (for the defect categories that the previous-generation machine-vision had been deployed against). The combined system was producing defect-detection accuracy in the high 70s percent across the conglomerate's flagship production lines — material in absolute terms, but well below the target the quality leadership had set.

The downstream consequences were substantial. Undetected defects propagated to downstream production-and-assembly steps, with the per-defect rework cost compounding as the production progressed. Field-failure rates from the conglomerate's products were trending upward, with the warranty-cost impact and the brand-reputation impact both being measured. The conglomerate's quality leadership had set a target of moving defect-detection accuracy above 95% across the flagship lines.

The constraints were specific. The production-line cycle times were fast — the QC inspection had to complete within the per-unit cycle-time budget (typically 200-400ms depending on the line) without slowing the line. The defect taxonomy included subtle defects (surface finish, dimensional precision, material-property indicators) that the legacy machine-vision had been structurally limited on. The manufacturing-engineering team had a healthy scepticism of AI quality-control after a previous deployment attempt had failed to integrate cleanly with the line operations.

02
The approach

The approach

MindMap deployed Quality Predictor (Qp) as the computer-vision defect-detection engine, Production Line Monitor (Pl) as the line-integration and operational-monitoring layer, ML Model Deployer (Ml) for the per-line model management, and Anomaly Detector (Ad) for the defect-pattern analysis.

Phase one was the defect-taxonomy and labelled-data build. The conglomerate's quality team worked with our delivery team to define the defect taxonomy for each production line — typically 12-24 distinct defect classes per line — and to build the labelled-defect dataset that the per-line models would train on. The labelled dataset combined historical-defect imagery from the legacy machine-vision and human-inspection records, with new high-resolution imagery captured specifically for the model training where the historical imagery was inadequate.

Phase two was the per-line model build. For each production line, a fine-tuned vision-transformer model was trained on the line-specific defect taxonomy. The base model was a Phi-3.5-vision variant chosen for its inference latency on the cost-optimised edge GPUs the line deployment used; the fine-tuning was per line, with the per-line model handling the line-specific product characteristics and defect patterns.

Phase three was the line-integration build. Each line's QC integration sits at the inspection-station with cameras capturing each unit at the required angles and resolution, with the model inference running on the per-line edge GPU and returning the defect classification within the per-unit cycle-time budget. The inspection outcome flows into the line's existing reject-and-routing mechanism (defective units routed to the rework station or scrap; passed units continue downstream).

Phase four was the operational-feedback layer. Quality engineers can review the per-unit inspection outcomes with the model-confidence and the imagery, with model-correction-feedback flowing into the per-line model continuous-learning loop. The platform's per-line defect-pattern analytics surface systemic defect causes for the manufacturing-engineering team's root-cause work.

Accelerators in this engagement

The pre-built building blocks

Rather than commission a ground-up build, the engagement leaned on MindMap's pre-built accelerator library — production-tested components that compress what would otherwise be a six-to-nine-month build into weeks.

Qp

Quality Predictor

Per-line computer-vision defect-detection engine

Pl

Production Line Monitor

Line-integration and inspection-rate monitoring

Ml

ML Model Deployer

Per-line model-fleet management and continuous learning

Ad

Anomaly Detector

Defect-pattern analytics for root-cause work

03
The architecture

The architecture

The platform runs as an edge-and-cloud hybrid: per-line edge components handle the real-time inspection-and-classification with sub-cycle-time latency, while the central platform handles the model-management, the cross-line analytics, and the continuous-learning loop.

Quality Predictor's per-line model is a fine-tuned Phi-3.5-vision variant served on the line-side edge GPU (typically a single L40S per line). The model inference completes within 60-80ms per unit including the imagery pre-processing, fitting well inside the typical per-line cycle-time budget. The model is per-line and per-product-variant where the line produces multiple variants.

Production Line Monitor's line-integration layer handles the camera-and-sensor integration at each inspection station, the inspection-outcome flow into the line's reject-and-routing mechanism, and the inspection-rate-and-quality-rate monitoring for line-operations visibility. The integration uses each line's specific PLC and SCADA framework.

ML Model Deployer manages the per-line model fleet — model training (running in the central environment on the cumulative labelled-data plus the continuous-learning feedback), model validation (on held-out test sets per line), model promotion (canary deployment per line with rollback capability), and model monitoring (drift detection on the inference outcomes).

Anomaly Detector's defect-pattern analysis surfaces the systemic patterns — specific defect classes increasing in incidence (suggesting a root-cause shift in the line operations), specific defect-cluster patterns (suggesting equipment-condition issues), specific defect-temporal patterns (suggesting shift-and-operator variations) — for the manufacturing-engineering team's improvement work.

The outcomes

The numbers behind the story

96%
Defect-detection accuracy
14
Production lines on-platform
71%
Downstream rework reduction
<80ms
Per-unit inspection latency

Defect-detection accuracy across the 14 flagship lines has risen to 96% on the rolling 30-day measurement, against a pre-platform baseline in the high 70s. The improvement is consistent across the lines, with the per-line accuracy varying within a narrow band rather than the wide variance the legacy machine-vision had shown.

Downstream rework volume has dropped approximately 71%. The combination of higher defect-detection (more defects caught at the inspection station) and earlier defect-detection (the defects are caught at the inspection-station rather than at the downstream-assembly stage) has compressed the rework-cost-and-time impact materially.

Field-failure rates on the conglomerate's products have improved measurably on the post-platform-deployment cohort. The warranty-cost impact has been material, with the conglomerate's CFO measuring annual warranty-cost reduction in the high single-digit millions.

Quality-engineering productivity has improved. The platform's defect-pattern analytics has eliminated much of the per-defect-event root-cause work that the previous workflow had required; the quality engineers now focus on the systemic patterns the platform surfaces rather than on individual defect investigations.

An unexpected outcome: the per-line defect-pattern analytics has identified specific equipment-condition signals that correlate with defect-rate shifts. The manufacturing-engineering team has used these signals to refine the predictive-maintenance approach on the affected equipment, producing a virtuous loop between the quality-control and the maintenance functions.

Our previous AI-quality-control attempt had failed on cycle-time integration. MindMap delivered ninety-six per cent defect-detection accuracy across fourteen flagship lines with sub-eighty-millisecond inference latency, with the line-operations integration that made it sustainable. Field-failure rates are down and our quality-engineering team is doing systemic improvement work instead of individual defect investigations.
Chief Quality Officer· Indian Conglomerate Manufacturer
04
Why MindMap was chosen

Why MindMap was chosen

The conglomerate had previously attempted AI-driven quality control with a global computer-vision vendor. The attempt had delivered acceptable model accuracy in lab conditions but had failed to integrate cleanly with the per-line cycle-time budget — the model-inference latency on the vendor's cloud-hosted deployment was incompatible with the line operations.

MindMap's accelerator-composition approach — bringing Quality Predictor, Production Line Monitor, ML Model Deployer and Anomaly Detector together with the per-line edge-deployment architecture that respected the cycle-time budgets and the line-operations workflow — was the structural differentiator. The edge-deployment approach was the unique element.

Our embedded manufacturing-engineering expertise on the delivery team (three former quality-engineering heads from peer Indian manufacturers and a former computer-vision specialist with industrial-deployment experience) was the third factor. The conglomerate's quality leadership felt that the team understood the line-operations reality of quality control, not just the computer-vision technology.

Want an outcome like this?

Start with a 2-week AI Readiness Sprint. We deliver a prioritised use-case backlog and business case grounded in what's actually buildable with our accelerator library.

Book a walkthrough →Explore Manufacturing
Talk to the product team