AERONEXUM
Request a Demo

Reference

Aviation ERP

Aviation ERP gave the industry something it genuinely did not have: one authoritative commercial record, shared across departments, that could be trusted and audited. That was a real achievement and it still matters. This page covers what ERP established, where it continues to earn its place, and why the operational complexity of a modern parts or repair business has begun to ask for something ERP was never designed to provide.

What aviation ERP is

Enterprise resource planning is the discipline of holding a company's commercial activity in one consistent set of records. Aviation ERP is that discipline applied to a business whose inventory happens to be certificated, serialized and legally consequential.

A vertical aviation ERP typically covers customers and vendors, RFQs and quotes, sales orders and purchase orders, receiving, stock, repair orders, invoicing, exchange and core billing, and the general ledger underneath all of it. The good ones understand aviation vocabulary out of the box — part numbers and alternates, condition codes, tag types, exchange versus outright, consignment ownership — rather than expecting you to bolt that onto a generic product with custom fields.

Working definition

Aviation ERP is the authoritative commercial system of record for an aviation business: the place where what was agreed, what was owed, what was owned and what was booked are held consistently enough to be audited and closed.

What it accomplished

It is easy, from inside a business that already has ERP, to forget what the problem looked like before it. It is worth being specific, because the achievement was substantial.

Before ERP, the commercial functions of an aviation supplier ran on separate books. Sales had order pads. The warehouse had cards or a standalone stock program. Purchasing had its own files. Accounting had a ledger that was reconciled to the others periodically and imperfectly. Every department had a version of the truth, and a meaningful part of the working week went into deciding whose version was correct.

ERP replaced that with four things that are now so normal they are invisible:

  • One recordA sales order is a single object that sales, the warehouse, purchasing and accounting all look at. Disagreements about the facts largely ended.
  • Transactional integrityStock movements, receipts and invoices post consistently. A shipment cannot quietly fail to reduce inventory or fail to bill.
  • Financial truthMargin, cost, exposure and receivables are computed from the same transactions the operation actually ran, not re-keyed into a separate ledger.
  • An audit trailWhat was agreed, when, by whom, at what price — recoverable years later. In a regulated industry with long-lived assets, this is not a nicety.

Those four properties are the foundation everything else in an aviation business stands on. Nothing in this page should be read as suggesting they are optional or that the industry would be better off without them.

Where ERP still earns its place

ERP is not a legacy technology waiting to be displaced. There are jobs it does that nothing else should be asked to do, and those jobs are not shrinking:

  • The commercial system of record. Somewhere in the business there must be one place where the agreement is definitive. That is ERP's job and it is a good design for it.
  • Financial closure. Period close, revenue recognition, cost of goods, inventory valuation, tax. These are demanding, rule-bound disciplines and ERP is where they belong.
  • Transactional discipline. Enforcing that a receipt, an issue and an invoice all happen, in order, with matching quantities. Operational awareness does not remove the need for a system that will not let the books drift.
  • Auditability. A durable, queryable history of commercial commitments, which regulators, insurers, customers and acquirers all eventually ask to see.
  • Aviation-specific commercial modeling. Exchange billing, core charges, consignment ownership and repair-order costing are genuinely difficult to model, and vertical aviation ERPs have decades of accumulated understanding of them.

Any argument that begins "you should replace your ERP" should be treated with suspicion. In most aviation businesses the ERP is doing exactly what it was bought to do.

What changed around it

The pressure on aviation systems has not come from ERP getting worse. It has come from the operating environment getting more complex while the shape of the record stayed the same.

The market got faster

RFQs arrive continuously through marketplaces, customer portals and email, and are frequently won on response time rather than price. The window in which a quote is useful has compressed from days to minutes. A system designed to record a transaction accurately after it is agreed is not, by itself, much help in the period before it is agreed.

The number of counterparties grew

A single unit may now involve a customer, a broker, a repair station, a subcontract shop, a freight forwarder and a customs agent. Repair capacity is distributed across a network of certificated facilities rather than held in-house. Most of the elapsed time on a transaction is now spent waiting on somebody outside the company — which is precisely the part an internal record has least visibility into.

The evidence burden increased

Customers ask for more documentation, in more specific forms, more consistently than they did twenty years ago. Trace expectations have hardened. Dual release, back-to-birth records for certain rotables, and complete teardown history have moved from differentiators to conditions of sale. The volume of evidence attached to an ordinary transaction has grown substantially.

More work happens concurrently

A single order may be simultaneously waiting on an inspection, a vendor repair, a certificate revision and a core return — four independent clocks running against one commitment. The record can describe each of those states. Knowing which one is actually holding the order up is a different question.

Where the ERP model reaches its natural limit

This is the important distinction, and it is a distinction about design intent rather than quality.

ERP is built to answer questions about records. What is this order? What did we agree? What is the balance? What did we pay? Is this posted? Those are record questions and ERP answers them exactly, durably and defensibly.

The questions that consume an operations team's day are a different shape. They are questions across records, about the present, with time pressure attached:

  • Which of our commitments are at risk this week, and what specifically is holding each one?
  • Which shipments are physically ready but not documentally ready?
  • Which open cores are approaching the point where they become a write-off rather than a receivable?
  • Which units are we quoting as available that are in fact allocated, on hold, or awaiting inspection?
  • What arrived this week that nobody has dispositioned?
  • If this vendor slips another ten days, what does that cost us and who needs to be told?

Every fact needed to answer those questions usually exists somewhere. The inspection status exists. The document revision exists. The core obligation exists. The vendor promise date exists, possibly in an inbox. What does not exist is a place where those facts are assembled into a single picture of the work while the work is still in progress.

Record questions versus operational questions A lower band represents the ERP system of record holding individual records such as sales orders, purchase orders, repair orders and invoices, each answered accurately in isolation. An upper band represents operational questions that span several records at once, drawn as arcs crossing multiple record boxes. OPERATIONAL QUESTIONS — SPAN SEVERAL RECORDS AT ONCE “What is holding this order?” “Is this shipment actually ready to leave?” “Which cores are aging?” SYSTEM OF RECORD — EACH RECORD ANSWERED EXACTLY Sales order Agreed, priced, committed Purchase order Issued, received Stock movement Quantity, value, location Repair order Vendor, scope, cost Invoice Billed, aged, collected Ledger Posted, closed, auditable Each of these is answered correctly, durably and defensibly. That is what the system of record is for. The gap is not accuracy. Every fact above is correct. The gap is that no single place assembles them into a picture of the work while the work is still moving — so people assemble it by hand, every day.
ERP answers record questions precisely. Operational questions cut across several records at once and are asked while the work is in flight. Both are legitimate; they are simply different shapes of question.
Worth being clear about

This is not a deficiency that better ERP configuration fixes. A system of record is deliberately conservative: it commits facts, enforces consistency and resists ambiguity. Those properties are exactly what you want from the books, and they are in tension with the tolerance for in-progress, partial and fast-changing state that operational awareness requires. Asking one system to be excellent at both is asking it to hold two opposing design goals.

What organizations do in the meantime

Because the questions still have to be answered, aviation businesses answer them manually. The shape is consistent across companies of very different sizes:

  • A morning standup that exists to reconcile what several systems each half-know.
  • A spreadsheet tracking open cores, because the sale closed and the record considers the matter finished.
  • An inbox folder that is, in practice, the vendor promise-date database.
  • An experienced coordinator who knows which orders are actually at risk this week, and would be genuinely difficult to replace.

This is competent work by capable people and it should not be disparaged. But it is worth naming what it is: a human layer performing cross-record awareness on top of a system deliberately designed to hold records. It works, it is expensive, it does not scale linearly, and none of the knowledge it generates is retained by the company.

The natural next step

If the record layer is sound and the missing capability is awareness across records while work is in progress, then the sensible move is not to replace the record. It is to add the layer that was previously supplied by people.

That is the reasoning behind the Aviation Operating Platform: a system whose primary concern is the state of operational work — what is committed, what is blocked, what is waiting on whom, and whether the physical unit, the commercial record and the airworthiness evidence still agree with one another — while assuming a commercial system of record continues to do its job underneath.

Framed that way, the progression is not a rejection of ERP. It is the same progression the industry has made before. Paper records were not wrong; they were outgrown. Departmental systems were not wrong; they were outgrown. ERP is not wrong. The operational complexity around it has simply grown past what a system of record was ever asked to carry alone.

AERONEXUM is built on that reading of the problem. The category page sets out what defines an Aviation Operating Platform and what changes for an organization that adopts one, and the aviation software overview puts ERP back in context alongside the other systems a typical operation runs.