Running Inspections on a PC

To open and run an inspection on a PC, you must have already published at least one inspection for use on a PC. See Publishing your inspection for more information.

If you are running in Windows Tablet mode, see Using the touch keyboard for data entry.

1. Open the PC Collect module

You can open the PC Collect module from the:

• LaunchPad module

• .Launch module

• Power Tools menu in the SPC Data Entry, SPC Planner, and SPC Designer modules

You can also create a shortcut to launch any GainSeeker module from your desktop or Start menu.

These options will only be available if you log in as a User whose Role has Module Access rights to the PC Collect module.

Other methods for opening and running a PC Collect Inspection

• Using parameters to open a PC Collect inspection

• Using the click action on a Button dashboard control

2. Pick an inspection to run

The PC Collect module main window is where running an inspection begins.

When you launch the PC Collect module, the Inspection Viewer window or the Script Selector window may be automatically displayed. You can change this default behavior by closing the displayed window and then choosing an option from the Startup menu.

When all windows have been closed, you can work with buttons and menu options on the PC Collect module main window.

Click the Start Inspection button on the PC Collect module window to open the Inspection Viewer.

Inspections you can run display on the Pick an Inspection page in the Inspection Viewer.

• Click an inspection name to select it. Then, click Next to proceed to the next inspection page. The Next or Submit buttons used on Inspection Viewer pages help move you through the inspection process.

3. Click the label for a Unique ID in the list or enter a new Unique ID

• Enter a new Unique ID for this inspection or pick an existing one in the list. Depending on how an inspection was designed, this screen may not display.

4. Choose a sub-inspection to run

• Click a sub-inspection to open and run it.

A sub-inspection is a page that contains tests to be performed for a specific segment of the inspection. Every inspection contains at least one sub-inspection.

Depending on how the auto AutoAdvance property is set for the inspection you are running, you should:

• Click a sub-inspection to run from the list, You should select the Traceability sub-inspection (if there is one) to run first, followed by other inspections). The Traceability sub-inspection uses basic information you supply for the inspection that might include your name, shift, and department, for example.

• Or, the sub-inspection to perform next will be highlighted in the list of available sub-inspections

• Or, you will be automatically advanced through the sub-inspections in the order intended by the person who designed the inspection.

5. Perform the tests in each sub-inspection

• Perform all required tests in a sub-inspection.

Every sub-inspection will have at least one task to perform. This might include selecting a checkbox to confirm you have completed a task, for example, or clicking a Pass or Fail button when the inspected item passes or fails the criteria set for the test.

• See the topic Performing sub-inspection tests for information about how to complete each test type.

6. Submitting data and information for each sub-inspection

After you have completed all the tests on a sub-inspection page (not all of the tests may require completion), you need to submit the information to the database where it will be stored.

To submit all the data and information for that sub-inspection:

• Click the Submit button located at the bottom of each sub-inspection page.

Note: Your inspection may also include a Cancel button, depending on how the inspection has been designed. When you click the Cancel button, data and information for that sub-inspection is not saved to the database. When you click the Cancel button, in most cases, you will automatically be returned to the page where you can select a sub-inspection to run.

Using the features buttons on the sub-inspection pages

Each sub-inspection page may display buttons for additional features that you can use. Whether these buttons display depends on how the inspection has been set up by the inspection designer. For example, your sub-inspections may feature one or more Notes buttons that allow (or in some cases, require) you to include a note when a test for that sub-inspection fails.

For information about all the features buttons, see the topic Using sub-inspection features

This is an example of some of the features buttons that may be included on a sub-inspection page, depending on how your inspection has been designed:

Related topics

• See an example of a running inspection on a PC

• Differences in PC and Mobile Inspections

• Creating and Editing inspections