Why Mario Draghi Is Right: The ERP Crisis Behind Europe’s Construction Productivity Gap

Mario Draghi didn’t mince words. Europe’s problem is not ambition. It’s execution.

 

In his recent interventions on European competitiveness, Draghi points directly at fragmentation, low productivity, and weak industrial coordination—especially in defense, energy, and infrastructure. What he doesn’t explicitly say, but every engineer on a megaproject knows, is this:

 

Europe is trying to solve engineering problems with accounting software.

 

That is the ERP crisis at the heart of European construction.

 

The Core Problem: Financial ERPs Managing Physical Reality

 

For three decades, European contractors, shipyards, and infrastructure owners have been told they are using “best practice.” In reality, they are using systems optimized for financial consolidation, not for building ships, grids, or cities.

 

These platforms were designed for:

 

• Service-driven operating models
• Transaction-centric financial control
• After-the-fact reporting, not real-time execution control

 

Construction, shipbuilding, and infrastructure are the opposite:

 

• Physical production
• Time-critical sequencing
• Engineering-driven cost behavior

 

This mismatch is why productivity stalls, margins evaporate, and projects drift until the auditors arrive.

 

The productivity gap exists because we are using finance tools to manage engineering systems.

 

---

 

Stop Managing Construction With Accounting Software

 

Accounting systems answer one question well: “What did we spend?” They fail at the question that actually matters: “What is happening on the ground right now?”

 

In an era of:

 

• High energy costs
• Thin margins
• Public scrutiny and audits

 

Quantum Cost Control is not a luxury. It is the only way to protect capital.

 

Quantum Cost Control means linking:

 

• Time (WBS)
• Quantities (BoQ)
• Physical progress
• Cost behavior in real time

 

Not after the fact. Not at month-end. Not when it’s already too late.

 

1. Defense & Shipyards: Draghi’s Wake-Up Call

 

Context

 

Draghi explicitly calls out Europe’s fragmented defense market and the absence of a true Defense Industrial Base. Shipyards are central to this ambition—frigates, patrol vessels, refits, naval readiness.

 

The Pain

 

European shipyards struggle with:

 

• Complex, multi-tier subcontracting
• Poor visibility of block fabrication and assembly
• Excel-driven coordination between engineering, procurement, and production

 

The result? Cost overruns that don’t appear until they become state-audit issues.

 

The Reality Check

 

You cannot build naval vessels with:

 

• Disjointed Excel sheets
• Generic US finance ERPs
• After-the-fact cost reporting

 

The Move

 

ProjectVIEW Shipyards Module connects:

 

• Ship assembly & hull structure breakdown
• WBS-driven production sequencing
• BoQ-driven cost control

 

Cost overruns are detected during fabrication, not during parliamentary hearings.

 

Draghi demands a unified defense industrial base. You don’t get that without a project-centric ERP built for shipyards.

 

2. Energy Infrastructure & Grids: Where Europe Is Bleeding Time

 

Context

 

Europe needs over €500 billion in grid investments this decade to meet climate and electrification targets. The bottleneck isn’t funding alone—it’s execution.

 

The Pain

 

Grid projects are:

 

• Linear, spread across geography
• Capital-intensive
• Constantly changing in scope and quantities

 

An accounting-based ERP tracks invoices. Excel tracks assumptions. Neither tracks physical progress vs. cost.

 

The Move

 

WBS-driven budgeting with BoQ alignment.

 

ProjectVIEW doesn’t ask, “What did we pay?” It asks, “What quantity was installed, where, and at what unit cost?”

 

This is the only way to:

 

• Control scope creep
• Support EU Green Deal regulatory reporting
• Defend claims and certifications

 

Differentiation matters:

 

• Generic ERPs track spend
• DANAOS tracks physical reality vs. spend

 

That distinction decides whether grids get built on time—or not at all.

 

3. Large-Scale Construction: Scale Without Control Is Bankruptcy

 

Context

 

As Enrico Letta points out, Europe’s Single Market is too fragmented. Construction firms must scale through mergers and cross-border operations to survive globally.

 

The Pain

 

Post-merger reality:

 

• Different estimation standards
• Incompatible cost structures
• Disconnected systems per country and business unit

 

Growth without governance doesn’t create champions. It creates chaos.

 

The Move

 

A Single Source of Truth.

 

ProjectVIEW standardizes:

 

• Estimation logic
• Procurement rules
• Execution tracking

 

Across projects, countries, and subsidiaries.

 

Scale without control is bankruptcy. Scale with project-centric governance is competitiveness.

 

The Hard Truth Europe Must Face

 

US-based ERPs are excellent financial reporting engines for the service economy.

 

But Europe’s future competitiveness depends on:

 

• Shipyards
• Energy grids
• Infrastructure
• Physical assets

 

That is the physical economy.

 

ProjectVIEW ERP was built for that reality.

 

Not as an accounting system with add-ons—but as a project-centric operating system where:

 

• Time drives cost
• Quantities define progress
• Deviations are exposed early

 

Final Call to Action

 

Mario Draghi is right. Europe doesn’t have a capital problem. It has an execution problem.

 

And execution will not improve until Europe stops pretending that:

 

• Accounting software can manage engineering complexity
• Financial visibility equals operational control

 

Stop managing construction with accounting software. If Europe wants to win in defense, energy, and infrastructure, it must first fix the systems that run them.