GainSeeker Inspections module

 

Contents  [Hide]

  

Introducing the GainSeeker Inspections module

You will use the GainSeeker Inspections module to customize data entry routines, which may include:

Inspections

Standalone data entry routines for collecting SPC data and DMS data via the PC Collect module (on PCs) and the legacy GS Collect app (on iPads), with a similar interface on both devices. You can also use an inspection to note that a check or task was performed, even if no measurements or defects need to be stored.

For example, you might create an inspection for the hourly checks that inspectors currently perform on a certain type of product at a particular process.

You can easily customize these data entry routines using a basic builder interface, with no programming needed. However, some basic programming allows you to further customize and extend the functionality of these inspections by integrating Python™ scripts (for PCs) or LiveCode scripts (for iPads).

Planned
Inspections

A Planned Inspection overlays an Inspection with a different set of Part Numbers, Processes, Traceability, and/or display files (such as images and instructions).

This allows you to create one Inspection for a type of product, and then create multiple Planned Inspections that are based on that Inspection - each for a different part number.

Planned Inspection data entry is performed via the PC Collect module (on PCs) and the GS Collect app (on iPads).

Python scripts

These are Python™ scripts that are always run on PCs. They can be used to enter data into GainSeeker - or perform other functions - with or without an Inspection.

These Python scripts can be executed in one of these ways:

  • using the PC Collect module to run an Inspection that is configured to execute a script

  • launched as a standalone script via GS Console or the PC Collect module

    • this includes dashboards that launch PC Collect to run a Python script - using the dashboard PythonRunBefore property, Button control ClickAction property, or DateTime control OverdueAction property

  • launched as a re-usable block of code from within another Python script (by executing the misc.executescript command)

Launching this module

You can open the GainSeeker Inspections module from the:

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 GainSeeker Inspections module.

Using the Main Window

When you launch the GainSeeker Inspections module, the Manage Inspections window, Manage Planned Inspections window, or Script Editor 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 GainSeeker Inspections main window:

  1. When all windows have been closed, the status bar at the bottom of the main window displays the name of the currently logged-in user.

Using the menu

The GainSeeker Inspections module window features four menus: File, Startup, Setup, and Help.

File menu

Command:

More information:

Manage Inspections

Using the Manage Inspections window

Manage Planned Inspections

Planned Inspections

Manage Python

Edit standalone Python scripts

Setup File Import

Use the File Import Wizard to set up direct data import from a file.

Login

Log in as a different user without exiting the GainSeeker Inspections module.

Change Configuration

Change to a different GainSeeker configuration but keep the permissions (role) of the current user or group name.

Change Password

Change the password for the currently logged-in user.

Exit

Close the GainSeeker Inspections module

Startup menu

You can choose which window (if any) to open by default when you launch the GainSeeker Inspections module on this computer:

Setup menu

Help menu

See Help menu