Maintenance journal
The Maintenance Journal is where you record what broke and how it was fixed, so Edmund can draw on your own experience when the same problem comes back.
Expert / technicianThe Maintenance Journal lives inside a project, alongside its documents. Every entry you write becomes knowledge Edmund can search and cite when someone asks about that machine. A clear record of a past repair is often the fastest answer to the next breakdown, so the journal is worth keeping up to date. For how this fits with documents and the rest of a project’s knowledge, see Core concepts.
Add an entry
Adding an entry is done from inside the project, so open the project first.
Open the project, then go to Maintenance Journal.
Choose Add entry to open the form.
Give the entry a short, searchable Name that names the symptom or the machine area.
Set the Event date and time to when the problem happened, not when you write it up.
Fill in Description (what was observed) and Solution (what fixed it).
Upload a photo if you have one. Files up to 10 MB are accepted, in jpg, png, jpeg, gif, bmp, tiff or tif format.
Save the entry. It appears in the list and becomes context Edmund can use.
Write an entry Edmund can use
A good entry reads as symptom, then root cause, then fix. That order is what makes it useful months later, to a colleague who wasn’t there and to Edmund when it searches the journal for a match.
- Symptom — what was actually observed: the fault code, the noise, the reading, what the machine did or stopped doing. Put this in the Description.
- Root cause — what you found once you looked: the worn part, the loose connection, the setting that had drifted.
- Fix — what you did to resolve it, and anything needed to confirm it held. Put this in the Solution.
- Photo — a picture of the failed part, the wiring or the panel makes the entry far easier to recognise than words alone.
Write the Name and Description the way someone would describe the problem when it recurs, using the words they would search for. The closer the entry is to how the fault is reported, the more reliably Edmund surfaces it.
Find past entries
The list shows each entry’s Name, Status, Source Type, Creator and Created At. To narrow a long journal, use the filters for Status and Source Type, or type into the search box to match by name. Source Type tells you where an entry came from, which is useful for separating entries your team wrote from those brought in another way.
