Introduction

Truke KF helps perform failure and risk analysis during the development of a product or process. It enables the recording of actual and potential defects and the generation of reports and reuse of this information in new products or processes. It helps to learn from mistakes.

First, a product or process must be created, optionally with components or subprocesses. Then defects (potential or actual) can be added, either to the product/process itself or to one of its components. For each defect, a cause-effect chain can be created and actions defined. In this way, reports such as an FMEA (DFMEA or PFMEA) and fault tree diagrams can be created.

[TODO: Solution diagram]

Each action can be analyzed for its impact on the product or process. If the action implies a change, a DRBFM report can be made after writing down the effects and risks. If the action implies a test, a DRBTR report can be derived once the concerns and actions are established.

Risk analysis is also supported. Each failure can have an associated severity and occurrence following a risk scale such as VDA/IAIG or SAE J1739, or even ISO 26262 for functional safety-relevant failures. The detection rating is associated with actions.

Wiki features

• Copy / paste of images and files, no duplicates stored.
• Revisions and immutable views, including images and uploaded files.
• Math (TeX syntax)
• Partial docs
• Print view
• Browseable data view (with the aid of 3 table styles)
• URLs to doc parts and to data items
• Type assignment for partial docs (in header: {!type})
• Partial doc parameters / attributes ([!] to do)

Products and processes

• A physical object
• A service
• A software product
• A process
• A tool for a process

(elements that can be used as resources: "needs/uses" relation)

Elements, failures and actions

Elements can be physical or not (can be functions) (elements are designed, events occur) Elements are systems, systems are elements.

An action is an element? Events (positive, negative) Relations: effect

A failure is an unwanted behavior or condition of an object, normally considered a deviation of its specifications.

Failures

• Event (cause-effect) chain
• FMEA, FMECA, FMEDA?
• Risk analysis
• Failure tree
• Solution tree

Actions

• Negative and positive effects
• DRBFM, DRBTR

Risk

Definition: the probability of something bad happening (harm to people, nature, the business; an ilegal situation). Risk is the product of probability and severity.

Learning

Learning works in these ways:

• Any object can be tagged as a 'rule'.
• Objects (or trees of objects) can be promoted to the know-how section (Documentation), and used as types or templates.

Once and object is defined as a rule, it should point to a process that assures the implentation of that rule. That is done by an 'implemented by' link to an action. In turn, that action needs to have a checkpoint.

Rules are specific to a type of element. If a new element is created with that type, how are rules enforced ? Each rule needs to be implemented by an action with the tag done.

Writing documentation: markdown and versioning

Truke FA is in a sense a wiki. Documentation in a markdown variant can be added to the Description field of each object. Also images and files can be copied into the same field. The headers in the document define its structure; each header has an associated URL that allows retrieving just that part of the document. Additionally, the markdown variant allows adding links between document parts, enabling traceability between those parts.

MD