Purpose
This procedure describes how to use the SPOTTYPE data element in a flow map to allow initial selection of a child spot type prior to selecting defect codes and other info associated with the child spot type in the inspection data collection flow.
The target audience is experienced administrators knowledgeable about base tables and checksheet setup.
Background
Previously, check items were associated to a single spot type giving a single list of defect codes. In complex inspection scenarios this can lead to either a proliferation of check items referencing relatively short defect code lists, or very long defect code lists. Either can decrease the validity of gathered data as inspectors have to hunt either for the right check item in a list or a long list of defect codes. Essentially what is needed is a two-level defect hierarchy.
The SPOTTYPE Flow Map data element allows you to define a check item that first selects from among several different child spot types. After the initial selection, the operation proceeds to the selected spot type, allowing collection of associated defect codes and any additional flow-based data (e.g. cause, responsible, part). This process is more natural in the flow of collecting defect data and allows for both smaller checksheets and shorter more easily understood selection lists at each point along the inspection flow.
Procedure
Overview
There are two preparation steps required to use the SPOTTTYPE data element, completed using the Base Table management utility
- Define a new spot type- using the SPOTTYPE data element in the flow map column
- Add defect codes to the new spot type that reference existing spot types - each defect code for the new spot type must reference an existing spot type in both the defect_code and child_spot_type columns
When these two preparation steps are complete:
3. Assign check items to use the new spot type- using eCS Builder or Model Management
Detail
1. Define a new spot type - using the SPOTTYPE data element as part of the flow map
The SPOTTYPE data element needed in the flow map column to use this feature has this form:
[{data: "SPOTTYPE", label: "Label Text Here", required: "REQUIRED"}]
To create a new spot type using the feature, follow these steps:
- Using Base Table Explorer, create a new record with the new spot type name, say e.g.MULTISPOT.
- Copy the text from above and update the highlighted "Label Text Here" to the FLOW_MAP field
- This label text will be the heading displayed by the defect data collection flow when the user initially clicks the X to fail a check item assigned the new spot type.
- Set other fields as needed, based on your other plant spot type setting
- Save the new record
Example: New SPOT TYPE record with the required flow map setting:
2. Add defect codes to the new spot type that reference existing spot types
After adding the required Spot Type table record above, you'll need to add Defect Code table records referencing the new spot type, each specifying a child spot type you want displayed when using this new spot type.
To finish setting up to use this the feature by adding defect code records using Base Table Explorer, follow these steps
- Create new defect code records, selecting the new spot type name in the spot type field
- The Defect Code and Child Spot Type fields must reference an existing spot type that will be displayed in a list, similar to how defect codes will be displayed after a spot type is selected.
- Set other fields as needed (e.g Defect Code Desc, which will be displayed to the inspector)
- Add as many such records as needed - one per spot type to be available for selection.
- NOTE: ONLY RECORDS REFERENCING A VALID SPOT TYPE CAN BE ADDED TO SPOT TYPES THAT USE THE SPOTTYPE flow type data element
- In other words, you can't mix and match - with some defect codes referencing a spot type and others simply being a defect code without an associated spot type.
Example: New defect code records with required references to existing child spot types:
Assign check items to use the new spot type
After completing the defect code setup, all that remains is to assign the new spot type to an eCheckitem. This can be done using either Model Management or the eCS Builder (based on how the parent eCS is managed) and using the eCI Edit Frame to set the Spot Type to the newly created spot type, as shown below for an eCheckitem "Multi Spot Selector", assigned spot type MULTISPOT from the previous steps.