Basic Info |
The Basic Info tab enables you to record and modify high-level information about an incident. It also lets you associate child incidents with the parent incident.
Note: If an incident is closed, it cannot be modified. You must change the status to something other than CLOSED before you can modify the data.
Delay incidents entered for trips that have been signed off by the dispatcher may be modified only by users that belong to a user group that has been granted the right to update signed-off trips and delays. This special right is granted on the Special Rights tab of the System Mgmt -> Setup -> Access Rights -> User Groups screen.
Tip: To limit the display of information in the grid and maximize performance, use the filter. You can sort on incident ID, status, symptom, responsibility, a range of occurred dates and reported dates, trip ID, and delay type, among other values.
The fields in the top section of the Basic Info tab display the incident ID and the name of the user who recorded the incident. These fields auto-populate and cannot be modified.
Incident ID
Numeric identification code for the incident.
Entered by
Identification code of the user who initially entered the incident. The user's name displays in the unlabeled field to the right.
The fields in the bottom section of the tab enable you to provide high-level information about the incident. Unless otherwise indicated, these fields are required.
Status
The status of the incident. This field has a predefined list of statuses:
REPORTED -- default
FOLLOW UP REQUIRED
UNDER INVESTIGATION
CLOSED
VOID
Incident category
The category of the incident.
Weather
The weather conditions at the time of the incident. Optional. This field has a list box:
CLEAR
CLOUDY
FOG
HAIL
ICE
RAIN
SLEET
SNOW
WINDY
Weather conditions for use on incident management screens are defined on the Data -> Incident Management -> Setup -> Weather screen.
Temperature
The temperature at the time of the incident. This field is optional.
Service impacted
If this field has a check, service was affected.
Offload required
If this field has a check, the passengers were offloaded.
Responsibility
Entity responsible for causing the incident. This field is optional. This field has a list box:
MECHANICAL
ENGINEERING
TRANSPORTATION
OPERATIONS SUPPORT
TRACK
COMM/SIGNALS
REVENUE
AMTRAK
CONTRACTOR
WEATHER
UNDER REVIEW
OTHER
Entities that might be responsible for causing incidents are defined on the Data -> Incident Management -> Setup -> Responsibility Types screen.
Symptom
Main symptom exhibited by the equipment involved in the incident. This field is optional. This field has a list box. Symptoms are defined on the Basic Info tab of the Data -> Shop Activity -> Setup -> Symptoms screen.
Date and time occurred
Date and time the incident occurred. The field defaults to either the actual departure date and time, if available, or the scheduled departure date and time. You can change the value. If the date and time occurred are changed, the trip ID is also updated.
Note: The date and time occurred may predate the trip's scheduled start date and time. Events may occur before a trip begins and cause a delay.
Date and time reported
Date and time the incident was reported. The field defaults to the current date and time, but you can change it.
Date and time closed
Date and time the incident was closed. The field defaults to the current date and time when you select the status CLOSED.
Operator
Identifier of the operator responsible for the equipment at the time of the incident. This field is optional. This field has a list box, which includes both employees and operators. If defined, the person's name displays in the unlabeled field to the right.
Reported by
Identifier of the person who reported the incident. You may enter either an employee ID or operator ID. This field is optional. This field has a list box. If defined, the person's name displays in the unlabeled field to the right.
Inspector employee ID
Identifier of the person who determined the importance of the incident. This field is optional. This field has a list box. If defined, the person's name displays in the unlabeled field to the right.
Note: The specified employee must be active. The employee does NOT need to be a qualified person or qualified mechanical person, however.
Tip: When you open a service request from the incident, the inspector employee ID is listed in the Imposed by employee field on the Operating Restrictions tab of the Data -> Equipment Activity -> Service Requests/Defects screen.
Equipment ID
Identifier of the equipment involved in the incident. Optional. This field has a list box. If defined, the equipment name displays in the unlabeled field below the Equipment ID field.
Consist ID
(Only applies to rail operations) Identifier of the consist involved in the incident. This field is optional. This field has a list box. If defined, the consist description displays in the unlabeled field below the Consist field.
Priority
Incident's priority. This field is optional. This field has a list box:
ASAP
URGENT
EMERGENCY
Incident priorities are defined on the Data -> Incident Management -> Setup -> Priorities screen.
Parent incident ID
If this incident is associated with an existing parent incident, you can specify the parent incident ID in this field. This field has a zoom button. Child incidents are listed on the Related Incidents tab of the Data -> Incident Management -> Incident Management screen for the parent incident.
Responsible location ID
This field is populated with the user's session location when inserting a new record.