Build vs Buy: Military MRO and Depot Maintenance Software

Buy the record system, and mean it

Start with what should not be built. IFS Maintenix is a serious fleet maintenance system with real configuration control and it is used across defense fleets for good reasons. Ramco Aviation covers a broad footprint from line to shop at a competitive price. Swiss AviationSoftware AMOS is excellent, though it is an airline product at heart, tuned for operators running scheduled checks. SAP will do whatever you configure it to do, and the cost and speed of that configuration is the whole issue rather than a detail.

If you run a single platform, your packages are largely predictable, over-and-above work is a small share of your hours, and your customer imposes no unusual property or data requirements, configure one of those properly and put the difference into tooling and people. That is the honest answer and it applies to more depots than the market wants to admit.

Buy also if you have no maintenance system at all. A commercial product will get you to a defensible airworthiness baseline faster than a build, because it arrives with a configuration control discipline your team would otherwise have to invent while learning it.

And whatever else you decide, do not replace a working record system. Rip and replace programmes at depots have a poor history, and the reason is consistent: nobody can afford to stop while it happens, so the migration runs alongside live production until it fails or quietly stalls. The airworthiness record is not the place to take that risk.

What a depot needs that fleet products do not provide

An airline heavy check has variability. A depot induction has discovery as the main event, and that difference produces four gaps that show up consistently.

• Over-and-above evidence. Commercial systems assume a work order and an invoice. A depot has a scope baseline and a claim for work outside it, and the claim only bills cleanly if the evidence chain was captured at the moment of discovery: photographs, zone and station reference, the affected configuration item, the inspection requirement that surfaced it, the person and the timestamp. In our experience the largest recoverable loss at a depot is not productivity, it is work that was performed, was entirely legitimate, and could not be substantiated well enough to bill without a fight.
• Government furnished material. A part you do not own, sitting in your bonded store, with its own accountability obligations, is a different object from a part you purchased. Because it is free to the contractor it usually escapes the inventory discipline applied to bought parts, which makes chronic delay structurally invisible exactly when you need it in writing.
• Technical data currency. Performing correct work against a superseded technical order revision is still a finding. Currency has to be checked at task issue and the revision recorded in the sign-off, not assumed from a document library.
• Depot shop flow. Back shops, plating, non-destructive test and a paint queue everybody competes for looks like factory routing, not an airline check.

Configuration volume compounds all four. Two airframes of the same model in the same hangar can differ by a decade of modifications applied in different sequences, so effectivity has to be evaluated at task issue rather than at package build.

Cost on both sides

Licensing and configuring a commercial fleet system is a substantial annual figure plus an implementation measured in quarters, and for the record keeping mission that money is well spent. What it does not buy is the execution behaviour above.

A depot execution layer covering serial level as-maintained configuration, task issue with certification and technical order currency checks, over-and-above capture with evidence, and rolling re-planning against the induction schedule runs $110,000 to $220,000 in sixteen to twenty two weeks. Adding government furnished material accountability, tooling and calibration control, back shop routing, record package assembly, contract milestone reporting and integration with the fleet system of record runs $300,000 to $750,000 across twelve to twenty months.

Cost drivers here are unusual. Platform count matters more than asset count, because a second airframe type is a second data model conversation rather than a configuration exercise. Integration with government systems moves at the pace of your customer's approvals rather than your sprint cadence. Offline capability is mandatory and roughly doubles the testing burden. And the compliant hosting boundary carries its own engineering and documentation weight.

What keeps cost down: one platform, one line, and the discovery to approval path first, because that path is where both the schedule and the money sit.

The costs that arrive in month nine

The controlled unclassified information boundary is the one that hurts if it is late. Maintenance records in a defense context are frequently controlled, retention is measured in decades, and that shapes where production runs, who can reach it, how support access is brokered, how the audit trail is protected from edit, and what export format will still be readable long after this system is gone. Retrofitting a compliance boundary after a security review is close to rebuilding, so decide it in the first sprint even though it feels premature.

Historical record migration is the second. Decades of paper may need to be brought forward, and the honest scoping question is how much needs to be live and searchable versus retrievable from an indexed archive. Full fidelity migration of everything is usually the largest avoidable line on any quote.

Third, offline. Hangar decks, dry docks and back shops have unreliable connectivity, and any system requiring a live connection gets worked around with paper within a fortnight, at which point your data is a month stale and the evidence chain is broken again.

Fourth, the customer's approval cycle for any interface into government systems. That timeline belongs to them, and no amount of development capacity shortens it, so sequence those integrations so nothing else waits behind them and never put one on the critical path to a first release.

A fifth cost is easy to miss and expensive to discover: certification currency data. Gating task issue on a technician's qualification only works if the qualification records are accurate and current, and in many depots they live in a training system that nobody has reconciled against the shop roster for years. Cleaning that data is a people exercise rather than an engineering one, it takes longer than the integration that consumes it, and it should start the week the project does rather than the week before go live.

Price one induction's over-and-above: the test

Take a completed programmed depot visit, ideally one that ran long. Pull every over-and-above item raised during it and sort into three piles: billed without argument, billed after negotiation, and written off.

Then, for the second and third piles, ask one question per item: what evidence existed at the moment of discovery. Not whether the work was justified, which it almost always was, but whether a photograph, a zone reference, an inspection requirement, a named inspector and a timestamp existed before anyone started arguing. Add up the value of pile three and the discount conceded on pile two.

That total is your business case, expressed in the only currency your finance director cares about, and most depots have never assembled it. Do the same exercise for schedule: count the days the line sat waiting on government furnished material during that visit, and check whether any of them are recorded in a document your customer has seen. Days reconstructed from emails at contract review are days you will not recover.

If both numbers are small, configure your existing product and stop. If either is large, the evidence layer pays for itself inside one or two inductions.

Sequencing, and how to interview a developer

Sequence the discovery to approval path first, on one line and one platform. That single path carries the schedule and the money, and it produces measurable results inside a quarter. Then technical order currency and certification gating at task issue, then government furnished material accountability with delay attribution, then record package assembly, then back shop routing and contract reporting.

Four questions separate real depot experience from aviation adjacency. Ask what an as-maintained configuration is and how it differs from a bill of materials; if those are the same thing to them, they will model your fleet as a product catalogue and you will discover the difference during the first modification. Ask how they will handle offline capture and synchronisation on a dry dock. Ask how they intend to coexist with your existing record system and which direction each object flows, because anyone proposing replacement is proposing a pause your customer will not grant. And raise the compliance boundary in the first conversation, not the ninth.

Digital Heroes builds execution layers that sit above an existing record system, and every engagement opens with a written product requirements document covering the configuration model, the evidence schema and the compliance boundary before any code exists. We are a fifty plus person team with 2,000 plus projects delivered, hold Fiverr Vetted Pro status, and publish our engineering work to 2.5 million subscribers on YouTube. Our India LLP, US LLC and UK LTD entities allow contracting and intellectual property assignment inside your own jurisdiction, and you own the repository, the hosting accounts and a readable export from the first commit, because depot records outlive contracts, vendors and usually the software itself.

If you would rather someone argued with your brief than agreed with it, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. You keep the specification either way.