---
title: "Experienced engineers' know-how in the Company Brain"
description: "Experienced engineers talk through cases and exceptions, an agent derives rules with their sources and the expert validates them before colleagues use them."
url: https://www.joinx.it/en/industries/use-cases/expert-technician-knowledge
---

# What the experienced engineer knows, written down before they retire

When a machine throws an error nobody has seen before or a customer asks for a non-standard job, the department always calls the same colleague, and when that colleague is away the answer is away too.

## The knowledge that never made it into a system

Manuals and data sheets say how a machine ought to work, while the way to handle exceptions lives in the memory of a few engineers, in the odd notebook and in the emails exchanged with the manufacturer's support. The youngest maintenance engineer, the engineering department and the service team therefore all end up phoning the same person, who spends part of the day repeating explanations already given. The problem becomes visible when that engineer nears retirement and the company discovers it does not know what it is about to lose.

## The expert explains and validates, the agent writes and cites

We work with the expert on real cases, with the drawing, the service report or the non-conformity on the table, and we take note of how they reason. The agent turns the conversation and the related documents into a draft rule or solved case, with the conditions under which it holds and the sources cited, and puts it to the expert, who corrects and validates it. Only then does the rule enter the Company Brain, the company's knowledge base, where colleagues find it again from the Workspace with the source alongside.

1.  The expert goes back over a real case with the documents on the table
2.  The agent derives a draft rule from it and cites the sources
3.  The expert corrects and validates it
4.  The rule stays in the Company Brain for colleagues and agents

Illustrative example

## Data, modules and responsibilities for writing down technical know-how

| Item | In this case |
| --- | --- |
| Data | Service reports, non-conformities, manuals and data sheets with their version, emails with the manufacturer's support |
| Modules | Company Brain, Agents, Workspace |
| Who decides | The expert on the content of each rule; the technical manager on which cases to write up first and on who validates the rules once the expert has gone |
| What we measure | The questions that reach the expert, the time taken to close an exception and jobs that have to be redone, against the starting point |
| AI Act risk class | Anyone who consults the assistant must know they are dealing with an AI system, as the transparency obligation requires. The system is not used to assess the engineers' performance, a use concerning staff that Annex III treats as high-risk; we set the classification with risk and compliance before development |
| Where to start | With Deployment on one department or one family of machines, because the knowledge to be gathered sits with a few people and the result soon shows in the questions put to the expert |

## Without the expert's time it is worth waiting

The work takes hours of the expert's time, and if the department cannot free them up the gathering stops halfway and nobody validates the rules that have been written. It is also worth waiting when the reference manuals have no definite version, because the agent would cite out-of-date documents. Finally, answers that concern safety-critical activities require a separate specialist assessment, which we do not carry out on our own.

The sheet grew out of the Industrials page.

[Data and AI for industrial companies](https://www.joinx.it/en/industries/industrials) · [The use case library](https://www.joinx.it/en/industries/use-cases)

## Let's begin with a question that always goes to the same engineer

Starting from an exception that only one person in the department knows how to resolve, we look with that person and their manager at which cases it makes sense to write up first.

[Contact us](https://www.joinx.it/en/contact?settore=industria)
