Manifest Tab

Set the target number of trips that the mobile computer should display. Local conditions including the number of vehicles, service area, and radio saturation levels usually determine this number.

The recommended level is at 6 to 8. This number provides the driver with a sufficient number of trips, while limiting radio traffic, especially at the start of a shift.

Locations with fewer than 20 vehicles may want to increase this number as high as 10, if your mobile computers support it.

Capacity:Critical (Set this is property depending on your mobile computer vendor’s requirements. Some mobile computers can only display a certain number of events.)

Set the number of events send out to a mobile computer.

If the Capacity is set at 10 and the Critical Capacity is set at 20, the MDT Server does not send more than 20 events to the mobile computer.

The reason that the Capacity can be overridden is due to the possibility of a dispatcher sending last minute additions to a driver’s manifest, which override the original capacity limit of 10. Another situation where the capacity is overridden is for a group trip.

Capacity: Supervisory

The recommended setting is 100 (default).

This property relies heavily on the type of communication system in use. If using a radio system, which is robust such as a full-duplex system, this property can be set to 1.

A pending message basically consists of an event message that the MDT Server is attempting to send out to the mobile computer but an ACK or NAK has not yet been received.

Ignore Pending Messages

(This property is specific to a mobile computer vendor.)

If set to Yes, the MDT Server does not wait for an ACK before sending another trip message resulting in messages sent out in bursts.

If set to No, the MDT Server sends the messages one at a time. It waits for an ACK before sending the next message to a vehicle.

This property works in conjunction with the Ignore Pending Messages property.

If the Ignore Pending Messages property is set to No, the messages are sent one at a time.

If the Ignore Pending Messages property is set to Yes, you must set times in the Ignore Pending Schedule property. Then, the messages are sent as a burst within the defined period of time. If no From Time and To Time values are set, then the messages are not sent as a burst.

This property tells the MDT Server the time range from the current time to send inserted trips.

For example: a vehicle logs in at 5:00 A.M. and receives the first six trips: 5:20, 5:30, 6:00, 6:25, 7:00, and 7:30 A.M. The dispatcher manually sends a 10:00 trip by accident. The trips between 7:30 and 10:00 become Inserts because they are unsent trips between two DM events. If the Insertion Time Tolerance property is set to 1h00 and the current time is 5:30 A.M., the trips between 7:30 and 10:00 are not sent because the Insertion Time Tolerance is 5:30 to 6:30 A.M.

The screen represents the inserts with three dots (...). This can look confusing to the dispatcher, who sees a series of DMs followed by …, and then more DMs on the Dispatch screen. The … events are not sent out until the time of the event falls within the Insertion Time Tolerance window.

The trip is sent before the driver’s estimated pull-in time towards the end of the day.

If set to No, only the data on unperformed trips is sent to the supervisor.