Anyone evaluating control of work software for an offshore wind asset quickly runs into the same problem: most of what's written about the market comes from the vendors themselves. Product pages describe their own platform in detail, occasionally alongside a comparison table that happens to favour them, but there's very little independent orientation for a buyer trying to work out what kind of system they're actually looking at before they start taking demos.
That's worth fixing before any procurement process starts, because the differences between vendor types matter more than the differences between individual products within a type.
What kinds of vendors sell control of work software to offshore wind operators?
Broadly, three categories serve this market: dedicated control of work platforms built specifically for high-hazard industries; broader EHS or governance, risk and compliance (GRC) suites that include a control of work module among several safety functions; and CMMS or ERP-adjacent systems that have added basic permit functionality onto an asset-management core. Each trades off depth of functionality against breadth of coverage differently.
Dedicated control of work platforms
These systems were designed around permits, isolations, and the interactions between them, usually with a lineage in oil and gas or another COMAH-regulated sector before extending into offshore wind. The strength here is depth: isolation registers that link directly to live permits, shared isolation handling across multiple concurrent work packages, and audit trails that hold up when a permit's history needs to be reconstructed months later.
For an offshore wind array, that depth matters more than it might first appear. A single high-voltage isolation on a substation or an inter-array cable can support several simultaneous work parties — a blade technician, a cable jointer, and a switchgear engineer might all depend on the same isolation being held. A platform built around isolation management as a first-class concept, rather than a permit form with a free-text isolation field, is generally better equipped to show that dependency and to stop an isolation being removed while other permits still rely on it. The trade-off is usually implementation effort: these systems tend to require closer integration with existing asset hierarchies and maintenance systems, and they're built with fewer assumptions about what the buyer's current process already looks like. We've written before about why isolation is the weak point in permit to work and how that plays out on assets running a high volume of concurrent activity.
EHS and GRC suites with a control of work module
A second group of vendors sell broader safety and compliance platforms — incident management, audit and inspection, risk registers, sometimes environmental reporting — with control of work as one module in a wider suite. The appeal is understandable: a single vendor relationship, one data model across several safety disciplines, and a procurement process that only has to happen once.
The trade-off tends to show up in the isolation and cross-permit functionality specifically. Where control of work is one module among many, it's worth checking how much genuine investment has gone into permit-specific workflows versus how much is a configurable form-builder applied to a generic case-management engine. That distinction isn't always obvious from a sales demo, which is exactly why it's worth testing directly rather than taking the feature list at face value.
CMMS-native and ERP-adjacent permit modules
The third category starts from the maintenance management system rather than from safety. Many CMMS and ERP platforms used in offshore wind O&M have added a permit or work-authorisation module to sit alongside work orders, spares, and scheduling. For straightforward, low-interaction maintenance tasks, this can work reasonably well, and it avoids the integration overhead of running a separate system alongside the CMMS.
The limitation tends to surface once work gets more complex — SIMOPS across multiple contractors, permits that need to be suspended and extended across a shift handover, or isolations that span more than one work order. These modules were generally built to authorise a task against a maintenance record, not to manage the interactions between several concurrent permits and a shared isolation boundary. Offshore wind operators moving from single-turbine campaigns to larger array-wide programmes, or bringing in specialist contractors alongside in-house technicians, are the ones most likely to find the gap here.
Offline capability and multi-contractor access matter more offshore than the vendor's marketing usually suggests
Offshore wind sites don't have the connectivity assumptions that a lot of enterprise software is designed around. A technician working inside a nacelle or a substation switch room may have no reliable signal, and a permit system that assumes constant connectivity will either fail quietly or push the crew back to paper. It's worth asking any vendor, regardless of category, how the system behaves offline — whether permits can be issued, accepted, and closed out without a live connection, and how that data reconciles once connectivity returns.
Multi-contractor access is a related question. Offshore wind O&M typically involves several contracting organisations working the same asset in parallel — turbine OEM technicians, cable specialists, marine coordination teams — and the control of work system needs to give each of them appropriate, auditable access without either locking them out of what they need or handing them visibility of unrelated work. How a vendor handles contractor onboarding, competency verification, and access scoping is usually a better indicator of maturity than the length of their feature list.
Questions worth bringing to a vendor briefing
Before a formal evaluation, a short orientation call with each shortlisted vendor is worth structuring around a handful of direct questions: which category the product falls into and why; how isolations are modelled and linked to permits; what happens when connectivity is lost mid-shift; how a contractor with limited system access gets a permit accepted and closed; and what integration work is required against the operator's existing CMMS or asset register. The answers will tell a buyer more about fit than a demo script will.
Understanding the category a vendor sits in is the orientation step — it doesn't replace a structured evaluation once a shortlist is in place. For operators building that shortlist, our related piece on digital control of work and connecting the system covers what integration between control of work and other operational systems actually involves, and isolation management and the SIMOPS blind spot goes further into the isolation-specific gaps that separate the vendor categories described here.
If you're starting to map the market for an offshore wind asset or O&M contract, we're happy to talk through where a dedicated control of work platform fits against what you're already running, without assuming the answer before we've looked at your current setup.