Case study / Manufacturing

Keeping machine know-how when engineers move on

An AI assistant that answers engineers' questions from the manuals and the breakdown history, shows exactly where each answer came from, and says so when it does not know.

Industry
Manufacturing and maintenance
Used by
Engineers, technicians and their managers
Our part
Design, build and manage
Built with
AWS (London), Claude, PostgreSQL
Status
Piloted, moving to production

01 / The industry

Knowledge that lives in people, not systems

Factories run on machines that stay in service for decades. The manuals run to hundreds of pages of PDF, and the record of what went wrong, and what fixed it, sits in breakdown logs and spreadsheets that nobody reads.

The real knowledge is with a few senior engineers: which setting stops a line jamming, which part always fails first, what a particular noise means. When one of them retires, moves on, or is simply busy on another line, newer technicians wait, guess, or ring the manufacturer.

02 / The problem

An answer on the shop floor has to be right

A general-purpose chatbot is the wrong tool here. It answers confidently when it does not know, and on a machine a wrong answer can damage equipment or hurt someone.

The brief was an assistant that:

  • answers only from the business's own manuals, procedures and breakdown records;
  • shows the page every answer came from, so an engineer can check it;
  • puts safety warnings first, every time;
  • says plainly when the documents do not cover a question, instead of guessing;
  • shows managers where knowledge is missing, out of date or not being used.

03 / What we built

An assistant that shows its working

Engineers ask questions in their own words, on a desktop or a tablet, usually about a particular machine. A printed QR label on the machine opens a conversation about it. If a question could mean more than one machine, the assistant asks which.

  • Cited answers. Each answer carries a confidence level and links to the exact page of the manual or procedure it came from.
  • Safety first. Any warning, caution or danger notice in the material used is moved to the top of the answer by the code, not left to the model.
  • Breakdown history. "Has this happened before?" is answered from past breakdown records, with names and contact details removed. Faults reported from the assistant become history once they are fixed.
  • Counts from the database. Questions such as "how many times has this failed this year?" are answered by a database query, never estimated by the model.

Tracking knowledge

A second view is for the people responsible for the knowledge itself. Repeat questions show where training is needed. Questions the assistant could not answer show the gaps, machine by machine. Documents that are voted down, queried or never cited are flagged for review.

Every document has an owner and a review date, following the document control approach in ISO 9001, with an export to show an auditor. A withdrawn document stops being used for answers.

04 / How it works

Refuse rather than guess

Each question is searched two ways at once: by meaning, and by exact words, so part numbers and fault codes are found as reliably as descriptions. The best matches are re-ranked, and a confidence check runs before any answer is written.

  • Below the confidence threshold, the model is never asked. The assistant says the documents do not cover it.
  • The model may only cite passages the search returned, and page numbers come from the system, not the model.
  • Technicians' words are matched to the manual's ("everything died" to "all power lost"), so plain questions still find the right section.

It runs on AWS in London, with the infrastructure defined in Terraform. Documents are read inside the platform rather than sent to a third-party document service, each organisation's data is kept separate at the database level, and actions are recorded in an audit log.

A benchmark of test questions, including ones it must refuse, measures answer quality as the system changes, alongside more than 3,000 automated tests.

05 / Where it is now

Piloted on real manuals and records

The assistant has been piloted on real material: equipment manufacturers' manuals and years of a maintenance team's breakdown records. In the pilot evaluation:

  • 12 of 12questions the documents could not answer were refused
  • 5 of 5safety notices led the answer
  • 4 stypical time to an answer
  • 2pAI model cost of a typical answer

Next comes the production environment, reading scanned documents, and a mobile app for technicians on the shop floor.

06 / More work

Other case studies

Vehicle leasing

Salary sacrifice car leasing, joined up end to end

A vehicle leasing provider ran salary sacrifice schemes on a CRM, with manual steps at every stage. We built the pricing engine, portal, partner integrations and automation that take a deal from first quote to monthly mileage.

Platform · Integration · AWS

Commercial fit-out

Live dashboards from a decade-old project system

A commercial fit-out contractor's project and finance data sat in a decade-old system with fixed reports. We built live dashboards into it for forecasting, work in progress and daily changes, plus wallboards in its offices.

Data · QuickSight · SQL

Construction

A job app for site teams that works without signal

A building contractor's site teams often had no signal on the job, so updates went by WhatsApp and email. We built an iOS and Android app on its existing back office that works offline and syncs when it can.

Mobile · Offline · AWS

07 / Contact

Losing knowledge you cannot get back?

Tell us where the know-how in your business lives today, and what happens when the people who hold it are not there.