
If you’ve ever walked onto a site during commissioning, you’ll know the feeling: every cable tray, every cabinet, every terminal strip is buzzing with last-minute activity. People are testing, adjusting, documenting, correcting — all at the same time. And somewhere in the middle of that controlled chaos sits the low voltage systems that will eventually hold everything together once the project goes live.
The interesting thing is that reliable low-voltage systems rarely is a result of luck.
They occur when hundreds of small steps are executed in a disciplined, documented way and in the right order.
The truth is, reliable LV systems don’t just “happen.”
They’re built through a long chain of small, disciplined steps. And if even one link is weak, you’ll often see the consequences during handover or — worse — during operation.
At Sirius Energy, we’ve spent years commissioning critical systems across substations, hospitals, industrial plants, offshore assets, and energy facilities. And the same pattern always repeats: low voltage systems work beautifully when the process behind them has been handled with structure, patience, and a bit of healthy skepticism.
This blog explores what that process really looks like.
Most people think reliability begins when the first cable is pulled. But the truth is: by the time installation begins, many of the most important decisions have already been made.
This is where maskinmestre have a natural advantage.
They’re trained to look at a system in context, asking questions like:
• What does this circuit protect?
• What happens if it fails at 02:00 on a Sunday?
• Who depends on the alarm generated here?
• What other subsystems does this panel silently support?
These are simple questions, but they shape decisions about redundancy, cable routing, separation of critical circuits, testing requirements, and even the level of documentation needed. Without them, LV systems are installed “correctly” — but not necessarily reliably.
By far the most common source of LV failures is what happens during installation. Not because people are careless, but because LV work often involves so many hands, trades, changes, and interfaces that small inconsistencies accumulate.
Individually, these things look harmless. Together, they can create exactly the kind of intermittent, unpredictable faults that are hardest to find during commissioning.
Good installation oversight is not about policing contractors — it’s about making sure the thousands of small details add up to one coherent system.
Most problems are avoided simply by having someone who can walk through a room and intuitively see where inconsistencies or risks might appear later.
In theory, FATs and SATs are straightforward: test the system in controlled conditions, then test it again when installed.
In reality, they are often squeezed by schedules, access limitations, or simply the desire to keep things moving.
This is where discipline pays off.
A FAT that is too light shifts the risk to SAT.
A SAT that is rushed shifts the risk to operation.
And a system that goes live without both is an incident waiting to happen.
We often see FATs executed with everything running perfectly on a test bench — but when the equipment arrives on site, environmental conditions, grounding, cable lengths, vendor interactions, and installation realities change the behaviour completely.
A patient, thorough FAT/SAT doesn’t just check if the system works.
It checks if it works here, under these conditions, with these interfaces, for this facility.
It’s not glamorous, and it rarely fits neatly into a Gantt chart, but it’s where most reliability is “won” quietly in the background.
One of the most overlooked parts of LV commissioning is testing the system in something close to real operation. It’s easy to check whether a lamp lights up or an alarm comes through.
These are the kinds of tests maskinmestre instinctively push for — not because a specification demands them, but because they understand what actually goes wrong once a plant is live.
It’s also where unexpected issues are found: missing interlocks, signals reversed, delays longer than expected, fail-safe logic that doesn’t fail safely, or systems that recover poorly after a disturbance.
It’s the kind of insight that only comes from having lived with real systems — and knowing how they behave when things don’t go according to plan.
No one gets into engineering because they love documentation. But a reliable LV system without proper documentation is like a machine without a manual: eventually, someone will break it simply because they don’t understand how it works.
Good documentation doesn’t need to be pretty — it needs to be accurate.
It needs to reflect what was actually installed, not what someone originally designed.
And it needs to survive the first ten years of operation, long after the contractors are gone.
In our experience, the best documentation isn’t created at the end — it’s created as the project progresses. And it’s updated every time something changes.
It’s not glamorous, but it prevents a huge amount of frustration and failure later.
There’s a common theme across all reliable LV systems we’ve worked on: they weren’t created by “heroes” or miracles.
They were created by:
Maskinmestre tend to be good at this because their training forces them to see systems as living things — connected, layered, and dependent on human behaviour just as much as on technical design.
And that mindset is what ultimately turns a complex set of cables, logic, breakers, and cabinets into something you can trust.
Low voltage systems rarely get the attention they deserve. They’re overshadowed by the dramatic high-voltage equipment, and their complexity is often underestimated because they operate quietly in the background.
But the more facilities rely on automation, control, and interconnected systems, the more these small circuits carry heavy responsibilities. Reliability doesn’t come from good intentions — it comes from structure, testing, patience, and a deep understanding of how the system behaves when the unexpected happens.
As with so many things in engineering, reliability is never an accident; it’s the result of disciplined habits applied consistently over time.