It is very common to apply pay rates based on the mileage for a trip. Such a rate can have either or both of the following:

Mileage also comes into play when you apply a percent of revenue rate for a resource that was assigned to a split trip. When calculating pay, the system allocates the order's revenue based on the number of miles the resource drove. For example, if the resource drove 60% of the miles, his rate of pay is multiplied by 60% of the revenue amount.

In many cases, settlement miles are determined by miles calculated by a third-party mileage application to which TMWSuite has an interface. To find the mileage between two locations, TMWSuite first looks to its own mileage table. If it cannot find the mileage there, the system tries to find a match in a third-party mileage database. If the mileage is found, it is stored in TMWSuite's own mileage database for future reference.

TMWSuite places mileage figures in separate mileage "buckets" based on the type of interface used. For example, when looking up ALK Shortest miles, the system saves the mileage amounts to the “ALK Shortest bucket.” Similarly, for lookups of ALK Practical miles, the system places the mileage amounts in the “ALK Practical bucket.” During the rating process, these mileages subsequently can be adjusted for specific rating scenarios.

You must configure the system to use miles from the correct mileage interface when trips are rated. It is possible to use multiple mileage interfaces for pay purposes, or to enter mileage amounts manually. It is also possible to calculate $/mile rates based on hub miles, which reflect tractors odometer readings.

The following topics describe how to set up mileage interface defaults, as well as rate-specific overrides. Also provided is a listing of alternate ways that you can have the system apply mileage when it calculates pay based on miles.