Add a Rating test to a sub-inspection when you want the inspector to rate a particular metric on a scale such as 1 to 5. This type of scale-based metric is also known as a Likert scale. A Rating test can be stored as variable SPC data, attribute DMS (defect) data, or both.
This test is only available for PC Collect data entry.
It is not available for iPad data entry on the GS Collect app.
Circumstances in which you may want to add a Rating test to a sub-inspection:
Rating a metric on a scale where both ends are unacceptable
and the middle is the desired result.
For example: the inspector must rate the saltiness of snack foods on
a scale of 1 - 5, where 1 = "Salt Missing", 2 = "Somewhat
Salty", 3 = "Perfectly Salted", 4 = "Somewhat
Over-Salted", and 5 = "Too Salty To Eat".
Rating a metric on a scale where one end of the scale is unacceptable
and the other end of the scale is the desired result.
For example: the inspector must audit the implementation of an employee
training program on a scale of 0 - 4, where 0 = "unaware of need
for training", 1 = "knows about training but not started",
2 = "started training but not finished", 3 = "finished
training but did not pass test", and 4 = "finished training
and passed test".
You may want to use the N/A ("not applicable") option for a Rating test if you use the same inspection for similar parts that do not all require this particular test. For example, you might use the same inspection for different kinds of snack foods. When inspecting a fruity or sweet snack food which does not require a score for saltiness, the inspector could select N/A for this Rating test.
|
Contents [Hide] |
Click the Rating test toolbar button to add
this test to the sub-inspection.
When prompted, enter a Label that will be displayed above this test during data entry.
Set any properties for this test on the Properties panel that displays after the test is added.
For information about using the Properties panel, see Changing property settings
Property |
Default setting or default display |
Allows |
APPEARANCE |
||
Label |
[blank] |
The label or instructions displayed for this test during data entry. |
All On First Row - All buttons are displayed on one row. |
You can display the buttons on two rows. Select which button should begin the second row. For an example of a Rating test with buttons on two rows, see Performing Rating tests. |
|
BEHAVIOR |
||
ButtonSettings |
1: , 2: , 3: , 4: , 5: (or similar).
The default labels for buttons from Minimum to Maximum (see below). By default, no DMS defects are assigned to any buttons, and all buttons use default colors. |
You can change the button labels, assign a DMS defect to any button, and set the color for each button. For details, see Setting the ButtonSettings property. You can double-click on the Rating test to edit this property. |
5 - The maximum rating value. |
Choose a Maximum rating value from 1-9. It must be greater than the Minimum rating value (below). |
|
1 - The minimum rating value. |
Choose a Minimum rating value from 0-8. It must be less than the Maximum rating value (above). |
|
False. When storing DMS data for this test, the NCU (nonconforming units) field is always set to 0 and the Number Good field is always set equal to the SampleSize property (below). Note: When the configuration setting Set nonconforming units = number of defects is enabled, the data looks as if this property were set to True. |
True. When storing DMS data for this test, if the inspector selects a button with a defect, the NCU field is set to 1 and the Number Good field is set to (SampleSize - 1). If the SampleSize property is 0, then NCU and Number Good will also be 0.
If the inspector selects the N/A button, the data record has Sample Size = 0, NCU = 0, and Number Good = 0 - regardless of this property. |
|
False. Does not display the N/A ("not applicable") button for this test. |
True displays an N/A button after the Maximum button.
If the inspector selects the N/A
button: |
|
DATA |
||
DMS - This Rating test will be stored as a DMS data record. You must set the TraceField property (below) for this test to function correctly. When the inspector selects a rating button for this test and submits the sub-inspection, that button's label will be stored in the traceability field set by the TraceField property. This test will be affected by the Inspection property StoreAll. |
SPC
- This Rating test will be stored as an SPC data record. You must
set the StandardSPC
property (below) for this test to function correctly. When the
inspector selects a rating button for this test and submits the
sub-inspection, that button's numeric value will be stored in
the first data field (Data 1) of that SPC data record. If the
TraceField property
(below) is set, the selected rating button's label will be stored
in that field. Both - This Rating test will be stored as a DMS record and an SPC record. You must set both the TraceField property (below) and the StandardSPC property (below) for this test to function correctly. This test will be affected by the Inspection property StoreAll. DoNotStore - No data records will be stored for this test. (Typically used in conjunction with a Formula test that runs a Python script.) |
|
[blank] - When storing DMS data for this test, the Sample Size for the DMS data record will be 1. |
Enter a different sample size for the DMS data record. Typical values are 0 or 1. If the inspector selects a button that sets a defect, the defect count will be 1 - regardless of this property.
If the inspector selects the N/A button, the data record has Sample Size = 0, NCU = 0, and Number Good = 0 - regardless of this property. |
|
[blank] |
Select an SPC standard for which to store a data record for this Rating test. Required if the DataStorage property (above) is set to SPC or Both. Short Run process specifications are not available for this property. |
|
[blank] |
Select a traceability field which in which to store the label of the button selected by the inspector. Required if the DataStorage property (above) is set to DMS or Both. |
|
PC |
||
|
[PC only] |
Use Sub-Inspection Settings. Apply the settings from the sub-inspection ForceNote property to this test. |
Click the ForceNote
property and then click the |
TestID [PC only] |
A unique TestID number is automatically assigned to each test in the inspection, but you can change this number to a more meaningful name. The TestID property is only used in Python scripts for PC Collect inspections. For more information, see About the TestID property |
Enter a name for the TestID. |
|
[PC only] |
[blank] |
You can specify one or more traceability values that will be applied only to this test on this sub-inspection. These values will not be displayed to the inspector during data entry. If you want to store this test's TestID property as a traceability value, enter [testid] . Any traceability values you set here will override values set by Traceability tests, Inspection properties, Planned Inspection traceability values, etc. |
Regular. Test is full-sized. |
Short. Helps you to fit more tests on the screen. Test may be shorter, and white space above and below this test may be reduced. |
|
By default:
No DMS defects are assigned to any buttons.
All buttons use the default colors - Plum for regular buttons and MediumSlateBlue for the "N/A" button.
All buttons use the default labels (1: , 2: , etc. - based on the Maximum and Minimum settings for this test).
You can change the label, color, and/or defect for any button.
You can configure different buttons with different settings - colors, defects (including not having a defect assigned), etc.
To configure the buttons, double-click the Ratings test, or use the ButtonSettings property to open the window shown above. Then:
Click any button you want to change.
Label - To change the button label, click in the Label box and enter the desired text. You can also remove the default label (1: , 2: , etc.).
The label cannot be left blank. If you clear the label, GainSeeker will reset it to its default value (1: , 2: , etc.).
GainSeeker will automatically resize the font as needed to make your text fit on the button. For a new line, press Ctrl+Enter.
Button labels can only display text. To display pictures that relate to these buttons, use the Image test or URL/HTML/File test for the sub-inspection.
Color - To change the button color, click the button for Selected Color and choose a different color.
To copy this color to all the other buttons, click Set Color for All.
To revert the selected button to the default color, press the Ctrl key while clicking click the button for Selected Color.
Defect - To set a DMS defect for the button, click the button for Defect and choose a defect.
To remove the defect, press the Ctrl key while clicking click the button for Defect.
Repeat these steps for another button, or click OK to finish.
Use Sub-Inspection Settings
Apply the settings from the sub-inspection ForceNote property to this test.
Set for this test (override Sub-Inspection settings)
Force Note
If this setting is checked:
The inspector is required to enter a note when this test has a defect. Required notes can be entered from either the Sub-inspection Note (bottom of the page) or the test's Individual Note (next to the test).
When the sub-inspection properties NoteVisible and ShowIndividualNote are set to False, the inspector is prompted to enter a note when the Submit (sub-inspection data) button is pressed.
If this setting is cleared:
The presence of a defect does not require the inspector to enter a note.
The
sub-inspection
ForceNote property and the presence of a Traceability
test for DMS Event
determine whether the presence of a defect will require the inspector
to enter a value for this test.
Force Event
If this setting is checked, the presence of a defect requires the inspector to use the test's Individual Note (next to the test) to enter a DMS Event. Or, if the sub-inspection properties ShowIndividualNote and NoteVisible are both set to False, then the inspector is prompted to enter the Event after the Submit (sub-inspection data) button is pressed.
If this setting
is checked, the sub-inspection properties NoteVisible
and ShowIndividualNote
must obey the following:
If NoteVisible is True, then ShowIndividualNote must also be True.
If ShowIndividualNote is False, then NoteVisible must also be False.
You can optionally choose to execute a formula for a Rating test when certain conditions are met during a running inspection.
For PC Collect inspections, they are added to inspections using the PythonScript property for the Formula test in the Inspection Editor.
See the OnChange topic for specifics about conditions that trigger the execution when a Rating test is used in a sub-inspection with a formula.
button to choose
a combination of options on the