Engineering practice

Managing vision components across integrator projects

A preferred component list is useful only when engineers know its tested limits and service can restore the delivered configuration. Use a configuration record, an exception procedure and a replacement test to manage vision components across projects.

The problem: a service task becomes a new engineering project

A system integrator may finish a cell successfully and still leave a difficult maintenance problem: the camera model is known, but the lens revision, light controller settings or software licence are missing from the service record. Replacing one component then requires reconstructing the inspection.

This article describes a practical component-management method for recurring projects. It does not report measured savings from a customer installation. The aim is to make each delivered configuration traceable and to define when a preferred component is unsuitable.

Standardise a tested combination

A list of camera models is not enough. Define a configuration that includes the camera, lens, light, controller, cables, power supply and software environment. Record the tested inspection task and its boundaries. A camera used for label presence is not automatically qualified for small-character reading on the same line.

Use a record with the following fields:

Field Information to retain
Configuration identity Internal reference, revision, owner and approval date.
Hardware Manufacturer part numbers and revisions, including adapters and cable assemblies.
Software Driver, firmware, inspection software, licence type and configuration backup.
Optical conditions Field of view, working distance, aperture, light position and settings.
Process limits Smallest tested feature, permitted product variation and measured result time.
Machine interface Trigger and result sequence, protocol version and timeout behaviour.
Acceptance evidence Identified samples, expected results, images and test report.
Service information Spare-part references, restore instructions and support owner.

The product catalogue helps identify component families. The approved configuration record establishes which combination was actually tested.

Give exceptions a clear route

Compare a new application with the recorded boundaries before ordering. Escalate when a required feature is smaller, the surface changes, the available exposure falls, the mounting distance changes or the interface is unsupported. Record the failed requirement and the evidence needed to qualify an alternative.

For example, changing from a matte printed label to a direct mark on reflective metal is a new optical task. Keeping the same camera may be possible, but the existing label test does not qualify its lighting or decoding performance for that mark. Run the relevant sample trial and create a new configuration revision if the combination passes.

Assign an application engineer to approve technical exceptions and identify who supports the resulting non-standard items. A purchase deadline should not silently turn an untested alternative into an approved replacement.

Qualify substitutions before service needs them

When a supplier changes or discontinues a component, compare the properties that matter to the inspection. For a camera, check active sensor dimensions, pixel size, shutter, trigger behaviour and software compatibility. For a light, check geometry, wavelength, controller compatibility and the tested image contrast. A connector match alone is insufficient.

Use the original acceptance samples and settings as the comparison baseline. Record any required recalibration or software change. Keep the old and replacement part references linked so the service team can see which machines require the revised procedure.

Test the documentation with another engineer

Ask an engineer who did not build the original cell to select the approved configuration for a defined task, find its spare parts and restore its saved inspection in a controlled test. Record missing information and the time spent searching. Then repeat the acceptance checks, including a restart and communication timeout.

Success means that the configuration can be identified and restored and that the required inspection results are reproduced within the agreed limits. Set the acceptable restoration time from the machine’s maintenance needs; do not infer it from the existence of a backup file.

Measure the business case

Track selection hours, documentation hours, service investigation time, stock value and obsolete parts. Also record the number of exceptions per project and the hours needed to qualify them. Compare equivalent project types; a more complex inspection may legitimately require more work.

Annual engineering effect = the change in relevant hours × the applicable rates. Add inventory carrying and obsolescence costs separately. Released engineering capacity is not automatically a cash saving, and a reduced downtime estimate needs actual service or production evidence. Include the effort required to maintain the approved configurations and retest replacements.

Start with a recurring task

Choose a task that appears in several current projects. Assemble its configuration record, identify the missing acceptance evidence and test restoration. Then decide whether it is ready to become a preferred configuration. For support defining the component set and exception boundaries, see our work with system integrators.

Vincent van Montfoort

Talk through your application.

We can help define a preferred product set for recurring applications, with clear exceptions for specialist requirements.