TABLE OF CONTENTS
- The Shipment File
- Shipment File Fields Table
- The TransportationModeler Truck File
- TransportationModeler Truck File Fields Table
- TransportationModeler Distance File
- The Rate File
- Rate File Fields Table
The TransMod files are used to provide the software specifics concerning shipment volumes, fleets available, shipment modes and rates, shipment rules, pickup locations, and destinations, volumes, and availability. Creating and/or updating these files are key to generating the best possible shipment solution. The program utilizes data from the following files:
Shipment File: The Shipment File is normally a tab-delimited text file (.xlsx or .xls) or a comma-delimited file (.csv). It is a composite list of all customers, order volume, and frequency, typically created from an Order File.
TransportationModeler Truck File: The Truck File contains information relating to the delivery fleet, including driver and truck assignments, availability, start, and end times, vehicle capacities, work rules, distribution centers or pool points, etc.
TransportationModeler Distance File: The Distance File contains distances as well as drive times from each pickup point to each stop, and/or distances from stop to stop.
Rate File: The Rate File contains transportation rates by mode of transport and volume, used to help calculate transportation costs for the shipments listed in the Shipment File.
The Shipment File
The Shipment File identifies the specific shipments that need to be scheduled, where the shipments will originate (Origin Point), deliver or pickup (Destination point), volumes to be shipped, time/date limitations or expectations, etc.
If you already have a Shipment File or a spreadsheet with the required information, it can be used in the project as long as it contains the required data columns, or a new Shipment File can be created that will automatically populate the necessary header columns and allow manual input of all data. Use the Shipment File Fields Table to assist in completing the required columns. Additional (optional) data fields can also be included in the Shipment File, if needed (ref. Stop File Fields and Descriptions Table).
Create/Update a Shipment File
From the menu, click File > Open > Shipment, or File > New > Shipment.
Enter the required data onto the spreadsheet, or double-click on the first cell to open the Shipment Dialog box, allowing entry of all necessary data per shipment in one window.
Geocode the Shipment File to locate the correct Lat/Long for each record listed in the file (Ref. Geocoding Records).
When completed, the file should be saved in the project folder (DirectRoute Data Directory).
Shipment File Fields Table
The TransportationModeler Truck File
The Truck File is a spreadsheet that contains all the information about the fleet (s) that could be used to make deliveries. Each row in the file represents a truck on which the shipments could be loaded. Some of the key fields in this file include vehicle Origin point, type, capacity, availability, work rules, and cost factors.
A new Truck File can be created that will automatically populate the necessary header columns and allow manual input of all data. Use the TransportationModeler Truck File Fields Table to assist in completing the required columns.
Create/Update a Truck File:
Click File > New > Truck from the menu.
A new spreadsheet will display with the required column headings.
Enter the vehicle data directly into the spreadsheet, or double-click on the first cell to open the Truck Dialog box, allowing entry of all necessary data per vehicle.
Geocode the completed file to locate the Lat/Long, if needed (Ref. Geocoding Records).
When completed, the file should be saved in the project folder (DirectRoute Data Directory).
NOTE: Address fields should only be used for Private Fleet vehicles, but should remain blank/empty for Common Carrier vehicles. Address, City, State, and ZIP are optional if Latitude/Longitude is known, however, if geocoding is to be used, then at least one field (City, State, or ZIP) must be populated. IF USING COMMON CARRIER VEHICLES: Cost factors do not need to be included in the Truck File, as this information will be listed in the Rate File. IF USING PRIVATE FLEET VEHICLES: After the Shipment and Truck Files have been prepared, a Distance File should be generated to be used in the Solution build (not used with Common Carrier vehicles.
TransportationModeler Truck File Fields Table
REQUIRED FIELDS | DESCRIPTION |
TrkID | Truck ID entry may be a number, truck name, driver name, or vehicle name; any type of entry is acceptable |
Available | TRUE or FALSE; must be set to TRUE to make the vehicle available for to use |
One-way | TRUE or FALSE. Set to TRUE for vehicles that terminate at the last stop, not returning to the depot (Common Carrier); set to FALSE if the vehicle will return (Private Fleet). |
Redispatch | TRUE or FALSE. Set to TRUE if vehicle will be re-dispatched if time remains in the workday; set to FALSE if Redispatching is not used |
Capacity/Volume | The maximum capacity/volume that a vehicle may carry. Should be the same as the Volume1 type used in the Shipment File (weight, cases, units, pallets, cubes, etc.) to determine when the vehicle is full. |
EDate | The earliest day, from the dispatch date, a vehicle may depart (date of Dispatch is DAY 1). One day vehicles may have an Edate of 1-7, depending on which day of the Dispatch cycle they are released to proceed. |
LDate | The latest date a vehicle must return to the terminal; 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. |
WorkDay | Sets the hours in a normal work day; overtime rates begin after the work day has been completed. |
NormalStart | The normal start time of the work day for the vehicle |
MaxWorkTm | The maximum time a vehicle may be out before returning to the depot. |
MaxDriveTm | The maximum drive time per shift before a layover is implemented. |
Longitude | leave blank if using Common Carrier |
Latitude | leave blank if using Common Carrier |
RECOMMENDED FIELDS | DESCRIPTION |
MinLayover | The minimum number of hours a vehicle can layover. |
MaxLayover | The maximum number of hours a vehicle can layover. |
MaxLayovers | The maximum amount of layovers allowed per route. |
City | City of the address (leave blank if using Common Carrier) |
State | State of the address (leave blank if using Common Carrier) |
Zip | Zip code of the address (leave blank if using Common Carrier) |
USEFUL FIELDS | DESCRIPTION |
Symbol | Symbol type to appear on the map |
Size | Size of symbol to appear on the map |
Color | Color of symbol to appear on the map |
USE IF DATA DICTATES | WHEN TO USE |
MinTm | If redispatch is set to TRUE |
TurnTm | If redispatch is set to TRUE |
SpEq | If implementing territories, zone routing, special equipment needs, custom sequencing, or backhauls |
EarStart | The earliest time (Military Time) vehicle may leave the terminal to begin a route. |
LatStart | The latest time (Military Time) vehicle must be out of the terminal. |
LatFinish | The latest time (Military Time) vehicle must return to the depot. Violation of the return time will result in a Return Time Violation. |
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. |
Brk1Duration | The break duration for driver break times. Enter times in decimal or whole number format. Example: Half-an-hour = .5, 15 minutes would be .25, etc. |
PreTrip | Used in accordance with DOT rules; time (minutes) added to start of each trip. |
PostTrip | Used in accordance with DOT rules; time (minutes) added to the end of each trip. |
POPULATED BY RATE ORDERS FUNCTION | DESCRIPTION |
TLMinCharge | Minimum charge applied for shipment by Truckload |
TLRate | The Truckload rate per mile. Example: $2.5/mile, is input as 2.5 |
TLTeamMinCharge | Minimum charge applied for shipment by Team |
TLTeamRate | The Team rate per mile. Example: $2.5/mile, is input as 2.5 |
LTLCost | Cost per pound to ship via LTL |
LTLTransitTime | Min time required to transport via LTL (hours). Example: 72.00 = three days |
Distance | The distance in miles between Origin and Destination |
POPULATED BY THE SOLUTION | DESCRIPTION |
Rt1 (Leg) | The Origin Route# |
Seq1 | The Origin Sequence# (order of loading) at Origin |
Rt2 (Leg) | The Destination Route# |
Seq2 | The Destination Sequence# (order of loading) on Destination Route |
TransportationModeler Distance File
The Distance File contains a record of distances and drive times between the pick-up point (terminal, DC, etc.) and every city in the Stop File (stem distance), and/or pick-up point to every stop, and from stop to stop. When a Distance File is used in the routing process, DirectRoute will calculate the distances and drive times between each stop location based on the entries in this file.
If a Distance File is not used, DirectRoute will calculate distances and drive times using an adjusted straight-line distance (as the crow flies) between locations. When there is a Distance entry for a pair of Stops, the software will use the Distance and Drive Time listed in the file, instead of calculating distances based on Lat/Long Coordinates, or other barriers that may be present. A Distance File can also be generated to record Stem mileage, the Distance between the terminal and each city listed in the Stop File.
Before beginning any type of routing project, or generating a new Distance File, it is a good idea to review and edit, if necessary, the current Distance File settings in use by the software.
From the menu, click File > Preferences > PreProcess > Generate Distance File.
Use the Distance File Settings Table to assist in updating each item, as necessary.
Click OK when all selections are completed.
For more information or instructions on generating a Distance File, see Generate a Distance File.
The Rate File
The Rate File is a comma-delimited file with a .rate extension that contains the costs associated with shipments for each mode or type of transportation between two points (Origin and Destination). The file will be called upon by the software to apply rates and determine the best mode of transportation for each shipment listed in the Shipment File.
The information used in the Rate File should be updated from time to time to ensure the most accurate, current rates are reflected. The sources of rate information for this file vary and may come from carrier bids, contract costs already sourced, Private Fleet cost records, and/or whichever means are normally employed.
A new Rate File can be created that will automatically populate the necessary header columns and allow manual input of all data. Use the Rate File Fields Table to assist in completing the required columns.
Click File > New > Rate File from the menu.
To edit/update an existing Rate File, select File > Open and the file’s name from the list of available files.
The file will open with the required column headings listed at the top.
Enter the necessary data directly into the spreadsheet under each column listed.
When completed, the file should be saved in the project folder (DirectRoute Data Directory).
Rate File Fields Table
FIELD NAME | DESCRIPTION | REQUIRED OR OPTIONAL |
Mode | Type of transport. TL = Truckload, LTL = Less than Truckload, PF = Private Fleet | Required |
Origin | The point from which a shipment starts. Enter the two-letter state abbreviation if using Origin Type State; enter the Zip Code if using Origin Type Zip, enter the City name if using Origin Type City. | Required |
Origin Type | The field type describing point of origin (City, State, or Zip) | Required |
Destination | Where the shipment is going. Enter the two-letter state abbreviation if using Destination Type State; enter the Zip Code if using Destination Type Zip, enter the City name if using Destination Type City. | Required |
Destination Type | The field type describing point of origin (City, State, or Zip) | Required |
FgtClass | Freight Class; enter the numerical freight class code for the shipment. Example: 60 = car parts, 110 = cabinets, 85 = crated machinery, etc. | Required |
Tariff | Input tariff information for CZARLITE. When used, the system will pull rates from CZARLITE instead of using pre-defined rates from the Rate File. | Optional |
AdjustmentFactor | Adjustment allowance, if any. Used by rateware to adjust rates/apply discounts or can be used to off-set pre-defined rates in the Rate File. | Optional |
Minimum | Minimum charge, if any, the carrier may charge. | Optional |
FSCType | Fuel Service Charge. User-defined code used to designate the type of Fuel Service Charge to be assessed. Example: Mileage based, percent-based, etc. | Optional |
FSCRate | Fuel Service Charge rate. An amount added to the freight invoice, above the starting point of the base freight rate. | Optional |
RateType | Value used to calculate the rate. For LTL (based on weight) = $/Weight For TL (based on miles/distance) - $/Distance | Required |
Rate1/ UpperRange1 | Used to input incremental rate charges, up to 10 increments (Rate2, Rate3, etc.); enter the rate and rate type. Example: A carrier presents a price list based on distance. 0–500 miles = $3/mile, enter Rate1 = 3, UpperRange1 = 500 501–750 miles = $2.5/mile, enter Rate2 = 2.5, UpperRange2 = 750 | Optional |
DropStopCount1 | The stop count number at which the carrier begins to assess additional fees for subsequent stops. Enter subsequent incremental stop counts as DropStopCount2, DropStopCount3, etc. | Optional |
DropCost1 | The fee assessed for DropStop1. Each subsequent DropStopCount in the record should also have a corresponding DropCost field (DropCost2, DropCost3, etc.). | Optional |
Service Time | Minimum time required to transport via LTL, in hours. Example: 72.00 is three days, or 72 hrs. Adds the time to the LTL Transit Time field in the Shipment File. | Optional |
Rating Error | System generated error message | System Generated |
NOTE: SMC3 Rateware XL is required to rate LTL shipments in TransportationModeler.