Short answer: Greenhouse automation should be commissioned from an approved input-output list and control sequence that defines every sensor, motor, valve, alarm, interlock, automatic stage, manual mode and failure response. A controller screen that shows values is not proof that the system operates correctly.
Assign each field device a unique tag, description, signal type, range, controller point, normal state, alarm use and drawing reference. Include analog sensors, digital status, motor commands, valve outputs, fault contacts, variable-frequency drives and communication devices. Keep spare points identified but separate from active logic.
| Sequence element | Required detail |
|---|---|
| Start condition | Sensor, schedule, setpoint, delay and equipment availability. |
| Stages | Order, deadband, minimum run time and transition conditions. |
| Interlocks | Conditions that permit, prevent or stop equipment. |
| Manual mode | Authorized local operation, limits and status indication. |
| Fault response | Safe position, alarm, backup and operator action. |
| Recovery | Restart method after power, communication or equipment fault. |
Vents, fans, pads, fog, heating, screens and circulation can conflict if programmed independently. Define priorities for high wind, rain, low temperature, high humidity and cooling demand. Use staged actions and outside conditions. Make clear whether a screen opens before roof vents or whether pad pumps require confirmed fan operation.
Define tank levels, pump permission, filter cleaning, dosing, zone selection, pressure and flow alarms, flushing and drain collection. Prevent dosing without verified water flow where required. Hydroponic circulation and recirculation need power-loss and sanitation responses.
Check every physical input from device to controller and every output from controller to equipment. Verify scaling, units, direction, tag and status. Simulate sensor ranges and fault conditions. Correct wiring or logic before integrated sequence tests.
Run automatic sequences through normal and abnormal conditions. Verify stages, delays, interlocks, alarms, manual override and recovery. Some climatic performance needs real outdoor conditions, so record what was tested directly and what requires seasonal follow-up.
Confirm motor direction, overloads, limits, valve travel, pump pressure, vent alignment, emergency stops and panel labeling. A software command cannot compensate for a reversed motor, blocked valve or incorrect limit switch. Qualified personnel should perform electrical tests and safe isolation.
Approved input-output list and control narrative
Point-to-point test sheet
Setpoint, delay and alarm register
Interlock and fault-response results
Equipment manual and automatic test records
Software version and backed-up configuration
Open issues, responsible person and due date
Operator training and handover sign-off
Authorize who can change setpoints, alarms or logic. Record old and new values, reason, date and result. Back up controller configuration before major changes. Seasonal tuning is normal, but undocumented changes can create hidden conflicts and make troubleshooting difficult.
It maps every sensor, status and command to a controller point, range, function and drawing reference.
No. It verifies signals, while functional tests verify sequences, interlocks, alarms and recovery.
Only authorized qualified personnel using documented change control and configuration backups.
The approved sequence should define safe states, restart order, alarms and any manual checks.
Use the control system category, document approval checklist and commissioning guide.
Send the equipment schedule and intended automatic functions through the contact page for an input-output checklist.