In defence and aerospace, the evidence matters as much as the result.
Most industries test to reduce the chance of disruption. This one tests for that reason and for another: someone may later ask you to prove what a system did, for a specific serial number, on a specific date, years afterwards. That changes what a test is for. A passing result that cannot be produced again is not much use.
What makes Defence and Aerospace different from a standard SAP landscape.
None of this is exotic. All of it is known. It goes wrong anyway, because the test plan is usually written against the process rather than against the way the process actually behaves here.
Traceability has to hold in both directions
Forward from a component to every assembly and customer it reached; backward from a delivered unit to every part, batch and process step that made it. SAP can hold that chain, but only if every transaction along it is configured to record what the chain needs. A single step that captures a quantity without a serial silently breaks the whole line.
Export control decides whether a document may move at all
Classification, licence determination, embargo and denied-party screening block or release documents. The dangerous test result is not a blocked document — it is one that was released and should not have been. That case will never appear unless it is deliberately constructed, because nothing about it looks like a failure.
Programmes outlive the systems that record them
A contract can run for a decade. Revenue recognition, milestone billing, progress measurement and cost-to-complete accrue across periods and across system changes. The interesting behaviour is at period and version boundaries, which is precisely what a transaction-level test does not reach.
Asbuilt rarely equals asdesigned
Concessions, deviations, engineering changes and repairs mean the configuration actually delivered differs from the one specified. The record of that difference is often the contractual deliverable, and it is generated by exactly the transactions least likely to be in a test plan.
Access control is part of the product, not the platform
Segregation of duties and role design are subject to audit, and a role change is a change to what the system permits. Treating authorisations as infrastructure rather than as tested scope is a common and avoidable gap.
The failures that reach production.
Each of these is quiet. Nothing errors, nothing is flagged, and no check that reads configuration would have caught it.
Everything worked; the chain has a hole where one step recorded a quantity rather than an identity. It is found when someone asks, which is the worst possible time.
Master data or classification changes alter which documents are blocked. Nothing errors — the population of blocked documents simply shifts.
Percentage-of-completion and cost-to-complete calculations are sensitive to configuration that upgrades touch, and the effect appears at period end rather than in the release window.
Where we would put the effort.
Scope is agreed with you before anything starts. This is where we would argue it belongs in Defence and Aerospace, and why.
Traceability chains as end-to-end scenarios
A serial or batch followed all the way through and back, with the evidence retrieved afterwards — because retrievability is the actual requirement.
Negative export-control cases
Deliberately constructed scenarios that should be blocked, tested for being blocked. A screening suite that only proves valid documents pass has tested the wrong half.
Period and milestone boundaries
Long-cycle revenue, progress billing and cost-to-complete exercised across boundaries rather than within a single period.
Evidence you can produce later
Results recorded so that any line can be substantiated on request, which is the standard this industry is actually held to.
Industry knowledge, stated plainly.
Our exposure to defence and aerospace comes from Rufouss engagements and from consultants who have worked inside defence, aerospace and adjacent high-assurance manufacturing environments, including the traceability and project accounting side.
Where we do not have that depth, we say so rather than take work on the assumption we will pick it up as we go. That answer has cost us engagements. It is still the right one, and it is the reason this page lists nine industries rather than thirty.
About SAP quality in Defence and Aerospace.
Why do you emphasise evidence over pass rates here?
Because in this industry a result you cannot reproduce has limited value. If a customer or an auditor asks what the system did for a given serial number on a given date, the answer has to be retrievable — so testing has to be run in a way that leaves a trail, not only a percentage.
What is most often missing from an export-control test scope?
The negative cases. Teams test that compliant documents flow, which proves the process works but not that the control works. The control is only proved by a document that should be stopped and is.
Can this work be done from offshore?
The SAP quality work usually can. Data residency, clearance and contractual restrictions vary by programme and by country, and they are a scoping question to settle before anything starts rather than an assumption to make.
Where this work usually starts.
Take any one of these on its own, or as one stage of a longer arc.
Tell us where your Defence and Aerospace programme is.
No business case needed, and a straight answer either way — including when the honest answer is that you do not need us yet.