Incidents: Left Grid Columns

Table 1. Description of Columns in the Left Grid in Dispatch
Column	Description
#	(In red) Indicates that the scheduled time for this incident is quickly approaching and should be relayed to the driver as soon as possible. If the field is empty and does not display the # sign, the incident is not considered urgent. This feature is controlled in File > Properties, on the Dispatch Screen tab, by the Urgent Tolerance property. For example, if the property is set at 1 hour, all incidents scheduled to occur less than one hour from the current time are flagged on the Incidents list with a red # sign.
Run	Shows the run on which the event is scheduled. For example, 103.
Sched	Shows the scheduled time for the event. A schedule time is the time scheduled for pick-up. Drop-off events always display a blank field in this column.
Est	Shows the estimated time the event (pick-up or drop-off) is set to occur. All incidents are sorted by the estimated time. For example, if you set the Time Range at 1 hour, the Incidents list shows all incidents with estimated times from the current time up to and including the next hour. If an event has a schedule time of 7:05 and an estimated time of 9:50, then the event is not shown on the Incidents tab until 8:50, and it will be too late to dispatch the incident to the driver. Be sure to monitor your schedule from time to time. For example, a scheduler manually changes the schedule time for an event in Schedule Editor from 7:00 to 10:00 and the current time is 6:30. Because the early/late tolerance is set at 15/15, the estimated time changes to 9:45 (the earliest time the event can be performed). All estimated times for events following this event change accordingly but all events maintain their original schedule times.
Send	Shows a code (DV - By Voice, DM - By MDT, DL - By Log Sheet) that indicates how the event was sent. If there is no indicator in this column, it means that the event has not yet been marked as sent (that is, it has not been given to the driver). When you select an incident and click the Send button, the Send column shows an ellipsis (…) indicating that the system is trying to send the incident by MDT. TS appears when the event has been successfully sent. To view incidents that were previously sent, select the Sent check box, and click Display.
Stat	Shows the status of the event. Common status types include the following: S Scheduled to occur CL Late Cancellation CA Advance Cancellation These codes may be highlighted in different colors in Dispatch and Schedule Editor.
Activity	Shows the activity. If the event is a pull-out, OUT is shown in the column. If the event is a pull-in, IN is shown. For booking events (that is, pick-ups and drop-offs), the client ID number is shown, preceded by a (+) sign indicating a pick-up or a (-) sign indicating a drop-off. Activities such as pull-ins, pull-outs, pick-ups, and drop-offs can be highlighted in different colors for quick and easy identification on the Incidents tab.

#

(In red) Indicates that the scheduled time for this incident is quickly approaching and should be relayed to the driver as soon as possible.

If the field is empty and does not display the # sign, the incident is not considered urgent.

This feature is controlled in File > Properties, on the Dispatch Screen tab, by the Urgent Tolerance property.

For example, if the property is set at 1 hour, all incidents scheduled to occur less than one hour from the current time are flagged on the Incidents list with a red # sign.

Run

Shows the run on which the event is scheduled. For example, 103.

Sched

Shows the scheduled time for the event.

A schedule time is the time scheduled for pick-up. Drop-off events always display a blank field in this column.

Est

Shows the estimated time the event (pick-up or drop-off) is set to occur.

All incidents are sorted by the estimated time. For example, if you set the Time Range at 1 hour, the Incidents list shows all incidents with estimated times from the current time up to and including the next hour. If an event has a schedule time of 7:05 and an estimated time of 9:50, then the event is not shown on the Incidents tab until 8:50, and it will be too late to dispatch the incident to the driver.

Be sure to monitor your schedule from time to time. For example, a scheduler manually changes the schedule time for an event in Schedule Editor from 7:00 to 10:00 and the current time is 6:30. Because the early/late tolerance is set at 15/15, the estimated time changes to 9:45 (the earliest time the event can be performed). All estimated times for events following this event change accordingly but all events maintain their original schedule times.

Send

Shows a code (DV - By Voice, DM - By MDT, DL - By Log Sheet) that indicates how the event was sent.

If there is no indicator in this column, it means that the event has not yet been marked as sent (that is, it has not been given to the driver).

When you select an incident and click the Send button, the Send column shows an ellipsis (…) indicating that the system is trying to send the incident by MDT.

TS appears when the event has been successfully sent.

To view incidents that were previously sent, select the Sent check box, and click Display.

Stat

Shows the status of the event.

Common status types include the following:

S: Scheduled to occur
CL: Late Cancellation
CA: Advance Cancellation

These codes may be highlighted in different colors in Dispatch and Schedule Editor.

Activity

Shows the activity.

If the event is a pull-out, OUT is shown in the column. If the event is a pull-in, IN is shown. For booking events (that is, pick-ups and drop-offs), the client ID number is shown, preceded by a (+) sign indicating a pick-up or a (-) sign indicating a drop-off.

Activities such as pull-ins, pull-outs, pick-ups, and drop-offs can be highlighted in different colors for quick and easy identification on the Incidents tab.