The premise
This is not a company history. It is an argument about the industry — and AERONEXUM only makes sense as a response to it. If the argument is wrong, so are we.
The short version: aviation software has solved each of its problems in turn, and solved them well. What it has not solved is the accumulated cost of having solved them separately.
Before systems: everything was a conversation
For most of the industry's commercial history, an aviation parts business ran on paper and people. Sales had order pads. The stores had cards. Purchasing had files. Accounting had a ledger reconciled to the others periodically and imperfectly.
This worked because the operation was small enough to hold in a room. Everyone knew what was on the shelf, who was waiting, and which repair was late — because they could ask. The coordination cost was real but invisible, absorbed by proximity.
Then ERP solved the record
Enterprise systems arrived and solved a genuine problem: every department had a different version of the truth, and a meaningful share of the working week went into deciding whose version was correct.
ERP replaced that with four properties so normal today that they are invisible: a single shared record, transactional integrity, financial truth computed from the transactions the business actually ran, and an audit trail recoverable years later. In a regulated industry with assets measured in decades, that fourth one alone justified the investment.
This was a real achievement, and it is worth being clear that it still is. Nothing that follows suggests otherwise. Our fuller treatment of what ERP established — and where it continues to be the right tool — is on the aviation ERP page.
Then the specialists arrived
ERP could not be excellent at everything, so the market did what markets do. MRO and maintenance systems appeared, built by people who understood work orders, quality gates and return-to-service. Warehouse systems appeared, built by people who understood locations and picking. Document systems appeared. Quality systems appeared. Marketplaces appeared and changed how parts were found and sold.
Each was a better answer to its own question than a general system could be. Each was, individually, a rational purchase. That is the part worth sitting with: no organization arrived at a fragmented systems estate through carelessness. Every step was defensible.
What changed around all of it
The pressure on aviation systems has not come from any of them getting worse. It has come from the operating environment getting harder while the shape of the record stayed the same. Three shifts matter most.
Work moved outside the building
Repair capacity distributed across networks of certificated facilities. Sourcing moved to marketplaces. Fulfillment moved to forwarders. A large share of the elapsed time on a transaction is now spent waiting on an organization you do not control — which is precisely the part an internal system of record has least visibility into.
The evidence burden grew
Trace expectations hardened considerably. Dual release, complete teardown history and back-to-birth records for certain rotables moved from differentiators to conditions of sale. The documentation attached to an ordinary transaction grew to the point where "is this package complete?" became a genuine operational question rather than a clerical one.
Response time became competitive
When quotes are won in minutes, knowing your true position — what is actually available, actually serviceable, actually documented — stopped being useful and became decisive.
How the industry absorbed it
It absorbed it with people. Every capable aviation business has already solved this problem, and the solution is almost always someone specific.
There is a spreadsheet tracking open cores because no system does. Someone knows which vendor is slow this month. There is a morning reconciliation of what shipped against what was invoiced. There is a coordinator whose actual job is to stand in the gaps between systems and keep work moving across them.
This works, and it works because the people doing it are genuinely good at it. It is expertise, not a workaround. But it carries three costs that compound:
- It does not scale linearly. Twice the volume needs more than twice the coordination, because the number of things that can be out of step grows faster than the number of transactions.
- It lives in individuals. When the person who tracks cores is away, the tracking is away. Operational knowledge held in a spreadsheet and a habit is not an asset the company owns.
- It is invisible until it fails. The compensating work appears in no system, so it cannot be measured, staffed for or improved. It becomes visible only when something is missed.
Why AERONEXUM exists
Read that way, the conclusion is fairly plain. If the record layer is sound and the missing capability is awareness across records while work is in progress, the sensible move is not to replace the record. It is to build the layer that was previously supplied by people.
That is what we are doing. Not a better ERP — a different concern entirely: the state of the work rather than the record of it. What is committed, what is moving, what is blocked, what each blocked item is waiting on, and whether the commercial record, the physical unit and the airworthiness evidence still agree with one another.
We call that category an Aviation Operating Platform, and we have defined it publicly — including the properties that qualify a system as one, what it is not, and the organizations that do not need it — because a category nobody can falsify is just a slogan.
This argument could be wrong in a way that matters. It is possible that coordination cost is simply the price of specialization, and that the right answer is better people rather than better software. We do not think so — the pattern is too consistent across organizations of very different sizes — but we would rather state the claim plainly and be judged on it than imply the case is settled.
The progression is not a rejection
Paper records were not wrong. They were outgrown. Departmental systems were not wrong. They were outgrown. ERP is not wrong, and specialist systems are not wrong. The operational complexity around them has simply grown past what any of them was asked to carry alone.
Every generation of aviation software inherited a problem created by the success of the one before it. We expect the same to be true of ours. That is not a pessimistic reading — it is what a maturing industry looks like, and it is a reasonable thing to build in the middle of.