The customer's own project team came back, post-pilot, with two further use cases they had identified themselves, before any expansion conversation from our side. Customer-named is structurally different from vendor-driven. That signal is the read this story turns on.
The pilot itself was deliberately bounded: one defense-confidential use case, closed in December 2025. The point of a bounded pilot at this customer is not throughput. The point is technical fit, tested cheaply, because the cost of a wrong tool decision inside this regulatory regime (EMAR · AS9100 · FAA Part 21, plus national defense supplements) is measured in program exposure across multi-decade lifecycles, not in procurement budget. A bounded pilot. The customer's team named the next two use cases themselves.
The customer and the entry
The customer sits at roughly €11–12B revenue and 30,000 employees, a prime contractor across military aircraft, helicopters, launchers, missile-system and electronic-warfare programs. Flagship platforms are in service to multiple national air forces with planned operational lifetime extending into the 2060s. Engineering data sits under multi-decade configuration management; regulatory traceability requirements exceed automotive by an order of magnitude.
What the engineer's day looks like
The structural problem defense aerospace OEMs face, and what an analytical layer over the engineering data graph addresses, looks something like this in practice:
"This [military-transport] variant for a national customer needs a software update on the flight management system. Before approval: which subsystem revisions are certified for this specific aircraft tail number? Which integration tests have been completed against the current avionics build? Which configuration deltas exist relative to original delivery, across two decades of program history? Which national-jurisdiction certification archives have to be checked?"
Today that verification spans PLM (product lifecycle management) + ALM (application lifecycle management) + ARXML (AUTOSAR XML) + multiple national-jurisdiction certification archives, often a multi-week senior-engineer task per change. The Product Explorer pilot put that verification into a single graph view, scoped to a specific defense-confidential use case.
The military-transport flight-management scenario is illustrative of the customer's R&D scope (the platform referenced is a public program); the actual pilot program is defense-confidential. The structural verification pattern is consistent with public defense-aerospace certification regimes (EMAR (European Military Airworthiness Requirements), AS9100, FAA Part 21).
What Product Explorer's view surfaces
For the flight-management-update query, Product Explorer surfaces in a single tail-number-scoped view:
- The tail-number-specific configuration tree, including national-customer-specific avionics deviations and as-delivered baseline
- Subsystem revisions certified for this exact build, ranked by recency and certification authority (EMAR / national MAA (Military Aviation Authority) / customer-specific addenda)
- Integration-test results from the current avionics build's regression cycle, scoped to the FMS subsystem and adjacent traffic on the same data bus
- Configuration deltas relative to original delivery, decomposed by certification-bearing subsystem with the certification path attached to each
- Cross-references to the relevant national-jurisdiction certification archives, surfaced as audit-trail-linked entries rather than free-floating documents
The view replaces what is currently a multi-week senior-engineer reconciliation across PLM + ALM + ARXML + multiple national archives.
What happened after the pilot
Two operational reads from the post-pilot conversation:
- The pilot was reframed from an IT proof-of-concept into a real engineering use case. That is a category shift in how the customer sees the work, the difference between a tool the IT organization evaluates and a layer R&D actually wants to build on.
- The customer's project team surfaced two further use cases on their own. That is structurally different from vendor-driven upsell. The customer is naming the next steps.
Why a bounded pilot at this customer signals more than it looks
The traceability bar at the customer is structurally above automotive. Defense aerospace certification regimes (EMAR, AS9100, FAA Part 21, plus national defense supplements) require auditable configuration trees from raw material to fielded unit, retained across decades. The cost of a configuration-management gap surfacing late in a program is measured not in single-digit millions but in regulatory program exposure, with consequences extending into national-security-relevant operational availability.
That is the context for reading the post-pilot reframe. Boring IT use case → real engineering use case sounds like an anecdote until you read it inside the regulatory regime above. Engineering at this customer does not have spare hours for vendor demonstrations. Customer-internal expansion at this traceability bar takes the form it took here: the team commits, then identifies further use cases on their own, because the technical fit cleared a bar that point-tools do not clear.
The pilot was bounded because the cost of a wrong tool decision in this regime is enormous. The customer-named expansion is real because the team did the work to identify it.
Program shape
| Customer | Prime contractor across military aircraft, helicopters, launchers, missile-system and electronic-warfare programs; flagship platforms in service to multiple national air forces with planned operational lifetime into the 2060s |
|---|---|
| Scale | €11–12B revenue · 30,000 employees |
| Program scope | Defense-confidential R&D, flagship platforms in service across multiple national air forces with planned operational lifetime extending into the 2060s |
| Pilot scope (regulatory regime) | EMAR · AS9100 · FAA Part 21 · national defense supplements, the bar the bounded pilot operated against |
| Verification baseline | 4 system classes (PLM + ALM + ARXML + national-jurisdiction certification archives) reconciled per change · multi-week senior-engineer task today · single tail-number-scoped view in pilot |
| Pilot pattern | Deliberately bounded to one defense-confidential use case; the team's identification of two further use cases is the post-pilot signal |