Clarify the inspection task and data
Define target features, constraints, available images, known failure modes and success criteria.
Structured support from available image data to a traceable evaluation – with explicit assumptions, measurable criteria and documented limits.
Machine vision consulting
An industrial inspection task is never determined by the algorithm alone. Image acquisition, illumination, perspective, optics, calibration, data quality and evaluation criteria jointly influence the result. I help make these dependencies explicit and build analysis workflows whose results remain reviewable.
I combine practical experience in industrial machine vision with Python at ZEISS in Jena with systems engineering, technical data analysis and my current work with knowledge graphs. This supports not only image evaluation but also structured documentation of requirements, assumptions, decisions and open validation points.
Define target features, constraints, available images, known failure modes and success criteria.
Load datasets, assess quality and distribution, organise metadata and prepare reproducible analysis workflows.
Prototype and compare preprocessing, segmentation, feature extraction or geometric analysis where suitable for the task.
Investigate misclassifications, unstable parameters and systematic deviations using defined examples and metrics.
Document test cases, measurements, acceptance criteria and missing evidence so the next test stage is explicit.
Present code, analyses, assumptions, known limits and recommendations clearly for the intended audience.
Evidence
An evaluation on example images can show whether an approach is fundamentally promising. It does not prove stable performance under production conditions. Defensible industrial assessment requires representative real images, the intended target hardware, controlled acquisition conditions, calibrated settings and predefined acceptance criteria.
This boundary is documented explicitly. Unsupported assumptions are not presented as confirmed results. That reduces later misunderstandings and makes the required follow-up tests visible.
The useful result depends on the project stage. It may be an early feasibility analysis, a focused prototype, a structured evaluation of existing tests or preparation for later technical validation.
Yes. An initial assessment requires context on acquisition conditions, classes, failure modes and the desired result. Confidential data should only be provided through an agreed, suitable transfer route.
Task clarification, data analysis, result reviews and documentation can generally be handled digitally. Whether work on the physical system is required depends on the inspection task and project stage.
That decision follows from the images and requirements. A simple, reviewable method is often more useful than a complex model without a sufficient evidence base.
Methods, parameters, sources, assumptions, test results and open gaps are connected. The article on knowledge graphs in industrial machine vision explains the approach.