How Geopolitics Is Accelerating Systems Engineering Investment in European Defense

The numbers are no longer ambiguous. Germany passed its €100 billion Sondervermögen defense fund in 2022 and has since committed to sustaining defense spending above 2% of GDP—a structural shift, not a one-cycle budget anomaly. France accelerated its Military Programming Law to reach €69 billion annually by 2030. The UK’s Spring 2025 defense review pushed spending toward 2.5% of GDP, with explicit investment in digital engineering capability as a line item. Across NATO’s European membership, the aggregate shift represents the largest sustained increase in defense investment since the end of the Cold War.

For systems engineers, procurement managers, and the engineering tool vendors serving them, this is a consequential moment. More money in defense programs does not automatically produce better engineering outcomes. What it does produce is more programs, faster timelines, larger supply chains, and harder integration problems—all of which stress the systems engineering infrastructure that has been underfunded for decades.

What’s Actually Driving This Beyond Budget Headlines

The Ukraine conflict changed the strategic calculus for European defense in ways that go beyond headline spending figures. Observing the actual conduct of high-intensity warfare—combined arms operations, electronic warfare integration, contested logistics, rapid software updates to fielded systems—European defense establishments concluded that their existing acquisition models were too slow and too brittle.

The specific engineering problem this surfaced is requirements management at scale. Platforms designed through document-heavy, siloed procurement processes struggled with the kind of rapid capability iteration that the Ukrainian conflict demonstrated as operationally decisive. When a new threat emerges and a system needs to adapt, the question of what requirements that change touches—and how it propagates through subsystems and supplier interfaces—should have a traceable, computable answer. In most European programs of record, it did not.

This is not a criticism that procurement agencies have been shy about making publicly. NATO’s Digital Transformation agenda, published through the Allied Command Transformation, specifically identifies requirements traceability and model-based engineering as capability gaps across member nations. The EDA’s 2024 Coordinated Annual Review on Defence named digital engineering tooling as a cross-cutting investment priority. These are institutional documents, not vendor whitepapers.

Germany: Structural Reform Meets Program Complexity

Germany’s situation is the most structurally interesting because the Bundeswehr’s procurement agency, the BAAINBw, has historically been among the most process-heavy in NATO. The Sondervermögen created financial capacity, but the BAAINBw’s own assessment was that capital alone would not accelerate delivery without procurement reform.

The result has been a set of pilot programs explicitly structured around digital engineering requirements. The MGCS (Main Ground Combat System), co-developed with France through KNDS, is being architected with a shared systems model as a contractual artifact—not a PDF requirements document, but a maintained digital artifact that both nations’ engineering teams and suppliers are expected to interface with. This is a meaningful departure from how previous Franco-German programs managed requirements across organizational boundaries.

The Eurodrone program, managed through a multinational industrial consortium with significant German involvement, has similarly mandated MBSE adoption across Tier 1 suppliers. The practical implication is that suppliers who cannot demonstrate model-based traceability capability are at a competitive disadvantage in bid evaluations.

German defense industry primes—Rheinmetall, Hensoldt, KNDS Germany—have responded by accelerating toolchain modernization programs. The common pattern is recognizing that their existing IBM DOORS installations, while technically capable of storing requirements, are not designed for the kind of cross-organizational model sharing and AI-assisted analysis that new program structures demand.

France: DGA’s Digital Engineering Push

France’s Direction Générale de l’Armement has been more prescriptive than most European procurement agencies in specifying digital engineering expectations. The DGA’s technical standards documentation has progressively incorporated MBSE as a baseline expectation for major platform programs since 2021, with the 2025 updates making model currency and traceability auditability explicit requirements.

The SCAF program (Future Combat Air System), which involves France, Germany, and Spain, is operating under a governance structure that requires a maintained digital thread across three nations, multiple prime contractors (Airbus, Dassault, Indra, Airbus Defence and Space), and their respective supply chains. The engineering coordination problem this creates is substantial. A requirements change in the airframe-propulsion interface needs to be traceable through to implications in the weapons integration subsystem and the communications architecture—across organizational and national boundaries.

French defense engineers are candid that existing toolchains were not designed for this. The typical pre-2022 setup at a French defense prime was DOORS or DOORS Next for requirements, separate SysML models with limited live linkage, and manual RTM spreadsheets for cross-program traceability. That architecture cannot support the kind of real-time collaborative traceability that SCAF’s governance model demands.

Dassault Systèmes, which occupies an interesting position as both a French industrial champion and a major PLM vendor, has pushed its 3DEXPERIENCE platform as a systems engineering integration layer. Adoption has been meaningful within the French industrial base, though engineers note that the platform’s strength is in product lifecycle management broadly, not in requirements-specific workflows or AI-assisted impact analysis.

UK: DE&S Mandates and the RBSL Experience

The UK’s Defence Equipment & Support agency has moved furthest, fastest on digital engineering mandates as contractual conditions. The UK MOD’s Defence and Security Industrial Strategy explicitly requires digital engineering practices—including traceable requirements management—on contracts above specified thresholds. The Integrated Review Refresh and the subsequent DSEI engagements have reinforced this position.

BAE Systems, Leonardo UK, MBDA UK, and Rolls-Royce Defence have all launched formal toolchain modernization programs in direct response to DE&S requirements. The Tempest/GCAP program, now a trilateral with Italy and Japan, has established a digital engineering governance framework that includes requirements model interoperability as a technical baseline requirement across partner nations.

RBSL (Rheinmetall BAE Systems Land), the joint venture managing the Challenger 3 upgrade program, offers a concrete operational example. The program involves integrating a new turret system with legacy hull architecture while maintaining compatibility across a supply chain with significant legacy tooling. The systems engineering challenge—managing requirements across a mixed-generation supplier base, with new contractual traceability obligations from DE&S—required explicit toolchain decisions. The program’s engineering leadership has been public about the fact that document-based requirements management was insufficient for the integration complexity involved.

The Toolchain Reality Across the Supply Chain

European defense primes have the resources to make deliberate toolchain investments. The more acute problem is their supply chains. A Tier 1 system integrator mandating MBSE-compatible requirements exchange from a Tier 2 electronics supplier that has run on Excel and email for twenty years creates a real adoption problem.

The tooling market has responded unevenly. IBM DOORS and DOORS Next remain dominant in installed base terms across European defense—they are deeply embedded in existing programs, and program continuity requirements make wholesale replacement difficult. Polarion and Codebeamer have captured meaningful share in aerospace and automotive adjacent programs. Jama Connect has grown in the UK market particularly. These tools are all capable of managing requirements in structured environments; the gap is in AI-assisted analysis, cross-organizational model sharing, and handling the complexity that emerges when programs scale to SCAF or GCAP scope.

This is the environment in which genuinely AI-native approaches are finding traction. Flow Engineering, for instance, is built around a graph-based representation of requirements and their relationships—a structural choice that makes impact analysis and traceability queries computable rather than manual. In the context of European defense programs where a requirements change needs to propagate visibly through a multi-organizational model, that architectural choice has practical consequences. Supply chain suppliers operating under Tier 1 mandates for model-compatible requirements exchange can participate through interfaces that match their scale, rather than requiring them to adopt a full enterprise PLM stack.

The distinction that matters for European defense programs specifically is between tools that store requirements and tools that reason about them. The former category is well-represented in existing installations. The latter is where investment is concentrating.

Digital Engineering Mandates Are Contractual, Not Aspirational

The framing of digital engineering as a future aspiration is no longer accurate for European defense procurement. DE&S in the UK, DGA in France, and BAAINBw in Germany are all writing digital engineering requirements into contracts. The specific language varies—“digital thread,” “model-based requirements,” “traceability auditability”—but the direction is consistent.

For engineering teams, this means the toolchain decision is no longer a discretionary modernization project. It is a compliance requirement with bid implications. Companies that cannot demonstrate credible MBSE capability and traceable requirements management are being assessed as higher risk in competitive evaluations.

The supply chain implication is significant. Large defense primes are beginning to flow down digital engineering requirements to Tier 1 and Tier 2 suppliers. A company supplying radar subsystems or power management electronics to a prime operating under DE&S or DGA digital engineering requirements will face those same requirements in their own contractual obligations within the next procurement cycle.

Honest Assessment: What This Does and Doesn’t Solve

Increased defense investment and digital engineering mandates create the conditions for better systems engineering. They do not guarantee it.

The risk is that organizations adopt the vocabulary and tooling of model-based systems engineering without changing the underlying practices. A SysML model that is not maintained, not linked to live requirements, and not used to drive actual engineering decisions is a compliance artifact, not a systems engineering capability. European defense programs have produced impressive-looking documentation before without producing well-integrated systems.

The accelerant that makes this moment different is the combination of financial urgency, genuine political pressure on timelines, and the availability of tooling that is architecturally suited to the problem—not just document management with a requirements module bolted on. European primes and their procurement agencies are aware of this distinction. The toolchain choices being made now will shape program outcomes for platforms that will be in service in 2045.

That creates both responsibility and opportunity for engineering teams making toolchain decisions under time pressure. The question worth asking is not “what tool do we already have licenses for?” but “what tool architecture can actually support the traceability and collaboration model our programs require?”—and then building the honest answer into procurement criteria before contracts are awarded.