You will need to perform a few tasks and meet a few requirements before you can create your first PC Collect and GS Collect inspections with the Inspection Editor
An inspection can be used for inspections on both PC (PC Collect) and mobile (GS Collect) devices or either one. Like other GainSeeker software, you will need an available GainSeeker software seat to use the mobile device for an inspection.
To run an inspection on a PC that was created using GainSeeker's Inspection Editor, you will need GainSeeker Suite version 8.4 or later installed.
If you are running in Windows Tablet mode, see Using the touch keyboard for data entry.
You will need an iPad or iPad Mini running iOS version 5.0 or later.
GainSeeker Mobile Web Service. This is a separate install and purchase in addition to GainSeeker Suite. Contact Hertzler Sales for more information. This is not needed for conducting inspections using PCs. This is only required to run inspections on mobile devices.
The GS Collect application ("GainSeeker Collect app") can be installed on your mobile device at no charge from the App Store (for iOS devices).
Which GainSeeker version is needed? Our team is constantly adding functionality to our inspections. To take advantage of all the latest features, make sure you are using the most recent version of GainSeeker Suite. See www.hertzler.com/gscollect for details.
If you plan to run inspections in offline mode, you will need to separately purchase a GainSeeker Offline Mobile license.
Contact Hertzler Sales for more information.
Does not use a GainSeeker license seat while it is being used in offline mode.
No network connectivity is needed to perform an inspection. Inspections can be uploaded to a database in online mode at a later time.
Because GainSeeker cannot display error messages to the user in real-time when the device is in offline mode, instances of operator error may go unnoticed.
Designate two new traceability labels in your current traceability list for inspection data. These can be fields that are already being used or you can add new fields for this purpose. These traceability fields will prefill when inspection data is submitted, which will allow you to later create Pareto charts and group data by the sub-inspection and individual tests.
Name one traceability field: Sub-inspection. This field will be used to store the sub-inspection names in the inspection.
Name another traceability field: Test. This field will be used to store the test names for the sub-inspections.
The Inspection Editor integrates with your existing GainSeeker system, including any processes, defects, DMS and SPC standards, and traceability items you have already added to your system.
Add any new items to your system for which you want to collect data in the new inspection (optional).
Each inspection can store data for only one process. The exception to this is when you select a process to override the specific defects using the Defects property for the Defects List sub-inspection test.
Each inspection should be associated with a process that has been added to your GainSeeker system. See DMS processes for more information.
You will need to have at least one DMS standard in your GainSeeker system to associate with that process. When you are creating or editing an inspection, you will be asked to pick a DMS standard if you add a DMS Standard to a sub-inspection. See Creating DMS Standards
You will need to have at least one SPC standard in your GainSeeker system before using the Inspection Editor. Creating and editing standards