Creating an inspection: Part 2

This is the second of two topics that detail steps for creating an inspection that can be used on PCs or mobile devices. See Creating an inspection: Part 1 for initial steps for creating the inspection before the Inspection Editor opens.

For a more general overview about how inspections are created, see Overview: Creating Inspections

The Inspection Editor

Launching the Inspection Editor

Steps after the Inspection Editor opens

First, set the properties for the overall inspection using the Properties panel of the Inspection Editor.

These properties include determining how the completed overall inspection displays and performs when it is run on a PC or mobile device. Notice that some properties are specific to PC or mobile devices. For a complete list of available properties for each inspection type, see the topic: Tests

• The StoreAll property for this inspection is set to False. This only stores data that fails any of the tests. It does not store data without defects. (Hint: Storing data of both types can tell you whether a test is being performed.)

• The UseRed property is set to True. This changes the color of the button for this sub-inspection to red when defects were present when data was last submitted for the sub-inspection. GainSeeker uses sub-inspection button color coding to help you quickly see the completion status of a sub-inspection.

• The text "Serial number" is entered in the IDLabel property. This is the display label for the Unique ID field for individual inspections that are run.

Set any properties you want to change for the sub-inspection you named "Traceability."

• The PictureMode property is set to Off for the Traceability sub-inspection. For a mobile device inspection, this disallows the inspector from taking any photos on this sub-inspection page. For a PC inspection, this disallows the inspector from attaching photos to the data for this sub-inspection. (Taking photos while the operator is on the Traceability page is deemed irrelevant to the inspection process, at least for this example.)

Add tests to the Traceability sub-inspection.

These tests are added to the sub-inspection:

• Four Traceability tests (one for each of these traceabilities: Shift, Department, Machine, and Temperature)

• One Date/Time test

• One DMS Standard test

4. Add four Traceability tests to the Traceability sub-inspection.

5. Change any properties for the tests.

The first Traceability test (see image below), the Traceability property is set to Shift. This is the label for the field where the data for this test is stored.

The EntryRequired property is set to True. This requires the operator to submit a value.

The EntryRestricted property is also set to True. This requires the operator to select the information to submit from a defined list (Shift 1, Shift 2, . . . , for example).

• For the second test, the Traceability property is set to Department. The EntryRequired property is set to True. The EntryRestricted property is also set to True. This requires the operator to select the information to submit from a defined list.

• For the third test, the Traceability property is set to Machine. The EntryRequired property is set to True.

• For the fourth test, the Traceability property is set to Temperature.

6. Add a Date/Time test to the Traceability sub-inspection.

No property settings need to be changed since we want to use the default setting Date/Time as the display label.

7. Add a DMS Standard to the Traceability sub-inspection.

The part number 7-foot steel is selected for the DMSStandard property. This is the part number under which all data is stored for the TUBES process.

Add a "Tube Welds" sub-inspection to the inspection

1. Add a new sub-inspection to the inspection. Make any property changes to the sub-inspection properties as needed. No changes are made for this example.

The sub-inspection is named Tube welds.

2. Add one or more tests to the Tube welds sub-inspection.

The following tests are added to the Tube welds sub-inspection:

• Defect List

• Line Break

• Text/Message

• Timer

• Numeric Input test

3. Add the Defects List test to the Tube welds sub-inspection.

4. Change any properties for the test.

1. • The text "Enter defect counts for these tests:" is entered in the Label property. This is the display label for the test.

   • Defects to associate with the test are selected for the Defects List property: Bad welds,Dirty welds,Leaks detected

   • The text 1 is entered for the SampleSize property.

5. Add a Line Break to the Tube welds sub-inspection. The line break has no property settings. It serves as a visual divider between tests on a mobile device page.

6. Add a Text test to the Tube welds sub-inspection.

• "Test pressure of welds by filling with air for 5 minutes using the Timer. Record the remaining time in the Part Number field below." is entered for the Label property.

7. Add a Timer test to the Tube welds sub-inspection. Set the properties for the test.

• Text for the Label property is entered: "Pressure Test".

• The TimerSeconds property is set to 300 seconds.

9. Add a Numeric Input test

• "End pressure test" is entered for the Label property for the test.

• The SPC standard 7-foot end pressure is selected for the SingleSPCStandard property.

Add a "Tube checks" inspection to the sub-inspection

1. Add a new sub-inspection to the inspection.

The sub-inspection is named Tube checks.

2. Add one or more tests to the Tube checks sub-inspection.

The following tests are added to the Tube checks sub-inspection:

• Text/Message

• Image

• URL/HTML/File

• Three Pass/Fail tests (one each for damaged anodizing, damaged hardware, and hinge installed)

3. Add a Text/Message test to the Tube checks sub-inspection.

• The text "PC inspections: Click the thumbnail to view diagram. Mobile inspections: Clink the link." is entered in the Label property field.

4. Add an Image  to the Tube checks sub-inspection.

The CenterImage property is selected for the positioning of the image. The full file path for the image is entered as the property.

5. Add a URL/HTML/File to the Tube checks sub-inspection.

• The text "Tube diagram" is entered for the Link/ThumbnailText property. This is the label for the link the inspector clicks to display the file in a mobile inspection, and the label for the thumbnail image in PC inspections.

• The file path for the diagram is entered in the URL/contents property.

6. Add the first Pass/Fail test to the Tube checks sub-inspection.

:

For the first Pass/Fail test:

1. • Damaged anodizing is selected for the DefectName property. This is the defect that is associated with this test.

   

For the second Pass/Fail test:

1. • Damaged hardware is selected for the DefectName property. This is the defect that is associated with this test.

For the third Pass/Fail test:

1. • Hinge installed is selected for the DefectName property. This is the defect that is associated with this test.

   • The ShowNotApplicable property is set to True. This displays an NA ("Not applicable") button on the sub-inspection page in addition to True and False buttons.

Save and publish the inspection to a Mobile Device and/or PC

Before you can run your inspection, you must save and publish it.

• For more information, see Publishing your inspection

If you create an inspection to run on a mobile device and at some point you want to create a similar inspection for use on a PC, you can copy your mobile device inspection and then make changes to tailor it to a PC. See using the Copy... button on the Manage Inspections dialog for more information.

See How this inspection displays on a Mobile Device and PC

• Mobile device inspection example display

• PC device inspection example display