Understanding and Resolving Untracked Trucks in FleetWatcher
Introduction
In the FleetWatcher platform, tracking trucks efficiently is critical for smooth operations. However, untracked trucks can cause disruptions. This article explores common causes for trucks appearing as untracked in FleetWatcher, diagnostics you can perform, and actionable steps to resolve the issues.
Common Causes of Untracked Trucks
1. Misaligned Shift Start Times
Untracked trucks may result from shift start times being set later than the first recorded load timestamp. For instance, if the first truck load occurs at 8:03 AM, but the shift start time is configured to 9:00 AM, this causes a mismatch. Updating the shift start time to before the first load and reprocessing resolves this issue.
2. Mismatched Aliases for Truck Names
When trucks are entered into the system under inconsistent naming conventions (e.g., “R1-2-3-4” vs. “ROU1-2-3-4”), they may not be properly tracked despite being scaled out. Resolving this issue involves adding aliases to the system. Ensure that all naming variations map back to the correct asset for accurate tracking.
3. Incomplete or Delayed Driver App Transmissions
Sometimes, trucks appear untracked on the shifts page even if drivers are logged into the Assign Drivers page. This happens when the Driver App fails to transmit data successfully. Common reasons include delayed or missing transmissions, device assignment conflicts (e.g., a physical CLA/telematics device overriding the Driver App), and incorrect app permissions (e.g., location access, motion/activity permissions, notifications).
Diagnostic Steps for Identifying the Issue
To determine the root cause of untracked trucks, use the following diagnostic tools available in FleetWatcher:
GPS Transmission Activity Report: - Navigate to Fleet > Location > GPS Transmission Activity to review when each asset last reported and for how long.
App-as-a-Device Fleet Status Report: - Go to Fleet > Devices > App > Fleet Status Report to check which drivers are logged in and their app transmission status.
Actionable Steps to Resolve Issues
Fix Shift Start Times: - Check and update the shift start times in the system to ensure they align with the first load timestamps. - Reprocess the data to reflect accurate tracking.
Standardize Truck Naming Conventions: - Add aliases for all the naming variations of trucks. - Verify that all variations map to the relevant asset.
Ensure Driver App Connectivity: - Follow these steps to restore tracking functionality:
Verify the driver is using the Driver App, not the Field App.
Check and enable app permissions (location, motion/activity, notifications).
Restart the app session (Stop Driving → Force-quit → reopen → Start Driving).
Log out and log back in.
Reinstall the app if necessary.
Decouple the truck from any physical CLA/telematics device if a device assignment conflict exists.
Check the Fleet Status report after each step to confirm "green" status.
Note that poor cellular signal may affect tracking until connectivity improves.
Best Practices for Preventing Untracked Trucks
Regularly audit shift times and truck aliases to catch inconsistencies early.
Educate drivers on properly using the Driver App by tapping "Start Driving" at the start of each shift and "Stop Driving" at the end.
Ensure the app is closed when not in use to conserve device resources and avoid potential tracking errors.
Periodically run diagnostic reports to monitor fleet status and GPS activity.
Conclusion
Untracked trucks in FleetWatcher can often be resolved by addressing configuration mismatches, standardizing naming conventions, and ensuring successful app transmissions. By following the diagnostic steps and best practices outlined above, you can proactively prevent tracking issues and maintain operational efficiency. For further assistance or if the issue persists, contact FleetWatcher support.