Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. AI Visual Inspection, and What It Actually Requires
AI & Machine Learning

AI Visual Inspection, and What It Actually Requires

What computer vision inspection needs to succeed — images, lighting, labels and a realistic view of what defects it can catch.

Updated 2 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer — TL;DR

Visual inspection works when defects are visible in consistent images and you have hundreds of labelled examples of each defect type. Lighting and camera consistency matter more than the model. Budget as much for the physical setup as for the software.

The model is the easy part

Most failed vision projects fail on data collection and physical setup, not on modelling. If images vary in lighting, angle and focus, no model compensates reliably, and the system that worked in the trial fails on the night shift.

Before anything else, get the camera position, lighting and trigger consistent. That single discipline determines most of the eventual accuracy.

What you need before starting

  1. Defects visible in an image. If a human cannot see it in the photograph, the model cannot either.
  2. Hundreds of labelled examples per defect type, including borderline cases.
  3. Consistent capture — fixed camera, controlled lighting, same trigger point.
  4. An agreed definition of a defect, because your own inspectors will disagree more than you expect.
  5. A decision about what happens on detection — reject, divert, flag for human check.
The definition point is the one that derails projects. Ask three inspectors to grade the same fifty parts and compare. If they agree only 80% of the time, that is the ceiling for any automated system, and the first job is agreeing the standard.

Realistic expectations

For well-defined defects with good images, detection rates comparable to or better than human inspection are achievable, with the significant advantage of consistency — a model does not get tired at the end of a shift.

For subtle, variable or novel defects, expect it to catch the known types and miss things it has never seen. This is why most deployments run as augmentation rather than replacement: the system catches the routine majority and humans handle the rest.

Tune the threshold to the cost of being wrong

Every system trades false positives against false negatives. Which error is worse is a business decision, not a technical one.

  • Safety-critical parts: tune towards catching everything, accept more false rejects
  • High-value parts: false rejects are expensive, so tune towards precision with human review
  • High-volume, low-value: optimise for throughput and accept a defined escape rate

Make this decision explicitly and revisit it with real data after a month, because the initial assumption is usually wrong in one direction.

Cost structure

ComponentTypical cost
Cameras, lighting, mounting£3,000–£20,000 per station
Image collection and labelling£5,000–£20,000, often underestimated
Model development and validation£15,000–£40,000
Integration with line control£10,000–£30,000
Ongoing retrainingBudget annually — products change

Plan for drift

Products change, suppliers change materials, lighting degrades, cameras drift. A model trained last year will quietly get worse and nobody notices until a customer complains.

Monitor the detection rate distribution and sample outputs for human review on a schedule. Plan for periodic retraining as a normal running cost rather than an unexpected project.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly — a senior engineer will get back to you.

Ask about your project

How many images do we need?

As a rough guide, several hundred examples per defect type including borderline cases, plus a good volume of normal examples. Rare defects are the hard part and may need deliberate collection over months.

Can we use existing production photographs?

Sometimes, if they were captured consistently. Usually they were not, and a proper capture setup is needed. Check a sample early — it changes the project plan considerably.

What accuracy should we expect?

For well-defined defects with consistent capture, high accuracy is achievable and should be validated on your own parts before deployment. Be sceptical of headline figures from other people's data.

How long does deployment take?

Three to six months typically, with a substantial share spent on data collection and physical setup rather than on modelling.

Keep reading

More on AI & Machine Learning

Start here

Considering vision inspection?

The first question is whether the defect is visible in a consistent image. Send us a few examples and we will tell you if the project is viable.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate — with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →