ServLore in two minutes
Transcript
- ServLore keeps a machine builder's service knowledge in one place: manuals, service bulletins, past cases and the experience of its experts.
- This is the cockpit of Demo Pumpen, a German pump manufacturer. Everything you see comes from its own data.
- A technician describes a fault to the AI Service Engineer.
- Every statement of the answer points to its evidence: a manual page, a service bulletin or a confirmed case.
- The diagnosis ranks the likely causes and proposes the next measurement.
- Behind every answer sits the knowledge library: error codes, causes, resolutions and procedures, verified by experts.
- An item shows the documents it comes from and the service cases that confirmed it.
- When a service case is closed, the cause and the fix that really worked flow back, so the next technician finds them faster.
- Contradictions and outdated documents are flagged, and knowledge health shows how complete and verified the knowledge is.
- The other films in this handbook show each of these steps in detail.
ServLore is the service knowledge platform for machine builders. It brings the four places where service knowledge usually lives, PDF manuals, service bulletins, past cases in a ticket system and the heads of experienced technicians, into one knowledge base that belongs to the machine and can always be traced to its source.
What it does
Section titled “What it does”- Answers with evidence. A technician describes a fault in their own words. The AI Service Engineer answers only from your organisation’s sources and shows, for every statement, the document page or service case it rests on. When the evidence is not enough, it says so and offers to ask an expert.
- Knowledge that belongs to the machine. Manuals and bulletins become linked knowledge items: error codes, symptoms, causes, diagnostic steps, resolutions, measurement ranges and procedures, each tied to the machine model and revision it applies to.
- Verified by your experts. Every item has a status. Experts confirm, knowledge managers approve officially, and contradictions between documents are put in front of a person instead of being averaged away.
- Learning from every job. When a service case is closed, the cause and the fix that really worked flow back into the knowledge, so the next technician finds them faster.
- Safety first. Questions about safety-critical parts, or answers that rest on contradicting instructions, go to an authorised expert before the technician sees a recommendation. Your organisation sets these rules.
Who uses it
Section titled “Who uses it”| Role | Typical work |
|---|---|
| Field technician | Asks the assistant, identifies machines, works and closes service cases |
| Expert / verifier | Confirms knowledge, answers escalations and capture questions |
| Knowledge manager | Uploads sources, resolves readiness findings and contradictions, approves knowledge |
| Service manager | Follows cases, escalations and analytics |
| Organisation administrator | Everything above, plus members, settings and the subscription |
The full list of what each role may do is in Roles and permissions.