Everything the root cause analysis module does, in plain language. Search it, or scan straight through.
Open an investigation against the machine that failed, with its history from the shared asset registry alongside.
A straight chain of questions for the failures that do not need a tree.
Branching causes with as many contributing paths as the failure actually had.
Causes move where you put them, a minimap keeps big trees navigable, and the toolbar follows the work.
Capture the teardown on a phone and the photos attach to the investigation.
Documents, photos, and results pin to the cause they support, not to a general folder.
No action exists without a person and a date attached to it.
An investigation closes when its fixes are verified in service.
What is still open, who owns it, and how old it is, without opening each investigation.
Conclusions get agreed by review, not assumed by the author.
The tree, the evidence, the reasoning, and the actions on paper, with the diagram rendered as an outline for print.
What was recorded is what remains; corrections are new entries, not rewrites.
Machines ranked by failure downtime and cost across the window you choose.
Repeat failures on the same asset surface on their own.
What failures took, in hours and dollars, by machine and by area.
Mean time between failures, trended so improvement is visible.
Investigations reference the same machines every other module uses. Nothing is imported twice.
A finding survives its subject: retire an asset and the investigation keeps its name and tag.
Viewing and changing are separate rights, granted per person.
Ask about open investigations or bad actors in plain language and get figures with links.