Machine builders: every machine in the field is a variant someone remembers
A machine builder's most valuable dataset is its installed base: hundreds of machines in the field, each a variant, each with its configuration, customizations and repair history. The official records capture a fraction; the rest — what was really customized in 2011 and why, which units have the problem batch, what that customer's line does to the machine — lives in one or two veterans. Service revenue, retrofit sales and reputation all draw on that memory.
What knowledge is at risk in machine builders
The knowledge at risk is keyed to machines and customers, accumulated over decades:
- Installed-base memory — what was actually built and shipped, per unit: configurations, customizations, undocumented field modifications — the delta between the fleet and its own drawings.
- Customer application knowledge — how each customer actually runs the machine — loads, materials, abuse patterns — which explains the failure history and predicts the next one.
- Variant and vintage knowledge — which generations share which weaknesses, which spare parts really fit what, which serial ranges got the bad batch.
- Field service diagnostics — the remote-diagnosis skill that saves site visits: this symptom on that vintage means that component — pattern recognition per machine family.
- Retrofit and upgrade judgment — what can be upgraded on which units, what was tried and failed, where the profitable retrofit opportunities sit in the fleet.
One process, step by step: a custom machine, from request to service
Take one custom machine. Its life runs from the first request to years of service — and the knowledge it needs passes through many hands.
- The request is qualified — sales and engineering judge whether the configuration is feasible.
- The machine is configured and priced — options, custom work and risk; the logic lives with a senior engineer and sales.
- The design is adapted — the choices are in the drawings, the reasons in the engineer's head.
- Parts are sourced — the buyer knows the single-source parts and the lead-time traps.
- The machine is built, tested and commissioned — commissioning tricks live with the commissioning engineer.
- The machine enters service — years later, a technician needs to know what was customised, and why.
Mapping this flow end to end, through business process flow mapping, connects knowledge that usually stays in separate departments — from the promise in the quote to the modification a technician finds on site.
Which knowledge lives where
| Knowledge | Where it lives today | Who usually holds it |
|---|---|---|
| Feasible and infeasible configurations | Configurator rules, partly; senior engineers | Senior engineers, sales engineers |
| Design rationale per machine | Drawings and change notes (what); engineers (why) | Design engineers |
| Modifications made after delivery | Service reports, partly | Service technicians |
| Commissioning know-how | Checklists (steps); commissioning engineers (tricks) | Commissioning engineers |
| Single-source parts and lead-time traps | Purchase records (lead times); the buyer (reality) | Buyer |
| Recurring faults per machine generation | Service tickets; technicians' memory | Lead technicians |
Process by process: Quote to order and service and maintenance show where this knowledge hides, what breaks when its holder leaves, and what to capture first.
The typical trigger moment
The trigger is the retirement of the service veteran who 'knows every machine' — often the builder's first or second service engineer, now sixty-something, whose memory spans the entire fleet's life. Warranty claims, retrofit quotes and second-hand valuations all quietly route through him. The exposure shows the first time a customer calls about a twenty-year-old unit and the answer is no longer one phone call away.
What a Knowledge Space looks like here
MentX is a personality-aware knowledge base: it captures the knowledge of a company's key person — from meetings and a guided intake track — into a living, temporal knowledge graph with full source attribution. A machine-builder Knowledge Space keys everything to the fleet: the intake track walks the installed base family by family — vintage weaknesses, customization stories, customer application patterns — while meeting ingest catches service debriefs and warranty discussions where fleet memory is used daily. The temporal graph matters doubly here: machine knowledge is dated by nature (what was true for pre-2015 units, what changed after the redesign). Service engineers query DigiME from the field, sources attached.
Questions we hear from machine builders leaders
Our service history is in the ERP. What's missing?
The ERP logs that repairs happened — parts and hours. The knowledge is why: what actually turned out to be wrong, what the customer's process contributed, what to check first next time. That diagnostic layer is what the veteran adds to every ticket, and what leaves with him.
Can the knowledge base cover machines from before our documentation standards?
That is its highest-value territory: the older fleet is exactly where records are thinnest and memory is the only source. The intake track prioritizes the families where the paper trail is weakest.
Does this help sell service contracts?
A demonstrable installed-base memory is a service-contract argument: response quality no longer depends on which engineer picks up. It also protects fleet knowledge through any future sale of the company itself — buyers price service continuity.
