Skip to content
Welzin
Case study · Computer vision & data annotation

Vision inspection that pays for its own labelling.

An electronics assembly line in western India was catching board defects too late, at final test, after the value had been added. Welzin put cameras on the line, built the labelled dataset and the model behind them, ran inference at the edge, and then reused the footage as first-person training data for a pick-and-kit robot pilot.

RoleData → model → edge deployment → robot pilot
Timeline12 weeks to first station live
StackOpenCV, Ultralytics YOLO, Label Studio, Jetson, MES integration
01 / The challenge

A defect found at final test is the most expensive defect there is.

The line assembled control boards through six manual and semi-automatic stations. Missing components, tombstoned parts, and misaligned connectors were only caught by functional test at the end, after soldering, coating, and enclosure. Rework was slow, scrap was rising, and the incumbent rule-based vision system flagged so many false rejects that operators had learned to override it.

01

Late detection

Defects passed four value-adding stations before anyone saw them, so every escape carried the full cost of the board.

rework and scrap
02

False rejects

The legacy fixed-threshold system rejected good boards on lighting changes and part-lot variation, and was routinely overridden.

03

No labelled data

Years of camera footage existed, but not one frame was labelled. The dataset had to be built before a model could be.

zero labels
04

An automation roadmap on hold

The plant wanted to pilot a pick-and-kit robot but had no demonstration data and no way to evaluate a policy safely.

02 / What we built

The dataset first, then the model, then the robot that learned from both.

Six pieces, delivered by one pod. The order matters: in vision the dataset is the product, and everything downstream inherits its quality.

[ 01 ]

Managed labelling pipeline

A Label Studio workflow with a closed defect taxonomy, gold sets seeded into every batch, and inter-annotator agreement thresholds per defect class.

[ 02 ]

Active learning loop

Each training run ranked unlabelled frames by uncertainty, so the next labelling batch was the one that moved recall most, not the next one in the folder.

[ 03 ]

Defect detection model

A YOLO-family detector fine-tuned per station, with a segmentation head for solder and coating defects and an explainable reject overlay for operators.

[ 04 ]

Edge inference

Models quantized and served on Jetson hardware at each station, inside the cycle time, with no frame leaving the plant network.

[ 05 ]

MES integration and drift monitoring

Every reject written to the MES with its overlay; per-class confidence tracked so a new part lot or a lighting change raises a drift alert before yield moves.

[ 06 ]

Egocentric capture for the robot pilot

Head and wrist cameras on eight operators, synced and segmented into task episodes, became the demonstration corpus for a pick-and-kit policy fine-tuned from an open VLA checkpoint.

03 / How the data flows

Two loops, one corpus: inspection and demonstration.

The inspection loop keeps the detector honest; the demonstration loop turns the same operators into the robot's teachers. Both feed one governed dataset.

Inspection loop

Every board, every station, inside the cycle time.

  1. CaptureFixed station cameras with controlled lighting and a calibration target in frame.
  2. DetectEdge model scores the board and draws the reject overlay.
  3. RoutePass, rework, or scrap written to the MES with the evidence attached.
  4. SampleUncertain and disputed frames queued for labelling.
  5. Retrain and gateWeekly retrain, held-out regression set, promotion only on a recall gain with no precision loss.

Demonstration loop

Operators recorded with consent, for the robot pilot.

  1. RecordHead and wrist RGB-D with a single time base and an automatic sync check per take.
  2. SegmentReach, grasp, place, verify, release, labelled with outcome and reason codes.
  3. Co-trainHuman episodes plus a few hundred teleoperated robot episodes on an open VLA checkpoint.
  4. EvaluateFixed scenario set in simulation and on a physical test rig before the robot meets the line.
04 / The stack

Open tooling, owned by the plant.

Nothing proprietary sits between the client and their data. Every component was chosen so the plant's own engineers can retrain, redeploy, and extend without Welzin in the loop.

Vision

OpenCV Ultralytics YOLO PyTorch

Labelling

Label Studio Gold sets Agreement checks

Edge

NVIDIA Jetson TensorRT Docker

Robot pilot

ROS 2 LeRobot Isaac Sim

Operations

MES webhooks MLflow Grafana
05 / The impact

Defects caught at the station, not at the end.

Figures below reflect observed outcomes over the first quarter after the third station went live and are directional, not guarantees. The client is confidential.

0%
fewer defect escapes to final test across the three instrumented stations.
0x
fewer false rejects than the fixed-threshold system it replaced, so operators stopped overriding it.
0k
labelled frames produced with QA gates, from zero, in the first eight weeks.
0h
of synced egocentric operator footage feeding the pick-and-kit robot pilot.
The old system cried wolf until nobody listened. This one shows the operator the exact pad it does not like, and it is usually right. And the same cameras are now teaching the robot.
- Plant quality head, electronics manufacturer (client confidential)

The service behind this

Computer Vision & Data Annotation

Vision models for inspection and safety, plus the labelled datasets behind them.

See the service

Next study

Rewiring how brands stay visible in the age of AI search

Search is being rebuilt around answers, not links. CogNerd optimizes brands for ChatGPT, Gemini, Claude and Perplexity - keeping organic reach from quietly disappearing into AI answers.

Read it

Answers to questions about this study

What problem did the vision inspection system solve?

An electronics assembly line was catching missing components, tombstoned parts, and misaligned connectors only at final test, after soldering, coating, and enclosure. The legacy fixed-threshold vision system produced so many false rejects that operators overrode it, and none of the existing camera footage was labelled.

What did Welzin build?

A managed labelling pipeline in Label Studio with a closed defect taxonomy, gold sets, and agreement thresholds; an active learning loop; a YOLO-family defect detector per station with a segmentation head and an explainable reject overlay; edge inference on Jetson hardware inside the cycle time; MES integration with drift monitoring; and egocentric capture on eight operators for a pick-and-kit robot pilot.

What is the stack?

OpenCV, Ultralytics YOLO, and PyTorch for vision; Label Studio for labelling; NVIDIA Jetson, TensorRT, and Docker at the edge; ROS 2, LeRobot, and Isaac Sim for the robot pilot; MES webhooks, MLflow, and Grafana for operations. Everything is open tooling the plant's own engineers can retrain and redeploy.

How was the same data reused for the robot pilot?

Head and wrist RGB-D cameras on operators were recorded with consent on a single time base, segmented into reach, grasp, place, verify, and release episodes with outcome codes, and co-trained with a few hundred teleoperated robot episodes on an open VLA checkpoint, then evaluated on a fixed scenario set in simulation and on a physical test rig.

Is the client named?

No. The client is confidential, and the study states that its figures reflect observed outcomes over the first quarter after the third station went live and are directional rather than guarantees.

Want an outcome like this one?

Talk to the senior pod that shipped it - we answer within one business day.

Prefer email? Write to us directly.