Customized route tracking
Disclosed are systems, methods, and non-transitory computer-readable media for automated fleet tracking. A route management system enables fleet managers to define and assign routes for vehicles in a fleet, as well as set route tracking configurations for customized tracking of the vehicles. For example, the route tracking configuration may include customizations to the scheduled start and/or end time of a route, a threshold for determining that a vehicle has arrived and/or departed from a scheduled stop, and the like.
1. A method comprising:
generating a first route tracking report for a first vehicle based on a first tracking customization to a set of route variables for tracking vehicles associated with a first fleet attribute;
generating a second route tracking report for a second vehicle based on a second tracking customization to the set of route variables for tracking vehicles associated with a second fleet attribute, the second tracking customization being different than the first tracking customization;
causing presentation of the first route tracking report on a first client device associated with a first account that comprises the first fleet attribute; and
causing presentation of the second route tracking report on a second client device associated with a second account that comprises the second fleet attribute.
2. The method of claim 1 , further comprising:
receiving first sensor data describing movement of the first vehicle and second sensor data describing movement of the second vehicle, wherein the first route tracking report is generated based on the first sensor data and the second route tracking report is generated based on the second sensor data.
3. The method of claim 1 , wherein the set of route variables includes a start time and an end time defining a scheduled route window for a first route to be traveled by the first vehicle, and the first tracking customization includes a modification to the start time or the end time for the first route.
4. The method of claim 3 , further comprising:
generating a route tracking window based on the scheduled route window for the first route and the first tracking customization, the route tracking window being an expansion of the scheduled route window based on the first tracking customization, wherein the first route tracking report is generated based on sensor data describing movement of the first vehicle during the route tracking window, including sensor data describing movement of the first vehicle that is outside of the scheduled route window.
5. The method of claim 1 , wherein the set of route variables for tracking vehicles associated with a first account defines a threshold period of time for determining arrival at a scheduled stop.
6. The method of claim 5 , wherein generating the first route tracking report comprises:
determining, based on first sensor data describing movement of the first vehicle, that the first vehicle is within a first geographic region associated with a first scheduled stop;
determining that a period of time that the first vehicle is within the first geographic region meets the threshold period of time; and
including data in the first route tracking report indicating that the first vehicle arrived at the first scheduled stop.
7. The method of claim 1 , wherein the set of route variables for tracking vehicles associated with a first account defines an expected amount of time to be spent at a scheduled stop.
8. The method of claim 7 , further comprising:
determining, based on first sensor data describing movement of the first vehicle, that the first vehicle is within a first geographic region associated with a first scheduled stop; and
determining a departure time for the first vehicle from the first scheduled stop based on the expected amount of time.
9. A system comprising:
one or more computer processors; and
one or more computer-readable mediums storing instructions that, when executed by the one or more computer processors, cause the system to perform operations comprising:
generating a first route tracking report for a first vehicle based on a first tracking customization to a set of route variables for tracking vehicles associated with a first fleet attribute;
generating a second route tracking report for a second vehicle based on a second tracking customization to the set of route variables for tracking vehicles associated with a second fleet attribute, the second tracking customization being different than the first tracking customization;
causing presentation of the first route tracking report on a first client device associated with a first account that comprises the first fleet attribute; and
causing presentation of the second route tracking report on a second client device associated with a second account that comprises the second fleet attribute.
10. The system of claim 9 , the operations further comprising:
receiving first sensor data describing movement of the first vehicle and second sensor data describing movement of the second vehicle, wherein the first route tracking report is generated based on the first sensor data and the second route tracking report is generated based on the second sensor data.
11. The system of claim 9 , wherein the set of route variables includes a start time and an end time defining a scheduled route window for a first route to be traveled by the first vehicle, and the first tracking customization includes a modification to the start time or the end time for the first route.
12. The system of claim 11 , the operations further comprising:
generating a route tracking window based on the scheduled route window for the first route and the first tracking customization, the route tracking window being an expansion of the scheduled route window based on the first tracking customization, wherein the first route tracking report is generated based on sensor data describing movement of the first vehicle during the route tracking window, including sensor data describing movement of the first vehicle that is outside of the scheduled route window.
13. The system of claim 9 , wherein the set of route variables for tracking vehicles associated with a first account defines a threshold period of time for determining arrival at a scheduled stop.
14. The system of claim 13 , wherein generating the first route tracking report comprises:
determining, based on first sensor data describing movement of the first vehicle, that the first vehicle is within a first geographic region associated with a first scheduled stop;
determining that a period of time that the first vehicle is within the first geographic region meets the threshold period of time; and
including data in the first route tracking report indicating that the first vehicle arrived at the first scheduled stop.
15. The system of claim 9 , wherein the set of route variables for tracking vehicles associated with a first account defines an expected amount of time to be spent at a scheduled stop.
16. The system of claim 15 , the operations further comprising:
determining, based on first sensor data describing movement of the first vehicle, that the first vehicle is within a first geographic region associated with a first scheduled stop; and
determining a departure time for the first vehicle from the first scheduled stop based on the expected amount of time.
17. A non-transitory computer-readable medium storing instructions that, when executed by one or more computer processors of one or more computing devices, cause the one or more computing devices to perform operations comprising:
generating a first route tracking report for a first vehicle based on a first tracking customization to a set of route variables for tracking vehicles associated with a first fleet attribute;
generating a second route tracking report for a second vehicle based on a second tracking customization to the set of route variables for tracking vehicles associated with a second fleet attribute, the second tracking customization being different than the first tracking customization;
causing presentation of the first route tracking report on a first client device associated with a first account that comprises the first fleet attribute; and
causing presentation of the second route tracking report on a second client device associated with a second account that comprises the second fleet attribute.
18. The non-transitory computer-readable medium of claim 17 , the operations further comprising:
receiving first sensor data describing movement of the first vehicle and second sensor data describing movement of the second vehicle, wherein the first route tracking report is generated based on the first sensor data and the second route tracking report is generated based on the second sensor data.
19. The non-transitory computer-readable medium of claim 17 , wherein the set of route variables includes a start time and an end time defining a scheduled route window for a first route to be traveled by the first vehicle, and the first tracking customization includes a modification to the start time or the end time for the first route.
20. The non-transitory computer-readable medium of claim 19 , the operations further comprising:
generating a route tracking window based on the scheduled route window for the first route and the first tracking customization, the route tracking window being an expansion of the scheduled route window based on the first tracking customization, wherein the first route tracking report is generated based on sensor data describing movement of the first vehicle during the route tracking window, including sensor data describing movement of the first vehicle that is outside of the scheduled route window.