Offshore-Wind Construction Operating Model Architect

The mandate

Six offshore projects were developed under different joint-venture, package and regional assumptions, yet now compete for the same installation vessels, commissioning experts and fabrication oversight. Each project schedule is locally optimised and interface risk is pushed across foundations, cables, turbines, substations and marine logistics. Portfolio leaders cannot distinguish unavoidable weather exposure from weak readiness or commercially protected float. The narrowly defined task is to design a common construction operating model without replacing project-specific contracting or accountable project directors.

The named deliverable is a portfolio construction architecture covering lifecycle gates, package accountabilities, integrated readiness, interface ownership, marine resource allocation, schedule-confidence rules, change escalation, technical-query closure, HSE independence, joint-venture decisions and portfolio intervention. It will include a minimum controls data set, gate evidence catalogue, cross-project capacity board, interface heat map, schedule-assurance method and escalation protocol. The design must preserve legitimate consent, seabed, contracting and partner differences while eliminating accidental variation in how risk becomes visible.

Milestone one closes at week three with comparative mapping of all six projects and twenty recurrent interface failures. At week seven, milestone two presents three design options tested against vessel delay, fabrication slippage and late design change. Week eleven delivers a working simulation using two current project schedules and the constrained marine-capacity plan. The fourth milestone at week sixteen supplies the final architecture, adoption sequence, forum charters, role transitions and executive decision paper; billing follows each completed gate.

The chief projects officer accepts the model after every project director can run one adverse scenario through the proposed gates, the HSE leader confirms that escalation preserves stop-work independence, and portfolio planning reproduces the vessel-allocation logic. Acceptance also requires joint-venture reserved matters, contractual notice ownership and schedule uncertainty to remain explicit. An attractive diagram without tested decision paths, named evidence owners and agreed intervention thresholds will not satisfy completion.

The client will provide integrated schedules, package responsibility matrices, vessel commitments, interface registers, change histories, readiness evidence, partner governance documents and access to project and package directors. Consultants will not renegotiate EPC terms, certify schedules, issue engineering judgments, allocate vessels, mediate joint-venture disputes or run construction. Detailed redesign of project-control technology, claims preparation and implementation beyond the sixteen-week term remain outside scope and require separate authorisation.

Why this is external work

Project teams are accountable for their own outcomes and reasonably resist a model they fear will centralise authority without understanding contract reality. The portfolio office has data but lacks neutral construction credibility across packages and regions. External design leadership can compare patterns, arbitrate operating-model choices and conclude with a tested artefact rather than building a permanent parallel control tower.

What you will own

• Map six construction systems across gates, package boundaries, partner decisions, marine commitments and escalation behaviour.
• Identify recurrent interface failures and trace how schedule, contract, engineering and readiness signals were handled.
• Design portfolio forums, evidence thresholds and intervention rights that preserve project-director and HSE accountability.
• Simulate vessel loss, fabrication delay, cable defect and late design change through competing operating-model options.
• Define a minimum controls data set with source, owner, freshness, uncertainty and decision-use requirements.
• Reconcile joint-venture reserved matters and contractual notices with internal decision speed without offering legal interpretation.
• Deliver the tested architecture, adoption plan, role migration, unresolved dependencies and executive approval paper.

Candidate qualifications

• Has designed or reset construction governance across multiple offshore-wind or comparably complex marine megaprojects.
• Can evidence decisions spanning foundations, cables, substations, turbines, ports, vessels and commissioning interfaces.
• Understands integrated scheduling, package contracts, joint ventures, marine weather, readiness gates and independent HSE authority.
• Has won adoption from project directors without confusing portfolio visibility with central command of every package.
• Can facilitate adverse-event simulations and translate findings into precise role, evidence and escalation design.
• Is independent of relevant EPC contractors, vessel owners, certifiers and claims advisers benefiting from recommended choices.

Non-negotiables

• Can work in Copenhagen and complete two active port or fabrication-site evidence reviews.
• Will not certify schedules, interpret contracts or dilute independent stop-work and technical decision accountabilities.
• Brings direct offshore construction leadership across multiple packages; generic transformation experience is insufficient.
• Will make schedule uncertainty and unresolved joint-venture constraints visible in the final decision artefact.

1. 49 words maximum. Which offshore package interface has most often defeated an apparently integrated construction schedule in your work?
2. 49 words maximum. How would you test portfolio intervention rights without weakening the accountable project director?
3. 49 words maximum. What evidence would you require before treating installation-vessel float as genuinely available?