Commissioning — proving it works under real conditions
A system that works on the bench and a system that works on site are different claims. Commissioning is where that difference gets found, and it's the phase most likely to be compressed when a project runs late.
Testing against what it's supposed to do
Commissioning works through the functional description systematically: every sequence, every interlock, every alarm, every failure mode that can safely be induced. Not just confirming the machine runs when everything is right, but confirming it does something sensible when a sensor fails, a guard opens, or air pressure drops. That's the part that gets skipped, and it's the part that matters at 3am.
Fault-finding on plant that won't behave
Often the call isn't for a new install but for a system that intermittently misbehaves and nobody can pin down. That's a methodical process — instrumenting the problem, narrowing it down, and resisting the temptation to change three things at once. Intermittent faults are usually mechanical, environmental or a marginal signal rather than the code, but the code is where everyone looks first.
Handover to the people who run it
The system gets handed to operators and maintainers who weren't there while it was built. Walking them through the sequences, what the alarms mean, and how to diagnose the common faults determines whether the plant runs well or whether you're on the phone every fortnight.
Working around production
Commissioning usually has to fit around a plant that still has to produce. Shutdown windows, night work and staged cutover are normal rather than exceptional, and planning for them is part of the scope.
Common questions
Can you commission a system you didn't design?
Yes. Coming to it fresh is sometimes an advantage — you test what the system actually does rather than what you assumed when you wrote it.
Do you travel to site?
Yes. Security work is South-East Queensland, but commissioning and automation work travels further — that's the nature of it.
We have an intermittent fault nobody can find. Can you help?
That's a common reason for the call. It's approached methodically rather than by guessing — instrument the problem, narrow it down, change one thing at a time.
Talk through the scope
Grouped technical hours or a fixed-scope project, depending on how defined the work is.