Aviation Technical Publications Software: Build or Buy at Your Fleet Mix

When is off the shelf genuinely the right call for technical publications?

More often than the people selling builds admit. If you operate one type from one manufacturer, your aircraft were delivered to a common configuration, and your engineering department raises a handful of engineering orders a year, a packaged product will carry your revisions and your distribution properly and you should buy one.

Web Manuals is the strongest answer when the pain sits in flight operations manual authoring and compliance linking. The editing experience is accessible to the people who actually write operations content, which matters more than any feature list, because a manuals system only the publications manager can drive becomes a bottleneck the first time that person is on leave. Comply365 is built for distribution and read and sign across a large population, so if your exposure is proving that six hundred people received and acknowledged a notice before performing relevant work, that is the product aimed at the job. Vistair DocuNet spans document control across both sides with a long aviation track record, and is worth looking at when you would rather deal with one supplier than two.

Buy and stop there when the operator specific work you would be automating amounts to a few days a month for one person. That is the honest test, and you can run it this week. Ask your publications manager how many days a month go into applying fleet effectivity by hand and producing a superset with warning notes. If the answer is two or three, a build will not repay itself, and the money is better spent documenting the mappings and training a second person so the revision process does not pause when the first one takes annual leave.

When does a custom build actually pay off?

When effectivity stops being a clerical task and becomes an engineering one. The manufacturer publishes applicability by serial number range and modification status. Your fleet diverges from that baseline continuously, through service bulletins applied at different times, supplemental type certificates inherited from previous operators, cabin configurations that differ across subfleets, and engineering orders your own department raised last quarter. Wet leased aircraft arrive carrying somebody else's history and leave again.

At some point that reconciliation cannot be held in a spreadsheet, and it is usually being held in one person's head with the spreadsheet acting as a memory aid. A build pays off when two or more of the following are true. You carry a mixed fleet with real configuration variation. You are a maintenance organisation working customer aircraft whose configuration you do not control, so effectivity uncertainty is permanent rather than exceptional. Your effectivity process depends on one person whose retirement would be a compliance event. Or your maintenance and engineering system and your publications have no link at all, and your exposure is the gap between them.

That last case is the most common trigger we see and it does not improve on its own. A compliant library sitting alongside a process nobody can evidence is the specific shape of finding that expands an audit, because the question asked is not whether the work was performed correctly. It is whether the organisation can demonstrate that the mechanic had the current, applicable data in front of them at the time.

How do they compare on the things that matter in aviation?

Compare on five things a practitioner can verify rather than on a feature grid.

Effectivity resolution. Packaged products let you tag content by aircraft type and usually by serial range. What they hand back to you is resolution against your own fleet, meaning applying your bulletins, your supplemental type certificates and your engineering orders to produce one procedure for one tail. That work exists either way. The only question is whether a person performs it monthly or a system performs it at the moment the mechanic opens the task, and records what it presented.

Ingest burden. Every manufacturer applies S1000D or ATA iSpec 2200 with its own conventions on data module codes, applicability expressions, illustration handling and change marking. Two manufacturers on the same standard are two ingest projects whether you buy or build. A product absorbs part of that. It does not absorb the conventions specific to your particular source set, and nobody can price your build without counting your sources first.

Linkage to maintenance. The feature that turns publications from a library into a control is task cards bound to a specific data module and revision, with the revision in force recorded at sign off. Products in this space generally leave that join to the operator.

Data portability. Ask for a full export of your content, your effectivity rules and your acknowledgement records, and ask what format it arrives in. This system forms part of your continuing airworthiness evidence and it has to outlive any supplier relationship.

Reporting rigidity. Auditors ask for acknowledgement by person, by role and by station across a date range. Check whether that is a report you can run yourself or a request you have to raise.

What does total cost of ownership look like at your fleet size?

Build figures first, from Digital Heroes delivery experience. A first release covering source ingest for your primary manual set, effectivity resolution to tail level, and controlled offline distribution with read and acknowledge tracking runs $80,000 to $190,000 and ships in 14 to 20 weeks. A full platform adding operator authoring with approval workflow and expiry, flight operations manual management, task card linkage into the maintenance system and full revision audit reporting takes the total to $220,000 to $550,000 across 6 to 14 months. Task card linkage alone is typically $25,000 to $60,000 of that, depending on what your maintenance and engineering system exposes.

Running costs are not trivial. Storage and delivery for a mixed fleet holding preserved originals alongside web optimised renditions typically runs $800 to $3,000 a month, and it grows every revision cycle because you retain the old revisions. Support and enhancement runs 12 to 18 percent of build cost annually, and a standing allowance for revision ingest maintenance is sensible, because manufacturers change conventions and delivery mechanisms without asking you first. If you distribute to tablets, device fleet management is a real line, and operating system upgrades break offline readers on their own timetable rather than yours.

Against that, put your current subscription plus manufacturer portal costs plus any per user component, then be honest about the residual manual workload the subscription leaves behind. For a single type operator that residual is a few days a month and the licence wins comfortably. For a mixed fleet operator it is a role, and often one irreplaceable person.

What does the hybrid look like, and when is it the honest answer?

Buy for flight operations, build for engineering. That is the split we recommend most often, and for a mixed fleet operator it is usually the cheapest correct answer rather than a compromise.

The reasoning is that the two halves are different problems wearing the same job title. Flight operations manuals are authored content with a compliance library behind them, and products in that space handle authoring, approval and read and sign well. Engineering data is structured source material that has to be resolved against your fleet before it is safe to present to a mechanic, and that is precisely the work packaged products hand back to you. Keeping Web Manuals or Comply365 for the operations side while building an effectivity and distribution layer over the engineering data means you only pay to build the part nobody sells.

There is a smaller hybrid worth naming for operators whose immediate exposure is distribution rather than effectivity. Offline distribution with a device manifest, differential synchronisation and immutable acknowledgement records, running over the files you already produce, costs $40,000 to $70,000 over eight to ten weeks. It proves the mechanic had the revision. It does not yet prove the revision was the applicable one for that tail, and you should be clear with yourself about which of those two problems is currently costing you.

Sequence matters inside a hybrid. Ingest one source format first and prove the normalised model on it before adding the second manufacturer. Attempting all four sources at once is how a fourteen week release becomes a thirty week one.

Which should you choose, by operator size and stage?

Single type operator under about twenty aircraft. Buy. A packaged product handles your revisions and distribution, and the operator specific work is small enough that automating it will not repay a build. Spend the difference on documenting your mappings and training a second preparer.

Two types, one manufacturer, stable configurations. Buy, and put the effort into your configuration records instead. Effectivity resolution is only ever as accurate as your knowledge of what is fitted to each tail, and recovering that is engineering work your own department does faster and cheaper than any developer.

Mixed fleet, three or more type ratings, thirty aircraft and up. Hybrid. Keep the packaged product for flight operations manuals and build the engineering layer covering ingest, effectivity resolution to tail level and controlled offline distribution. Expect $80,000 to $190,000 for that first release, and treat clean configuration records as a prerequisite rather than a project deliverable.

Maintenance organisation working customer aircraft. Build, and budget for customer separation, which adds roughly 15 to 25 percent across the work because isolating each customer's data, configuration and specific instructions touches authorisation, search, distribution and reporting rather than sitting in one module. You also do not control the configurations you work on, so the system has to surface uncertainty loudly rather than resolving confidently.

Any operator that has taken a records finding on data currency. Start with the distribution and acknowledgement layer at $40,000 to $70,000 while you decide about the rest. It buys evidence quickly and it is the piece you would build first in any case.

If you want a second opinion before signing anything, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. Nothing about that commits you to the build.