Process
Use this fill-in intake and sample record to define the decision, timing, product variation and acceptance limits before a vision trial. Identify missing information and the evidence needed for the next project decision.
A proof of concept (PoC) is a limited trial to resolve an uncertain technical requirement. Define which decision it must support: proceed with a configuration, change the approach or stop because the required evidence is missing. A successful image on one part does not establish production acceptance.
Copy the intake sheet below into your project document. Complete it with production, controls and maintenance. Mark unknowns explicitly and assign an owner to obtain the missing information. The feasibility checklist supports the subsequent test planning.
| Question | Information to enter |
|---|---|
| 1. What decision is required? | Inspection or measurement; expected output; machine action; requirement owner: … |
| 2. What must pass or fail? | Product variants; defect classes; acceptable variation; disputed borderline cases: … |
| 3. What time is available? | Speed range; shortest trigger interval; result deadline; source of these values: … |
| 4. What is the installation geometry? | Product dimensions; field of view; working distance; height variation; mounting drawing: … |
| 5. Can the feature be made visible? | Surface finish; existing light; ambient changes; access for candidate lighting; trial uncertainty: … |
| 6. What must be measured or read? | Smallest relevant detail; dimensional tolerance or code type; independent reference method: … |
| 7. How will the machine communicate? | PLC/robot type; protocol and electrical signals; result format; timeout and restart behaviour: … |
| 8. Who maintains the configuration? | Recipe owner; change approval; backup location; restore-test owner: … |
| 9. Which environmental conditions matter? | Temperature; vibration; contamination; cleaning; enclosure and ESD requirements: … |
| 10. What constitutes a pass? | Missed-defect limit; false-reject limit; timing limit; test conditions; approver: … |
Do not combine the product interval and result deadline into one timing value. A reject mechanism downstream may require a decision before the next product arrives. Record whether time includes transfer, processing, communication and any retries.
Use a record for every distinct part or image group:
| Sample field | Entry |
|---|---|
| Sample ID and product variant | … |
| Production batch or capture session | … |
| Expected outcome and defect class | … |
| Reason and person approving that outcome | … |
| Surface, position or height condition | … |
| Photograph or stored image reference | … |
| Development or independent validation set | … |
Keep repeated images of the same part together when separating development and validation. A count of repeated reads is different from a count of distinct production examples. Retain borderline cases for explicit review and avoid silently relabelling them to improve the result.
Record attempted inspections, missed defects, false rejects, invalid results and result times. Report errors with the relevant denominator and by important product or defect class. For measurement, compare against an independent reference and state its uncertainty. For identification, distinguish a no-read from a decoded but unexpected value.
Test the conditions the trial is intended to cover, including speed and presentation extremes. Include missing data, communication loss or restart when the trial includes machine integration. Record untested conditions as open requirements rather than treating them as passed.
Agree the trial deliverables, sample preparation, engineering hours, equipment and number of planned test rounds. Estimate work as hours multiplied by the applicable rates and identify what a changed requirement would add.
Bring measured current inspection labour, rework, scrap and intervention time. These are inputs for a later investment comparison, not savings established by the trial. Record any production capacity limitation and avoid valuing the same recovered output twice.
The closing record should state the tested configuration, conditions, results, limitations and recommended next step. Proceed to detailed design only when the required evidence supports it; otherwise define the remaining test or revise the requirement. Send the completed intake and sample inventory to discuss a suitable trial scope.

Send representative samples and information about cycle time, environment and interfaces. We can help define a useful feasibility test and the results it must provide.