Location: Manage > MMS > MMS Controls: (Dispatch Settings section)

Label on the page: "Time between arrival and load should be [X] mins"

What it controls: This setting defines the default number of minutes between a truck's arrival time and load time when creating dispatch orders using Staggered or Grouped arrival patterns on the Dispatch Board page. For Example, If set to 15 minutes, there will be a 15 minute gap between when a truck is scheduled to arrive and when it's expected to load.

Why it was created: Previously, the gap between arrival and load was hard-coded at 15 minutes and had to be changed individually on every order. Many customers' "arrival time" is their expected load time, so the extra 15 minutes caused drivers to arrive earlier than needed or get out of sync because they thought their load times were 15 minutes later than intended. This setting lets each customer store their preferred default so they don't have to change it every time.

How it flows through the system:

Fallback behavior: If the setting lookup fails for any reason, the system defaults to 15 minutes.

FleetWatcher uses the column headers "Plant" and "Location" across dispatch pages and reports to identify where a shift's material originates and where it is being delivered. However, these labels can be confusing particularly for off-road CMS jobs where no plant is involved, or for milling jobs where the source is a mill rather than a plant.

The "Change Location/Plant information to Starting Location/Haul Location" setting allows you to rename these column headers to more intuitive labels:

This is a label-only change. It does not alter the underlying data mapping or how Source and Destination are determined. It simply changes what the user sees on screen and in reports.

This feature is enabled on a per-customer basis by your FleetWatcher administrator.

When enabled, the "Starting Location" and "Haul Location" labels replace "Plant" and "Location" on the following pages and reports:

When the setting is enabled, the display order of the location fields on the Dispatch Board (both the Order Form and the Shift Drawer) is also updated:

This was implemented because dispatchers naturally read top-to-bottom and were scanning quickly, mistaking the first listed location as the starting point.

When the setting is disabled, the original baseline layout is retained.

For CMS shifts where no destination geozone is set, the system displays the Project as the "Haul Location" on Dispatch pages and Dispatch Reports. This is existing system behavior and is not new to this setting.

When disabled (the default), the system uses the original column headers:

The original baseline field order is also retained.

Some shifts use a piece of equipment (like a paver or mill) as the source or destination, instead of a plant or geozone. The system now correctly shows the Starting Location and Haul Location for these shifts. When needed, it uses the Project Name so the location shown always makes sense.

This setting works alongside another Dispatch Settings flag: "Plant Name as Source & Location as Destination for Dispatch Assignments." Both settings affect the same Plant/Location columns but in different ways:

By default, the Dispatch Board sorts all shifts in standard alphanumeric order (0-9, A-Z), regardless of whether a shift is currently active or not. For high-volume dispatchers managing many shifts, this means active shifts that need immediate attention are mixed in with inactive shifts, requiring dispatchers to scroll through the full list to find actionable work.

The "Alternate Jobs ordering for Dispatch" setting changes this behavior by sorting active shifts to the top of the Dispatch Board, making it easier for dispatchers to focus on the work that matters right now.

This feature is enabled on a per-customer basis by your FleetWatcher administrator.

When enabled, the Dispatch Board sorts shifts in the following order:

This sort order dynamically recalculates when the dispatcher changes the viewed date on the calendar. Active shifts for the newly selected date range will automatically move to the top.

When disabled (the default), the Dispatch Board uses standard alphanumeric sorting (0-9, A-Z). Active and inactive shifts are mixed together based on their name, with no priority given to active shifts.

This setting only affects the Dispatch Board. Other dispatch pages, reports, and views are not impacted by this setting.

FleetWatcher includes an optional setting that controls how the Source and Destination of a shift map to the Plant Name and Location columns across dispatch surfaces.

By default, FleetWatcher uses a complex set of rules to determine what appears in the Plant Name and Location columns. Taking into account whether the source or destination is a geozone polygon, a piece of equipment, or matches the project. This means the Plant Name column does not always display the shift's source, and the

Location column does not always display the shift's destination.

When the "Plant Name as Source & Location as Destination for Dispatch Assignments" setting is enabled, the system overrides that default logic with a straightforward mapping:

This feature is enabled on a per-customer basis by your FleetWatcher administrator.

This is the verified primary area of impact. When enabled:

Note: The column headers on the Dispatch Assignment Report remain labeled "Plant" and "Location" — they do not change to "Source" and "Destination."

When disabled (the default), the system uses its legacy mapping logic to determine what appears in the Plant Name and Location columns. This logic evaluates multiple factors including:

As a result, the Plant Name column may display the destination in certain shift configurations, and vice versa.

Scale Ticket Matching: Enabling this setting may affect how scale tickets are matched to shifts. A case was identified where scale tickets were matching the destination of a shift instead of the source, because the column mapping was reversed. If you notice scale tickets incorrectly appearing on shifts after enabling this setting, contact support.

This setting works alongside another Dispatch Settings flag: "Change Location/Plant information to Starting Location/Haul Location." These two settings affect the same fields, and their interaction may produce different behaviors depending on which combination of flags is enabled. Consult your FleetWatcher administrator before enabling both simultaneously.

FleetWatcher includes an optional setting that allows the Live Shift Completion KPI bar on shift cards to use Paving Start/End times instead of the standard Shift Start/End times. This provides a more accurate view of paving progress by aligning the completion bar with when actual paving operations begin and end, rather than the broader shift window.

This feature is enabled on a per-customer basis by your FleetWatcher administrator.

When the "Use Paving Start/End for Shift Cards" flag is turned on, the following changes apply to the shift card:

If either the Paving Start or Paving End time is missing for a shift, the system automatically falls back to using the standard Shift Start and Shift End times for the KPI bar. No action is required from the user — this happens automatically.

When the flag is set to Off (the default), the shift card behaves as it always has:

This setting only affects the Live Shift Completion KPI bar on the shift card. All other KPIs continue to use their existing calculation logic and are not impacted by this setting.

Q: Who can enable this setting?

A: This setting is managed by your FleetWatcher administrator under Manage > MMS > MMS Controls > Dispatch Settings.

Q: What happens if I only have a Paving Start time but no Paving End time (or vice versa)?

A: The system requires both Paving Start and Paving End to be present. If either is missing, the shift card falls back to using the standard Shift Start/End times.

Q: Does this affect other KPIs like TPH or Feet Per Minute?

A: No. This change is limited to the Live Shift Completion KPI bar on the shift card. Other KPIs continue to use their existing logic.