Operational memory
What the last person knew.
The diagnosis that took three visits. The repair that did not hold. The reason a setting was changed. Mainte keeps what was learned on the machine itself, in the words of the person who learned it, so whoever works on it next starts from there.
Published 4 min read5 sources
Written for maintenance managers · reliability engineers · supervisors · plant and fleet managers
The problem: the history is in people, and in the wrong system
Every maintenance team has the person the others ask. They know the pump that cavitates when the tank is low, the excavator whose hose chafes on the boom bracket, the setting that was changed after the last breakdown and why. When they are on leave, move sites or retire, or the contractor changes, that history leaves with them. What remains is a list of closed work orders: dates and costs, not causes.
That is not a small-site problem. Investigating a refinery explosion that killed fifteen people, the US Chemical Safety Board found:
“The maintenance work order system was primarily an accounting program that lacked crucial information about work order history, the cause of failures, and whether equipment was successfully repaired.”
Research for the UK's Health and Safety Executive on ageing plant warns that 'a lifetime's knowledge that has been built up by one person can be easily lost upon retirement'.[2] In Australia, the next person on the job is increasingly likely to be new to the site or the trade: in 2025, almost one in two technician and trades occupations were in national shortage.[3]
Where knowledge gets lost
- At the shift change. The HSE notes that many accidents have followed a failure of communication at shift handover, and that most of those involved planned maintenance work.[4]
- At close-out. 'Repaired, OK' tells the next technician nothing about what was found, what was tried first, or whether the fix is expected to hold.
- In a system built for something else. Work-order systems are often configured for cost and compliance. They record that a job happened, not what the person doing it learned.
- In a person. The longest-serving operator's knowledge is the plant's most valuable record, and the one with no backup.
How Mainte handles it
- The close-out note is the service record
- 'What did you do?' is one question at close-out, and the answer is kept as written, on the machine. That free text matters: research on Australian mobile-equipment work orders found the coded fields often missing or wrong, and the technicians' own words were what made the history usable.[5]
- One timeline per machine
- Readings, checks, findings, notes, service records, requests, work orders, stand-downs, documents and photos, in order, searchable, with who recorded each. It exports as a branded machine report when someone outside needs it.
- A finding stays with its fix
- A finding stays open until a person resolves it, and the work that resolved it stays linked. When the same fault returns, it is counted against the machine ('recurred 3× in 90 days') rather than rediscovered.
- Notes from the field
- An operator or technician adds a note or a photo to the machine from their phone, starting from its QR label. 'Slow slew on cold start, cleared after warm-up' becomes part of the record the next person reads.
- The manual, at the page
- Manuals, service reports and certificates are read and filed against the machine they describe, each item pointing back to its page. Anything uncertain is held back for a person to review.
- Ask the machine
- The assistant answers from the machine's own record and documents, names the source and opens it. An OEM procedure, a technician's note and an AI observation are labelled as what they are. If it cannot ground an answer, it says so.
- Handover that carries forwardFixed plant
- The shift log holds handover notes, routine tasks and dose changes by process area, linked to the work they touch, and the morning report summarises the shift from it.
- Through Claude, as youMainte Connect
- With Mainte Connect, an authorised Claude can read the record with your permissions and draft work orders, requests and shift notes for you to approve. It never signs, completes work or changes who can do what.
What it changes
- A new starter or a new contractor starts with the history. The machine's page tells them what has gone wrong before and what was done, without finding the person who remembers.
- The second diagnosis is faster than the first. What the last technician found, and what did not work, is on the record before the next one opens the cover.
- Decisions have a basis. Whether to keep repairing, change the maintenance or replace the machine is argued from its own record, not from recollection.
- Less depends on any one person. Knowledge that used to live in a few heads lives on the equipment, in their words, with their name on it.
The inquiries that make this case most clearly are set out in The history was there. It wasn't on the record.
Sources
- [1]Investigation Report: Refinery Explosion and Fire, BP Texas City (Report No. 2005-04-I-TX) · US Chemical Safety and Hazard Investigation Board · March 2007 · Federal incident investigation reportQuoted from section 10.1.1, p. 181.
- [2]Plant ageing: management of equipment containing hazardous fluids or pressure (RR509) · Health and Safety Executive (UK); prepared by TWI, ABB Engineering Services, SCS and Allianz Cornhill Engineering · 2006 · Research report commissioned by the regulatorQuoted from section 2.5.2. Internet Archive copy; the HSE has since moved its research pages.
- [3]2025 Occupation Shortage List: key findings report · Jobs and Skills Australia · October 2025 · Government labour market reportMeasures occupations in shortage, not knowledge lost.
- [4]Human factors: shift handover · Health and Safety Executive (UK) · Current guidance · Regulator guidance
- [5]Cleaning historical maintenance work order data for reliability analysis · M. Hodkiewicz and M. Ho, University of Western Australia; Journal of Quality in Maintenance Engineering 22(2) · May 2016 · Peer-reviewed journal articleCited from the published abstract.
