Watch a Video Tutorial
AngelTrack tracks all fuel purchases across your fleet, providing the accountability and analytics needed to identify problems, waste, and theft. Crew members use their mobile device (even a personal smartphone) to log their fuel purchase right at the pump, even photographing the receipt if ordered to do so. Fuel purchases can also be input by back-office staff, or bulk imported from logs downloaded from your fuel account's website.
Fuel purchases can be logged in AngelTrack using any of the following methods:
Because AngelTrack is constantly receiving odometer readings from vehicles as they run calls, it can continuously estimate each vehicle's remaining fuel, based on miles travelled since the last fillup, and on the vehicle's known range on a full tank*. Each estimate is further refined when dispatchers collect fuel levels and odometer readings from crews at shift start and shift end.
The latest estimates are always available on the Fuel Status Report page, which Supervisors should bookmark on their mobile devices in order to quickly and easily check the fleet for vehicles in need of fueling.
Note that the estimates depend on accurate entry of odometer readings. If a crew member or dispatcher mistypes a vehicle's odometer reading, then its fuel estimate will be incorrect or unavailable until AngelTrack receives a better odometer entry for it.
*Edit a vehicle's full-tank range on its Vehicle Edit page. If no range is specified, AngelTrack assumes 360 miles.
AngelTrack calculates the fuel estimates using the stream of odometer readings it receives from the following sources:
Oftentimes those data sources will contain errors and typos, but AngelTrack can usually figure out which records are bad and thus ignore them. However, sometimes an error will be nearly valid enough to escape detection, and thereby cause the estimator to fail.
When that happens, review the above data sources as they pertain to the vehicle in question to see which record contains an error. Check the vehicle's fuel log entries, its maintenance records, its shift records, and the patient transports attached to those shifts.
The fuel status system, the fleet maintenance system, and the many statistical reports concerning vehicle mileage and costs, all depend on the stream of odometer readings submitted by crews.
The system is tolerant of occasional typographical errors, but it does not function when crews are permitted to shortcut their odometer entries by starting every transport at 0.0, like this:
| Starting Odometer | Ending Odometer | |
|---|---|---|
| Incorrect / Lazy / Risky | 0.0 | 15.5 |
| Correct | 78,143.3 | 78,158.8 |
Proper odometer readings enable AngelTrack's statistical features, and also protect your company in the event of an insurance audit. Require your crews to type in their actual odometer readings.
Each vehicle's fuel purchase log can be analyzed to calculate the vehicle's effective miles per gallon. The analysis is shown, as a graph, on the Fuel Usage Analysis page. The graph should be smooth, showing consistent miles-per-gallon readings over the analyzed date range. Here is a typical graph, with a group of normal entries highlighted:
Normal Fuel Log
See how our vehicle gets a consistent eight to nine miles per gallon? It will always vary by a few miles per gallon, plus or minutes two, according to what sort of driving the vehicle did that day.
Now let's see what a problem looks like...
Typographical errors are the most common problem with fuel purchase logs. Here is how they look in the analysis:
Typographical Error
A typographical error appears as a sudden jump and an accompanying dip. We see a vehicle perform very poorly, then suddenly perform very well... or vice versa. If the two entries were averaged out, the performance would be normal.
This is caused by a typographical error on one of the fuel receipts -- probably the odometer reading, or the date of purchase.
Here is what a missing fuel receipt looks like in the fuel log analysis:
Missing Fuel Receipt
A missing receipt appears as a sudden jump without an accompanying dip. From AngelTrack's point of view, the vehicle drove for two tanks' worth of fuel, but only purchased one tank's worth.
When a vehicle develops a mechanical problem, it will often manifest like this in the analysis:
Mechanical Problem
The mechanical problem usually appears as an ongoing decline. The vehicle is using more and more fuel to travel the same distance. First things to check are:
There is no way to tell the difference between a day of excessive idling, versus an incident of fuel diversion. They both look like this:
Excessive Idling, or a Diversion
A day spent idling, or an incident of fuel diversion, appears as a sudden dip without an accompanying jump. From AngelTrack's point of view, the vehicle took on a large amount of fuel but was not able to drive very far, before needing to fill up again.
Anyone submitting a fuel receipt can check the ☑ This fuel purchase record needs review by a supervisor box, to request that a supervisor review and -- if necessary -- correct the receipt. Employees should check the box when submitting fuel purchase records after-the-fact, when the receipt is missing and the cost or gallons is no longer known with certainty.
All fuel purchase records thus marked will appear in the Fuel Receipts With Problems report, accessible from the Supervision home page. Supervisors should monitor this report and clear up problems while they are still fresh in the mind of the employees who submitted them.
To import a fuel purchase log into AngelTrack, the file must be .CSV ("Comma-Separated Values") and must include the following columns:
Vehicle, Date, Odometer, Gallons, Cost, Location, Tank
If the .CSV file has a header row, then the header row must mention the aforementioned columns by name exactly, but they can be in any order. All other columns are ignored.
If the .CSV file has no header row, then the first six columns must exactly match the aforementioned columns, in order; 'Tank' data, if provided, must be the seventh column. All additional columns are ignored.
Microsoft Excel can save its spreadsheets as .CSV files. Each worksheet in a workbook must be individually saved as a .CSV and then imported here.
The 'Location' field is optional and can be empty. Note that it does not necessarily contain the location of the gas station used; instead it can be used to specify a fuel card number, or a user ID from your fueling program. If location data is provided in the .CSV, only the first 100 characters of location data will be imported into AngelTrack.
The 'Tank' field is optional and can be omitted if the purchased fuel was added to the vehicle's primary tank. If a 'Tank' is specified in the .CSV, then it should contain contain one of these values: 'Aux', 'Auxiliary', 'Secondary', or 'Generator'. Any other values are assumed to be the Primary tank. When AngelTrack scans the fuel logs to estimate each vehicle's remaining fuel, only Primary tank entries are counted.
For each data row in the .CSV, AngelTrack attempts to locate an existing fuel purchase record, by matching the vehicle, purchase date, and gallons or cost. If an existing purchase record is found that matches those three criteria, then the record is updated with new data (from the .CSV) for its odometer, gallons, cost, and location fields.