RFQ Checklists

Vision Inspection RFQ Checklist

Collect the details engineering teams need before requesting cameras, lenses, lighting, readers or inspection systems.

Direct answer

Vision Inspection RFQ Checklist

A useful vision inspection RFQ should define the production decision, not just request a camera price. Send the part, target defect or measurement, FOV, working distance, line speed, tolerance, lighting failure examples, output requirement and acceptance rule.

Where this matters

Start with the inspection condition.

The strongest RFQ includes good/bad samples, borderline parts, line video, current images and the exact output expected from the vision station.

Why projects fail

Confirm the limits that change hardware.

Include field of view, working distance and line speed.

RFQ preparation

Send enough context for a real review.

List any reference model or current failure mode.

What engineering should check

What this page should help teams decide.

Send part images and target defects.
Include field of view, working distance and line speed.
List any reference model or current failure mode.

Related Deyi routes

Product families commonly involved.

Practical note

Define the inspection decision first.

State whether the station must detect a defect, measure a dimension, read a code, guide a robot or verify presence. The decision output determines camera, lens, lighting, controller and I/O route.

Practical note

Send samples that include borderline conditions.

Good and bad samples are not enough if the real line has gray-zone cases. Include borderline defects, batch variation, reflective parts, damaged labels, dirty surfaces and any current failure images.

Practical note

Quantify the geometry and speed.

Field of view, working distance, part speed, trigger method, tolerance and installation space turn a vague quote into an engineering route. These numbers decide resolution, lens, exposure and light power.

Practical note

Make acceptance measurable.

Define target read-rate, detection rate, measurement repeatability, false reject tolerance, no-read handling or PLC output before purchase. This makes factory testing and buyer confirmation clearer.

How to test before buying

Use this guide as a pre-RFQ decision filter, not as a part-number shortcut.

Machine vision selection is usually stable when the project starts from the inspection condition instead of a catalog model. Before requesting a quote, define what must be detected or measured, how the part moves, what surface behavior affects contrast and which factory constraint cannot change.

Use this guide to translate the requirement into testable inputs: sample images, target tolerance, line speed, field of view, working distance, mounting envelope and the current failure mode. That gives the factory enough evidence to map the request to camera, lighting, optics, reader or 3D routes.

Decision checks

Three checks before locking the route.

Part and defect evidence

Send good, bad and borderline samples plus current images.

FOV and working distance

Provide part size, required inspected area and mounting envelope.

Speed and trigger

Send takt time, conveyor speed, trigger method and reject timing.

Decision table

Use these data points to turn the concept into an RFQ-ready decision.

Factor	Practical rule	RFQ impact
Part and defect evidence	Send good, bad and borderline samples plus current images.	Allows supplier to test the actual contrast problem.
FOV and working distance	Provide part size, required inspected area and mounting envelope.	Drives camera resolution and lens route.
Speed and trigger	Send takt time, conveyor speed, trigger method and reject timing.	Prevents blur and missed capture assumptions.
Tolerance or read-rate	State the measurable acceptance target.	Turns the quote into a testable plan.
Integration output	Define PLC, robot, database, alarm, reject or image-storage output.	Clarifies controller and software scope.

Application proof

Related delivery routes that make this selection decision concrete.

View all cases

Battery inspection

Battery Tab Weld Height Inspection

Battery tab weld inspection needs geometry confidence, stable position reference and traceability under high station throughput.

Automotive parts inspection

Automotive Metal Surface Defect Inspection

Reflective metal surfaces can hide scratches and burrs unless the lighting geometry is matched to the defect direction and part movement.

Electronics inspection

PCB Connector Pin Presence Inspection

Small connector features require stable contrast, low distortion and repeatable part positioning before a pass/fail threshold can be trusted.

Common mistakes

Problems that slow down selection.

Selecting by model number before the inspection target is measurable.
Treating lighting as an accessory instead of the main contrast-control tool.
Ignoring fixture stability, part variation and operator maintenance workflow.

Factory handoff

What Deyi Vision reviews after receiving the project details.

The factory route review starts by checking whether the image can be made stable with lighting and fixture control. Then the camera, lens, reader or 3D sensor route is sized against speed, resolution, interface and installation constraints.

If you already have a Keyence, Cognex, Basler, OPT, LMI, Hikrobot or barcode-reader reference, include it as a reference model. Deyi Vision uses it to understand the application class; final selection still depends on real samples and production limits.

Guide to RFQ

Have a real part, sample image or production constraint?

Use the guide to frame the question, then send the details so engineering can recommend a route.

Request engineering RFQ

Guide FAQ

Questions related to vision inspection rfq checklist.

Ask engineering

What should be included in a vision inspection RFQ?

Include part photos, good and bad samples, target defect or measurement, FOV, working distance, speed, tolerance, lighting condition, trigger method, output requirement and acceptance criteria.

Why do suppliers ask for sample images before quoting?

Sample images reveal whether the issue is resolution, lighting, reflection, fixturing, code quality, surface variation or software logic.

What makes a vision inspection RFQ weak?

A weak RFQ asks for a camera model without describing the inspected feature, tolerance, speed, working distance, output route or current failure mode.