Publication Date
author
An industrial vision inspection supplier should be selected on evidence that the complete system can make the required quality decision at production speed. Camera resolution, model accuracy, and a successful demonstration provide only partial evidence. Acceptance should depend on agreed defect definitions, representative parts, measured error rates, and proof that rejected parts actually leave the production flow.
For procurement, the strongest approach is to agree on acceptance tests before comparing final bids. This exposes differences in scope and makes performance commitments enforceable. A supplier that detects a defect on a stationary sample may still struggle with changing surface finishes, inconsistent presentation, or the time available to trigger a downstream reject mechanism.
A useful acceptance specification starts with the quality decision: which conditions make a part unacceptable, and under what circumstances must the system identify them? “Detect scratches” leaves too much room for disagreement. Scratch width, length, contrast, location, and relationship to a functional surface can all change the inspection task.
Separate cosmetic judgments from functional requirements. A visible mark may be acceptable on one surface and disqualifying on another. If human inspectors disagree about borderline samples, resolve that disagreement before using those samples to score the supplier. Otherwise, the acceptance test measures an unsettled quality policy as much as machine performance.
For each required inspection, establish:
Some defects will be inaccessible to the proposed optical arrangement. A camera cannot reliably judge a concealed surface merely because its software recognizes similar defects elsewhere. Require suppliers to identify visibility limits and explain whether additional views, controlled positioning, or another inspection method is necessary. An explicit exclusion is more useful than an undefined promise of complete coverage.
Where dimensional inspection is involved, add a separate measurement acceptance requirement. Specify the reference method, allowable measurement error, and repeatability across the working range. A system can classify obvious defects correctly while lacking the measurement capability needed for a tight dimensional tolerance.
The acceptance sample set should contain acceptable parts across legitimate process variation and defective parts across the conditions the system must detect. Include defects near the acceptance boundary, difficult locations, and combinations of defects where relevant. Testing only severe defects establishes little about the system’s ability to protect the actual quality limit.
Good parts deserve equal attention. Changes in supplier lots, machining texture, molded color, oil residue, print appearance, or permitted surface variation may resemble defects. If these conditions belong within normal production, they belong in the test. Otherwise, an apparently sensitive system may achieve detection performance by rejecting too much saleable output.
Establish a reference classification for every sample through the agreed quality process. Where necessary, use independent measurement or specialist review. Preserve the sample identity and reference result separately from the supplier’s output so that disagreements can be investigated without rewriting the original evidence.
Artificial defects can help explore system limits, but they need justification. A machined notch, digitally altered image, or manually applied mark may produce different optical behavior from the production defect it represents. Record which samples are natural, which are constructed, and what each is intended to demonstrate. Do not let an easy-to-image substitute silently become the contractual definition of a difficult defect.
Give the supplier development samples, then reserve a separate set for acceptance. Freeze the relevant software, model, recipes, exposure settings, and decision thresholds before scoring begins. If the supplier tunes the system after seeing a failed acceptance sample, treat the subsequent run as a new test and assess whether fresh held-out samples are needed.
Repeatedly presenting the same defective part does not provide the same evidence as testing many independent defective parts. Repetition helps assess consistency. Independent samples help assess coverage of defect variation. Both are useful, but the acceptance report should distinguish them.
Overall accuracy can hide the failure procurement most needs to understand. If most test parts are good, a system can appear highly accurate while missing an unacceptable share of defects. Require results by defect category and, where relevant, by product variant or difficult operating condition.
Set limits according to the consequences. A missed safety-related defect and a cosmetic false reject carry different costs. Suppliers should demonstrate that the agreed detection threshold and false reject limit can be met together, using the same locked configuration. Separate demonstrations at different sensitivity settings do not prove that both requirements are achievable in production.
Sample size must support the claim being purchased. Zero misses in a small test does not establish zero risk. As an illustration, with zero misses across 300 independent, representative defective samples, the approximate one-sided 95% upper confidence bound on the miss probability is still about 1%. This statistical interpretation depends on the sampling assumptions; it does not prove equivalent performance for untested defect types or operating conditions.
For rare defects, obtaining enough representative samples may be difficult. Address that limitation openly in the purchasing plan through staged qualification, additional validation, or continued containment. A short demonstration cannot substantiate an extremely low escape-rate guarantee merely because no failures appeared.
A laboratory image test answers whether the inspection method can recognize the sampled conditions. Production acceptance must also answer whether the installed system can acquire the image, process it, associate the result with the correct part, and complete the required action before the available window closes.
Measure timing from the agreed production trigger to the point at which the result is usable by the line control or reject mechanism. Include acquisition, processing, communication, and actuation where they fall within the supplier’s scope. Average processing time alone can conceal occasional delays that cause missed decisions.
Run at the required sustained throughput with realistic part spacing and product mix. Include the fastest permitted operating condition and relevant start-stop behavior. A system that meets nominal speed with generously separated parts may fail when parts arrive close together or when several inspections compete for processing resources.

Challenge the physical reject sequence using identified samples. Verify that the defective part is removed, adjacent good parts remain correctly tracked, and a reject confirmation is recorded where required. Then test fault conditions such as a blocked reject path, loss of communication, a missed trigger, or an unavailable camera. The specified safe response should occur without silently releasing uninspected parts.
Repeatability testing should include removing and re-presenting parts, rather than repeatedly processing one stored image. Vary position, orientation, and other permitted presentation conditions. For measurement applications, compare results against the agreed reference and evaluate whether variation consumes too much of the tolerance available for the decision.
Environmental challenges should reflect the installation. Relevant conditions may include ambient light changes, vibration, temperature variation, or gradual contamination of protective windows. Define test conditions and maintenance intervals together: performance demonstrated with freshly cleaned optics cannot establish performance throughout a longer cleaning interval without supporting evidence.
A sustained run should be long enough to expose the risks identified for the application, including warm-up effects, image storage limits, communication interruptions, and operator interventions. Specify the duration and conditions before testing. Report stops, manual resets, bypasses, dropped images, and uninspected parts alongside throughput. A headline parts-per-minute figure loses value if maintaining it requires frequent intervention.
Use the same acceptance schedule for shortlisted suppliers. Ask each bidder to state compliance, exclusions, required buyer inputs, and the equipment included in its offer. This makes a lower price interpretable: it may reflect a simpler solution, or it may exclude fixturing, lighting control, reject confirmation, or integration work needed to achieve the promised result.
Divide verification between factory acceptance testing and site acceptance testing. Factory testing can establish inspection capability and integration behavior under controlled conditions. Site testing must address the actual installation, including the production interface, permitted environmental variation, and material flow. Passing the factory test should not automatically close requirements that could only be demonstrated on the buyer’s line.
The contract should identify who supplies and approves samples, who establishes reference classifications, who controls test execution, and who pays for corrective work and retesting. It should also define what happens if the system passes some defect categories but fails others. Conditional acceptance needs explicit restrictions, remaining obligations, and a completion date; otherwise, temporary workarounds can become permanent operating costs.
Connect payment milestones to evidence within the supplier’s control and the agreed division of responsibilities. If the buyer must provide stable fixturing or upstream part presentation, define those interfaces precisely. If the supplier owns complete inspection performance, its scope must include the components and integration needed to deliver it.
Require an acceptance record that preserves sample identities, reference results, system decisions, relevant images, timing records, and the tested configuration. Define access to those records and practical export arrangements. Retest rules should cover changes that could affect performance, such as a replacement camera, altered illumination, software updates, model changes, or new product variants.
Operator handover also belongs in acceptance. Confirm that authorized staff can select the correct recipe, recognize a degraded inspection condition, recover from defined faults, and restore the approved configuration. Uncontrolled threshold changes can invalidate a carefully demonstrated balance between missed defects and false rejects.
When choosing between suppliers, unresolved acceptance exceptions deserve as much attention as the quoted price. A credible offer states what will be detected, under which conditions, with what evidence, and what happens when the system cannot decide. The purchasing decision becomes defensible when those commitments survive testing on the parts and production conditions the buyer actually needs to run.
Search News
Hot Articles
Popular Tags
Recommended News