Skip to content
Complete-line project desk · Allot Tech (Suzhou) Co., Ltd.

Verify available functions before shipment

Bottled Water Production Line Factory Acceptance Test

A factory acceptance test is useful when the protocol, materials, operating basis and disposition rules are agreed before participants arrive at the manufacturing site.

Direct answer

What should a bottled water production line factory acceptance test include?

A factory acceptance test should confirm equipment identity and scope, inspect workmanship and available documents, verify safety and functional behavior that can be tested before shipment, and run the agreed reference bottle, closure, label and pack under defined conditions. The protocol should name prerequisites, test sequence, measurements, sample plan, records, pass criteria and treatment of deviations. FAT does not replace site acceptance because final utilities, installation and complete-line operation may only be available at the destination factory.

System focus 01

Approve the protocol before test readiness

Build the protocol from the signed specification and approved exceptions. It should identify the equipment and software revision, reference format, test products or substitutes, utilities, sequence, duration, measurement methods and required records. Separate mandatory acceptance checks from demonstrations or observations. Advance approval gives both parties time to resolve impractical criteria and prepare meaningful evidence.

  • Referenced contract, specification and approved revisions
  • Equipment, tooling and software configuration under test
  • Test format, materials, services and environmental conditions
  • Check method, measurement point and acceptance basis
  • Witnesses, records, deviation and sign-off process

System focus 02

Establish readiness before inviting witnesses

The supplier should complete internal inspection and functional trials before the formal event. Required bottles, preforms, closures, labels, film or cases must be representative, sufficient and compatible with the approved basis. Calibrated measuring equipment, safe access, utilities, operators, data sheets and available manuals should be ready. Missing prerequisites should trigger a documented decision to defer, limit or reclassify affected checks.

  • Internal test completion and known-item review
  • Representative materials with quantities and identification
  • Utilities, tools and calibrated instruments
  • Safe test area and authorized operating team
  • Available drawings, lists and inspection records

System focus 03

Inspect identity, build and functional behavior

FAT normally begins with equipment identity, included components, workmanship, access, guarding and documented interfaces. Functional checks can then examine sequences, manual and automatic modes, sensors, alarms, interlocks, recipe or format selection, reject handling and controlled recovery. The test depth should reflect the supplied scope and what can be reproduced safely at the factory, without implying site-dependent conditions have been proven.

  • Equipment identity and supplied component schedule
  • Workmanship, access, guards and visible interfaces
  • Manual, automatic and controlled-stop sequences
  • Alarms, sensors, interlocks and reject behavior
  • Change parts, settings and restart procedure

System focus 04

Run the agreed reference production scenario

Where the assembled scope and factory services permit, the production run should use the agreed format and materials. Record start conditions, operating periods, planned pauses, unplanned stops, rejects, output counts, product or package observations and adjustments. If water substitutes, shortened conveyors or temporary services are used, the protocol should state the limitation and reserve relevant verification for the site test.

  • Confirmed start conditions and line configuration
  • Output counts tied to defined time periods
  • Stop, alarm, reject and adjustment log
  • Bottle, fill, closure, label, code and pack checks
  • Limitations caused by temporary factory test conditions

System focus 05

Control disposition and shipment release

Every result should be recorded as accepted, accepted with an agreed action, pending evidence or not accepted under the contract process. Classify open items by effect on safe shipment, installation and later verification. Assign owner, action, evidence and due date. FAT sign-off should describe what was tested and its limitations; it should not erase unresolved items or waive site-dependent obligations unless explicitly agreed.

  • Signed test data and inspection records
  • Deviation description and requirement reference
  • Owner, correction, due date and closure evidence
  • Retest or site-verification decision
  • Formal shipment-release status and reservations

FAT readiness gate

Confirm the test can produce usable evidence

Do not treat attendance as readiness; confirm the basis, setup, evidence and disposition process first.

Approved basis

Everyone tests the same requirement set.

  • Signed specification and exceptions referenced
  • Protocol and check sequence approved
  • Reference format and configuration identified
  • Measurements and acceptance basis stated
  • Witness and sign-off authority confirmed

Physical readiness

Equipment and materials support the planned checks.

  • Internal inspection and trial completed
  • Bottles, closures, labels and packs available
  • Utilities and safe test access ready
  • Tools and instruments in suitable status
  • Known limitations disclosed before the event

Evidence package

Results can be traced and reviewed later.

  • Equipment and component records available
  • Run data and event log prepared
  • Inspection samples and photos identified
  • Document review status recorded
  • Witness notes linked to protocol items

Disposition control

Open points have a defined route to closure.

  • Deviation categories agreed
  • Action owner and due date assigned
  • Correction evidence or retest defined
  • Site-dependent checks transferred explicitly
  • Shipment-release status signed

Specific legal, safety and contractual requirements may require additional checks or independent inspection for the destination project.

Technical reading

Authoritative references behind the planning framework.

Confirm the standards, guidance and legal requirements that apply to the project location and product before final design.

Buyer questions

Frequently asked questions

Use these answers as a project-planning starting point. Final equipment and performance remain subject to the confirmed brief.

Is FAT the same as final acceptance?

Not usually. FAT verifies the supplied equipment under available factory conditions. Installation, final utilities, retained-equipment interfaces and integrated operation are commonly verified during site acceptance.

Who provides bottles, caps, labels and packing materials for FAT?

The order should assign supply, quantities, delivery timing and material approval. Representative buyer materials are preferable when available; substitutes and their limitations must be recorded.

Should FAT include a continuous production run?

Only when the signed protocol defines the scope, prerequisites, duration, conditions and measurements and the factory setup can reproduce them. A universal run duration should not be assumed.

What happens when a FAT item fails?

Record the requirement, observed result, classification, correction owner, due date and required evidence or retest. Shipment disposition should follow the contractual process and the effect of the open item.

Project-specific confirmation

Capacities, process routes, layouts, utilities and equipment shown on this site are decision frameworks and reference examples. They are not a final specification, performance guarantee or offer. Confirmed scope and performance are defined in the signed technical and commercial agreement.

Allot Tech project desk

Turn your requirements into a comparable line brief.

Share the source water, bottle, target output, pack format, factory status and destination. We will use them as the basis for a project-specific configuration discussion.