Introduction
Choosing an AI visual inspection system is less about comparing feature lists and more about matching a system to your environment, your defects and the way your plant runs. Leaders who get it wrong usually picked the right technology for the wrong problem: a fixed camera rig for assets that need mobility, or a handheld tool for a line that needs 100 percent coverage.
This framework assumes you already understand the technology. If you need the fundamentals first, start with our complete guide to AI visual inspection in quality control. Here we focus on the decision itself: which type of system fits, how to evaluate options against each other, and how to avoid the mistakes that sink most selections.
Step 1: Match the system type to your environment
There are three broad form factors, and the first decision is which one your inspection problem needs.
| System type | Best for | Coverage | Cost profile |
|---|---|---|---|
| Fixed machine vision (line-mounted cameras) | High-speed inline quality control on production and assembly lines | Every unit, continuously | Higher integration effort; lowest cost per inspection at scale |
| Mobile robotic (drones, rovers, crawlers) | Large, remote or hard-to-reach assets: tanks, pipelines, structures | Scheduled surveys of whole assets | Higher hardware cost; flexible across sites |
| Handheld and portable (phones, tablets, scanners) | Technician rounds, spot checks, field inspections | Point-in-time, operator-driven | Low entry cost; coverage depends on people |
Many organisations need more than one. A manufacturer may run fixed cameras on the line and handheld inspection in incoming goods; an energy operator may combine drones for structures with mobile apps for routine rounds.
Step 2: Let industry context set your priorities
The same criteria carry different weight in different sectors.
| Industry | Typical inspection targets | What to prioritise |
|---|---|---|
| Manufacturing | Inline surface, assembly and packaging defects | Line-speed latency, PLC and MES integration, low false reject rate |
| Automotive | Paint, body panels, welds, pre-despatch checks | High-speed fixed inspection plus coverage of large reflective surfaces |
| Oil and gas | Tanks, pipelines, flare stacks, offshore structures | Hazardous-area suitability, corrosion and thermal detection, audit records |
| Infrastructure | Bridges, roads, utilities | Mobile form factors, long-range coverage, regulatory reporting |
Step 3: Evaluate options against eight criteria
Once you know the system type, compare candidates on these eight criteria. Ask for evidence, not assurances.
- - 1. Detection performance on your partsRequest escape rate and false reject rate per defect class, measured on your own samples at a stated threshold, ideally in a shadow-mode trial. A single "accuracy" figure tells you little when defects are rare.
- - 2. Defect-specific model trainingHow many labelled images are needed per defect class? Is anomaly detection available for defects too rare to collect? Who labels, and against whose acceptance standard?
- - 3. Form factor and environment fitLine speed, part size, surface finish, lighting conditions, dust, heat, vibration and hazardous-area classification.
- - 4. IntegrationNative connections to your PLCs, MES, QMS, ERP and existing cameras, and the protocols used (for example OPC UA, MQTT, Modbus, REST). Integration effort is the most underestimated cost in most projects.
- - 5. ScalabilityCan one approach grow from a single station to many lines and sites without re-architecting? How are models managed centrally?
- - 6. Data security, ownership and governanceWhere images and models live, who owns trained models, and whether edge, on-premises or air-gapped operation is supported.
- - 7. Regulatory and safety complianceTraceability records that satisfy ISO 9001, IATF 16949 or sector rules; hazardous-area certification where relevant.
- - 8. Total cost of ownershipHardware, software, integration, training, support and retraining over three to five years, with capital and subscription models normalised to the same basis.
Step 4: Score candidates with a weighted checklist
Weight criteria by what failure would cost you. A typical weighting for production-line inspection:
| Criterion | Weight | Evidence to request |
|---|---|---|
| Detection performance on your parts | High | Shadow-mode results per defect class |
| Defect-specific training | High | Labelling requirements; anomaly detection support |
| Integration | High | Reference integrations with your PLC and MES types |
| Form factor and environment fit | High | Site survey; imaging feasibility on real samples |
| Total cost of ownership | High | Three to five year cost model |
| Scalability | Medium | Multi-line or multi-site references |
| Data security and governance | Medium | Deployment options; model ownership terms |
| Regulatory and compliance support | Medium | Example traceability records and audit outputs |
Score each candidate 1 to 5 per criterion, multiply by weight (High = 3, Medium = 2) and compare totals, but treat any score of 1 on a High criterion as disqualifying regardless of the total.
Step 5: Decide between build, buy and partner
| Model | When it fits | Watch out for |
|---|---|---|
| Build in-house | A strong internal vision and ML team, unusual defects, long-term strategic value | Hidden costs of MLOps, imaging engineering and ongoing support |
| Buy a point solution | One well-defined defect type on one line | Islands of tools that do not scale or share data |
| Partner end to end | Multiple lines or sites, limited internal ML capacity, need for integration and lifecycle support | Dependency; insist on clear model and data ownership |
Six mistakes to avoid
- - 1. Choosing the form factor before assessing the environmentSurvey the line or asset first.
- - 2. Ignoring integration costA system that cannot write to your MES or trigger a reject is a demonstration, not a deployment.
- - 3. Accepting accuracy claims without validation dataInsist on results from your own parts.
- - 4. Underestimating change managementInspectors must help define defects and trust the review workflow.
- - 5. Comparing hardware price aloneIntegration, retraining and support usually outweigh it over five years.
- - 6. Not planning for scaleAsk how the pilot becomes the tenth line, not just the first.
For how to quantify the payback of your chosen option, see building the AI visual inspection ROI case. For how AI compares with rule-based and manual methods, see AI visual inspection vs traditional inspection methods.
Putting the framework to work
Run the framework on one candidate line before committing broadly: survey the environment, write the defect catalogue, score two or three options, then validate the leader in shadow mode on real production. For fixed-camera inspection on assembly and production lines, you can compare your shortlist against Ombrulla's AI visual inspection system for production lines. For drones, rovers and handheld rounds, see AI Infrastructure Inspection and Mobile AI Inspection.
Frequently asked questions
What are the most important criteria when choosing an AI visual inspection system?
Detection performance on your own parts, defect-specific training requirements, integration with your plant systems, environmental fit and total cost of ownership. Validate each with evidence from a shadow-mode trial rather than brochure figures.
Should we build our own AI inspection system or buy one?
Build only if you have a strong vision and ML team and a long-term strategic reason. Most manufacturers get to production faster by buying or partnering, provided they keep clear ownership of their data and trained models.
How long should a selection process take?
A structured process, from site survey to a validated shadow-mode result on one line, commonly takes two to four months, most of it spent on data collection and validation rather than paperwork.
Can one system cover both production lines and field assets?
The AI methods overlap, but the hardware differs: line-mounted cameras for production, drones and handheld devices for field assets. Choose platforms that share models and data across form factors if you need both.

