| Anchor |
|---|
top | top | The X Route dispatch The Route Dispatch board is used to dispatch routes to drivers and to monitor driver's route activity. It consists of two summary grids:
Active Routes Grid: Routes are assigned to drivers, and driver, stops, and parcels are monitored.
Active Drivers Grid: Driver's on-demand orders are monitored from this grid when in X Route.
Other important detail screens are:
Route Manifest: Double click on a route in the Active Route grid. Displays selected route's stops with related parcel and other information. See
X Route - Dispatch - Route Manifest.
Parcels: Right click on a route in the Active Route grid and select "View Parcels...". Displays selected stop's parcel information. See Parcel Manifest.
Driver Active Work: Double click on a driver in the Active Driver grid. Displays orders and routes currently assigned to the driver. See Driver Active Work.
To get to the X Route dispatch board, go to X Route > Dispatch.
Image RemovedTo get to the Route Dispatch board, go to X Route > Dispatch.
...
| Anchor |
|---|
| ActiveRoutesWindow |
|---|
| ActiveRoutesWindow |
|---|
|
Active Routes GridThe Active Routes grid is where routes are assigned and drivers, stops, and parcels are monitored.
Image Removed
...
Field Name | Description |
|---|
DriverID | Driver ID of driver assigned to the route. A blank DriverID means that there is no driver is assigned to the route. |
RouteID | Alphanumeric route ID of the route. The "UNASSIGNED" route ID is a group active stops without an assigned route. |
Description | Description of the route. This can only be edited in the route form. See Planning - New/Edit Route. |
RO | Status of last route optimization. See Route Optimization. Green Checkmark: Route has been optimized. Yellow !: Warnings such as no possible solution or the end/begin time being incompatible. Red X: Cannot run optimization for the route.
|
FleetID | Fleet ID assigned to | Tip |
|---|
Quick Tip: Only validated addresses will be included in the optimization process, any unvalidated stops would be removed before processing. |
|
FleetID | Fleet ID assigned to route upon creation of the route. See Planning - New/Edit Route. |
FleetName | Fleet name associated with Fleet ID assigned to the route. Fleet names can be edited in Maintenance > Fleets. See Fleets (Classic Operations App). |
PostDate | Date the route was posted. See Post Recurring Orders or Routes. |
StartTime | Start time set on the route form. It's used for reporting and display purposes only. |
EndTime | End time set on the route form. It's used for reporting and display purposes only. |
| Stops | Total number of stops on route. |
| Completed | Total number of completed stops on route. |
Red highlight: Not all of the stops have been completed, the current time is past the Start time, and the End time is greater than the Start time, or if the route End time is more than 24 hours ago, the route is still active, and the End time is greater than the Start time.
|
Stops | Total number of stops on route. |
Completed | Total number of completed stops on route. |
Status (Max) | Each field shows the number of late stops depending on the time evaluation (Max Time, Preferred Time or ETA Time). Ideally, all stops are delivered before the customer's preferred time, however, sometimes this isn't the case and the stop may not officially be considered late until delivery time exceeds maximum defined time. These fields show three pieces of information: Number: The number of late* stops. Status:
|
. No late All stops are on time. Yellow: One or
|
more the last stop is not late Late stops existLate Late: A late stop is when the current time exceeds the time specified in parenthesis (Max, Preferred, or ETA) for stops on the route. |
Status (Preferred) |
Status (Min) |
Status (ETA) |
Total | Total number of parcels existing on completed stops for the route. This does not include parcel counts for expected parcels. |
| Over | Total number of parcels indicated as "Overages" on completed stops for the route (parcels not originally on the stop as expected). |
Short | Total number of parcels indicated as "Short" on completed stops for the route (unscanned or undelivered parcels). |
Exceptions | Total number of parcels indicated as "Exceptions" on completed stops for the route (driver or CSR adds "Exceptions" / status codes). |
| NextETAMax | Time difference in minutes between the current time and the next stop's ETA value supplied for the |
preferred max field + the grace period for route stops in the route optimization settings. |
| Anchor |
|---|
NextETAPreferred | NextETAPreferred | NextETAPreferredTime difference in minutes between the current time and the ETA Unhighlighted: ETA is more than 10 minutes before the Max time. Yellow highlight: ETA is between 0 to 10 minutes before the Max time. Red highlight: ETA is after the Max time.
|
| Anchor |
|---|
| NextETAPreferred |
|---|
| NextETAPreferred |
|---|
|
NextETAPreferred | Time difference in minutes between the current time and the next stop's ETA value supplied for the preferred field in the route optimization settings. |
| Early | Number of stops on the route that were completed early (before the preferred time). |
Late | | Info |
|---|
For X Dispatch 18.0 to 19.2, calculated as the number Unhighlighted: ETA is more than 10 minutes before the Preferred time. Yellow highlight: ETA is between 0 to 10 minutes before the Preferred time. Red highlight: ETA is after the Preferred time.
|
Early | Number of stops on the route that were completed |
after min Driver Nickname | Nickname Number of stops completed after the Max time of the route stop.
Green highlight: All stops are on time. Yellow highlight: One or two stops are late, however, all other stops are on time. Red highlight: Three or more stops are late.
|
Late | Number of stops completed after the Max time of the route stop. Green: All stops are on time. Yellow: One or two stops are late, however, all other stops are on time. Red: Three or more stops are late.
|
Driver Nickname | Nickname of the driver assigned to the route. |
See Drivers - New / Edit Driver.PayLocked | X Route - Dispatch - Set Driver Pay. |
| Anchor |
|---|
| HHManifestComp |
|---|
| HHManifestComp |
|---|
|
HHManifestComp | Number of route stops where the driver clicks on the |
Stop stop in their manifest to open and complete it. |
| Anchor |
|---|
| HHActiveStopScan |
|---|
| HHActiveStopScan |
|---|
|
HHActiveStopScan | Number of route stops where the driver scans the X-xxxx-Rxxxx barcode to open the stop and completes it. The R barcode is found on the |
Route Manifest route manifest from the Dispatch Board. |
| Anchor |
|---|
| HHContractStopScan |
|---|
| HHContractStopScan |
|---|
|
HHContractStopScan | Number of route stops where the driver opens and PODs the stop by being on the route manifest and either scanning the L or C barcode related to the stop. The L barcode is the lookup barcode for the stop (X Mobile Secondary Lookup) and the C barcode is the |
PKID of the Contract Stopcontract stop barcode. |
| CSRComp | Number of route stops where an |
X Dispatch Operations App user manually completed the |
Route Stoproute stop. |
| Anchor |
|---|
| XInternetComp |
|---|
| XInternetComp |
|---|
|
XInternetComp | Number of route stops where the |
driver internet user marks the route stop as completed in the Driver Portal (through X Internet or |
RapidshipClient Portal) manifest. |
| Status Code | Number of status codes on a route. |
Back to top
Selection (Shortcut) | Description |
|---|
Dispatch Or Remove Driver... (6) | Opens a form to dispatch or remove a driver from the route. |
Edit... | Opens route manifest. See |
X Route - Dispatch - viewParcels | View Parcels...| Anchor |
|---|
viewParcels | Activate All Stops | Activate any stops on the route that are currently deactivated. | Info |
|---|
Requires “Activate/Deactivate Stops” permission enabled and “Include Completed Stops” if needed for completed stops. See Users (Classic Operations App). |
|
Deactivate All Stops | Deactivate any stops on the route that are currently active. | Info |
|---|
Requires “Activate/Deactivate Stops” permission enabled and “Include Completed Stops” if needed for completed stops. See Users (Classic Operations App). |
|
| View Parcels... | Opens parcel manifest. See Parcel Manifest. |
Distribution Parcel Sort... | See Route Parcel Sort. |
Depot Scan | See Dispatch - Depot Scan. |
Select Date... | Select which postdate to view, from a calendar. |
Filter Routes by Fleets (*) | Opens fleet selection window from which fleets can be checked. Dispatchers must be granted permissions to Fleets before they can be selected. |
Set Driver Pay | See |
X Route - Dispatch - Set | Run Custom Procedure | Allows access to specific custom procedures, available from CXT Software custom services. |
Save Layout | Saves current layout. If adjustments are Clone Route | Clone the route. You can choose whether or not to clone all route stops. Cloning does not include information such as parcels, completion times, PODs, etc. | Tip |
|---|
Quick Tip: Cloning of an active route will not post the new route automatically. If routes have already been posted for the day, you can post routes again for the same day to bring in any new routes that were not previously included. |
|
Run Custom Procedure | Allows access to specific custom procedures, available from CXT Software custom services. |
Save Layout | Saves current layout. If adjustments are made to field sequence that need to be saved, use this feature. When saving a layout the option exists to save the "Routes", "Drivers", or "Both" grids. Layouts may also be saved as a custom grid for later retrieval. | Tip |
|---|
Quick Tip: Save grids to custom layout in case you need to restore any undesirable changes. |
|
Reset Layout | Resets dispatch field layout to CXT Software standard layout. The "Routes", "Drivers", or "Both" grids can be reset. | Warning |
|---|
All dispatch specific changes will be lost. |
|
Load Layouts | Restores a layout previously saved using the "Save Layout" function. |
Show/Hide Route Fields | Adds or removes columns from routes grid. Use the "Save Layout" function after selecting fields to save changes. |
Find Route | Opens a window to search for a route ID. If a matching route is found, the route will be highlighted. |
Find Driver | Opens a window to search for a driver ID. If a matching driver ID is found, the first route with the driver assigned will be highlighted |
Find Parcel... | Opens a window to search for a parcel barcode. If a matching parcel is found, another window will open to allow parcel edits and details (including all assigned route stops associated to the parcel). |
Print All Manifests... (Ctl + P) | See Dispatch - Print Route Manifest. |
Print Shown Manifests |
Merge Group Values | Merges any cells to the left of the thick black bar, with the same value. |
Show OSD | Enables the Over, Short, and Exception columns to display data. See "Over" in the table above. |
Show ETA | Displays or hides the NextETAMax and NextETAPreferred columns. See " |
377159857377159857NextETAPreferred" in the table above. |
Show Status Code | Displays or hides the "Status Code" column. See "Status Code" in the table above. |
Show Completion Types | Displays or hides the HHManifestComp, HHActiveStopScan, HHContractStopScan, CSRComp, and XInternetComp columns. See " |
377159857377159857377159857377159857377159857Override Highlight After Dispatch | Where the highlight should be immediately after dispatch. |
Override Start Times | When checked the route start times for the dispatch board come from the preferred time of the stop with the lowest sequence number, when unchecked, start time is the time set on the route. |
Override End Times | When checked the route end times for the dispatch board come from the preferred time of the stop with the highest sequence number, when unchecked, end time is the time set on the route. |
Set ETA Speed... | Opens the "ETA Speed" form to enter an average speed to use when calculating the ETA. |
Show All | Displays all the routes in the routes grid (including completed routes). |
Alert on non-current date | When enabled, a yellow banner is present on any route manifests viewed from previous or future postdates. |
Toggle Grid Orientation | Switches dispatch screen orientation between horizontal and vertical. |
Back to top
| Anchor |
|---|
| ActiveDriversWindow |
|---|
| ActiveDriversWindow |
|---|
|
Active Drivers GridThe Active Drivers grid displays the
...
same Operations App information as the on-demand dispatch board. Route information is not included in this section.
Image Removed
 Image AddedField Name | Description |
|---|
Driver | Driver ID. A warning icon  Image Modified is displayed in front of a driver ID 5 minutes after an order is dispatched to a driver and the driver has not marked it confirmed. | Vehicle Class (vehicle icon) | Displays an icon according to the class of the vehicle that is set in the driver record. The available icons are a bicycle, bobtail, car, motorcycle, pickup, scooter, or van. |
|
...
...
...
| Direction (compass icon) | Displays the direction of travel if GPS is enabled on the driver's mobile device. | RO | Status of last route optimization. See Route Optimization. Green Checkmark - Driver has been optimized. Yellow ! - Warnings such as no possible solution or the end/begin time being incompatible. Red X - Cannot run optimization for the driver.
| Bearing | The direction or course of motion determined by the GPS chip of the mobile device. Similar to "Direction" but the bearing is represented numerically from 0-360 | Speed | This reports the speed of the driver through GPS report data collected from the mobile device. | Nickname | Nickname from the "Nickname" field in the "General" tab of the driver's human resource record. See Human Resources - New / Edit Human Resource. | Vehicle | Vehicle description from the vehicle record associated with the driver's record. |
|
...
...
...
...
...
or Drivers (Classic Operations App). | LastReportLat | Latitude coordinate of the last time the mobile device GPS communicated with the server. | LastReportLon | Longitude coordinate of the last time the mobile device GPS communicated with the server. | Previous Zip | Longitude Zip Code associated with the driver's previous location, prior to the Current Zip. | Previous Report | The last time either GPS was reported or an action caused the location to be updated (At Origin, At Destination, Completing a stop, etc.). | GPS Lat | GPS latitude point from the last GPS update reported from a driver. | GPS Lon | GPS longitude point from the last GPS update reported from a driver. | GPSReportZip | Zip code from the last GPS update reported from a driver |
|
...
when either an update is made to an order status or an order was updated | GPSReportZone | Zone from the order of the last GPS update from a driver |
|
...
when either an update is made to an order status or an order was updated | GPSReportTime | Time and date of the last GPS update from a driver. Gray - The time is 10+ minutes in the past, and the LastMobileReport field is less than 5 minutes ago, or the GPS Report time is 5-10 minutes in the past and the LastMobileReport field is less than 5 minutes ago. Red - The LastMobileReport field is older than 5 minutes AND GPSReportTime > 10 minutes old Yellow - More than 5 minutes in the past, (will be gray in the situation above if the LastXTReport is within the last 5 minutes)
|
|
...
Zone from the last time either the GPS was reported, or an action caused the location to be updated (At Origin, At Destination).
...
| Tip |
|---|
Quick Tip: The GPS will show as current as long as the driver’s GPS isn't turned off or the application closed out. |
| GPS Post | Displays a 1 if there was a GPS update from the driver. | CurrentReportLat |
|
...
Lattitude from the last action taken on any of the driver’s assigned orders/route stops. If the action is coming from the driver, the driver’s lattitude at the time of the action will be displayed. If the action is coming from an Operations user from inside of the application, the order or route stop location’s lattitude that is associated with the action will be displayed. For example, if the last action for any of the driver’s assignments came from a dispatcher marking an order as ‘Picked Up’, the pickup location’s lattitude would display. | CurrentReportLon | Longitude from the last action taken on any of the driver’s assigned orders/route stops. If the action is coming from the driver, the driver’s longitude at the time of the action will be displayed. If the action is coming from an Operations user from inside of the application, the order or route stop location’s longitude that is associated with the action will be displayed. For example, if the last action for any of the driver’s assignments came from a dispatcher marking an order as ‘Picked Up’, the pickup location’s longitude would display. | Current Zip | Zip code from the last action taken on any of the driver’s assigned orders/route stops. If the action is coming from the driver, the driver’s zip code at the time of the action will be displayed. If the action is coming from an Operations user from inside of the application, the order or route stop location’s zip code that is associated with the action will be displayed. For example, if the last action for any of the driver’s assignments came from a dispatcher marking an order as ‘Picked Up’, the pickup location’s zip code would display. | Current Zone | Zone from the last action taken on any of the driver’s assigned orders/route stops. If the action is coming from the driver, the driver’s zone at the time of the action will be displayed. If the action is coming from an Operations user from inside of the application, the order or route stop location’s zone that is associated with the action will be displayed. For example, if the last action for any of the driver’s assignments came from a dispatcher marking an order as ‘Picked Up’, the pickup location’s zone would display. | Current Report | Time and date from the last action taken on any of the driver’s assigned orders/route stops. This can come from either a driver or Operations App user such as a dispatcher. | NextLat | Latitude for driver's next stop. A 0 will be displayed if no "next stop" is selected. | NextLon | Longitude for driver's next stop. A 0 will be displayed if no "next stop" is selected. | NextZip | Zip code for driver's next stop. A 0 will be displayed if no "next stop" is selected. | NextZone | Zone for the driver's next pickup/delivery set on an on demand order. | NextReportTime | Timestamp for |
|
...
when Operations App last synced with the mobile device to get next stop details. | FurthestLat | Furthest pickup/delivery location latitude for linking on demand orders from the current GPS location. Only updates if there has also been a GPS update within the last 3 minutes of updating an order. | FurthestLon | Furthest pickup/delivery location longitude for linking on demand orders from the current GPS location. Only updates if there has also been a GPS update within the last 3 minutes of updating an order. | FurthestZip | Furthest pickup/delivery location zip for linking on demand orders |
|
...
from the current GPS location. Only updates if there has also been a GPS update within the last 3 minutes of updating an order. | FurthestZone | Furthest pickup/delivery location zone for linking on demand orders from the current GPS location. Only updates if there has also been a GPS update within the last 3 minutes of updating an order. | Furthest Report | Furthest longitude point from a GPS coordinate reported by a driver. | Status | Green - All orders assigned to driver are beyond the orders pickup/delivery warning settings on the corresponding order type Yellow - An order assigned to the driver is between the required pickup/delivery time and its corresponding warning time, but not late Red - An order assigned to the driver is late for pickup/delivery
| Email | Driver's email from the "Primary Email" field on the driver's record. |
|
...
...
...
...
the last time the mobile device communicated to the server, regardless of if GPS was collected. For example, this updates even if the GPS chip was broken on a mobile device. | MinIdle | Mins between no and the last update to an order status value. | CurrentXTVersion | The |
|
...
Driver App version of the driver's device |
|
...
. | Previous Report (Local) | The last time either GPS was reported or an action caused the location to be updated (At Origin, At Destination, Completing a stop, etc.). | GPSReportTimeLocal | Localized Timestamp of the last GPS update from a driver. | Current Report (Local) | Localized |
|
...
time and date from the last action taken on any of the driver’s assigned orders/route stops. This can come from either a driver or Operations App user such as a dispatcher. | NextReportTimeLocal | Localized Timestamp for |
|
...
when Operations App last synced with the mobile device to get next stop details. | Furthest Report (Local) | Localized Timestamp of furthest GPS report, reported by a driver. | LastMobileReport (Local) | Localized Timestamp of the last time the mobile device communicated to the server, regardless of if GPS was collected. | GPSLocationError |
|
...
| Numeric code for the location error. | LastErrorGPS |
|
...
| Description of the location error. | Max Dim Weight |
|
...
| Maximum amount of dimensional weight that can be assigned to the vehicle (driver). | Dim Weight Total | Total dimensional weight assigned to the driver. |
|
...
| Info |
|---|
Requires X Dispatch 21.0 or newer. |
Maximum amount of dimensional weight that can be assigned to the vehicle (driver).
...
| Info |
|---|
Requires X Dispatch 21.0 or newer. |
...
| Count(Routed) | Number of route stops on active routes assigned to the driver. | AD | Displays whether the driver has the Assisted Dispatch permission enabled or disabled. See Assisted Dispatch. | Count(All) | Number of both on demand orders and route stops that are active and assigned to the driver. | NextStop | Name of the stop that is either marked as the next stop for the driver or is the next stop on the driver sequence. This will be blank if no stop is marked or if the driver is not checked in. |
Back to top Selection (Shortcut) | Description |
|---|
Details... (Enter) | Opens the "Driver - Active Orders" grid. See Driver Active Work. | | Edit Comments... | Updates driver comments column in drivers grid. Driver comments can be very helpful to provide additional information about a driver's status. Example If a driver becomes unavailable, the ETA for the driver can be inserted. In this way, if a dispatcher's shift ends the information is easily visible to the next dispatcher. | Edit Driver... (Num 8) | Opens the driver form. |
|
...
See Drivers or Drivers (Classic Operations App). | Position Driver... (P) | Positions driver within a postal code. Useful if the driver is not using GPS enabled mobile devices. | Locate Driver... (L) | Displays map with an icon showing the location of driver. Uses GPS data if available, last known location based on driver pickups or deliveries, or where the driver was positioned by the dispatcher using the "Position Driver" menu selection. | Send Text Message (M) | Sends a message to the driver's mobile device. |
|
...
...
: Entering a URL in the message body will display as a clickable link in |
|
|
...
the Driver App 3.1.1 or newer. |
| Optimize Route | Optimize the driver's pickups and deliveries in the order the driver should perform them, and then send the sequence to the driver's mobile devices. See Route Optimization. | Optimization Status | Displays the last time of optimization, status, and errors. | Filter active drivers by fleets... (*) | Opens fleet selection window from which fleets can be checked. Drivers are displayed for selected fleets only. Dispatchers must be granted permissions to fleets before they can be selected. | Filter active drivers by zone... | Filters drivers based on zone and zone type. Available zone types are "Current Zone", "GPS Zone", "Previous Zone", "Furthest Zone". | Note |
|---|
Drivers without a zone will always appear. |
| Activate Driver... (Insert) | Activate drivers when they are ready to work. After pressing "Insert" the driver appears in Drivers Grid. | Deactivate Driver (Delete) | Deactivates drivers when they are finished working. After pressing "Delete" the driver is removed from Drivers Grid. | Logout Driver | Logout drivers from the mobile app. | Inactive Drivers... | Shows list of all deactivated drivers. |
|
...
...
: Activate a driver by double-clicking. |
| Save Layout (Num 0) | Saves the current layout. If adjustments are made to field sequence that needs to be saved, use this feature. When saving a layout the option exists to save orders/route grid, drivers grid, or both. Layouts may also be saved as a custom grid for later retrieval. This is the same "Save" function that exists in the Orders Grid. |
|
...
...
: Save grids to custom layout in case an undesirable change is made so that the "good" grid can be restored. |
| Reset Layout | Resets dispatch field layout to CXT Software standard layout. The Orders/Routes Grid, Drivers Grid, or both Grids can be reset. | Note |
|---|
All dispatch specific changes will be lost. |
| Load Layouts | Restores a layout previously saved using "Save Layout" function. | Show/Hide Driver Fields | Adds or removes columns from the Drivers Grid. Use "Save Layout" function after selecting fields to save changes. | Run Custom Procedure... | Allows access to specific custom programs that may be available. | Find Driver... (.) | Finds driver in orders grid by highlighting first order assigned to the driver. | Sync Dispatch Grid... (+) | A useful function to help dispatchers locate a drivers route in the "Active Orders"/"Active Routes" grid, by selecting this function from the "Active Drivers" grid. This is especially beneficial for delivery companies that have large dispatch environment with hundreds of orders and dozens of drivers. | Clear Next Stop | Clears "Next Stop" indicator for the driver if it was set using "Make Next Stop" feature noted above in Orders/Routes Grid. | Sort Fields | Sorts drivers based on up to five selectable sort |
|
...
GPSLocationError
| Info |
|---|
Requires X Dispatch 19.2 and Nextstop 3.0 or newer. |
fields. Overrides default sort by driver number. | GPSLocationError | The numeric value associated with a location error code. Examples: |
|
...
| Info |
|---|
Requires X Dispatch 19.2 and Nextstop 3.0 or newer. |
Display text for the related GPSLocationError that was generated. |
|
Back to top
| Page Properties |
|---|
|
CXTU Courses/Lessons | Dispatcher Role Training: Dispatch Boards Dispatcher Role Training: Dispatch Boards - Routes Dispatching Routes & Distribution: Dispatching Routes & Distribution: Route Troubleshooting
|
|---|
|