For a sample Truck File, see About Route Files.
| FIELD NAME | DESCRIPTION | REQUIRED IN DIRECTROUTE |
| TrkID | Truck ID entry may be a number, truck name, driver name or what is of most importance to the user (DirectRoute identifier) | yes |
| LoadID | LoadID entry may be a number, truck name, driver name or what is of most importance to the user (DRTrack identifier) | no |
| Territory | Territory entry may be a number, truck name, driver name or any reference to a geographic grouping of stops (req'd for TerritoryPro) | no |
| Available | This must be set to TRUE in order to make the vehicle available for DirectRoute to use in the routing solution. | yes |
| OneWay | Set to TRUE for vehicle which will routed out, but not return to the depot. Set to FALSE if the vehicle will return to the depot upon completion of the route. | no |
| Redispatch | Set to TRUE if vehicle will be sent back out, on another leg of the same route, if time remains in the workday. Set to FALSE if Redispatching is not used. | no |
| MinTm | Minimum Time is used with Redispatching. This reflects the amount of time (hours) that must remain in a workday upon return to the depot, in order to redispatch the vehicle. | no |
| TurnTm | Turn Time is used with Redispatching. The amount of time (minutes) it takes to reload or any required time at the depot, between routes, before Redispatching. | no |
| SpEq | Special Equipment Codes, along with Equipment Codes in the Stop File, are alphanumeric, used to identify special considerations for the vehicle. | no |
| Volume 1 (Cube) | The maximum volume/quantity that a vehicle may carry. This is a user defined field in Preferences/Configuration/Volumes settings, and can be any quantity type (i.e. weight, cases, units, pallets, cubes, etc.). Should be the same as the Volume1 type used in the Stop File, to determine when the vehicle is full. | yes |
| Volume 2 (Weight) | The maximum volume/quantity that a vehicle may carry. This is a user defined field in Preferences/Configuration/Volumes settings, and can be any quantity type (i.e. weight, cases, units, pallets, cubes, etc.). Should be the same as the Volume1 type used in the Stop File, to determine when the vehicle is full. | no |
| UnldPerf% | Unload Performance regulates changes to the Unload Rate. When a value is entered into this field, the unload rate will either increase or decrease. 100% is the default value. An increase to 110 will increase the Unload Rate by 10% (shorter time to unload). A decrease to 90 will decrease in the Unload Rate by 10% (increase the time to unload). | no |
| MiCost | Mileage Cost is estimated cost per mile to operate this vehicle and is typically considered the variable component, such as fuel or non-preventative maintenance | yes |
| HrCost | Hourly Cost is the estimated hourly cost of the driver for this vehicle. | yes |
| OTCost1 | Overtime Costs is the cost per hour added if the time to complete the route exceeds the time set for WorkDay. | no |
| OTCost2 | Overtime Costs is the cost per hour added if the time to complete the route exceeds the time set for WorkDay. | no |
| OTCost3 | Overtime Costs is the cost per hour added if the time to complete the route exceeds the time set for WorkDay. | no |
| OTCost4 | Overtime Costs is the cost per hour added if the time to complete the route exceeds the time set for WorkDay. | no |
| OTHrs1 | The level at which overtime hours are calculated and works in conjunction with OTCost1. Example: OTHrs1 = 2 (pays in 2hr increments) and OTCost1 = 5, then the cost for the first two hours of overtime is $5. | no |
| OTHrs2 | The level at which overtime hours are calculated and works in conjunction with OTCost1. Example: OTHrs1 = 2 (pays in 2hr increments) and OTCost1 = 5, then the cost for the first two hours of overtime is $5. | no |
| OTHrs3 | The level at which overtime hours are calculated and works in conjunction with OTCost1. Example: OTHrs1 = 2 (pays in 2hr increments) and OTCost1 = 5, then the cost for the first two hours of overtime is $5. | no |
| OTHrs4 | The level at which overtime hours are calculated and works in conjunction with OTCost1. Example: OTHrs1 = 2 (pays in 2hr increments) and OTCost1 = 5, then the cost for the first two hours of overtime is $5. | no |
| UnldHrCost | Cost to unload per hour. | no |
| DropCost | Drop Cost is the drop cost for each stop. User input in Preference settings File/Preferences/Routing/General (Drop Count). A number in this section will add a drop cost to each stop on the route. | no |
| WaitHrCost | The cost per hour, if a vehicle must wait at the stop before making its delivery. | no |
| UnitCost | The cost of each unit delivered (volume). | no |
| FixedCost | Costs that do not change, such as Monthly Tractor Rental or Monthly Lease divided by 20 | yes |
| LayoverCost | The cost applied when a vehicle must layover before completing its route and returning to the terminal. | no |
| EarStart | The earliest time (Military Time) a vehicle may leave the terminal to begin a route. | no |
| EDate | The earliest day, from the dispatch date, a vehicle may depart. The Date of Dispatch is DAY 1. A one (1) would be entered in this field if the trucks could leave on the first day of dispatch. One day vehicles may have an Edate of 1-7, depending on which day of the Dispatch cycle they are released to proceed. | yes |
| LatStart | The latest time (Military Time) a vehicle must be out of the terminal. | no |
| LatFinish | The latest time (Military Time) a vehicle must return to the depot. Violation of the return time will result in a Return Time Violation. | no |
| LDate | The latest date a vehicle must return to the terminal. This day is calculated from the dispatch date. A one day route may have an Edate of 1, but also an Ldate of 1, while a weekly route may have an Edate of 1 and an Ldate of 7. | yes |
| WorkDay | Sets the hours in a normal work day. Overtime rates begin after the work day has been completed. | no |
| NormalStart | The normal daily start time of the vehicle. The Load algorithm will obey this setting, but when Between Route Optimization is run, that algorithm may adjust the start time to a more cost effective time. | no |
| Brk1Start | The break start refers to how far into the shift/route the break should start. If driver should take a break four hours into the route, enter the number 4. Note: Up to five break fields can be used. | no |
| Brk1Duration | The break duration is used to establish driver break times. Times should be entered in decimal or whole number format. Example: Half-an-hour = .5, 15 minutes would be .25, etc. Entries are optional and up to five break fields (duration and start) can be entered. | no |
| Brk2Start | The break start refers to how far into the shift/route the break should start. If driver should take a break four hours into the route, enter the number 4. Note: Up to five break fields can be used. | no |
| Brk2Duration | The break duration is used to establish driver break times. Times should be entered in decimal or whole number format. Example: Half-an-hour = .5, 15 minutes would be .25, etc. Entries are optional and up to five break fields (duration and start) can be entered. | no |
| Brk3Start | The break start refers to how far into the shift/route the break should start. If driver should take a break four hours into the route, enter the number 4. Note: Up to five break fields can be used. | no |
| Brk3Duration | The break duration is used to establish driver break times. Times should be entered in decimal or whole number format. Example: Half-an-hour = .5, 15 minutes would be .25, etc. Entries are optional and up to five break fields (duration and start) can be entered. | no |
| Brk4Start | The break start refers to how far into the shift/route the break should start. If driver should take a break four hours into the route, enter the number 4. Note: Up to five break fields can be used. | no |
| Brk4Duration | The break duration is used to establish driver break times. Times should be entered in decimal or whole number format. Example: Half-an-hour = .5, 15 minutes would be .25, etc. Entries are optional and up to five break fields (duration and start) can be entered. | no |
| Brk5Start | The break start refers to how far into the shift/route the break should start. If driver should take a break four hours into the route, enter the number 4. Note: Up to five break fields can be used. | no |
| Brk5Duration | The break duration is used to establish driver break times. Times should be entered in decimal or whole number format. Example: Half-an-hour = .5, 15 minutes would be .25, etc. Entries are optional and up to five break fields (duration and start) can be entered. | no |
| MaxWorkTm | The max time a vehicle may be out before returning to the depot. | yes |
| TargetWrkTm | The target work time (shift) for each vehicle. The Load algorithm will obey this setting, but when Between Route Optimization is run, that algorithm may adjust the Total Work Time on each route to a more cost effective amount. | no |
| MaxDriveTm | The maximum drive time per shift on a route before a layover is implemented. | yes |
| MinLayover | The minimum number of hours a vehicle can layover. Recommend 10 for single driver, 0 for team drivers. | no |
| MaxLayover | The max number of hours a vehicle can layover. Recommend 18 for single driver, 0 for team drivers. | no |
| MaxDrvTmB4Layover | Used by DirectRoute to determine how long a vehicle must drive before a layover can be implemented. | no |
| MaxLayovers | The maximum amount of layovers allowed per route. (i.e # of Occurances) | no |
| Longitude | The longitude and latitude fields are coordinates that define where the truck terminal is located. DirectRoute geocoding will create these coordinates using the supplied Address, City & State info) | yes |
| Latitude | The longitude and latitude fields are coordinates that define where the truck terminal is located. DirectRoute geocoding will create these coordinates using the supplied Address, City & State info) | yes |
| Address | if Geocoding is required, we need the Address where the Depot, Terminal or Distribution Center is located. | yes |
| City | Name of the city (Address). This field can be used in conjunction with the distance file to determine distances and drive time. Required to geocode. | yes |
| State | 2 letter state (Address) abbreviation. | yes |
| Zip | The zip code (Address). Can be used for geocoding in conjunction with the Address field, or geocoding by 5-Digit or 9-Digit Zip. | yes |
| LocationTimeZone | Populated by DirectRoute during the Geocoding process if set to true in Preferences > Geocode Options | no |
| Zone | A percentage adjustment to the drive time. Default is 100 = normal rate of speed. An increase to the drive time will lower speed; a decrease to drive time will increase speed. Example: A value of 110 would increase the drive time by 10%, hence lowering the speed by 10%. A value of 90 would decrease drive time by 10%, increasing speed by 10%. The speed adjustment is only applied to the first 8 miles of each route segment (from Depot). Example: If all customers in downtown Chicago have a value of 110 in this field, DirectRoute will increase drive time for the stops in downtown Chicago (within the 8 mile radius), while lowering the speed of travel. | no |
| Symbol | Specifies the symbol that represents the stop, displayed on the map when the Stop File is open. Symbols are chosen while in the Stop File; DOUBLE CLICK on the column/field to open the dialog box; make your selection and LEFT CLICK on OK. | no |
| Size | Specifies the size of the symbol to be displayed on the map. Default size is 8. | no |
| Color | Specifies the color of the chosen symbol. Select colors in the same fashion/at the same time as selecting symbols. | no |
| PreTrip | Used in accordance with DOT rules; time (minutes) added to the start of each route. | no |
| PostTrip | Used in accordance with DOT rules; time (minutes) added to the end of each route. | no |
| DeviceID | PeopleNet device ID, if populated can be used to preassign a device to a TrkID / route | no |
| DriverID | DRTrack driver ID, if populated can be used to preassign a driver to a TrkID / route | no |
| AMStart | Set AM start time to adjust speed to account for heavier/lighter traffic. | no |
| AMEnd | Set AM end time to adjust speed to account for heavier/lighter traffic. | no |
| AMAdj | Set drive time adjustment for AMStart and AMEnd. AM/PM Adjust works the same as Zone; increase the number (110) to increase the drive time by 10 percent. In turn the speed is decreased by 10 percent. The radius is based on the rush hour distance setting in the Preferences. Zone is hard coded to eight miles, while AM/PM Adjust is based on the rush hour distance. Example: If rush hour distance is set to 30 miles, it will apply to the truck for a 30 mile radius from the depot. If it is set on the customer in the Stop File, it will be a 30 mile radius from the customer. | no |
| PMStart | Set PMStart to adjust speed to account for heavier or lighter traffic. | no |
| PMEnd | Set PMEnd to adjust speed to account for heavier or lighter traffic. | no |
| PMAdj | Set drive time adjustment for PMStart and PMEnd. See AMAdj for additional info. Note: AM/PM Adjust works the same as zone; increase the number (110) to increase the drive time by 10 percent. In turn the speed is decreased by 10 percent. The radius is based on the rush hour distance setting in the Preferences. Zone is hard coded to eight miles, while AM/PM Adjust is based on the rush hour distance. Example: If rush hour distance is set to 30 miles, it will apply to the truck for a 30 mile radius from the depot. If it is set on the customer in the Stop File, it will be a 30 mile radius from the customer. | no |
| Country | Blank assumes USA, need to input 3 digit Country Code if using outside of USA (Ex. CAN or MEX) | no |