Define
Agree failure modes, test products, operating envelope and objective acceptance criteria.
Prove the complete reject sequence
Automatic reject system validation and fail-safe testing.
Define what must be tested, what constitutes a pass and what the line must do when rejection cannot be confirmed.
Direct answer
How do you validate an automatic reject system?
Challenge the entire chain with known pass and fail products at agreed operating conditions. Confirm detection, product tracking, reject actuation, physical removal, independent verification, containment, alarms, line-stop behaviour and controlled reset.
Record the product, recipe, speed, test method, expected result, actual result, date and responsible person so the test is repeatable and auditable.
Acceptance test sequence
Detect
Prove that the inspection equipment reliably creates the intended pass/fail result.
Track
Confirm the decision remains assigned to the correct product through speed and spacing variation.
Reject
Verify single-product removal without damage, blockage or disturbance to good product.
Confirm
Use an independent sensor or agreed method to prove arrival in the reject area.
Fail safely
Force relevant faults and prove alarms, stops, messages and recovery controls.
Typical fault challenges
Test the conditions that defeat an ordinary reject.
No confirmation
Block or withhold the expected reject confirmation and verify the defined response.
Low air
Reduce pneumatic pressure below the set threshold and prove the alarm or stop.
Bin full
Operate the level sensor and verify production cannot continue into unavailable containment.
Access open
Open the monitored reject area and confirm the agreed interlock behaviour.
Position fault
Prevent the actuator reaching home or reject position and prove fault detection.
Documentation that supports repeatable testing.
A practical test record identifies the line, machine, product, recipe, speed, test item, fault introduced, expected response, observed response, result and sign-off. Photographs or event-log references can support the record where appropriate.
Validation boundaries
Oxford Vision Systems can support machinery acceptance and agreed challenge testing. The customer remains responsible for its site risk assessment, product-safety plan, operating procedures and final decision on routine test frequency and regulatory suitability.
Common questions
Validation and challenge-test answers.
The agreed test scope should reflect the product risk and system architecture.
What is reject verification?+
It is separate evidence that the intended failed product reached the reject area, rather than an assumption based only on the actuator firing.
Should tests run at maximum speed?+
The agreed envelope should include worst-case conditions such as maximum speed, minimum spacing and the least stable product where those conditions are relevant.
Can test results be logged automatically?+
Potentially. Event outputs, counters, timestamps and data interfaces can be defined as part of the control and traceability scope.
Is a machinery test the same as site validation?+
No. Machinery testing supports the evidence base, but the manufacturer must incorporate the equipment into its own risk, quality and compliance procedures.
Test mixed good and failed packs in a known order
A reject mechanism can remove one challenge pack correctly yet still struggle when faults arrive close together. Add a numbered sequence of known good and failed products to the acceptance plan, using the actual pack format and agreed spacing. The aim is to check which physical items leave the line, including the good packs immediately before and after each failure.
Include isolated failures, adjacent failures and failures separated by one good pack where these patterns are credible for the process. If several inspection devices share a reject station, identify which device issued each decision and whether one product can carry multiple failure reasons. A count of reject commands should not be mistaken for a count of distinct rejected products.
Reconcile the numbered test sequence with the collected packs and event record. Record unwanted removal of good product separately from a failed pack that remained on the accepted route. This gives production and quality teams a more useful result than a single overall pass rate. Agree the challenge products and execution method with the responsible site team before testing on production equipment.
Can two failed inspections refer to the same pack?
Yes, when several inspections check one product. The control design should retain its identity and failure reasons without counting it as two physical packs.
Why include good packs beside reject test samples?
They reveal whether timing or mechanism recovery removes an adjacent acceptable product along with the intended failed pack.
Understand independent reject confirmation Define shared inspection and reject interfaces