For a sample Stop File, see About Route Files.

 

FIELD NAMEDESCRIPTIONREQUIRED IN DIRECTROUTE
NameTechnically called 'Name', anything could be used as Alias for Nameno
ContactStop / Customer contact nameno
PhoneStop / Customer contact phone #no
ID1Primary ID - Store # would be an Alias for ID1yes
ID2Secondary ID - Invoice # or Delivery # could be an Alias for ID2, needs to be unique by Branch and best if unique for entire DRTrack database, if usingno
ID3Tertiary ID - Most often thought as SKU #no
AddressLegal address of stop, used for geocodingno
Address2Suite, Building info…no
CityUsed for geocodingno
StateUsed for geocodingno
ZipRequired for use with internal PCMiler, Google Geocoding requires first digit of zipno
FixedTimeStop duration timeno
RtDirectRoute reserved fieldno
SeqDirectRoute reserved fieldno
SzRestrictionrelated to the Volume1 (primary volume) and the Max Capacity as setup in the Truck File and defined in Preferencesno
EqCodetons of uses, training will cover this in detail (Ex. - Liftgate or a Territory)no
CubeVolume - need at least one, can be named anything (i.e. Pallets, Pounds, Gallons, VolAlias1, etc.)yes
WeightVolume - need at least one, can be named anything (i.e. Pallets, Pounds, Gallons, VolAlias1, etc.)no
UnldCubeused for variable unload rate per hour, adds time to any already defined FixedTimeno
UnldWeightused for variable unload rate per hour, adds time to any already defined FixedTimeno
CloseTWif TRUE, stop must be completely unloaded or serviced by the Close timeno
Open1Military Time format of when stop is available for service / deliveryyes
Close1Military Time format of when stop is closed for service / deliveryyes
Pattern1Days that delivery can occur - SMTWRFA for each day of the weekyes
Open2Optional time for service / delivery - up to 10 Open/Close Patterns can be developedno
Close2Optional time for service / delivery - up to 10 Open/Close Patterns can be developedno
Pattern2Optional time for service / delivery - up to 10 Open/Close Patterns can be developedno
Longitudeif not provided, DirectRoute will populate during the Geocoding processyes
Latitudeif not provided, DirectRoute will populate during the Geocoding processyes
Symbolrecommended but not requiredno
Sizein pixels, size of stop iconno
Colorrecommended but not required, use for enhanced map interactionno
Selectedused to permanently mark a stop with a bounding square on the Mapno
EarliestDatefurther stipulates a day or range of days for the delivery to occur, uses MM/DD/YYYY formating, Pattern1 still appliesno
LatestDatefurther stipulates a day or range of days for the delivery to occur, uses MM/DD/YYYY formating, Pattern1 still appliesno
EarlyBufferAdditional time before Open1 that a stop could be serviced - in Hours (Ex. .25, .5, 1, 2 or 3). Used to activate the Soft TimeWindows function within the software, allowing stops to be delivered outside of the hard time window. A penalty cost should also be used in conjunction as it guards against the use of the buffers when they are not needed. Note: EarlyBuffers and LateBuffers are used to expand time windows.no
LateBufferAdditional time after Close1 that a stop could be serviced - in Hours (Ex. .25, .5, 1, 2 or 3). Used to activate the Soft TimeWindows function within the software, allowing stops to be delivered outside of the hard time window. A penalty cost should also be used in conjunction as it guards against the uses of the buffers when they are not needed. Note: EarlyBuffers and LateBuffers are used to expand time windows.no
PenaltyCostThe penalty cost applies only when the delivery is within the early or late buffer period. The penalty is prorated, and a value of 60 is suggested, equal to $1 per minute of buffer time used. Without a PenaltyCost the algorithm interprets the Buffer Time as “free” and will use it to a larger degree.no
AddressErrReserved for DirectRouteno
GeoResultPopulated by DirectRoute - accuracy of Lat / Longno
MaxSplitsSpecifies maximum number of times a stop can be split by the Splitting logic setup in Preferencesno
CurrentRouteStop user field (setup in Preferences > Configuration)no
RouteSequenceStop user field (setup in Preferences > Configuration)no
ServiceDateStop user field (setup in Preferences > Configuration)no
LocationTimeZonePopulated by DirectRoute during the Geocoding process if set to true in Preferences > Geocode Optionsno
ZoneSpeed Adjustmentno
AMStartSpeed Rush Hr Adjustmentno
AMEndSpeed Rush Hr Adjustmentno
AMAdjSpeed Rush Hr Adjustmentno
PMStartSpeed Rush Hr Adjustmentno
PMEndSpeed Rush Hr Adjustmentno
PMAdjSpeed Rush Hr Adjustmentno
TerritoryTerrPro will assign, or user can prepoplulate to Initialize current Stop to Territory assignments (req'd for TerritoryPro)no
DayTerrPro can assign, not standard useno
FrequencyRequired for SchPro (Regular and Vollume Allocation versions) - value represents # of service occurances per week (Ex. 1=1x per wk, .5=2x per mo, .25=1x per mo)no
ServTmTerritoryPro reserved fieldno
EstTimeTerritoryPro reserved fieldno
StemTmTerritoryPro reserved fieldno
DrvBtwnStopTerritoryPro reserved fieldno
LockTerritoryPro reserved fieldno
OrgTerritoryTerritoryPro reserved fieldno
OrgDayTerritoryPro reserved fieldno
ChangeTerritoryPro reserved fieldno
PatternsVollume Allocation SchPro field, populated by SchPro via the Pattern Library (can be user populated for special circumstances)no
Delivery DaySchPro reserved fieldno
AssignedDaysSchPro reserved fieldno
PriorityNot standard functionality, used with DRTrack database integration and the Priority Routing moduleno
OnFinalizeDRTrack reserved fieldno
CountryBlank assumes USA, need to input 3 digit Country Code if using outside of USA (Ex. CAN or MEX)no