Truke KF features

• Wiki:
• based on markdown
• drag and drop images and files (duplicates are avoided transparently).
• all revisions are stored.
• a link to any revision can be used as an immutable version, including a MD5 signature that covers images and files.
• Documents are browsable (headers are links, and return partial documents)
• Documents can be represented as data, and that data is browsable
• A paged media preview is available.
• Math can be included (Latex as per Mathjax)

• Items can be either objects, actions, events or documents. The reason for this classification is that each item class has a slightly different handling. The structure of an action is a gantt chart, while the structure of an object is a component hierarchy.
• Items can have components
• Actions can have duration and order. Actions can be marked as 'done', 'change', 'test'.
• Items can have events. Events in KF are of one class: failures (actual or potential).
• Failures can have causes and effects. This structure creates an event tree.
• Failures can have associated actions.
• Failures can have an associated risk (severity and probability, plus detection and controllability that are specific for automotive).
• Actions can have an associated risk (normally a risk mitigation effect on the associated failure)
• A failure analysis is a report of an item and its components, its failures and risks, and their associated actions, in a 4 column format. The full event trees are represented in this format.
• Each item has an associated (possibly empty) failure tree.
• Items can have multiple types (not classes). An item inherits failures and actions of all its types
• Wiki document structure comparison. An item that is a type of another item is checked againts the structure of it (all headers are required to be present).
• A checklist of an item is defined as those actions associated with a type of an item
• The following special formats are integrated into the 4-column failure report: FMEA, FMECA, DRBFM and DRBTR. FMEA and FMECA are the same thing, the failure analysis of an item and its components. A DRBFM is the failure analysis of a change. A DRBTR is a failure analysis of a test.