The shutdown window problem
Planned shutdowns on industrial plant are scheduled around production requirements, not engineering convenience. A sugar mill shuts between crush seasons. A mine shuts for scheduled maintenance on a fixed calendar. A food processing facility shuts for a few days each month. These windows are finite and the cost of overrunning is real — lost production, contractor penalties, season delays.
Control system engineering work that is not completed before the shutdown begins will either overrun the window or be left incomplete. Neither outcome is acceptable.
The answer is front-loading: completing as much engineering work as possible before the shutdown opens, so the window is used for physical installation, I/O commissioning, and handover — not for writing programs or resolving design questions.
What should be done before the shutdown
Engineering and design
Everything that can be done off-site should be done off-site:
- Full I/O list documented and reviewed with the site team
- Control panel design and hardware selection complete
- Electrical design drawings complete and RPEQ-reviewed if required
- PLC program written, commented, and reviewed
- HMI screens developed against agreed operator requirements
- Functional specification agreed and signed off
Hardware preparation
Hardware should arrive on site pre-built, configured, and tested:
- Control panel assembled in the workshop
- PLC hardware configured and program loaded
- HMI hardware configured with project loaded
- Network switches configured with VLANs and port assignments
- All hardware bench-tested against simulation I/O
Factory acceptance testing
A factory acceptance test (FAT) run in the workshop before shipping to site is the single most effective way to reduce commissioning risk. The FAT simulates the installed condition — I/O forcing, sequence stepping, fault injection — and identifies issues before the shutdown window is at risk.
Issues found during a FAT cost an hour in the workshop. The same issues found on site during a shutdown cost far more.
Contractor coordination
Other trades working during the same shutdown need to know what you need from them and when. Instrument technicians for loop testing, electricians for cable terminations, operators for functional sign-off — coordinate these hold points in advance so the commissioning sequence flows without waiting for people.
During the shutdown
With the engineering work complete and hardware pre-built, the shutdown activities become:
- Installation - panel mounting, cable connections, network patching
- I/O verification - each field signal checked against the I/O list with the PLC online
- Loop testing - each control loop exercised from field to HMI and back
- Functional testing - sequences and interlocks tested against the functional specification
- Operator walkthrough - operators stepped through the HMI and handover documentation
Each step has a documented hold point with sign-off. The commissioning record is built as the work progresses.
Managing the unexpected
No shutdown goes entirely to plan. The key is distinguishing between issues that must be resolved before the system can be handed back (blocking issues) and issues that can be resolved post-startup without affecting safe operation (punch list items).
Blocking issues — a fault in a critical interlock, a signal that does not respond as expected — must be resolved before handover. Punch list items — a label missing on an HMI screen, a minor sequence improvement — can be documented and addressed in the first weeks of operation.
A well-scoped project has a very short punch list at handover. A poorly scoped or under-prepared project has a blocking issue list that stretches the shutdown.
Documentation at handover
The shutdown is complete when the site is handed back with:
- Commissioning record with all loop test results and sign-off
- As-built drawings updated to reflect what was installed
- PLC program with current version tagged
- HMI project with current version tagged
- Outstanding punch list items documented with agreed resolution timeline
Documentation produced during a live commissioning is more accurate than documentation written from memory weeks later. Build it as you go.