Controls commissioning should reduce uncertainty in deliberate stages. When power, safety, network, field I/O, software and mechanical readiness are tested at the same time, failures become difficult to isolate and the team can create new risks while trying to solve the original problem.
The checklist below is a planning framework for owners, OEMs, integrators and contractors. It does not replace site electrical procedures, lockout requirements, engineered safety validation or the project’s approved test plan. It helps organize those requirements into traceable evidence and clear ownership.
Before mobilization, translate the checklist into project-specific test sheets. Remove items that truly do not apply, add equipment identifiers and expected results, and name who can execute, witness and approve each stage. A generic list becomes useful only when it is connected to the installed system and the site’s authority structure.
Commissioning pressure often encourages teams to test around open construction work or accept verbal confirmation. The disciplined alternative is to record the condition, identify what it blocks and obtain the authorized disposition. This does not slow a well-managed startup; it prevents hidden dependencies from returning later as production faults or incomplete handover.
Readiness before power-on
Confirm approved drawings, completed construction checks, protective-device settings, grounding, enclosure condition, device labelling and an agreed energization boundary.
Hold a readiness review before energization. Confirm approved-for-test drawings, panel inspection status, conductor terminations, protective settings, grounding and bonding, enclosure condition and access control. Verify that the correct PLC, HMI, drive and device files are available and that licences and cables work. Open items must state whether they block power, block motion, limit a later test or can remain with an approved temporary control.
- Lockout and site-permit requirements
- Panel and field wiring inspection
- Network and addressing plan
- Current software and configuration backups
- Open deficiencies assigned to owners
Static and I/O checkout
Verify power supplies, controller health, safety circuits, input states, output wiring and instrument scaling before running equipment.
Use a controlled point list and prove one signal path at a time. For inputs, confirm field condition, electrical state, PLC address, engineering value and HMI indication. For outputs, verify the command path, interposing devices, field wiring and actual device response under an authorized method. Instrument checks include range, units, scaling, failure state and reasonable process response. Record swapped channels, inversions and temporary simulations instead of correcting them invisibly.
Manual functions and devices
Test each motor, valve, drive, actuator and instrument in a controlled mode. Confirm direction, feedback, limits, permissives and diagnostic messages.
Before automatic operation, test each device in the approved manual or maintenance mode. Confirm motor rotation, valve travel, limit switches, drive references, actuator feedback, local and remote selection and mechanical permissives. The HMI should explain why a command is unavailable and distinguish a missing permissive from a failed output. Complete safety and equipment-protection prerequisites before allowing motion or energy that depends on them.
Automatic sequences and faults
Run normal sequences and deliberately test credible abnormal conditions including device failure, communication loss, emergency stops and restart after interruption.
Run automatic tests from a known initial state and use a written sequence. Verify normal transitions first, then credible abnormal cases such as failed feedback, blocked material, instrument out of range, communication loss, emergency stop, power interruption and restart. Confirm that faults latch and reset as intended and that recovery does not bypass the condition that originally stopped the process. Performance trials should use defined duration, product and acceptance limits.
Handover
Preserve as-left backups, drawings, change records, test evidence, issue status and operator or maintenance actions. The final package should show exactly what was tested and what remains open.
Close commissioning with an as-left review. Compare online programs with the accepted files, preserve backups and record firmware, addresses and temporary settings. Every deficiency needs a final status, owner and due date; unresolved items should not disappear into informal notes. Handover includes approved drawings, test records, alarm or setpoint changes, training actions, spare-parts needs and the exact operational restrictions that remain.
Frequently asked questions
Who should own the commissioning checklist?
One commissioning lead should control the master record, while individual tests have named executors and approvers from the responsible electrical, controls, mechanical, safety and operations groups.
Can I/O checkout begin before mechanical completion?
Some static checks may proceed within an approved boundary, but the team must label unavailable equipment and prevent outputs or motion that depend on incomplete construction or safety work.
What is the difference between a deficiency and a failed acceptance test?
A deficiency records an issue requiring action. A failed acceptance test means a defined requirement was not met and must be corrected, retested or formally dispositioned by the authorized stakeholder.
What files belong in the final controls handover?
Include as-left PLC, HMI, drive and network files; drawings and redlines; version information; test evidence; issue status; setpoint changes; and operating or maintenance actions.
Use the guide inside an approved work process
This guide supports planning and technical review; it does not authorize a change to live equipment. Before applying it, identify the system owner, production boundary, electrical and machine hazards, required permits, current backups and the person authorized to approve testing. Keep confirmed evidence separate from assumptions, and record any temporary simulation, force, inhibit or workaround under the site’s approved method.
If the installed condition does not match the available drawings or software, preserve the discrepancy and resolve ownership before downloading, energizing or bypassing a protective function. Final acceptance should reference the actual as-left configuration, executed test evidence, open actions and responsible approver.
Planning a related controls project?