Describes the purpose and the main scenario uses of the Time Tracker function in FleetLogic.
FleetLogic web and mobile applications
In This Article
In the web application
The time tracker in FleetLogic is mainly used for payroll and analytics purposes. It is closely tied to the clock in/out functionality present in both the web and mobile applications.
You can record when your operators are starting and ending their daily activities as well as create reports based on this information to determine the strengths and weaknesses of your workforce.
You can export the time tracker information and pass it along to a third party payroll application, ensuring that your payroll information is error-free.
In the mobile application
In the web application, clocking in/out is a manual task that can be performed by any users with permission to do so. In the mobile application, clocking out is a manual task (although it is automatic if you log out of the application), but clocking in is dependent upon the task you are performing in the mobile app.
Any user with sufficient permissions can log into the mobile application and manually clock themselves in. However, if, as a technician, you start working on a work order, you are automatically clocked in as well.
In the web and mobile applications, manually, clocked hours apply to the time tracker, and do not have an influence on any other part of the application.
However, in the mobile application, if you initiate a clock in by starting work on a work order, then you are automatically clocked in, and your hours are logged in the time tracker. Those same work hours are also tracked on the work order itself as billable labor.
If you pause a work order, the hours tracked on the work order are paused as well, but the hours tracked against the time tracker continue to accrue. When you resume work on the work order, the hours tracked on the work order begin to accrue again, while the hours on the time tracker continue as if there were no interruption.
Updating work hours
It is important to note that, while these two sets of tracked time exist side by side in the web application, they do not have any influence over one another and ultimately exist independently of each other.
For example, if you update the hours in the time tracker in the web application, no updates occur on the corresponding work order, and vice versa.
From the moment these hours enter the web application, they are treated as separate sets of information, even though they have the same point of origin.