The BITD "Stress Test": Would Your Engineering Survive a Wartime Production Ramp-Up?

At Eurosatory, in June 2026, French Armed Forces Minister Catherine Vautrin used a phrase that the French defense industry will not soon forget: she put manufacturers through a "stress test" to verify their capacity to respond to a massive and simultaneous surge in demand under a high-intensity conflict scenario.

The message is clear. The State no longer merely asks the manufacturers of the French defense industrial base (BITD) to deliver what was ordered. It asks them to prove, starting today, that they could multiply their production rates by five or ten if the geopolitical situation required it. Recent orders show the scale of the shift: DGA (the French defense procurement agency) has ordered 5,000 DELCO drones for the Army, Eurenco has announced a production capacity of 10,000 to 15,000 military warheads per month, and France has committed to delivering sixteen Rafale F4 aircraft to Ukraine.

Faced with this stress test, manufacturers almost always concentrate their responses on the same levers: machines, buildings, material stocks, hiring. These are real levers. But they obscure a quieter and often more binding bottleneck: engineering data.

Production rate is not decided in the workshop alone

When we picture a production ramp-up, we visualize production lines running faster, teams working around the clock, suppliers delivering more. That is the visible part. The invisible part is everything that must stay consistent while volume explodes: technical definitions, bills of materials (BOM), requirements, qualification evidence, waivers, delivered configurations.

Here is a concrete example. A manufacturer of loitering munitions produces 200 units per month. Its engineering office manages design changes with a mix of aging PLM, Excel files, and meeting minutes. At 200 units per month, this system holds up, because the engineers who know the product's history can manually compensate for the gaps in the tooling. They know that version 3.2 of the guidance board is only compatible with firmware 5.1, that the batch of connectors delivered in March was covered by a waiver, that the export customer requires a specific variant of the safety system.

Now ask that same manufacturer to move to 2,000 units per month. It will have to hire, open a second line, qualify new suppliers, duplicate production on a second site, perhaps transfer part of the manufacturing to a partner. Each of these operations rests on a simple question: what exactly is the applicable definition of the product, and who has the right to modify it?

If the answer to that question lives in the heads of five engineers and across forty scattered files, the ramp-up will not merely be slow. It will be dangerous. Configuration errors in weapons production do not generate customer returns, they generate incidents.

What the stress test really reveals

The stress test invoked by the minister officially concerns production capacity. But anyone who has lived through a ramp-up audit knows that the questions drift very quickly toward engineering:

How long does it take you to integrate a design change requested by DGA and propagate it all the way to the production stations? Can you prove that the 500 units delivered last month conform to the qualified configuration? If your electronic board supplier fails, how long to qualify a substitute and document the impact on the entire system? Can you produce the France variant and the export variant simultaneously without any risk of crossing configurations?

These questions share a common thread: they are not about the capacity to build, but about the capacity to know. To know what is defined, what is applicable, what is impacted, what is proven. That is exactly the scope of what we call configuration management and requirements traceability, two disciplines that the defense industry has practiced for decades but with tools that were never designed for the era of wartime production rates.

The documentary legacy, the Achilles' heel of the BITD

The French defense industry has a remarkable culture of documentary rigor. The problem is not the rigor, it is the medium. In a significant share of the mid-sized firms of the BITD, technical documentation still rests on documents: Word specifications, Excel compliance matrices, PDF drawings, definition files frozen at milestones.

A document is a photograph. It freezes a state of knowledge at a given instant. But a production ramp-up is a film: changes follow one another, waivers multiply, suppliers change, variants proliferate. Managing a film with photographs imposes a constant task of manual synchronization, which ties up the most experienced engineers precisely at the moment when they are needed on design.

The figures we observe at the manufacturers we meet are consistent: between 30 and 50 percent of systems engineers' time is spent on document reconciliation tasks that create no technical value. At a constant production rate, this is a cost. During a ramp-up, it is a glass ceiling.

Three capabilities that make the difference

What would it take for a mid-sized defense firm to pass the stress test on the engineering side? Three capabilities stand out.

First capability: a single, living source of truth. All requirements, design elements, bills of materials, and supporting evidence must exist as objects linked to one another in a single repository, not as paragraphs inside documents. When DGA modifies a requirement, that modification must be instantly visible to everyone it concerns, along with its status, its history, and its impacts.

Second capability: instant [impact analysis](/features/impact-analysis). This is the crux of the matter, quite literally the nerve of war. Faced with a change (a requirement change, a component obsolescence, a supplier failure), the manufacturer must be able to answer, in minutes rather than weeks, the question: what is affected? Which subsystems, which qualification documents, which production lines, which contracts? This capability exists only if the links between engineering objects are formalized in a graph, rather than left implicit in the memory of the teams.

Third capability: certification traceability by construction. Proving conformity must not be a project, but a byproduct of daily work. Each requirement linked to its design elements, each design element linked to its verification evidence: when this structure exists, producing a supporting file for DGA or for an export customer becomes an extraction, not a reconstruction.

The paradox of the new entrants

An interesting phenomenon is currently playing out in the BITD: the massive arrival of startups and scale-ups, particularly in drones, loitering munitions, space, and electronic warfare. These players have a symmetrical advantage and handicap compared with the incumbents.

Their advantage: they have no documentary legacy. From day one they can build engineering structured as a graph, where traceability is native. Their handicap: they often discover defense qualification requirements along the way, and the documentary improvisation that worked for a demonstrator becomes a wall at the point of serial production for a state customer.

For these players, the choice of engineering infrastructure is a strategic choice on par with the choice of a factory. Those who structure their repository before the ramp-up turn compliance into a competitive advantage: they respond faster to tenders, absorb changes requested by DGA faster, and reassure the prime contractors who are looking for subcontractors capable of keeping pace.

What prime contractors will demand tomorrow

The logic of the stress test will not stop at production capacity. The major prime contractors, under pressure from the State, will gradually pass the resilience requirement down onto their supply chain. Questions that would have seemed exotic five years ago are already appearing in consultations: what is your propagation time for a design change? How do you manage multi-site traceability? Can you demonstrate control of your delivered configurations?

The subcontractors who can answer these questions with demonstrations rather than promises will gain market share. The others will become the weak links that the primes will seek to replace.

Engineering as a defense capability

We must take seriously the idea that mastery of engineering data has become a defense capability in its own right. Industrial superiority is no longer measured only in tons of steel and labor hours, but in speed of adaptation: speed to integrate lessons learned from the battlefield, speed to work around an obsolescence, speed to derive a variant for a new customer.

This speed has a precise technical condition: that the product exists in the form of a structured, queryable, traceable model, and not in the form of a documentary archipelago. This is the conviction that underpins Koddex's approach: a graph-based engineering repository that centralizes requirements, bills of materials, impact analyses, and certification traceability, designed for Europe's regulated industries.

The stress test of 2026 was an exercise. The next one might not be. The question every technical director in the BITD should ask today is not "would our machines hold up?" but "would our engineering hold up?". For many, the honest answer is: not yet. The good news is that this particular undertaking requires neither a building permit nor two years of civil engineering. It requires a decision.

Sources

- Réarmement, innovation, coopération : Catherine Vautrin inaugure Eurosatory 2026 (Ministère des Armées, juin 2026)
- Exercice « Endurance », préparer l'industrie de défense à l'éventualité d'un conflit majeur (Esteval, juin 2026)
- La DGA commande 5 000 drones du combattant Delco pour l'armée de Terre (Ministère des Armées / DGA, juin 2026)
- Le ministère des Armées commande 5 000 drones DELCO supplémentaires auprès du français Harmattan AI (Opex360, 23 juin 2026)
- Après la poudre et les charges d'obus, Eurenco va fabriquer en masse des têtes explosives pour les drones-kamikazes (L'Usine Nouvelle, juillet 2026)
- Paris et Kiev s'entendent sur une « feuille de route » pour livrer 16 Rafale à la force aérienne ukrainienne en 2028/29 (Opex360, 14 juillet 2026)

Koddex is the Engineering OS for regulated industries: a graph-based engineering repository that links requirements, bills of materials, impact analyses, and certification traceability. To assess the resilience of your engineering in the face of a production ramp-up, contact our team.