Add a Pass/Fail/NA test to a sub-inspection when you want the inspector to indicate whether set criteria is met for the inspected item.
Circumstances in which you may want to add a Pass/Fail test to a sub-inspection:
The Pass/Fail test is best used for testing procedures that need a yes (passes) or no (fails) answer to an explicit testing question such as "Does the bolt have threading?" It is not used for testing procedures that require recording specific variables, such as the number of missing or superfluous bolt threads.
You may want to use the N/A ("not applicable") option along with Pass/Fail if you use the same inspection for similar parts that have distinct traits. For example, the inspection is used for a bolt that has threading in its specification and for a nail that does not have threading included in its specification. N/A would be the option the inspector would select for this test when the nail is inspected.
Note: If you have multiple defects associated with a test, consider using the Defects List test instead of Pass/Fail/NA tests.
|
Contents [Hide] |
Click the Pass/Fail test toolbar button to add this test to the sub-inspection.
Select a defect to include in the analysis for the test from the Selects Defects window that opens.
Set any properties for this test on the Properties panel that displays after the test is added.
For information about using the Properties panel, see Changing property settings
|
Property |
Field type |
Default setting or default display |
Allows |
|
APPEARANCE |
|||
|
Text field |
Fail |
Enter text to display on the fail button. [For example, you may want to display "No" or "Reject" on the button.] |
|
|
Text field |
Pass |
Enter text to display label on the pass button. [For example, you may want to display "Yes" or "Accept" on the button.] |
|
|
Label |
Text field |
[blank] |
Enter text for a display label for this test. |
|
BEHAVIOR |
|||
|
True/False |
False. The NCU (nonconforming units) field is always set to 0 and the Number Good field is always set to 1. Note: When the configuration setting Set nonconforming units = number of defects is enabled, the data is always stored as if this property were set to True. |
True. When the inspector fails the test, the NCU field is set to 1 and the Number Good field is set to 0. [PC]: When the inspector clicks the N/A button, a data record is stored with Sample Size = 0, NCU = 0, and Defects = 0 - regardless of this property. |
|
|
True/False |
False. Does not display the N/A ("not applicable") option along with Pass and Fail options for this test. |
True displays all three options (Pass, Fail, and N/A) for this test. [PC]: When the inspector clicks the NA button, a data record is stored with Sample Size = 0, NCU = 0, and Defects = 0 - regardless of the SetNCU and SampleSize properties. [Mobile]: When the inspector clicks the N/A button, no data is stored for the test - even if the Inspection property StoreAll is set to True. |
|
|
DATA |
|||
|
Defect |
[blank] |
Select a defect for the test. |
|
|
Number |
[blank] - The Sample Size for the data record will be 1. |
Enter a different sample size for the data record. Typical values are 0 or 1. If the inspector clicks Fail, the defect count will be 1 - regardless of this property. [PC]: When the inspector clicks the N/A button, a data record is stored with Sample Size = 0, NCU = 0, and Defects = 0 - regardless of this property. |
|
|
PC |
|||
|
The TestID property is only used in Python scripts for PC Collect inspections. A unique TestID number is automatically assigned to each test in the inspection, but you can change this number to a more meaningful name. For more information, see About the TestID property |
|||
You can optionally choose to execute a formula for a Pass/Fail/NA test when certain conditions are met during a running inspection.
For PC Collect inspections, they are added to inspections using the PythonScript property for the Formula test in the Inspection Editor
For GS Collect inspections, they are added using the FormulaMobile property for the Formula test in the Inspection Editor
See the OnChange topic for specifics about conditions that trigger the execution when a Pass/Fail/NA test is used in a sub-inspection with a formula.