Skip to main content
Find a technical tolerance in seconds — not in a 10,000-page manual
← Back to journal
Process 7 min read

Find a technical tolerance in seconds — not in a 10,000-page manual

The tolerance is in the manual. The bottleneck is finding it in time, on the current revision, without ambiguity.

In this article

When the right answer is already written — but not queryable

In ACMI or MRO operations, a technical question is not theoretical: it is the time the aircraft or crew wait for a correct answer. The tolerance is in the manual. The procedure is in the SOP. The current revision is on a specific page of a PDF thousands of pages long — or split across documents that update on different cadences.

The usual problem is not that the information does not exist. It is that finding it in time, on the correct revision, without ambiguity, still depends on whoever “knows where to look.”

What changes when the manual can be asked

A RAG (Retrieval-Augmented Generation) system does not replace the airworthiness manual or the sector ERP: it makes them queryable in natural language, returning the answer with the exact source. In practice:

  • Controlled ingest — Manuals, bulletins, SOPs, and relevant history are indexed in a private knowledge base, respecting versions and documentary traceability — not an indiscriminate dump into a generic model.
  • Cited query — The technician asks: “What is tolerance X for this component on the current revision?” The system retrieves the official fragment, identifies document and section, then formulates the answer.
  • Operational continuity — The same layer can connect to operational systems (for example via MCP to an aeronautical ERP) so the query does not live apart from the real fleet workflow.

Why PDF search is not enough

Searching a word in a PDF finds matches. It does not resolve which revision is current, which document supersedes another, or whether the answer is safe to operate on. In a regulated environment, that difference is not cosmetic: it is the difference between “I found a paragraph” and “I can defend this decision in an internal audit or before the regulator.”

That is why a useful design does not promise “AI that knows aviation.” It promises retrieval with controlled sources over your corpus, with a record of what was queried and which document backed the answer.

Where the model lives (and why it matters here)

Technical manuals and operational data are not material for public training tools. A viable aeronautical deployment uses local models or a private cloud, under sovereignty and access-control criteria — aligned with the same security standard any serious industrial cognitive infrastructure would require (including ISO 27001 where it applies).

Without that point closed, the project should not move beyond a demonstration pilot.

How to start without freezing operations

You do not need to digitize the entire library on day one. The pattern that works is to scope: one fleet, one aircraft type, or a high-use SOP pack; validate real queries with the technical team; measure whether answers cite the correct source; then expand the corpus.

It is the same diagnose → audit → MVP → scale logic: first evidence that queries are reliable and auditable, then coverage. If your team still searches PDFs for what is already written — just not queryable — the next step is to scope the pilot corpus and the model-sovereignty criterion. For an example of RAG cognitive memory connected to ACMI operations, see the Shark Airways case.

Unlock the full article

Sign in with your Kodex community account to keep reading.

Ready to apply this in your organization?

Kodex executes with you — or start with resources. Same standard of rigor.

Tell us your goal

A short triage to qualify your request. In a few minutes we reach the right scope.

1

How would you like to collaborate with Kodex?

We open the right path — no unnecessary questions.

How would you like to collaborate with Kodex?

Tap a card to continue