Three ways to lose knowledge on a site
The retirement of the maintenance manager who "hears" the pump. The resignation of a process engineer whose replacement takes nine months to recover the yield. And the silent single point of failure: one person knows how to restart flotation after an emergency stop, and nobody decided that.
Why the usual tools are not enough
Procedures describe the normal case; the value is in the abnormal one. The CMMS knows what was done on the machine, not who knows how to do it. The skills matrix says who holds the certificate, not who is the only person able to do the job.
What the map changes
- By process: plant operation, maintenance, laboratory, HSE. Each task calls on its knowledge.
- By site: a health score per structure, with your thresholds, to compare a mine with a smelter.
- By person: mastery from 0 to 5, assessed, dated.
- By deadline: the five-year retirement wave, and the transfers to organise urgently.
On site, without depending on the network
The self-hosted edition runs with no outbound connection: built-in video conferencing for transfer sessions between an expert and a successor, local AI for search and CV reading. An installation cut off from any external network is a supported configuration.
Recruiting when no internal successor exists
A need starts from knowledge at risk. Internal candidates are ranked on measured mastery; external CVs are read locally and compared against the same knowledge.
Four languages on one site
French, English, Spanish, Arabic: a head office and sites that do not speak the same language share one map, with search across languages.
Drawings, work instructions and maintenance routines stored in a document management system (Alfresco, Nuxeo, Nextcloud…) or in SharePoint connect read-only: see DMS and knowledge management and the SharePoint connector.