This topic shows an example of a running inspection on a PC. There are unlimited other combinations for how an inspection might display, depending on how each inspection is designed. For step-by-step instructions about how this inspection was created, see Creating an inspection: Part 1
|
Contents [Hide] |
For instructions on opening the PC Collect module, see Running inspections - PC
The inspector performs these actions on this page of the Inspection Viewer:
The Tubes Inspections is the inspection selected to run in the Inspection viewer on a PC (Fig. 1).
Then, Next is clicked to move the inspector to the next page in the inspection—the page where a Unique ID can be selected for the inspection (Fig. 2). The Unique ID label has been changed to "Serial number" in this example.
See how this was configured for this inspection
The inspector performs these actions on this page of the Inspection Viewer:
To accept the Serial number that is prefilled in the text field, the inspector clicks Next. The inspector is navigated to the page where a sub-inspection can be selected to run. (Fig. 3).
The blue-colored buttons indicate that none of these sub-inspections have been completed.
The inspector performs these actions on this page of the Inspection Viewer:
The Traceability sub-inspection button is clicked. This action navigates the inspector to that sub-inspection page (Fig. 4).
See how this sub-inspection was configured
The inspector performs these actions for the following tests:
Shift (Traceability test). The inspector clicks the drop-down arrow 
to display a list of available shifts, and clicks the 1 SHIFT 1 option.
Machine (Traceability test). The inspector enters the machine number 612 in the text field.
Date/Time (Date/Time test). The current date and time prefilled in the value field—the correct value the inspector is to use in this example. No action is required from the inspector. In this inspection, the inspector does have the option of choosing another date and time. The drop-down arrow in the value field could be used select another date and time for the inspection.
Part Number (DMS Standard test). The part number is prefilled in the value field in this example. No action is required from the inspector.
The inspector clicks the Submit button to submit the sub-inspection data to the database. This action navigates the inspector back to the Pick a Sub-inspection page where the next sub-inspection to run can be selected (Fig 5). Note that the button for the Traceability sub-inspection has changed from blue to green, indicating that this sub-inspection is complete.
For this example, the inspector next clicks the Tube Welds sub-inspection button. This action navigates the inspector the Tube Welds inspection page (Fig. 6).
See how this sub-inspection was configured
The inspector performs these actions for the following tests:
"Enter defect counts for these tests:" (Defects List test). The sample size is prefilled as 1 in the Sample size field. The NCU field can either match the number of defects (as in this example) or there may be multiple defects per unit allowed. In this example, the inspector entered 1 defect for Dirty welds.
The inspector clicks the start button (Timer test) to start the timer counting down from 300 (seconds) to 18 in this example.
The remaining time of 18 seconds is recorded under the Part Number: 7-foot end pressure.
The inspector clicks the Submit button to submit the inspection data to the database. This action navigates the inspector back to the Pick a sub-inspection page (Fig. 7). Note that the Tube Welds sub-inspection button has changed from blue to red, indicating that this sub-inspection, though complete, contains defects or real-time failures.
For this example, the inspector clicks the Tube Checks sub-inspection button. This action navigates the inspector to the Tube Checks inspection page (Fig. 8).
See how this sub-inspection was configured
The inspector performs these actions for the following tests:
Per the instructions in the Text (Text test), the inspector clicks the thumbnail for the Tube diagram to display the item larger in the right-side panel. (In this example, the inspector could also click the other thumbnail to display that item larger.)
Damaged anodizing (Pass/Fail test). The inspector clicks the Pass button when the test passes.
Damaged hardware (Pass/Fail test). The inspector clicks the Fail button when the test fails.
Hinge installed (Pass/Fail test). The inspector clicks the N/A button when the test is not applicable.
The inspector clicks the Submit button to submit the inspection data to the database. This action navigates the inspector back to the Pick a Sub-inspection page (Fig. 9). Note that the Tube Checks sub-inspection button has changed from blue to red, indicating that this sub-inspection contains defects or real-time failures, but it is complete.
After all or some of the sub-inspections have been completed for an inspection, the inspector can (depending on how the inspection is designed and other factors):
Continue running other sub-inspections in the inspection. Note: If data is submitted for sub-inspection "A," for example, and sub-inspection "A" is run again using the same Unique ID, data records for both sessions are maintained. Sub-inspection data submitted for "A" the second time it is run, does not replace or overwrite the data submitted for sub-inspection "A" the first time it is was run.
Rerun the same inspection using the same Unique ID after hitting cancel. This can be helpful for inspections that are run or partially run and then continued later. For example, an assembly is inspected that fails a few important sub-inspection tests. The assembly parts with defects are repaired or replaced and the assembly undergoes those sub-inspections again to determine if the assembly will subsequently pass inspection.
Rerun the same inspection using a new Unique ID after hitting cancel. You would do this when you are ready to inspect the next item.
Click the Cancel button to return to the Pick an Inspection page (Fig. 1) to run a new inspection.
