Search
Type a symptom, a part number, or whatever you have, and articles, guides, notes from the floor and lessons learned answer together — ranked, not separated into four lists you would have to check one by one. Two filters sit beside the box for browsing rather than searching: the kind of asset, and a failure code.
A guide is the one result besides an article with enough to it to expand rather than read in one
line: its probable causes and its steps to check, in order, followed by what to do about it, with
any safety note shown first regardless of where it was written.
Articles
The register tab behind the search box, for authors: everything that has been written, its status, who wrote it, how many people have read it, and how it has been rated. An article is a controlled document in every way that matters. Amending a published one opens a new draft rather than rewriting what people are currently following — the published version stays exactly as it is until the draft is published in its place. Its page carries:- Version and history — every revision, who changed it, and when, on the page rather than behind an audit tab.
- Was this helpful? — asked once, at the end of the body: two buttons, not a star rating, because the thing worth knowing is whether to keep the article at all, not how many stars it earns. A no opens a comment box; that comment is what an author can act on, and the dissenting comments are shown as sentences rather than folded into a single percentage.
- Came from the floor — the technician’s notes that were promoted into this article, if any.
Article status runs draft → in review → published → archived. Archiving keeps every past
version — somebody followed them — and asks why the article is no longer the answer, for the next
author’s benefit.
From the floor
The raw material knowledge is made of: short notes technicians write against a job or an asset, typed as a tip, a warning, a workaround, something about a tool or a part, how to get to it, or just something noticed. They are searchable from the day they are written, and this tab is where somebody reviewing a week’s worth decides which one is worth turning into an article with Make this an article — which starts a draft from the note; the note itself stays where it was written, and a note already promoted is shown greyed rather than hidden, so nobody writes the same article up twice.Lessons learned
What an event taught, raised against the work order, root cause investigation, shutdown, incident, inspection or audit that taught it. Closing a lesson asks the one question the register exists for: did the maintenance plan change because of this? — answered yes or no, never left as “we discussed it”. The header counts how many lessons have actually changed a plan, because that number, not how many were recorded, is the point of keeping the register.On the job
A What we know about this panel appears on a work order without anybody having to go and search for it: it reads the job’s own asset, its type, and what was recorded as wrong, and turns those into the handful of articles, guides, notes and lessons worth reading — absent entirely rather than shown empty, so the one job that does have something to say still stands out. The same panel is where a technician writes a note or records a lesson without leaving the job, and a link back to the full search is always one click away.Discussed in
A record — an asset, a work order, anything with a comment thread — can show Discussed in: the conversations that mentioned it, drawn from wherever people talked about it in Messages. It only ever shows threads you already have access to, and it draws nothing at all where nobody has mentioned the record — the same absent-rather-than-empty rule as the knowledge panel above.Documents
The controlled document library and the folder tree it files into — the other half of what used to
sit under Assets.