Process outcome
Define decision, tolerance, speed and exception handling.
Knowledge · System design
A vision system must work beyond the demonstration. Platform, algorithm, measurement approach, control and support must meet the process requirement through changeovers, maintenance and normal production variation.

Decision sequence
Define decision, tolerance, speed and exception handling.
Choose where processing and support take place.
Use rules or AI according to variation and validation.
Use 2D or 3D according to the information required.
Assign maintenance, data, changes and acceptance.
Platform
Choose the platform by computing load, camera count, interfaces, frequency of change and available support skills. A compact system is not necessarily simpler if every change requires external support.
Suitable for bounded tasks, limited camera counts and local I/O. Assess tools, storage, spares and line-side support.
View smart-camera applicationsSuitable for multiple cameras, heavier algorithms, central data or custom software. Include operating system, updates and replacement strategy.
View PC-based visionAlgorithm and data
Use explicit rules when measurable image features can separate acceptable products from defects across the expected variation. Evaluate AI when the appearance is difficult to describe with stable rules and representative training data is available. Compare both approaches on independent test images, including processing time, missed defects and false rejects.
Test normal parts, boundary cases, defects and future variants.
Define measurements, fault definitions and acceptance by product family.
Decide who changes rules, stores data, releases models and rolls them back.
Measurement approach
A 2D image can support presence checks, contours, codes and position measurements in a controlled plane. Evaluate depth sensing when the decision depends on height or spatial shape that the chosen 2D view cannot resolve reliably. The sensing method and the location of processing are separate choices; a 3D sensor may still require external processing.
Lifecycle cost and support
Include hardware, engineering, licences, validation, changeovers, data storage, updates, training, spares and downtime.
Define who manages recipes, checks calibration, releases changes and supports production faults.
Test a representative product mix including boundary cases and changeovers. Measure missed defects, false rejects, cycle time, availability and recovery time. Have production and maintenance operate the system and handle faults before releasing the architecture.
Next step
Share the task, product variation, tolerances, cycle time, line control and available support skills. This provides the basis for a trial plan and clear system boundaries.