Maintenance journal
How to set up maintenance journals in Edmund, assign them global, by project or by tag, add records Edmund can search and cite, and view a project's journals.
A maintenance journal is another layer of a project’s knowledge, alongside its documents, PLC programs and connected data. The obvious use is a log of how a machine has run and been repaired. The less obvious one matters as much: a journal takes what is written down nowhere else — a procedure someone worked out on the floor, a setting that has to be restored after a part is changed.
Each record you add becomes knowledge Edmund can search and cite when someone asks about that machine, so a clear write-up is often the fastest answer to the next breakdown — see how answers link back to their sources.
Journals are set up once at the organization level, then assigned to the projects that should use them. A project can have one journal, several, or none.
Set up a journal
Setting up journals lives in Organization settings, so these steps are for administrators. If you’re an Expert user, skip to Add a record below — you add records to journals an administrator has already set up. Users and readers can open and read journals, but only Experts and administrators manage records.
In Organization settings, open Maintenance journals. This lists the journals you already have; you can search, or filter by project and by source.
Click Add journal, give it a Name and an optional Description, then choose Next.
Choose how it’s assigned — Global (every project in the organization), specific projects, or by tag — then save.
Assigning by tag is available when your organization uses tags. Global is the quickest way to make one journal available to every project at once.
Add a record
Open a journal — from Maintenance journals, or from a project’s Project journals — and choose Add entry.
Give the record a short Title that names the symptom or the machine area.
Set the Event date — when the problem happened, not when you write it up.
Fill in the Description (Description — what was observed) and the Solution (Solution — what fixed it).
Attach a file if you have one — a photo of the failed part or panel makes the record far easier to recognize later than words alone. Then Save the record.
Write the Name and Description the way a colleague would describe the fault when it recurs, using the words they’d actually search for. The closer a record is to how the problem is reported, the more reliably Edmund surfaces it.
Inside a journal you can search and filter the existing records, and keep adding new ones as work is done.
Edit a record
A record is not fixed once saved. Edit it and Edmund keeps a new version rather than overwriting what was there, so the earlier wording is not lost — useful when a repair turns out to have been described wrongly, or when the same fault comes back and teaches you more about it.
The list shows each record’s Version and when it was Last edited, so a record that has been revised is visible without opening it. Once there is more than one version, open the record to move between them and see what changed.
View a project’s journals
From inside a project, open Project journals in the left bar to see the journals assigned to that project. You can add and work with records there exactly as above.