8D Software | TREVIOS

The TREVIOS 8D Report Software provides you with complete support for the entire 8D process. From forming the team to implementing containment actions to evaluating possible root causes to remedying the problem – TREVIOS supports you through its logical workflow and simple operation.

A variety of integrated tools, such as the classic Ishikawa (cause-and-effect) diagram or the 5 Whys, help you to achieve a more thorough analysis. The workflow is flexibly tailored here to the customer’s wishes.

0D – 8D in outline

The problem encountered is assigned according to such aspects as customer, type of failure and location of failure at this stage. The organization of the data (what should be entered) is flexible here and adaptable to each customer. Additional documents and report templates for the team can be made available by means of attachments.

Figure 1: Entering the basic data for 8D

1D – Team formation

1D involves assembling the team and defining their responsibilities in subsequent process steps. The software may differentiate at this stage between different levels of responsibility (8D owner, kick-off owner, etc.).

Figure 2: Forming the team

2D – Problem description

This step allows the 8D owner to enter further details about the problem or add to the description made under 0D. As with all the screens, these entry forms can be flexibly tailored to the customer’s requirements.

Figure 3: Defining the problem encountered

3D – Containment actions

Step 3 involves defining interim actions. These actions need to be assigned in the software to dedicated people in the team. Actions may be predefined by the system (recurrent actions that are fundamentally necessary in the context of processing your 8Ds) and/or manually entered under this step. Each action can have its own processing status. The software monitors whether or not processing has been carried out on time by the person responsible. For every action it is possible to decide whether or not it is to be included in the 8D report.

Figure 4: Defining containment actions

4D – Root cause analysis and solution finding

The software supports the user by graphically identifying likely causes in a cause-and-effect (Ishikawa) diagram. The causes can be evaluated and/or graded in relation to their importance by means of color-coding.

For each cause, any number of solutions can be proposed. A 5-Why tool facilitates the progression from cause to solution.

Solutions found can be evaluated, classified and included as actions in 5D.

Figure 5: Cause-and-effect diagram

Figure 6: Deriving solutions

5D – Planning corrective actions

At step 5, actions are identified or adopted as the result of previous steps (e.g. 4D). All the actions are assigned to dedicated people in the team and are allocated percentage values for their effectiveness. Every action can have its own processing status. The software monitors whether or not processing has been carried out on time by the person responsible. For every action it is possible to decide whether or not it is to be included in the 8D report. Any further processing (6D) can be linked to the completion of individual actions (plausibilities).

Figure 7: Corrective actions, scheduling and responsibilities

6D – Implementing corrective actions

Similar to step 5, step 6D involves actions being identified or adopted as the result of previous steps. In other respects, the performance of the software corresponds to step 6D. After successful implementation of the corrective actions, the containment actions are cancelled.

Figure 8: Implement corrective actions

7D – Preventing recurrence

Analogous to the previous steps, actions that prevent a recurrence of the failure are identified or adopted and monitored to ensure they are being processed on time. In addition, documents which, as part of the root cause analysis, represent newly recognized risks in the development and manufacturing process (e.g. under the FMEA method) need to be uploaded.