Customer Quality and Field Service Series Issue 2: Field Failure Analysis — From "Replace and Forget" to "Root Cause Closure" Management Advancement

1. Introduction

The story does not end when a product is delivered to the customer.

Every returned faulty item, every customer complaint, and every field failure report are "health check signals" for the company's quality management system. However, in many companies, field failure handling remains at the basic level of "replace and forget" — the replacement is quick, but the root cause analysis is shallow, leading to repeated occurrences of similar issues and a gradual decline in customer satisfaction with repeated complaints.

Field Failure Analysis (FFA) is the key management activity that upgrades this passive response to proactive improvement.

2. What is Field Failure Analysis? How Does It Differ from Laboratory Analysis?

Field Failure Analysis refers to the entire process of systematically collecting data, analyzing root causes, and implementing improvement loops for failures that occur in products already delivered to customers during their use.

It fundamentally differs from design verification or incoming inspection conducted in a laboratory:

In short: The laboratory tells you "whether this thing works," while field failure analysis tells you "why it broke at the customer's site and how to prevent the next customer from encountering the same issue."

3. Three Levels of Field Failure Analysis

Level One: Failure Data Collection

This is the most fundamental but also the easiest to handle superficially. Many companies have records of returned items, but the data quality is often poor — failure descriptions are vague, such as "broken," "not working," or "unusual noise," which do not support any meaningful analysis.

Effective failure data collection should at least include:

• Product Information: Model, batch number, production date, serial number
• Usage Information: Installation date, operating duration, operating environment (temperature/humidity/load)
• Failure Information: Failure mode (specific phenomena), failure time, whether it has been repaired
• Customer Information: Customer type, industry, geographical location

It is recommended to establish a standardized "Field Failure Information Registration Form" for frontline after-sales personnel to fill out, avoiding subjective descriptions.

Level Two: Failure Physics Analysis

After receiving the faulty item, conduct the analysis following the principle of "first appearance then microscopic, first non-destructive then destructive":

1. Visual Inspection: Take photos and observe for any obvious signs of cracks, deformation, burn marks, or corrosion.
2. Function Reproduction: Reinstall the faulty item on the test bench to confirm if the failure mode can be reproduced.
3. Non-Destructive Testing: X-ray, CT scan, ultrasound — inspect for any internal structural abnormalities.
4. Semi-Destructive/Destructive Analysis: Cross-sectional analysis, SEM/EDS spectroscopy, metallographic analysis — determine the failure mechanism (fatigue, overload, corrosion, wear, etc.).
5. Comparison with Similar Items: Compare with normal items from the same batch or production period.

Note that not every failure requires analysis "at the atomic level." For low-frequency, low-impact failures, stopping at the second step "function reproduction" is sufficient. The depth of analysis should be proportional to the risk level of the failure.

Level Three: Root Cause Tracing and Improvement Loop

After identifying the failure mechanism, return to the manufacturing chain and ask three questions:

Question One: Design Phase — Does the design specification cover this operating condition?

• If the design did not consider this failure mode, update the DFMEA.
• If the design considered it but the margin was insufficient, trigger a design change.

Question Two: Manufacturing Phase — Did the manufacturing process introduce defects?

• Trace the production records, inspection records, and equipment parameters of this batch.
• Check if the procedure documents clearly specify the control methods for this characteristic point.
• Verify if any 4M changes occurred without validation.

Question Three: Inspection Phase — Can the current inspection methods detect this failure?

• Is the sampling plan for outgoing inspection reasonable?
• Is it necessary to increase full inspection or adopt more reliable testing methods?

Only by answering these three questions can field failure analysis truly form a closed loop.

4. Management Mechanisms for Field Failure Analysis

A good field failure management system requires the support of the following four mechanisms:

4.1 Tiered Response Mechanism

Establish a tiered response standard based on the severity and frequency of failures:

4.2 Failure Item Management

Establish a "failure item library" and retain all analyzed faulty items for at least 6 months, along with their analysis report labels. This not only aids in cross-referencing similar failures but also serves as excellent training material for new engineers.

4.3 Failure Database

Record the data, photos, analysis conclusions, improvement measures, and verification results of each failure analysis in a database. When similar failures occur again, historical records can be directly retrieved for comparison, significantly reducing analysis time.

4.4 Monthly Failure Review Meeting

Each month, the quality department should lead a failure analysis review meeting involving design, process, after-sales, and procurement departments:

• Review the progress of all Level A and B failure analyses from the previous month.
• Confirm whether improvement measures have been implemented.
• Evaluate whether there are any abnormal changes in market failure trends.
• Formulate meeting minutes and track pending items.

5. Common Misconceptions

Misconception One: "Only analyze returned items, not those not returned" Field failure analysis should include failures reported by customers but not returned, as well as suspicious cases identified by field service personnel. Waiting for items to be returned often misses the optimal window for collecting on-site information.

Misconception Two: "Analyzed a lot, made changes, but the same issue keeps recurring" This indicates that the improvement measures have not been standardized. Each root cause should be matched with specific document updates — FMEA updates, control plan adjustments, inspection standard changes, and work instruction supplements. Any improvement not documented is not a true closed loop.

Misconception Three: "Failure analysis is the responsibility of the quality department" The root causes of field failures often lie in the design and manufacturing phases. If only the quality department is driving the process, it often lacks the necessary resource investment from design and manufacturing, leading to incomplete follow-through. A cross-functional failure analysis team must be established, and the quality department should be granted the "right to halt" — the issue cannot be easily closed until the root cause is identified.

6. Conclusion

Field Failure Analysis is a crucial indicator of a company's quality management maturity. It tests not just the analysis equipment and techniques but also the organization's systemic capabilities — whether it can convert information from a single failure into improvement actions across the entire chain.

The gap between "replace and forget" and "root cause closure" is not in technology but in management mechanisms.

When every returned faulty item is not wasted and every failure drives improvements in design and manufacturing, the company's quality competitiveness can truly extend from the "manufacturing end" to the "usage end."

Knowledge code: 10.2.2

Version: v20260601

Author: Quality Think Tank