August 26, 2026
Shipbuilding

Europe’s shipyards build some of the world’s most sophisticated vessels, but maintaining that position will depend on more than technical capability. Protecting margins means understanding the true cost of how engineering information moves through a shipbuilding programme.

European shipbuilding occupies an unusual position. In terms of global volume, Europe is dwarfed by the major Asian shipbuilding nations. Yet when it comes to naval vessels, cruise ships, specialist offshore projects and other highly complex programmes, European shipyards continue to demonstrate some of the strongest capabilities in the world.

The challenge, then, is not a lack of engineering capability. Europe already possesses world-class shipyards, engineering organisations and specialist resources.

The challenge is turning that expertise into predictable, profitable programme delivery across increasingly diverse networks of partners, suppliers and stakeholders.

This is becoming more difficult as shipbuilding programmes become increasingly distributed. A vessel may involve a lead yard, external design organisations, specialist engineering contractors, equipment suppliers, production partners and, in naval programmes, government and security stakeholders. Each organisation can be highly capable in its own right, but the commercial performance of the programme depends on how well information and decisions move between them.

That is where a significant amount of cost can remain hidden.

The hidden cost of fragmented shipbuilding

Shipyards have spent years improving the efficiency of individual departments. Engineering has its targets. Procurement has its targets. Planning and production have theirs. External suppliers and contractors are measured against their own commitments.

Over the past two decades, shipyards have invested heavily in improving individual functions. Engineering and Planning became more digital. Production and Procurement became more efficient.

Those improvements created real value. However, improving individual functions does not automatically improve programme performance.

In many cases, collaboration improved, but organisations continued to optimize locally. The result is that the interfaces between organisations, disciplines and suppliers increasingly determine whether a programme protects margin or loses it.

Put simply, improving individual functions does not automatically improve programme performance.

A ship is not delivered by a collection of independent departments or organisations.

A decision made in engineering affects what planning schedules, what procurement orders, what a supplier manufactures and what production eventually has to build. If information is late, incomplete or no longer current, the cost rarely stays where the problem originated.

It moves downstream.

A design change may require a work package to be revised. An item may already have been ordered. A supplier may be working from an earlier revision. Production may discover that something cannot be installed as expected. The result can be replanning, additional procurement, rework, disruption or delay.

None of these events on its own is unusual in a complex shipbuilding programme. The problem is their cumulative effect.

I think of this cumulative cost as a fragmentation tax: the hidden cost a programme pays when information crosses organisational and departmental boundaries without sufficient continuity, visibility, or control.

The fragmentation tax doesn’t appear in one budget

The important point is that this tax does not appear neatly in one budget.

It may show up as additional production hours, a supplier change, an engineering revision, schedule contingency or lost time on the shop floor. Each department may still appear to be performing reasonably well while the overall programme loses margin.

This is where I believe shipyards need to rethink the way engineering is viewed by the business.

Engineering is more than a cost centre

Engineering is generally treated below the budget line as a cost centre. Its expenditure is visible and relatively easy to measure: people, hours, contractors, systems and software.

It is completely reasonable to manage those costs carefully. But there is a danger in assuming that reducing the cost of engineering is the same as improving the economics of shipbuilding.

It is not.

A shipyard can reduce engineering expenditure and still increase the total cost of delivering the vessel.

The reason is simple. Engineering does not only consume cost. It also has a major influence on the costs that appear later in planning, procurement and production.

That makes engineering an above-the-budget-line issue.

Senior management typically thinks above the budget line in terms of revenue, margin, delivery commitments, commercial risk and profitability. Engineering needs to become part of that conversation, not because it suddenly becomes a sales function or a profit centre, but because the quality and flow of engineering information have a direct effect on those business outcomes.

That changes the question leadership should be asking.

Instead of looking only at how much engineering costs, the business should also look at how much uncertainty engineering can remove from the programme.

  • Can changes be understood before they create disruption downstream?
  • Can planning see the information it needs at the right level of maturity?
  • Can procurement understand when a change affects an order?
  • Can external partners work with controlled information without the lead yard losing visibility?
  • Can production trust that what it receives reflects the current design intent?

These are not simply engineering questions. They are questions about programme performance.

Moving files isn’t the same as coordinating organisations

This is also why digital transformation in shipbuilding should not be treated solely as an engineering or IT initiative.

Much of the industry discussion around interoperability still focuses on moving information between systems. That is important, particularly in an industry where multiple CAD platforms, legacy systems and third-party data are a fact of life.

But moving a file is not the same as coordinating organisations.

Modern maritime programmes require decisions, requirements, responsibilities, and work packages to move across organisational boundaries while preserving traceability, accountability and control.

The larger challenge is maintaining control over requirements, revisions, configurations, responsibilities and decisions as work moves between engineering, planning, procurement, production and external organisations.

That is where technologies such as product lifecycle management and the digital thread become relevant. Their value is not simply that they connect software. Their value is that they can provide continuity and traceability across the programme.

For management, the outcome that matters is visibility.

When information remains connected, it becomes easier to understand where a project is moving away from plan and what the consequences may be. Problems can be identified while there is still time to act, rather than once they have already appeared as rework, delay or additional cost.

Capacity is hiding in the interfaces

This becomes particularly important as European yards look for ways to increase capacity.

Capacity is not only a question of facilities and labour. It is also a question of how efficiently information moves between the organisations involved in delivery.

Naval programmes provide a useful preview of where the industry is heading. Multi-yard collaboration, sovereign information, strict configuration control, long programme lifecycles, and complex stakeholder environments – all magnify the cost of poor coordination.

The immediate answer to a capacity problem is often more people, more infrastructure or more external resources. But there is another source of capacity available: reducing the amount of time and effort lost in the interfaces between organisations.

European yards already collaborate extensively. Engineering is outsourced. Specialist partners provide expertise. Suppliers take on significant portions of design and manufacture. Other facilities may provide additional production capacity.

The issue is therefore not whether shipyards should collaborate. They already do.

The question is how to make that collaboration more predictable and scalable without sacrificing intellectual property, configuration control, security or accountability.

If information, decisions and work packages can move between trusted participants while the lead organisation maintains control, external capability becomes easier to use effectively. Collaboration can then increase capacity rather than simply introducing another layer of risk.

Turning European engineering strength into commercial advantage

This is especially important for Europe, where the competitive advantage is unlikely to come from matching Asia yard for yard or competing solely on labour cost.

Europe’s strength lies in its engineering capability, specialist knowledge and ability to deliver technically demanding vessels.

The opportunity is to make better commercial use of that capability.

That requires looking beyond the performance of individual departments and asking how efficiently the entire programme operates.

For leadership, that means recognising that engineering is not simply a cost to be controlled. It is one of the functions that determines how much uncertainty, rework and downstream cost a programme will ultimately carry.

Until that connection becomes visible, shipyards risk improving departmental efficiency while allowing margin to disappear somewhere between engineering and delivery.

Moving engineering above the budget line is therefore not about changing accounting terminology.

It is about changing the management conversation.

The question is no longer simply: “How much does engineering cost us?”

The more important question is: “How much uncertainty can we remove from programme execution?”

Because in modern shipbuilding, competitive advantage increasingly depends not only on the capability of individual organisations, but also on how organisations work together.

For Europe, that may be the most important opportunity of all.