Basic Info |
The Basic Info tab enables you to define symptoms and associate tasks with them for use on work orders. You can also specify a severity level (useful for external interfaces) and a default priority ID. If the symptom code BRAKES NOT WORKING has a default priority of 1, for example, all new service requests with that symptom code have a priority of 1.
To limit the display of information in the grid and maximize performance, use the filter. You can sort on symptom, severity comment, default shop location ID, default priority ID, work management classification, asset category ID, and reporting source ID. Filtering on reporting source and asset category, for example, may provide the most appropriate list of possible symptoms for a particular situation.
Tip: There is no standard list of symptoms.
The top section of the Basic Info tab displays the symptom currently selected in the grid or that you are defining.
Symptom
Identifier of the symptom. This field has a list box. Each symptom must be unique. The maximum field length is 20 characters. This field is required. If the symptom already exists, its name displays in the unlabeled field to the right.
Data in the fields in the bottom section of this tab define additional information about the symptom. Unless otherwise indicated, these fields are optional.
Name
Name of the symptom.
Description
Description of the symptom. If a description already exists, it displays in the unlabeled field to the right of the Symptom field.
Note: This description displays in symptom choice lists and on screens that reference symptoms.
Severity
The severity fields are useful in external interfaces that record service requests.
Comment
Text field in which you can enter comments regarding the severity rank. Maximum field length is 30 characters. This field is optional.
Tip: You can add a custom list to this field if you would like to drive the values that can be entered.
Rank
Numerical rank associated with the severity of the symptom. Defaults to 0. You can enter whatever value has significance for you, but it must be a positive number. Multiple symptoms may have the same ranking. This field is optional.
The Supported tasks screen group enables you to associate task IDs with symptoms.
Delete: If this field has a check, the entire row is deleted when you click Save.
Task ID: Identifier of the task. This field has a list box. Task IDs are defined on the Data -> Shop Activity -> Setup -> Tasks -> Primary Information screen.
Tip: The task ID choice list on the Tasks tab of the Data -> Shop Activity -> Work Order Center screen is limited to those tasks associated with the specified symptom.
Task description: Description of the task. This field is display only.
Default shop location ID
Identifier of the default shop location for service requests created for the symptom. This field has a list box. The location description displays to the right of the ID. This field is optional.
You may want to specify a default location if your operation is relatively localized and you have specialized shops for different types of subcomponents or issues. For example, if you have a tire shop that only does tire maintenance, service requests for tire-related issues can be routed directly to the tire shop regardless of the equipment unit's assigned repair location.
Work management classification
Identifier of the work management classification. This field has a list box. The classification description displays to the right of the ID.
Work management classifications are defined on the Data -> Shop Activity -> Setup -> Work Management Classification screen.
Default priority ID
Identifier of the default priority. This field has a list box limited to priorities with a Work orders/shop priority function. The priority description displays to the right of the ID.
When a service request with a symptom is added, the following hierarchy is used to determine the default priority ID:
Task and equipment asset category (DES_ACAT) (applies to service requests based on task rather than symptom)
Task (DES_MAIN) (applies to service requests based on task rather than symptom)
Symptom and equipment asset category (SYMP_ACAT)
Symptom (SYMP_MAIN)
Equipment (EQ_MAIN)
The first value found is the one that is used. If both task and symptom are present, task takes priority. For multi-unit projects: if the project has a priority code, that takes precedence over the aforementioned hierarchy.
Priority IDs and their functions are defined on the Data -> Shop Activity -> Setup -> Priority Codes screen.
Default restriction type ID
This setting is used for creating restrictions. This field has a list box. Select a Restriction type ID and click Save to associate it with the symptom. Restriction type must be defined in the system.
External identifier
The external identifier associated with the symptom. The system uses this code to look up a symptom when creating a service request. This data may be used in interfaces or for reporting. The maximum field length is 100 characters.
Supports service request or incident with no asset
If checked this symptom will support service requests or incidents with no associated asset. A service request symptom will not validate the symptom "Enforce asset category restriction for this symptom" when this setting is also enabled and there is no asset on the service request.