Order File Data Table
Because the Account Master exists in the database, data elements that are required for routing aren’t necessarily required in the order file. Any information missing from the order file will automatically populate from Account Master information. The order file can contain simple order summary data, or be as detailed as line-level data.
REQUIRED OR OPTIONAL
The name of the customer/business (stop) to be delivered.
The name of a contact at the customer stop.
Telephone number at the stop location. If the Area code is included, the software can use it for geocoding.
Primary unique identifier for the customer/stop (Acct#, Customer#). User defined (Preferences→Configuration) used in extract process.
Secondary unique identifier for the customer/stop. Example: Store#, Stop#. User defined field in Preferences→Configuration.
Tertiary unique identifier for the customer/stop. Example: Line Item, SKU. User-defined in Preferences→Configuration.
Street Address for the customer. Address, along with City, State, and Zip are used to geocode by address. Also used by Address Cleanup.
Additional Address information. Example: Suite#, building#, Door#, Dock#.
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.
2 letter state (Address) abbreviation. Example: WA, CA, OR. Required to geocode.
The zip code (Address). Can be used for geocoding in conjunction with the Address field, or geocoding by 5-Digit or 9-Digit Zip.
Used to identify a required/mandatory time that all vehicles must spend at the stop (in addition to unload rate/time). Can be used to account for completing required paperwork. Input Fixed Time in minutes; may be different for each customer. Example: An entry of 15 would require the truck to be at the stop for 15 minutes, in addition to the time calculated by the UnldRate. Total time at the stop will be calculated by the software by adding these two fields together. Note: DR will route without this field, but in practice a Fixed Time is needed as the truck will have to stop for certain amount of time to unload (and perform other activites). Typical range is 15-45 (15 to 45 minutes). Enter number in minutes.
Size Restriction will inform the software that this is the maximum size or volume for a vehicle that may deliver to this stop. Using a size restriction will limit which truck size the customer load can be put on. Example: A quantity of 20,000 would mean that the customer load could only be put on trucks with a capacity of 20,000 or less in (Volume 1 field) the Truck File.
An alphanumeric code (unlimited number of characters) used to designate special equipment or requirements for a stop (lift gate, refrigerated compartment, etc.). Corresponding Truck File field: SpE. When EqCodes are used, the software will only load the stops on a vehicle with a matching SpEq code listed in the Truck File. Example: If a stop requires a lift gate in order to complete delivery, place a code in the EqCode field that designates lift gate, and use the same code in the SpEq field on a truck in the Truck File. It is possible to combine the use of several EqCodes, but each code should be separated by a dash (i.e. AJ-BH-HH-XX). If there are no special requirements for a stop, this field should be blank. Note: There are also special EqCodes that can be utilized for Back Hauls, prioritizing and sequencing of stops, territory codes and exclusion codes.
The volume to be delivered; user defined field (Preferences→Configuration) can be any quantity type (weight, cube, pallets, cases, etc.). If no volume type is entered, the software will load all stops on one route, or until it reaches the maximum stops per route, as defined by the user. The capacity fields in the Truck File correspond to the volume fields in the Stop File. Example: Volume used is Cases; the column heading appears in the Stop File as Cases. Capacity 1 column heading in the Truck File will also appear as Cases. Note: Must be at least one (1) volume field in use, even if left blank.
Identifies the amount of time it takes to unload Volume1 value, in hrs. Example: Volume1 = Cases. The field appears in the Stop File as UnldCases. it takes one hour to unload 1000 cases. A truck that carries 2000 cases would have an unload rate of 2 (2000 ÷ 1000/per hr.). The UnldRate time is added to the Fixed Time. The UnldRate heading will mirror the volume name defined in the Preferences→ Configuration→Volumes (Weight = UnldWeight, Cases = UnldCases).
TRUE or FALSE. When this option is set to TRUE, a vehicle must reach the stop, deliver and complete unloading before the Time Window closes (including Fixed Time plus UnldRate).
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. Zone is hard coded to eight miles. 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. Example (Truck File): 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 (Stop File): If all customers in downtown Chicago have a value of 110 in this field, the software will increase drive time for the stops in downtown Chicago (within the 8 mile radius), while lowering the speed of travel.
Set AM start time to adjust speed to account for heavier/lighter traffic.
Set AM end time to adjust speed to account for heavier/lighter traffic.
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 (Preferences→Routing→General). 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.
Set PMStart to adjust speed to account for heavier or lighter traffic.
Set PMEnd to adjust speed to account for heavier or lighter traffic.
Set drive time adjustment for PMStart and PMEnd. See AMAdj for additional info.
Earliest time of day delivery can be made. Using Military Time format (0000-2400), delivery time windows are entered in the Open1 and Close1 fields. Multiple Time Windows can be established (up to ten), and are defined as Open1, Close1, Pattern1; Open2, Close2, Pattern2; Open3, Close3, Pattern3 and so forth. Example: Customer can receive deliveries between 800 and 1130 on Sunday, Wednesday, and Saturday. This corresponds to Open1=0800, Close1=1130, and Pattern1=SWA.
Latest time a delivery can be made. See Open1 for additional info.
Days of the week when the customer will accept deliveries. Time Windows are entered as patterns of opening and closing times and days of the week (SMTWRFA) that define when the customer will accept deliveries. Example: Customer can receive deliveries between 800 and 1130 on Sunday, Wednesday, and Saturday. This corresponds to Open1=0800, Close1=1130, and Pattern1=SWA. S=Sunday, M=Monday, T=Tuesday, W=Wednesday, R=Thursday, F=Friday, A=Saturday
(MM/DD/YY). May be used to ensure that a stop is not serviced before a specific date, or when used in combination with LatestDate, used to ensure the stop is delivered within a specific time window, and can allow multi-day/week deliveries based on date versus time window only. If this column is blank, it will be ignored.
(MM/DD/YY) Used in conjunction with EarliestDate; determines the latest the date that the stop may be serviced. May be the same date as EarliestDate if there is only one day in which the stop may be serviced. If this column is blank it will be ignored.
Used to activate the Soft TimeWindows function within the software, allowing stops to be loaded before the hard time window. A penalty cost is counted against the uses of the buffers. Note: EarlyBuffers and LateBuffers are used to expand time windows.
Used to activate the Soft Time Windows function within the software. allowing stops to be loaded after the hard time windows. A penalty cost is counted against the use of the buffers. Note: EarlyBuffers and LateBuffers are used to expand time windows.
Used in conjunction with the EarlyBuffer and LateBuffer, is used to calculate and apply a penalty cost to stops that use the buffers. During the Optimization process, the software will try to move a stop with a penalty cost to another route in an attempt to eliminate the penalty (calculated per hour). Enter dollar amount per hour.