Surface and component inspection
Check defined defect patterns on products and surfaces using reproducible images.
Industrial computer vision
Computer vision for mid-sized manufacturers
Manual visual checks can be difficult to scale consistently across products, lighting conditions and defects. We define image capture, labeling, evaluation and operator review before integrating vision models into inspection workflows.
Start with the business workflow.
Repeated visual checks can become bottlenecks when throughput increases, shifts change or defects are difficult to recognize. Manual inspection logs are often disconnected from orders, batches and machines.
The right use case depends on available data, operational value and verification requirements.
Check defined defect patterns on products and surfaces using reproducible images.
Verify whether required components are present and correctly positioned.
Detect missing labels, incorrect codes or packaging defects.
Count objects or classify known variants in controlled image conditions.
Link visual findings to process steps, images and production data.
Route uncertain or critical findings to operators instead of replacing accountable checks.
Industrial computer vision begins before the model: camera placement, lighting and triggers determine image quality. Pre-processing, classical algorithms or trained models produce scores; thresholds and business rules determine whether an operator or system receives the result. Integration connects the finding to a part, line and manufacturing order.
We validate the assumptions and practical workflow before expanding implementation scope.
Specify which errors matter, their consequences and acceptable review steps.
Capture good and defective items across variants, lighting and real production conditions.
Evaluate conventional image processing and ML for relevant errors and throughput.
Connect camera capture, results, data storage and production applications.
Measure missed defects, false alarms, throughput and changes over time.
Computer vision is economically relevant where inspection volume or failure consequences justify camera setup, annotation, integration and maintenance. A model's average accuracy is not enough: measure missed defects and false alerts by class, and determine when human review is required.
These factors define feasibility, evaluation effort and ongoing responsibility.
Control light, focus, position and camera triggers.
Include rare faults, component variants and realistic negatives.
Connect decisions to part identity, operator workflow and ERP or MES.
Evaluate false negatives, false positives and operational throughput.
Retest after changes to product, camera, model or process.
We engineer computer vision as a complete operational system rather than an isolated model demonstration. Camera setup, tests, software integration and human review are all part of the implementation. Published case results are not implied by these illustrative use cases.
Practical questions about feasibility, integration, cost and quality.
Those with a clearly defined inspection task, meaningful error costs and suitable imaging conditions.
Not always. Data needs depend on the defect, variation and whether conventional vision methods suffice.
Only when the process, risks and test results justify that decision. Many systems retain human review for uncertain findings.
Through stable identifiers, event APIs and explicit failure handling.
Compare inspection performance, false alarms, missed faults, time and operating cost against the current process.
No. Deployment can be local or cloud-based depending on latency, connectivity and data constraints.
Discuss your project
Describe the current workflow, systems, available data and intended result. Aleksandar Basara can discuss a technically grounded starting point.
Managing Director
aleks@valanor.co
+49 (0) 711 16 44 6 83
Lindenspürstrasse 22, 70176 Stuttgart
