An isolation on an offshore wind turbine can span three different levels of switchgear, a section of array cable that sits inside the balance-of-plant contract, and a bay inside an offshore substation owned by a separate transmission asset. Isolation management software for offshore wind has to treat all three of those points as one register, not three, because a technician working inside a nacelle needs certainty that nobody has re-energised a cable forty kilometres away without their isolation still being reflected in it.
That's a different problem to isolation on a single platform or a land-based process plant, where most of the isolation points sit inside one asset owner's control. Offshore wind spreads the same isolation across parties, vessels and weather windows, and that's before you get to the parts of the boundary that only exist because the array is split across multiple owners of adjacent infrastructure.
What is isolation management for offshore wind turbines?
Isolation management for offshore wind is the process of proving equipment has been made safe before work starts: identifying every isolation point, confirming it's locked, tagged and proven dead, and keeping that status visible until every dependent task is closed. In offshore wind, those points typically span turbine, array cable and substation plant under different ownership.
The Electricity at Work Regulations 1989 require a system to be made dead and proved dead before work begins on it, and that duty doesn't shift because the point of isolation sits on a jack-up outside cellular signal range, or because three different organisations each own a piece of the boundary. The regulation doesn't care who's holding the paperwork. It cares whether the isolation actually holds.
Layered isolation boundaries across turbine, array and substation
A boundary of isolation on an offshore wind asset rarely stops at a single switch. A turbine-level isolation might need the tower base switchgear opened, a nacelle-level disconnect confirmed, and a lock applied at both — sometimes by different technicians on different shifts. Extend the work into the array cable and the boundary now includes a joint that belongs to the cable installation contractor's as-built drawings, not the turbine OEM's. Extend it again into the offshore substation and you're dealing with switchgear that a transmission owner, not the wind farm operator, may hold operational authority over.
Each of those layers has its own point of isolation, its own proving-dead procedure, and potentially its own competent person authorised to sign it off. A paper isolation certificate, or a spreadsheet held by one contractor's site team, struggles to show all three layers as a single connected boundary. It tends to show whichever layer that team is responsible for, which is exactly where gaps between scopes open up.
Multi-party sign-off between OEM technicians, contractors and marine coordination
Offshore wind O&M runs on a mix of turbine OEM service technicians, independent service providers, and the asset owner's own operations team, often on the same array in the same week. An isolation raised by one party frequently needs acceptance by another before work can proceed — the OEM technician isolating turbine-level switchgear, the BOP contractor confirming the array cable side is clear, and a marine coordinator confirming no vessel movement will disturb access while the isolation is live.
We've written before about why isolation is the weak point in permit to work, and the pattern in offshore wind is the same failure mode with an extra layer of complexity: more parties, more handoffs, and a marine element that most onshore or platform-based isolation processes don't have to account for at all.
Working offline: capturing isolation status on vessels and inside the nacelle
A technician isolating switchgear inside a turbine tower, or a crew member on a crew transfer vessel logging an isolation before boarding, often has no usable signal. If the isolation register only exists as a live system back onshore, the technician either has to leave the isolation unrecorded until they're back within range, or fall back to a paper tag that someone has to transcribe later.
Neither is a good position to be in when a second technician, an hour later, needs to check whether that point is already isolated before touching it. Mobile capture that works offline and syncs once connectivity returns closes that gap without asking technicians to change how or where they work.
What a digital isolation certificate needs to do
High voltage isolation certificate software for offshore wind needs to do more than replace a paper form with a screen. It needs to hold a boundary diagram against the certificate, not just a text description, so that a technician can see exactly which switchgear, which cable section, and which substation bay the isolation covers. It needs to record who applied each lock, who verified it, and what proving-dead method was used, with timestamps that survive a shift change or a crew rotation. And it needs to let a technician working offline log an isolation on a tablet inside a turbine and have that record appear in the shared register the moment the vessel is back within range — not the next morning, once someone remembers to enter it.
Where multiple permits depend on the same isolation, the system also needs to stop that isolation being removed while any dependent permit is still live. That's a check worth asking any vendor to demonstrate directly, rather than taking on trust.
Visibility for the onshore control room and marine coordinator
A marine coordinator planning vessel movements, or an onshore control room monitoring the array overnight, needs to see the state of every live isolation without phoning round each vessel or turbine team. That's less about dashboards and more about a single register that both operations teams and marine coordination are actually looking at, rather than each holding their own version updated at different times. Our work on digital control of work and on the SIMOPS blind spot in isolation management covers the same underlying problem: isolation status that only exists in one team's system isn't really shared, whatever the intention behind it.
The audit and incident-investigation case for digital isolation records
Isolation failures are among the more serious safety events in offshore wind, and an incident investigation will want to reconstruct exactly what the isolation boundary looked like at the moment work started — who verified it, what the boundary diagram showed, and whether any change to that boundary was recorded and communicated. A paper isolation log, split across a turbine OEM's binder, a BOP contractor's spreadsheet and a marine coordinator's radio log, makes that reconstruction slow and, in places, incomplete. A digital record that ties the certificate, the boundary diagram and the sign-off history together doesn't remove the risk of isolation failure, but it does mean the reconstruction after the fact is a query, not an exercise in cross-referencing three organisations' paperwork.
If you're reviewing how isolation is currently recorded and shared across your turbine, array and substation contracts, we can look at the existing process with your operations and marine coordination teams and identify where a shared, offline-capable isolation register would close the gaps between them.
Source: OEUK's Process Safety Leadership Principles: What the 2025 Strategy Means for Asset Integrity Teams