"Wir haben rotierendes Radar, wir haben ein nicht rotierendes Radar, wir haben Landradar... wir möchten jetzt die drei verschiedenen Radarsystemspezifikationen vereinheitlichen. Alleine dieses Konsolidieren setzt's mir momentan grade drei Monate an."
(We have rotating radar, non-rotating radar, land radar... we want to consolidate three different radar system specifications. Just this consolidation is currently costing me three months.)Lead radar specification engineer · NATO supplier · April 2026
The customer is a NATO supplier of rotating, non-rotating, and land radar systems, roughly €2B revenue and 7,000 employees. Three radar variants, three Lastenhefte, ~3,000 requirements to align. Three months of senior-engineer effort per consolidation cycle.
The architecture the engagement would test is already in production at a peer European land-systems prime: on-premise, across four national defense procurement authorities, audit-grade access controls layered into the data model itself. Hensoldt-equivalent is another deployment of the same architecture, in radar. The structural argument the lead engineer raised in the same conversation, Berechtigungsverwaltung (need-to-know access control), is the structural argument that holds here.
What three months of consolidation buys today
Each radar variant is its own program. Each Lastenheft runs into the thousand-requirement range. Without a unified base, every new radar variant duplicates the requirements-engineering effort. With one, requirements inherit from a base spec and only the variant-specific deltas need bespoke work.
The economic reasoning is straightforward; the bottleneck is in the consolidation step itself, which currently costs three months of senior-engineer effort before any new program can build on it.
+ need-to-know access controls
In the structural argument, the graph ingests the three Lastenhefte, computes the requirement intersection, and surfaces the variant-specific deltas. The three-month senior-engineer consolidation cycle compresses to a graph-query exercise plus engineer review. That is the structural argument. The peer-prime production reference establishes the access-control side.
Berechtigungsverwaltung is a structural argument, not a feature ask
In the same conversation, the lead engineer surfaced the gating question:
"Bis dann wir im Bereich das den Ausdruck 'need to know' in den Raum schmeißen. Dann ist meistens dann nicht mehr so ganz klar, was ist überhaupt da."
(Until we throw the term 'need to know' into the room, then it's usually no longer clear at all what's even there.)Lead radar specification engineer · NATO supplier · April 2026
In a defense engineering organization, access to specification data is not uniform. Need-to-know compartmentalization is the default rather than the exception. A graph that represents requirements has to also represent who can see what, and the who can see what layer has to hold up to defense audit standards. Any platform that does not represent the compartmentalization is asking the customer to bypass it.
The existence proof for the access-control answer is already running in production at a peer European land-systems prime: on-premise, across four national defense procurement authorities, audit-grade access controls layered into the data model itself. The Hensoldt-equivalent engagement is another deployment of the same architecture, in radar. On this side the architecture meets the customer's specific compartmentalization; the architecture itself is already in production at the peer prime.
The value math behind the consolidation
Three months of senior-engineer effort per consolidation cycle is the bottom of the value envelope. Industry-benchmark cost of a senior German defense-systems engineer-hour in 2025–26 sits around €110–150 per hour fully loaded.
That is before opportunity-cost accounting on senior radar specialists not working on novel program content during the consolidation window.
Why this is a category signal, not an account ask
The fact that two independent European defense primes have converged on the same structural requirement, audit-grade need-to-know access controls layered into the data model itself, is itself the category signal. Berechtigungsverwaltung shows up because defense engineering data is structurally compartmentalized. Defense as a customer category pulls product strategy toward the structural shape of regulated engineering data: on-premise topology, jurisdiction-aware audit, role-based and need-to-know access controls layered into the data model itself. Two-of-two so far is the evidence.
What the test is bounded to
Scope is held to the radar-Lastenheft consolidation on the leading workstream for the duration of the evaluation. The access-control layer is not what the test is for; that question is answered at the peer prime in production.
Program shape
| Program | Three-radar specification consolidation |
|---|---|
| Radar variants | Rotating · Non-rotating · Land |
| Current consolidation effort | 3 months per cycle |
| Direct engineering cost per cycle | €55–145k |
| Customer voice | Lead engineer (radar specification) |
| Structural gating concern | Need-to-know access management (Berechtigungsverwaltung) |
| Architecture existence proof | Peer European land-systems prime, in production. On-premise. 4 national jurisdictions. Audit-grade. |
| This engagement | Second instance of the same architecture |