01 Answer first
What should be verified during dry commissioning of a water bottling line?
Verify point-to-point I/O, tags, motion and direction, sensors, alarms, interlocks, safety responses, machine states, users, recipes, data, backups, and every temporary bypass or simulation under an approved safe protocol.
02 Where it fits
Position in the project journey
Dry commissioning — after safe energization and before process-water and product trials.
03 Buyer inputs
What the buyer should prepare
- Local energization and safety control
- User, data, and operating requirements
- Witness and release authority
04 Allot Tech and manufacturing-resource inputs
What should be clarified or provided
- Current software and controls records
- Executable functional tests
- Backups, findings, and bypass removal
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
Freeze Software, Drawing, and Tag Revisions
Record panel drawings, I/O list, network, device tags, control narrative, safety documentation, recipes, backups, and software version used for the test.
Prove Point-to-Point Identity
Verify each field input and output reaches the correct controller, display, actuator, record, and alarm with current labels and drawings.
Check Rotation, Motion, and Limits Safely
Use qualified procedures for motor direction, actuator travel, position feedback, limit switches, guards, jog, local and remote control, and exclusion zones.
Challenge Alarms and Interlocks
Simulate approved abnormal conditions and verify detection, message, state change, inhibit, stop, reset, event record, and operator response.
Test Machine-State Exchanges
Verify ready, run, starved, blocked, fault, emergency, format, speed reference, permissive, stop, and restart signals across connected packages.
Verify User Access and Recipe Control
Check authorized roles, login, setpoint limits, recipe identity, change records, backup, restore, time, and response to unauthorized or mismatched selection.
Record Bypasses and Temporary Simulations
Identify every forced signal, defeated device, temporary jumper, simulation, unavailable package, responsible approver, removal check, and test limitation.
Release the Configuration for Wet Tests
Close required findings, remove temporary states, preserve backups, update redlines, sign functional evidence, and define remaining water-dependent tests.
Buyer questions answered
Practical answers before you request a quotation
Can I/O checks be completed at the factory?
Factory tests help, but installed wiring, devices, networks, site interfaces, and final configuration need site verification.
Why record forced signals?
Forces can mask unavailable devices or logic; they need authorization, test limits, removal, and independent verification.
Does dry commissioning prove process performance?
No. It verifies defined installed functions without the complete process and production conditions.
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
- Forced signals remain after testing
- Site wiring differs from factory configuration
- Machine-state faults appear only after packages connect
08 Acceptance or completion
How to know the stage is complete
Release when installed identity, motion, I/O, states, alarms, interlocks, access, backups, and temporary conditions are evidenced and controlled.
09 Required documents
Records that support the decision
- I/O test sheets
- Interlock test record
- Software and bypass register
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.