Twenty years of service documentation, answerable in one question

The Challenge

Two decades of equipment meant nine overlapping generations of machinery in the field, each with its own manual revisions, service bulletins and wiring diagrams. The documentation existed — that was never the problem. Finding the right revision for a specific serial number, on a phone, in a plant room, was.

What happened in practice was a phone call to one of four senior engineers who carried the history in their heads. That worked, until it didn’t: it capped how many calls the team could handle, concentrated critical knowledge in a handful of people, and made onboarding a new engineer a two-year project.

The Solution

We built a knowledge system indexed by equipment generation rather than by document. An engineer scans or types the serial number and the system already knows which revisions apply — so an answer from the wrong generation is not a ranking problem to be tuned away, it is structurally impossible.

Answers come back with the source page or diagram attached, because an engineer standing in front of a machine needs the diagram, not a paraphrase. The interface works on a phone and holds a cached index for sites with no signal.

Questions the system cannot answer well are not discarded. They land in a review queue owned by the service documentation team, who now have, for the first time, a ranked list of what their documentation is actually missing.