|Overview: No Fault Found|
A repair process that is unable to detect reported problems.
Returning an item to service in a repeated cycle of failure.
What is No Fault Found?
John Spacey, updated on November 16, 2016
No fault found is when a repair process is unable to detect reported problems. In some cases, this results in a defective unit being returned to service in a repeated cycle of failure. No fault found is often the result of diagnostic methods that are inadequate or buggy. Ideally, an organization uses no fault found cases to improve diagnostic processes and tools. In many cases, it is assumed that the user who reported the fault was wrong or that the problem has magically gone away.
QualityThis is the complete list of articles we have written about quality.
If you enjoyed this page, please consider bookmarking Simplicable.
A list of quality types.
The subtle difference between quality and value.The common types of quality metrics. The primary types of service quality.
The common types of experience quality.
A definition of critical to customer with examples.An overview of design life with examples.
The common types of planned obsolescence.The definition of quality objectives with examples.
A definition of credence quality.A list of ways to automate.
An overview of over-automation.
The difference between process orchestration and choreography.A reasonably comprehensive list of information technologies.
The different between robots and AI.
The difference between automation and robotics.
The common types of machine data.
The common types of office automation.
Common types of autonomous systems.
A definition of automation risk with examples.
TrendingThe most popular articles on Simplicable in the past day.
Recent posts or updates on Simplicable. Site Map
Management First Principles