FIELD | DESCRIPTION | REQUIRED, OPTIONAL, OR RECOMMENDED | ||||||||||||||||||
Account Name | Name of the Customer (stop). | Required | ||||||||||||||||||
ID1 | Primary unique identifier for the stop (Account#, Customer#, etc.) | Required | ||||||||||||||||||
ID2 | Secondary unique identifier for stop (Order#, Store#, etc.) | Populated by the Volume Allocation Algorithm | ||||||||||||||||||
Address | Street Address of the stop; used to geocode. | Required | ||||||||||||||||||
City | City where address is located; used to geocode, and in the Distance File. | Required | ||||||||||||||||||
State | Two-letter state abbreviation for the address; used to geocode. | Required | ||||||||||||||||||
Zip | Zip Code of the address; used to geocode. | Required | ||||||||||||||||||
FixedTime | Mandatory time that all vehicles must spend at the stop; typical range is 15 to 45 (minutes). | Recommended | ||||||||||||||||||
EqCode | Alphanumeric code used to designate special equipment or requirements for the Stop (lift gate, refrig, etc.); used with Truck File field SpEq. | Optional | ||||||||||||||||||
Volume1 | The quantity of volume to be delivered; can be any quantity type (weight, cube, pallets, cases, etc.). | Required | ||||||||||||||||||
UnldRate (UnldVol1) | Amount of time it takes to unload Volume1 (hours). Example: Volume1 = Cases (UnldCases), and 1 hr = unload 1000 cases, and Veh Capacity = 2000 cases then the unload rate would = 2 (2000 ÷ 1000/per hr.) Note: SchedulePro will add UnldRate to Fixed Time, to determine how long the truck will be at the stop. | Optional | ||||||||||||||||||
Open1 | Earliest time of day delivery can be made to the stop (0000 - 2400). | Required | ||||||||||||||||||
Close1 | Latest time of day delivery can be made to the stop (0000 - 2400). | Required | ||||||||||||||||||
Pattern1 | Days of the week the stop can accept delivery (SMTWRFA); used with Open1 and Close1 to determine days/times that deliveries can be made. | Required | ||||||||||||||||||
Rt ID | The route number to which the stop is assigned; discovered during the build. | Not used in Schedule Pro | ||||||||||||||||||
Seq | The sequence in which the stop is loaded on the route; discovered during the build. | Not used in SchedulePro | ||||||||||||||||||
Longitude | Longitude of the stop, discovered during the geocode process. | Required | ||||||||||||||||||
Latitude | Latitude of the stop, discovered during the geocode process. | Required | ||||||||||||||||||
Symbol/Size/Color | The symbol (size and color) displayed on the map represents the stop. Symbols are chosen from the stop File; Double-click the customer record to open the dialog box; select the symbol, size, and color, then click OK. | Recommended | ||||||||||||||||||
MinDaysBetween Deliveries | The minimum number of days required between deliveries to the stop. Example: Customer requires deliveries no more than once a week, then input 7 (number of days). | Required for the Regular Algorithm, not used with Volume Allocation | ||||||||||||||||||
MaxDaysBetween Deliveries | The maximum number of days allowed between deliveries. Example: Customer requires deliveries at least every two weeks, then input 14 (number of days). | Required for the Regular Algorithm, not used with Volume Allocation | ||||||||||||||||||
Frequency | The number of times a stop is serviced during the planning period (enter the number conversion)
| Required |
SchedulePro Stop File Fields Table Print
Modified on: Thu, 22 Aug, 2024 at 2:15 PM
Did you find it helpful? Yes No
Send feedbackSorry we couldn't be helpful. Help us improve this article with your feedback.