Filled-Bottle Reject Handoff: Prove Diversion and Counts

Buyers need more than a rejector in an equipment list. Ask which supplier owns the decision, the bottle tracking, the physical diversion and the result record, including loss of confirmation. This ownership card belongs in the connected-system review before FAT or SAT acceptance is agreed.

Trace one event across the whole boundary

Map the detector's result to the reject request, tracked bottle, diversion point and confirmation evidence. State what each signal proves and what it does not: an output can show a request without proving bottle removal, while a general sensor transition may not uniquely identify the intended bottle. Include fault, missing-confirmation and unavailable-reject-path states in the supplier review. Do not infer successful rejection from the normal-run counter alone. The required device arrangement and timing remain project engineering decisions.

Reconcile one count interval, not unrelated totals

Use a common physical boundary and time interval before comparing counters. Account for bottles entering, accepted bottles leaving, confirmed rejects and the change in held or in-process inventory, including movements explicitly excluded from the comparison. Document counter resets, stop/start events, tracking loss and any manual movement. A mismatch is a reason to preserve evidence and identify the affected interval; it is not a basis for editing the totals to agree. Name the owner who closes every unexplained difference.

Separate recovery readiness from product release

When the outcome is uncertain, use the approved quality procedure to identify and hold the potentially affected bottles. Record location, count basis, cause, lot or interval, and the party authorized to decide disposition. A machine reset can restore a ready state without proving the previous bottle was removed or suitable for sale. Reintroduction, rework and disposal each need their own authorized route. Acceptance testing should use an agreed safe test plan, responsible personnel and approved challenge material; this guide is not an instruction to force faults on a running line.

Keep the event record through a reset

Hypothetical review: an inspection counter is reset between a stop and the packing total. Preserve both original intervals and the stock remaining between the measurement points; do not compare the new inspection total directly with the old packing total. The acceptance record should show the cause, tracked bottle, physical result, confirmation state and authorized disposition together. This is a review scenario, not a completed project or instruction to create a live fault.

Reject ownership card: required evidence

• Detector result, cause code and bottle/tracking reference, plus the machine that owns the reject decision.
• Request, diversion and confirmation records with defined meanings; explicitly record missing or contradictory evidence.
• Common count/time boundary, counter reset history and opening/closing in-process stock, with manual movements documented.
• Hold location, affected lot/interval, investigation owner, approved acceptance method and authorized disposition record.

Project engineering and quality review are required. No universal reject delay or actuator setting is specified. Do not bypass safeguards, force live-line faults or return held bottles without an approved procedure.

Review the connected interfaces

• Cap supply and closure lot control — Identify closure-related events before defining affected bottles.
• Filler discharge handoff — Locate the bottle and ownership boundary after filling.
• FAT and SAT evidence — Agree safe acceptance evidence for normal and abnormal states.