All TopicsReliability

Cause and Effect Analysis – Interactive Simulator

Cause and Effect Analysis Using the Fishbone Diagram – Interactive Simulator

When a problem occurs repeatedly in a plant, the first reaction is often to repair the equipment and restart the process. However, repairing the immediate fault does not always eliminate the actual reason behind the problem. Unless the root cause is identified and corrected, the same issue may happen again.

This is where Cause and Effect Analysis, also known as the Fishbone Diagram or Ishikawa Diagram, becomes useful.

The fishbone method helps engineers and maintenance teams list possible causes, investigate them systematically, identify the actual causes and decide where corrective action is required.

This interactive simulator demonstrates how the method works through practical industrial examples.

1. What is Cause and Effect Analysis?

Cause and Effect Analysis is a structured problem-solving technique used to identify and investigate the possible reasons behind a particular problem.

The problem is called the Effect, while the contributing factors are called Causes.

For example, consider a centrifugal pump with repeated mechanical seal leakage. Instead of immediately replacing the seal again, the maintenance team investigates possible causes such as:

  • Incorrect seal installation.
  • Shaft misalignment.
  • Worn bearings.
  • Incorrect seal material.
  • Lack of alignment checks.
  • Changes in fluid temperature.

The objective is to distinguish actual causes from assumptions and unrelated observations.

2. Understanding the Fishbone Diagram – 6M Categories

The fishbone diagram organizes possible causes into six major categories, commonly known as the 6M method.

Man

This category covers human-related factors that may contribute to a problem.

Examples:

  • Incorrect equipment operation.
  • Inadequate training.
  • Improper maintenance practices.
  • Communication gaps during shift handover.

Machine

This category covers equipment-related problems.

Examples:

  • Shaft misalignment.
  • Worn bearings.
  • Pump vibration.
  • Equipment deterioration.
  • Incorrect equipment sizing.

Method

This category covers procedures and working methods.

Examples:

  • Incorrect operating procedure.
  • Missing inspection steps.
  • Improper maintenance sequence.
  • Inadequate preventive maintenance practices.

Material

This category covers raw materials, spare parts and consumables.

Examples:

  • Incorrect seal material.
  • Unsuitable gasket material.
  • Poor-quality spare parts.
  • Incorrect process material properties.

Measurement

This category covers instruments, measurements and monitoring practices.

Examples:

  • Temperature transmitter drift.
  • Incorrect pressure indication.
  • Lack of vibration monitoring.
  • Calibration errors.
  • Failure to review equipment trends.

Environment

This category covers surrounding and operating environmental conditions.

Examples:

  • High ambient temperature.
  • Dust and contamination.
  • Humidity.
  • Process temperature fluctuations.
  • Corrosive atmosphere.

These categories help the team investigate the problem without focusing only on the most obvious equipment fault.

3. How to Perform Cause and Effect Analysis

A practical investigation can be carried out in the following sequence.

Step 1 – Define the problem

Clearly describe the effect that needs investigation. Avoid vague problem statements.

For example: “Pump mechanical seal leakage” is more useful than simply writing “Pump problem.”

Step 2 – Identify possible causes

List possible causes under the six categories. At this stage, do not assume that every listed item is an actual cause.

Step 3 – Test the possible causes

Investigate each cause using inspection, measurements, maintenance history, operating data or other suitable evidence.

Step 4 – Identify actual causes

Separate confirmed causes from causes that are not related to the problem.

Step 5 – Implement corrective action

Correct the confirmed causes and monitor the equipment or process to check whether the problem has improved.

Step 6 – Verify the result

Check whether the defect rate has reduced and whether the problem has been eliminated or brought within an acceptable limit.

4. Understanding the Simulator

The interactive Cause and Effect Simulator demonstrates this investigation process using three industrial scenarios:

  • Pump seal leaks.
  • Off-spec product.
  • Valve passing.

Select a scenario from the Effect dropdown to start the exercise.

The fishbone diagram displays the six cause categories. Select a category to view its possible causes, then add the causes you want to investigate.

The simulator provides three important actions:

Add Causes

Select possible causes from the categories and add them to the cause list. You can also use Add All Causes to include all the listed possibilities.

Adding a cause does not mean it is confirmed. It only means that it has been selected for investigation.

Test Causes

Testing represents an investigation to determine whether a suspected cause is genuine.

The simulator uses two outcomes:

  • Red – Real cause: The cause is identified as contributing to the problem.
  • Grey – Not related: The cause is not identified as a contributing factor in the scenario.

The testing cost is 1 unit per cause in the simulator.

Fix Real Causes

After testing, use the Fix action to correct the confirmed causes.

The simulator assigns a cost of 4 units for each fix. Fixing an unrelated cause is treated as an incorrect action when using the individual Fix button.

This demonstrates an important maintenance principle: identifying the actual cause before implementing corrective action can avoid unnecessary expenditure.

5. Understanding Defect Rate and Cost

The simulator displays three important values:

Defect Rate

The defect rate starts at 100%. When a confirmed cause is corrected, the defect rate reduces according to the contribution assigned to that cause in the selected scenario.

Cost

The cost indicator increases when causes are tested or fixed. Testing costs 1 unit, while fixing costs 4 units.

Causes Listed

This indicates the total number of possible causes added to the investigation.

The simulator considers the problem solved when the defect rate reaches 5% or below.

These values are simplified training indicators. In an actual plant investigation, defect rate and cost should be calculated using real operating, quality, maintenance and financial data.

6. Practical Exercise: Investigating Pump Seal Leakage

Try the following exercise in the simulator.

  1. Select Pump seal leaks from the Effect dropdown.
  2. Select the Machine category.
  3. Add causes such as shaft misalignment and worn bearing.
  4. Test the selected causes.
  5. Observe which causes are identified as real.
  6. Fix the confirmed causes.
  7. Monitor the defect rate and total cost.

Repeat the exercise using Method, Material and Measurement categories.

Notice that not every possible cause contributes to the problem. The objective is to identify and correct the actual causes rather than spending money on every suspected issue.

7. Practical Exercise: Off-Spec Product

Select Off-spec product and investigate possible causes.

Consider the following examples:

  • Wrong recipe loaded.
  • Heater overshoots.
  • No hold time set.
  • Feed purity low.
  • TT-102 drifted.

Add and test the possible causes. Then correct the confirmed causes and observe how the defect rate changes.

This scenario demonstrates how the fishbone method can be applied to process and product-quality problems, not just rotating equipment.

8. Practical Exercise: Valve Passing

Select Valve passing and investigate possible reasons for passing through a control or isolation valve.

Possible causes include:

  • Seat wear.
  • Plug erosion.
  • Actuator weakness.
  • No seat test.
  • Soft trim used.
  • Abrasive solids in the process.

Test the causes before applying corrective action. This exercise helps demonstrate the difference between a suspected valve problem and a confirmed contributing factor.

9. Fishbone Analysis vs. Root Cause Analysis

The fishbone diagram is a useful tool for organizing possible causes, but it does not independently prove the root cause.

For example, if a pump has repeated seal failures, shaft misalignment may be identified as a contributing factor. Further investigation may still be needed to understand why the misalignment occurred.

The team may need to check:

  • Foundation condition.
  • Pipe strain.
  • Coupling condition.
  • Alignment records.
  • Maintenance history.
  • Operating conditions.

Therefore, fishbone analysis should be used along with inspection, measurement, trend analysis and other Root Cause Analysis (RCA) techniques.

10. Important Points for Maintenance and Reliability Engineers

  • Do not assume that the first suspected cause is the root cause.
  • Use actual evidence to confirm suspected causes.
  • Review equipment history and repeat-failure records.
  • Involve operators, technicians and engineers in the investigation.
  • Distinguish between symptoms, contributing factors and root causes.
  • Implement corrective actions that prevent recurrence.
  • Verify the effectiveness of corrective actions after implementation.

For reliability improvement, the result should ultimately be reflected in actual plant performance, such as reduced repeat failures, improved equipment availability and lower maintenance expenditure.

Conclusion

Cause and Effect Analysis is a simple but effective technique for organizing problem investigations. The 6M fishbone method helps maintenance and process teams consider different categories of possible causes instead of concentrating on only one area.

Use the interactive simulator to practise adding possible causes, testing them and correcting confirmed causes. The exercises are designed to demonstrate the investigation approach through simplified industrial examples.

Important: This simulator is intended for learning and training. Its scenarios, cause classifications, defect-rate reductions and cost units are predefined examples, not live plant data or a substitute for an actual engineering investigation.