What could be a greater waste of time and money than to pull a component, send it for test, and have it returned only to find that no failure was found. Why was it pulled in the first place? We outline the problem and describe some solutions. NFF is a major headache. We discuss: 1. Contributing factors such as inaccurate diagnosis, inability to duplicate the failure environment and failure to check first for failed connectors. 2. Potential solutions such as tagging rogue parts, encouraging communications and using a "hold" approach.
展开▼
