A small maker of suction units and oxygen concentrators gets a call from a district hospital. Three units trip their thermal cut-out after forty minutes. Whoever designed the cooling path would know instantly. A fan revision from a fresh supplier gave slightly weaker airflow, and he once cured it by shifting the intake grille. He left last year. The new engineer spends a fortnight and three site visits rediscovering it.
Our profile of monitor, pump and steriliser assemblers puts this strain at the top. Know-how pools in two or three heads, and each departure slows field repairs badly. Below: causes, costs, and fixes through roles, records, training and retention. Patterns shared with instrument, implant and disposables units are covered on our device and equipment people hub.
Where unrecorded fixes hide
- Tiny teams patch and move on. Someone tweaks a pump's relief valve or adds a firmware delay late on Friday. No note follows.
- Drawings lag reality. The released drawing shows the old grille, while units ship with the moved one.
- Field fixes travel home with the engineer. A service visit ends with the machine running, and the reason lives in a phone gallery.
- Knowledge feels like security. An engineer who is the only one able to tune the steriliser's pressure controller may not rush to share it.
- Nobody is asked. Without a routine, writing it down is nobody's job.
What it costs
Field repair times stretch, because juniors work by trial. Wrong spares go out with service engineers. Bench testers guess at limits that the designer once adjusted by ear. Dealers lose patience and push hospitals toward a rival brand. Inside the unit, the remaining senior engineer becomes the only route for every hard fault, which is exactly the overload that drove the first one out. Hospital biomedical engineers start keeping their own notes on your machines, and sometimes know more about a recurring fault than your factory does.
Turning memory into company knowledge
- 1
Log every field call and bench failure in one place
Machine, serial, fault, root cause, fix, parts and engineer. A shared sheet works. Pulling call-out trends from it is described in simple call-log reporting for assemblers.
- 2
Open a unit on the bench monthly
Half an hour, casing off, the senior talking through the month's hardest faults with juniors and a bench tester present.
- 3
Give every machine family an understudy
Suction, concentrators, sterilisers, monitors: each has a second engineer who joins the senior on calls and signs off when ready.
- 4
Close the drawing gap
Any field fix that changes a part or setting triggers a drawing or test-sheet update within the month, owned by a named engineer.
- 5
Write roles around knowledge-sharing
Make capturing and teaching part of a senior engineer's written role. See role maps for bench and field staff.
Keeping the engineers who hold it
Capturing knowledge only helps if the engineers do not leave in frustration first. Why do they go? No visible next rung. Dragged into every floor emergency. A dealer dangling more money and calmer days. Credit for fixes drifting to someone else. A dual ladder, with a technical branch beside the managerial one, lets a gifted designer progress without supervising anybody. Recognising knowledge-sharing in grades makes teaching a route up, not a threat. The study of why engineers leave for dealers and rivals explains how to dig out the true reasons inside your own team.
Building the backups
Backups grow on real calls, not in classrooms. Pair each junior with a senior on a machine family, sign off by fault type, and log progress. Over a year a junior might move from installation and user training, to routine repairs, to diagnosing the unusual faults. The staged path for service engineers describes how machine-family sign-offs can work. On joint visits, let the junior carry the spares bag. That way they learn which O-rings, solenoid valves and pressure transducers fail first on each model. Soon they stop ringing the senior from the corridor outside an ICU, because the answer is already in their own notes and the shared log.
A starting checklist
- Ask your senior engineer which machine faults only he or she can cure.
- Count last quarter's field calls handled by one person alone.
- Check whether the latest released drawings match what is actually shipping.
- Write down which engineers resigned over the last two years, and what fixes walked out alongside them.
- Pick an understudy for every machine family before month end.
