Bottling Line Performance Test Data Sheet

Assign a test ID, protocol revision, requirement ID, SKU and equipment boundary. Identify each counter and its unit. Record start/end timestamps, time zone or clock basis, meter conditions, materials and who captured the observations. Keep raw exports beside the summary.

• Use final minus initial counter values; document resets, rollover or manual corrections.
• Convert complete packs to bottles only with the actual pack count.
• Do not merge readings from different clocks or unaligned windows.

Illustrative two-hour window: opening work-in-process is 300 bottles and 20,000 bottles enter the boundary. During the window, 19,700 accepted bottles leave, 150 rejects are removed, 50 held bottles are moved to quarantine outside the boundary, and 400 remain as closing work-in-process. Both sides equal 20,300.

• 300 + 20,000 = 19,700 + 150 + 50 + 400.
• Accepted rate: 19,700 ÷ 2 = 9,850 bottles/h, not the entry-counter rate of 10,000.
• The 50 quarantined bottles are excluded from closing work-in-process here; never count one physical group twice.
• These values illustrate record logic, not a customer result or equipment rating.

Record when a stop began, which machine initiated it, affected states, intervention and when accepted output resumed. Use mutually exclusive categories for accepted, rejected, quarantined and retained units. Where a movement or quality decision is unknown, leave an explicit unresolved item.

• Do not sum overlapping stops as separate line elapsed time.
• Show gross elapsed time and any pre-agreed excluded time separately.
• Retain evidence references for inspections and changes; a count sheet is not proof of product-water safety or regulatory compliance.

Recalculate the unit-count balance in the agreed unit and compare the result with the approved criteria. Record unexplained differences, their investigation and the required retest. A blank field or unsigned summary must not become an automatic pass.

• List result, evidence file, deviation owner and closure condition per requirement.
• Record preparer and authorized reviewers without treating the template as a sign-off.
• Redact confidential or personal details before sharing a planning copy with Allot Tech.