Quality Assurance (QA) Module

1. Introduction

The QA Module in our portal is designed to help businesses manage and resolve customer complaints systematically. It provides a structured workflow to track, analyse, and solve issues efficiently, ensuring continuous improvement in product and service quality.

A key feature of this module is the 8D (Eight Disciplines) Problem-Solving Process, a structured approach used to identify root causes, implement corrective actions, and prevent recurrence of issues.

2. QA Module Overview

The QA Module consists of four key sections that enable effective complaint tracking and resolution:

2.1 Complaint Source

This section categorises the origins of complaints, helping in trend analysis and problem identification.

Features:

• Add, edit, view, and delete complaint sources.

 Examples of Complaint Sources:

• Job-related issues – Incorrect work instructions, missing documentation
• Product defects – Damaged goods, faulty components
• Production errors – Machine failure, incorrect assembly
• Tooling issues – Broken tools, incorrect settings
• Customer feedback – Complaints received from customers

2.2 Containment Actions

Containment actions are temporary measures taken to control the impact of an issue while a permanent solution is being developed. These actions ensure that defective products or faulty processes do not continue affecting customers or production.

2.2.1 Action Matrix

 Purpose

The Action Matrix allows users to define specific actions that must be taken to contain an issue. Each action is associated with a name, description, and type to help categorise and measure containment efforts effectively.

Fields in Action Matrix:

• Name → The title of the action (e.g., "Inspect Defective Items").
• Description → A brief explanation of the action (e.g., "Inspect all units in Batch #123 for dimensional accuracy.").
• Type→ Defines the data format:
  • Boolean (Yes/No) – Used when an action has a binary state (e.g., "Was rework required? Yes/No").
  • Number – Used when a numerical value is required (e.g., "Number of defective units identified").
    
    

Example of an Action Matrix Entry

2.2.2 Location Management in Containment Actions

Purpose

The Location field allows users to specify where a containment action is being applied. Different locations may require different containment strategies depending on where the issue has occurred.

 Fields in Location Module:

• Name → The specific location where containment is being applied (e.g., "Assembly Line A").
• Description → Details about the location (e.g., "Final inspection area for completed products").

 Example of Locations in Containment Actions

2.3 Customers

This section manages all customer-related information.

Features:

Add, edit, view, and delete customer records

• Maintain detailed information such as:

• First Name & Last Name
• Company Name
• Email & Phone Number

2.4 Complaint Management (Dashboard)

The complaint dashboard provides an overview of reported complaints, including their severity and key performance indicators (KPIs).

Complaint Submission Fields:

Once a complaint is added, it can be processed using the 8D problem-solving methodology to ensure proper resolution.

3. 8D Problem-Solving Process

The 8D methodology is a structured approach designed to identify, analyse, and resolve problems effectively.

Step 1: Form a Team (D1)

Assemble a cross-functional team with relevant expertise.

Example:
A company experiencing frequent product defects creates a team of:

• Production Manager (operations expert)
• Quality Control Expert (ensures standards)
• Design Engineer (product knowledge)
• Supplier Representative (material quality)

Step 2: Define the Problem (D2)

Purpose:
In this step, the problem must be clearly defined using factual data. A well-defined problem ensures that the team fully understands the issue before identifying the root cause and implementing solutions.

To define the problem effectively, we use the 5W2H (Who, What, Where, When, Why, How Big, and Problem Statement) approach.

Problem Description

Problem Statement

A problem statement is a concise description of the issue that provides enough detail to guide the next steps in the 8D process.

Example Problem Statement:
"During the final inspection at Factory A, 30% of smartphones in Batch #123 failed the touch sensitivity test. This issue affects customer satisfaction and has led to shipment delays. Initial observations suggest that the problem may be due to a faulty touchscreen module or incorrect assembly processes."

Example Scenario: Defining the Problem

Scenario:

A car manufacturing company receives multiple complaints about steering vibrations in newly delivered vehicles.

Problem Definition (5W2H)

Problem Statement:

"Customers who purchased Model X vehicles manufactured in Factory B have reported excessive steering vibrations at speeds above 80 km/h. This issue affects 20% of vehicles in recent production and is causing an increase in customer complaints and warranty claims. Initial investigations suggest improper wheel alignment or defective steering components as possible causes."

Why Defining the Problem Clearly is Important

• Prevents miscommunication and confusion within the team
• Helps in identifying the real root cause instead of just treating symptoms
• Ensures that corrective actions are targeted and effective
• Saves time and resources by focusing on the right problem

Step 3: Implement Temporary Containment Actions (D3)

Purpose:

This step involves taking immediate actions to contain the problem and prevent it from affecting more products or customers. These are temporary measures used while the root cause is being investigated and a permanent solution is developed.

Interim Containment Actions

Containment actions depend on the nature of the problem and where it occurs. These actions are defined based on specific locations where defects are detected and actions that need to be taken.

Example Containment Actions Matrix

Example Scenario: Containment Actions in Action

Scenario:

A smartphone manufacturer discovers that 30% of devices in Batch #123 have touchscreen issues.

 Step 1: Identify Locations for Containment

1. Receiving Inspection Area → Check incoming touchscreens from the supplier.
2. Assembly Line A → Halt production of new batches until the issue is resolved.
3. Warehouse Section B → Separate defective stock to prevent accidental shipments.
4. Final Quality Check (FQC) → Increase inspection for future batches.
5. Customer Service Desk → Contact customers to manage expectations.

 Step 2: Apply Containment Actions

 Why Temporary Containment Actions Are Important

    Prevents Defective Products from reaching customers
Reduces Impact on production and shipments
Helps Identify Problem Areas quickly
Minimizes Financial & Reputation Losses

These actions buy time while the root cause is identified in Step 4: Identify the Root Cause (D4).

Step 4: Identify the Root Cause (D4)

Root Cause Analysis (RCA) is the process of identifying the underlying cause of a problem rather than just addressing its symptoms. This step ensures that the corrective actions in later steps eliminate the issue permanently rather than just temporarily fixing it.

Root Cause Identification Methods

The "5 Whys" Method

The 5 Whys technique is a simple but effective method for identifying the root cause of a problem by repeatedly asking "Why?" until the fundamental issue is revealed.

 How It Works:

1. State the problem.
2. Ask "Why did this happen?"
3. Continue asking "Why?" until the real cause is identified. (Usually, five iterations are sufficient, but more may be required.)

 Example: Root Cause Analysis for a Smartphone Touchscreen Issue

Root Cause:
Lack of a routine calibration check led to misconfigured machines, which caused improperly calibrated touchscreens.

Uploading Evidence & Images

To support RCA, the system allows users to upload images of defective products, machine logs, and test reports. These images can provide valuable insights when analysing the root cause.

Examples of uploaded evidence:

• Defective touchscreen samples
• Calibration machine logs
• Production process images
• Test reports showing the issue
  
  Example: Applying RCA in a Real-World Scenario

A car manufacturing company receives complaints about steering vibrations in Model X vehicles.

   
    5 Whys Analysis:

Root Cause:
A lack of SOP updates led to outdated alignment procedures, causing steering vibration issues in vehicles.

Why Root Cause Analysis is Important?

• Prevents Recurrence – Fixes the real cause, not just the symptoms.
• Reduces Costs – Avoids repeated failures and warranty claims.
• Improves Processes – Strengthens quality control and production efficiency.
• Enhances Customer Satisfaction – Delivers consistent and defect-free products.

Step 5: Develop Permanent Corrective Actions (D5)

Once the root cause has been identified in Step 4, we must develop and implement corrective actions to eliminate the issue permanently and prevent it from recurring. Additionally, we implement detection improvement actions to catch similar issues earlier in the process.

Corrective Actions to Address Non-Conformance

Corrective actions are taken to eliminate the root cause of a problem. These actions directly address why the issue occurred and ensure it does not happen again.

Key Questions for Corrective Actions:

• What? → What action needs to be taken to fix the problem?
• Who? → Who is responsible for implementing the action?
• When? → By when should the action be completed?
• Who will verify? → Which manager or authority will confirm that the action has been properly implemented?
  
  Example: Corrective Action for Touchscreen Issue

Corrective Actions to Improve Detection

Detection improvement actions enhance quality control processes so that similar issues can be detected earlier, preventing defective products from reaching customers.

Key Questions for Detection Improvement:

• What? → What action will be taken to improve defect detection?
• Who? → Who is responsible for implementing the action?
• When? → By when should the action be completed?
• Who will verify? → Who will confirm that the detection improvement is effective?
  
  Example: Detection Improvement Actions for Touchscreen Issue

Example Scenario: Corrective Actions in a Car Manufacturing Issue

A car manufacturer finds steering vibrations in Model X vehicles due to misalignment issues caused by outdated procedures.

Corrective Actions to Address Non-Conformance

Corrective Actions to Improve Detection

Why Corrective Actions Matter?

• Prevents the problem from occurring again
• Reduces defect rates and rework costs
• Enhances quality control and detection systems
• Improves customer satisfaction and brand reputation

Step 6: Implement & Validate Corrective Actions (D6)

After implementing the corrective actions identified in Step 5, it is crucial to verify that they have been successfully executed and that they are effectively eliminating the problem. This step ensures that the root cause is permanently addressed and does not reoccur.

Verification Process

Each corrective action must be:

• Implemented correctly – The assigned person must confirm the completion of the task.
• Monitored for effectiveness – The corrective action should prevent recurrence of the issue.
• Verified and approved – A responsible manager must check if the issue has been fully resolved.
  
  Key Questions for Verification:
• What? → What action needs to be verified?
• Who? → Who is responsible for verification?
• When? → When should verification take place?
• Done? → Is the corrective action successfully completed?
  
  Example: Verifying Corrective Actions for a Touchscreen Issue

 Example: Verifying Corrective Actions for a Steering Vibration Issue

 Effectiveness Monitoring

To determine if the corrective actions are effective, the following metrics should be tracked:

• Defect rate reduction – Are fewer defective products appearing?
• Customer complaints – Has the number of complaints decreased?
• Rework costs – Are fewer resources being spent on fixing defects?
• Audit results – Do internal quality checks confirm the issue is resolved?

Why Verification is Important?

• Ensures Corrective Actions Are Fully Implemented
• Prevents the Problem from Reoccurring
• Validates the Effectiveness of Solutions
• Improves Overall Process Reliability

Step 7: Prevent Recurrence (D7)

The goal of this step is to ensure that the problem does not occur again in the future. It involves implementing preventive measures across all relevant processes, production lines, and facilities. Additionally, steps are taken to protect the customer from any potential recurrence of the issue.

Preventing the Occurrence of the Problem

To eliminate the root cause permanently, we must:

• Strengthen processes, training, and inspections
• Standardize solutions across similar production lines
• Communicate improvements to other facilities

Key Questions for Prevention:

• What? → What preventive action will be taken?
• Who? → Who is responsible for implementing the preventive action?
• When? → By when should it be implemented?
• Can the countermeasure be carried over to similar lines? → Should this be applied to other production lines?
• Can the countermeasure be communicated to other sites? → Should other locations be informed of this solution?

Example: Preventing a Touchscreen Issue in Manufacturing

Protecting the Customer from the Problem

Even after implementing preventive actions, customer protection measures ensure that if an issue arises, it is caught before the product reaches the market.

 Key Questions for Customer Protection:

• What? → What action will protect the customer?
• Who? → Who is responsible for implementing it?
• When? → By when should it be completed?
• Can this measure be applied to other production lines?
• Can this measure be communicated to other sites?

 Example: Customer Protection Measures for Touchscreen Issue

 Expanding Preventive Measures to Other Machines & Processes

To further improve manufacturing efficiency and quality, we need to extend successful preventive actions to other related machines and processes.

 Key Questions for Expanding the Action Plan:

• What? → What action should be expanded?
• Who? → Who is responsible for implementation?
• When? → By when should it be completed?
• Can this measure be applied to other production lines?
• Can this measure be communicated to other sites?

 Example: Expanding Preventive Measures to Other Machines

Why Preventive Actions Are Important?

• Eliminates the risk of recurrence
• Improves overall product quality and reliability
• Reduces customer complaints and warranty claims
• Enhances efficiency across production lines

Step 8: Recognize Team Efforts (D8)

The final step in the 8D Problem-Solving Process is to acknowledge and appreciate the efforts of the team members who contributed to resolving the issue. Recognizing their dedication and hard work fosters a culture of accountability, teamwork, and continuous improvement.

Recognition Details

In this step, we formally document:

• Who contributed to solving the problem?
• What roles they played in the process?
• How their efforts helped in successfully resolving the issue?
• Approval and closing remarks from the leadership team.

Example: Team Recognition for Touchscreen Issue Resolution

Approval & Final Remarks

After the problem resolution is verified, the team lead or management formally approves the closure of the 8D process.

4. Conclusion

The QA Module in our portal provides a structured approach to managing complaints and ensuring quality improvements. 

• The issue is now fully resolved, and preventive actions are in place.
• The 8D report is archived for future reference and learning.
• The team is acknowledged for their contribution.