User-Defined Dispatch Screen Properties

Dispatch Screen properties control the appearance and functionality of the Dispatch screen.

Open Dispatch (Task > Dispatching) to see Dispatch Screen properties.

Dispatch Screen properties are found in File > Properties, on the Dispatch Screen tab.

Table 1. Description of Dispatch Screen Properties
Property	Description
Allow Manually Send Performed Trip	Specifies whether to allow users to manually send a trip that is already performed. This property is typically set to No.
Autorefresh	Specifies whether to automatically refresh the Dispatch screen. If set to No, the system reverts to the autorefresh options set on the Workstation tab. Activating the autorefresh feature may disrupt the viewing of the screens from time to time; to prevent disruption, leave this value set to No. To refresh the screen manually, press F5.
Autorefresh Rate	Rate at which the screen refreshes. For example, if the value is set to `5`, the screen will automatically refresh every 5 minutes.
Dispatch by Run	Specifies whether to show events by run in Dispatch.
Dispatch Unassigned Runs	Specifies whether to show unassigned runs in the Unassigned tab to be dispatched.
Incidents Tab Time Range	Specifies the time range of events with estimated times falling to be shown in the Incidents tab of Dispatch. By default, the time range is set at 1h00, meaning that the Incidents tab shows events with estimated times from the current time up to and including the next hour.
Manual Send Trip has High Priority	Specifies whether users can manually send a trip. If the Autosend feature is enabled, trips are placed in a queue to be sent out. This trip takes precedence over the trips in the Autosend queue.
Manually Perform Trip Remove from MDC	Specifies whether the system can automatically remove trips from a driver’s manifest on the MDC when they are manually marked as Performed from Dispatch.
MDT Send Tolerance (for Due Time)	Specifies how long before an event the MDT server should keep sending a message to the MDT until the tolerance is accepted. For example, if the MDT failed to send the message to the driver, and this tolerance is set to 15, the MDT tries to re-send the message until 15 minutes before the estimated time of the event. If this tolerance is set to -15, it tries to re-send the message until 15 minutes after the estimated time for the event.
Runs Display sort order	For unassigned runs, the order method for runs shown in the filter results area: Run Name Pullout Time
Send PU and DO	Specifies whether users can send pick-up and drop-off incidents to the MDT at the same time. This functionality is only supported by Mentor MDT products.
Show Reordering Incidents	Specifies whether to create an incident when a trip is moved to a different spot on the same run. When set to Yes, this feature tends to create many incidents. Trapeze recommends leaving this property set to No.
Unassigned Tab Time Range	Time range during which all incidents and unassigned trips or events are shown in the Unassigned tab. This time range is the default on the Incidents tab.
Urgent Tolerance	Specifies when to show a Red Flag to the dispatcher as a warning and notification that an incident is nearing the current time so that the driver can take action. Trapeze recommends that this property be set for 1hr.
Vehicle Tab Time Range	Specifies the time range during which all vehicle and run violations are shown in the Vehicle tab. This value is used for the Range From and Range To on the Vehicles tab. If this value is set to 2h, the ranges show two hours in the future and two hours in the past.
Voice mark PU and DO	Specifies whether users can dispatch an incident by voice and mark both the pick-up and drop-off at the same time. As a result, users need not mark the drop-off as a single incident. When an add-on or cancellation is given to a driver, the system must be told that the information was given out. This process is called Marking as sent.