Trip types and how Settlements handles them
8. Trip types and how Settlements handles them
In TMWSuite, there are several types of trips. For example:
· Solo trips
· Team trips
· Split trips
· Consolidated trips
· Zero mile trips
· Fixed mile trips
· Hub mile trips
The following sections describe these various types of trips and how the system processes pay for them in the Settlements application.
Solo trips and team trips 8.3
Split trips 8.4
Looking up a split trip in the Trip Settlements Folder 8.5
Looking up split trips in the Trips Ready to Settle queue 8.6
How the system allocates percent of revenue pay for split trips 8.6
[Settlement] MileageRatio 8.7
Override of mileage allocation feature 8.7
How the system calculates pay when Override %Aloc is not selected 8.8
Example of how the system calculates pay if Override %Aloc is selected 8.9
Inactivating mileage allocation for revenue-based accessorial pay 8.10
[Settlement] PayFullAccessorialOnSplit 8.10
Settling the non-final leg of a uncompleted split trip 8.11
Consolidated trips 8.13
Configuring how consolidated trips are rated in Settlements 8.15
Indicating how the system is to apply rates based on shipper/consignee locations 8.15
[Settlement] CombinedOrdersUseShipCons 8.15
Indicating how the system is to apply rates based on commodity 8.18
[Settlement] CombinedOrdersUseOrderCommodity 8.18
How consolidated loads are shown in the Trips Ready to Settle queue 8.18
Calculating pay for trips with zero miles 8.20
Calculating intracity miles 8.20
[MileageInterface] DefaultIntraCityMileage 8.20
Computing zero mile trips 8.20
[Settlement] AllowZeroQty 8.20
Calculating pay for trips with fixed quantities 8.21
Recording fixed quantities for both Invoicing and Settlements 8.22
Recording fixed quantities for Settlements 8.23
Preventing mileage lookups for trips with fixed miles 8.24
Paying resources for canceled trips 8.25
Making an entry in the General Info Table 8.25
SettleCancelledTrips 8.25
Creating pay for cancelled trips 8.25
Solo trips and team trips
To determine whether a solo driver or a team handled a trip segment, the system checks for the presence of multiple drivers on a trip. One of the following occurs:
· If only one driver has been recorded, the system checks the pay rate entry for Single in Tm/Sgl field in the Assign Settlement Rates window. It uses this entry to search for a pay rate that has been set up for solo trips.
· If two drivers have been recorded, the system checks the pay rate entry for Team in Tm/Sgl field in the Assign Settlement Rates window. It uses this entry to search for a pay rate that has been set up for team trips.
Notes:
1. By default, if you are processing trips one-by-one in the Trip Settlements Folder, you will need to compute pay separately for the lead driver and the co-driver. To tell the system which driver you want to pay, you must select Driver or Co-Driver in the resource type drop-down located in the lookup tab.
2. You can also set up the system to calculate pay for both drivers on a team at the same time. For details, see:
Guide: Trip Settlements Guide | Chapter: Calculating Pay | Section: Calculating pay for a driver team
Split trips
There may be times when the resources used to start a trip are unable to or not intended to complete it. Whenever there is a change in driver and/or tractor for a trip, the dispatcher must split that trip into multiple trip segments. A trip segment is the portion of a movement that is executed by the same driver/tractor combination. (If a split involves a Hook Change Trailer (HCT) event, the change in trailer also causes the creation of a new trip segment.) In TMWSuite, a movement that consists of multiple trip segments is called a split trip.
When pay is calculated for a split trip, Settlements will determine pay based on the portion of the trip that was handled by each driver.
The following illustration shows how a split trip looks in Dispatch.
Looking up a split trip in the Trip Settlements Folder
The split trip shown above is associated with order 1479. When you look up this order in Settlements, the system prompts you to specify the trip segment for which pay is to be calculated.
When you highlight one of the trip segments and click OK, the system displays the stops associated with that trip segment. This illustration shows the first trip segment for order 1479.
Since DRV100 only executed the first three stops on the trip, those are the only stops for which he is to be paid.
Looking up split trips in the Trips Ready to Settle queue
When you look up trips in the Trips Ready to Settle queue, you will notice that each trip segment is listed separately. For example, in the illustration below, notice that order 1585 has two trip segments.
To open a trip segment, drag the order number from the queue to the Order Number field in the tab area of the Trip Settlements folder. For details, see:
Guide: Trip Settlements Folder Guide| Chapter: Looking up trips that are ready to be settled | Section: Using the Trips Ready To Settle queue to look up multiple trips
How the system allocates percent of revenue pay for split trips
If a driver has been assigned to a split trip and is paid a percent of revenue, the system uses the number of miles that the driver traveled on his segment of the trip to determine the appropriate revenue amount on which to base the driver’s pay. This reduction of the revenue amount based on percentage of miles driven is Settlements’ mileage allocation feature.
For example, suppose the following is true:
· A move consists of a total of 100 miles, and the billed line haul amount is $200.
· The move is split between Driver A and Driver B, both of whom get a percent of line haul revenue.
· Driver A drives 30 miles (30% of 100 miles), and Driver B drives the remaining 70 miles (70% of 100 miles).
Since Driver A drove 30% of the total miles, his rate of pay is multiplied by a reduced revenue amount of $60 ($200 x 30% = $60). Driver B drove 70% of the total miles; therefore, his pay is determined by multiplying his rate by $140 ($200 x 70% = $140). Driver B is allocated more of the revenue because he drove more miles. This example illustrates the mileage allocation that Settlements employs by default for split trips.
For the mileage allocation feature, you can have the system use all miles (empty and loaded) on the trip, or only loaded miles. An INI setting in the [Settlement] section of your TTS50 file allows you to configure the allocation method:
[Settlement]MileageRatio /
Applies to / TMWSuite: 2002.02_05.0090 and later
Description / This setting is applicable for calculation of percent of revenue pay for split trips. If a driver has been assigned to a split trip and is paid a percent of revenue, the system uses the number of miles that the driver traveled on his segment of the trip to determine the appropriate revenue amount on which to base the driver’s pay. This reduction of the revenue amount based on percentage of miles driven is Settlements’ mileage allocation feature.
This INI setting is used to configure the allocation method. It determines whether the system is to use all miles (empty and loaded) or only loaded miles.
Options / · TOTALMILES (default)
Use total miles (empty and loaded) for the mileage allocation.
· LOADEDMILES
Uses loaded miles only.
Override of mileage allocation feature
TMWSuite provides an override feature that allows you to inactivate the mileage allocation function used for split trips. The Override %Aloc check box is located on the rate header section of the Edit Settlement Rate Schedules Folder.
The mileage allocation override feature only affects primary and secondary rates that are based on a percent of revenue. When such rates are used for a split trip, the following will occur:
· If the Override %Aloc check box is unchecked (the default), the system will use the mileage allocation feature to determine the revenue amount for percent of revenue-based pay for split trips. The resource’s percentage will be multiplied by the adjusted revenue amount.
· If the Override %Aloc check box is checked, the system will multiply the resource’s percentage by the entire line haul or accessorial charge billed to the customer. In other words, the revenue amount will not be adjusted based on the number of miles traveled by the resource.
Although most TMWSuite customers will not want to override the mileage allocation function, the override feature is helpful for customers that use alternative methods of handling the equitable distribution of revenue among drivers who are paid a percent of revenue for split trips.
How the system calculates pay when Override %Aloc is not selected
The following illustration shows how the system handles pay computation for a split trip if the Override %Aloc check box is not selected on the primary and secondary rates used to calculate pay.
Mileage allocation feature is active
The system determines the total miles driven for all segments of a split trip. It then compares the miles traveled by each driver to determine the percentage each drove. This percentage is then used to adjust revenue amounts so that each driver is paid equitably.
For example, in the illustration above, Frank Roberts traveled 44% of the total miles; the other driver (whose portion of the trip is not shown here) drove the remaining 56% of the miles. Because Frank drove 44% of the total miles, the system allocated 44% of the revenue to him, as shown in the %Aloc column in the Revenue Recap area of the screen.
In the Pay Detail area of the screen, note that Frank’s line haul and accessorial pay is determined as follows:
Type of pay / Adjusted revenue based on mileage allocation / Driver’s rate of pay (% of revenue pay) / Resulting pay amount /Line haul / $1302.8256
($2,937.60 x 44%) / x / 50% / = / $651.41
Stop pay / $84.265
($190.00 x 44%) / x / 50% / = / $42.13
Trailer cleaning / $24.3925
($55.00 x 44%) / x / 50% / = / $12.20
Example of how the system calculates pay if Override %Aloc is selected
When the Override % Aloc check box is selected, the system will not reduce revenue amounts based on mileage allocation. In the illustration below, notice that the system determines that Frank Roberts drove 44% of the total miles (see the %Aloc column). However, the system does not adjust revenue when it calculates pay. Instead, the driver’s rate of pay is multiplied by the full revenue amount.
Mileage allocation feature is NOT active
In the Pay Detail area of the screen, note that Frank’s line haul and accessorial pay is determined as follows:
Type of pay / Revenue billed to customer / Driver’s percent ofpay / Resulting pay amount /Line haul / $2,937.60 / x / 50% / = / $1,468.80
Stop pay / $190.00 / x / 50% / = / $95.00
Trailer cleaning / $55.00 / x / 50% / = / $27.50
Note: If all drivers on a split trip have secondary rates for accessorials that are to be paid only if they are billed, all drivers will receive payment for those accessorials—even if they were not present at the stops where the accessorial labor occurred. This is true for resources paid via rates in the Rate Schedules application:
Inactivating mileage allocation for revenue-based accessorial pay
The mileage allocation feature is designed to work with both revenue-based line haul pay and revenue-based accessorial pay. However, an INI setting is provided that allows you to remove revenue-based accessorial pay from mileage allocation.
Most clients will not want to override the mileage allocation function for accessorials. However, some trucking companies use alternative methods of handling the equitable distribution of revenue among drivers who are paid a percent of revenue for split trips. An INI setting in the [Settlement] section of your TTS50 file allows you to disable mileage allocation for revenue-based accessorials:
[Settlement]PayFullAccessorialOnSplit /
Applies to / TMWSuite: 2002.01.0003 and later
Description / Determines whether the system is to employ the mileage allocation feature for revenue-based accessorial pay on split trips.
Options / · N (default)
Do not multiply the driver’s percentage by the total accessorial charge billed to the customer. Instead, use the mileage allocation feature to determine the percentage of miles that the resource traveled. Reduce the accessorial revenue by that percentage before multiplying the resource’s rate by the revenue amount.
Note: If needed, this setting can be overridden for a particular accessorial rate. To do so, select the Override %Aloc check box in the Edit Settlement Rate Schedule Folder.
· Y
Turn off the mileage allocation feature for revenue-based accessorial pay. Multiply the resource’s rate by 100% of the accessorial charge billed to the customer.
Note: This setting inactivates the Override %Aloc check box on the Edit Settlement Rate Schedule Folder for accessorial rates. Even if the Override %Aloc check box is cleared, the mileage allocation feature is not active.
Settling the non-final leg of a uncompleted split trip
TMWSuite can be configured to allow you to calculate pay for the completed legs of a split trip, even if the last leg of the trip is not yet complete and the order has not yet been invoiced. The configuration is set up in the GeneralInfo Table using the following two settings:
· STLMUSTINV
When you have Y set in the String1 field of the STLMUSTINV setting, the system will require that orders be invoiced before pay can be calculated.
· SPLITMUSTINV
This setting modifies the functionality of the STLMUSTINV setting.