Show TOC

Function documentationVerifying Defects Locate this document in the navigation structure

 

The system automatically logs a verified defect when a unit has moved through a repair loop and passed the test operation. As operators troubleshoot problems with units (SFC numbers) in a repair loop on your routing, they may log many failure, defect, repair cycles that do not fix the problem.

Example

The figure below illustrates the NC codes that operators may log during the first cycle through a repair loop:

This graphic is explained in the accompanying text.

The figure below illustrates that when the unit is retested, it still fails:

This graphic is explained in the accompanying text.

The SFC number is then sent through the repair loop again, and operators log other NC codes that reflect their actions the second time through.

The figure below illustrates that the unit is tested the third time and it passes:

This graphic is explained in the accompanying text.

The system logs the NO_POWER, CABLECONWRONG (Defect), and RECONNECT (Repair) sequence as the verified defect.

When a unit that has previously failed a test passes it, the last defect and repair logged against the unit indicates what was actually wrong with the unit and how it was repaired. This last defect and repair is then verified to be the actual case and is called a verified defect. In POD Maintenance, you can configure a POD to display a Verified Defects chart to the operator in the POD (see NC Chart).