01 Answer first
How should line performance be accepted without confusing speed and OEE?
Define the line boundary, reference pack, saleable output, conditions, staffing, planned stops, loss classification, data source, test stage, and decision. Machine rating, FAT, site acceptance, and ongoing OEE answer different questions.
02 Where it fits
Position in the project journey
Acceptance definition - before FAT and again before site performance review.
03 Buyer inputs
What the buyer should prepare
- Product, container and pack requirement
- Target output and operating plan
- Factory, utility and destination information
- Decision owners and required schedule
04 Allot Tech and manufacturing-resource inputs
What should be clarified or provided
- Clarified configuration and interface questions
- Project-specific technical and commercial boundary
- Required drawings, records and acceptance inputs
Allot Tech coordinates requirement, quotation and project communication. Detailed engineering, manufacture, testing, documentation and confirmed service are performed by selected manufacturing resources according to the signed scope.
05 Technical scope
Questions and work to control
Define the Measurement Boundary First
State where the line begins and ends, which product and package is tested, what constitutes an accepted saleable pack, which machines and operators are included, and how planned stops, material shortages, external utility events, quality holds, or buyer-side interruptions are treated.
Use Different Evidence for Different Questions
Individual machine checks, integrated dry tests, wet trials, FAT, installation completion, commissioning, site acceptance, and ongoing production monitoring occur at different stages. One result should not be silently reused as proof of another.
- Reference bottle, closure, label, code, pack, pallet, and approved materials
- Normal staffing, utility conditions, settings, duration basis, data source, and stop classification
- Output, reject, quality, availability, performance, and changeover definitions as agreed
Control Data and Stop Classification
Identify who records events, which clocks and counters are authoritative, how micro-stops and blocked or starved conditions are assigned, how rejected packs are counted, and how disputes or instrument issues are handled. The formula is only useful when the boundary and data are credible.
Write the Acceptance Decision and Open-Item Route
Define pass, conditional acceptance, retest, correction, and excluded-condition rules in the signed agreement or protocol. Avoid universal OEE targets, guaranteed efficiencies, or fixed test durations on a generic website.
| Evidence area | Define before the test | Controlled record |
|---|---|---|
| Reference package | Bottle, closure, label, code, finished pack, pallet, and approved material revisions | Package-data register and reference samples |
| Line boundary | Named start and end points, included machines, buffers, inspection, and saleable-pack definition | Controlled process and equipment boundary |
| Operating conditions | Utilities, environment, normal staffing, material replenishment, settings, and modes | Readiness record and approved test basis |
| Time and events | Start/stop rule, planned events, micro-stops, blocked/starved states, and external interruptions | Authoritative event and stop-classification record |
| Quality and rejects | Accepted pack, inspection method, reject counting, holds, and product disposition | Quality and release record |
| Decision | Pass, conditional acceptance, correction, retest, exclusions, and open-item owner | Signed protocol and result report |
Line Acceptance Evidence Planner
Mark only conditions already defined in writing. The result highlights definition readiness; it does not predict whether the line will pass.
Buyer questions answered
Practical answers before you request a quotation
What makes a fair reliability or performance run for a water bottling line?
Freeze the reference SKU and approved materials, accepted-output boundary, test duration, utility and staffing conditions, planned operator work, quality checks, stop and reject rules, data sources and retest process before the run. Report both raw events and the reconciled result.
How should stops, rejects and planned interventions be classified during acceptance?
Use an agreed taxonomy with synchronized evidence, first-cause ownership and consistent counting rules. Keep replenishment, changeover, sanitation, quality hold, buyer-side supply loss and equipment faults visible so events are not reclassified after the test merely to improve the reported result.
06 Responsibility
Assign the owner before the work is due
Land, building and civil work, permits, import and customs, local taxes, site utilities, unloading, lifting, local labor, travel support and commissioning materials are not automatically included. Confirm every responsibility before order.
07 Common risks
What commonly creates avoidable uncertainty
- Open assumptions are treated as agreed facts
- Interfaces or exclusions remain invisible
- Completion evidence is discussed too late
08 Acceptance or completion
How to know the stage is complete
Completion is based on the criteria and evidence defined for the project, not on a generic website statement.
09 Required documents
Records that support the decision
- Confirmed requirement or specification
- Scope and responsibility record
- Relevant drawings and review register
- Acceptance or completion record
10 Next project step
Turn this decision into a reviewable project brief
Share the product, container, target output, destination and available site information. Unknown inputs can remain open for the first review.
Turnkey scope is project-specific and is defined by the signed technical and commercial agreement.