Appian software can easily integrate with your business systems and be configured to follow your unique business rules and requirements.  Our software is designed to accept data passed from your Enterprise Resource Planning (ERP) system, Warehouse Management Software (WMS), or Order Management System (OMS) directly, where it can be used to create optimal routing solutions. The completed routing data can then be passed back to your ERP/WMS/OMS to update and maintain your customer accounts and records, and provide financial analysis of routes and fleet operations.


The following outlines some of the more common methods that most organizations use to send and receive data between their ERP/WMS/OMS and Appian software.   We can help you determine the best methods to use based on your business goals and operational needs.  


Capabilities 

Capabilities of an interface and integration with Appian software include: 

  • Track and route delivery of goods, or service vehicles with confidence
  • Build more efficient routes using your order info, time windows, volume and work constraints
  • Decrease total transportation costs with optimized route planning and execution
  • Instant updates of costs, mileage and hours as routes are modified
  • Generate detailed maps and turn-by-turn driving directions for drivers
  • Manage routes and deliveries by exception while improving customer service
  • Customized reporting for analysis of orders, routes and fleet operations
  • Track planned vs. actual mileage, hours and more
  • Measure success and identify opportunities to reduce overall transportation and fuel costs
  • Improve fleet and driver productivity with performance-based insight
  • Interface with real-time vehicle tracking, with visibility of vehicle and trailer locations

 

This guide outlines some of the more common methods that most organizations use to send and receive data between their ERP/WMS/OMS and Appian software.  We can help you determine the best methods to use based on your business goals and operational needs.  


Account Master Record

Regardless of the method used to send and receive data between your ERP/WMS/OMS and Appian, the data process flow will remain the same:  

  • An order is created and order details are sent to the database (Appian) prior to routing
  • Once a route is created, the route info can be retrieved and passed back to your ERP/WMS/OMS
  • The order information passed between systems can contain detailed routing info, but in many cases, simply needs to provide info specific to the current sales order; any route specific fields are automatically appended to the Account Master Records

 

An Account Master Record is created and maintained in the database for each customer. This record contains all the static information, or Master Account Data, that would be needed to complete an order delivery for that particular customer.

 

The Master Account Data typically includes Time Windows, Geocodes (Lat/Long coordinates), Contact Info, Special Delivery Instructions, etc. When daily orders are sent to the database for routing, the Master Account Data does not need to be included; this information will auto-populate from the Account Master Record.  

 

If there are any special order requirements which supercede the Account Master Data (new delivery times outside of current Time Windows, or shipping to an alternate address, etc), then that information can be sent on the order level and the Master Record Data will be ignored.  If an order is sent for an account that does not exist, an Account Master Record is automatically created, using the fields and data passed in the order. Any required fields that are not passed in the order will be auto-populated with pre-defined (user) defaults for Time Windows, Stop Times, etc.

 

The Account Master Data Table lists all required and optional fields that may be used in the Account Master Record.

 

Required Order Information

Orders generated from an ERP/WMS/OMS can contain as much, or as little, information as the system is able to generate.  Any required fields (data) missing from an order will be auto-populated from the Account Master Record, as described above.

 

The minimum, required information needed in an order file includes:  

  • Account Number 
  • ShipTo Address
  • Order Number 
  • Order Volume (Qty) 
  • Special Instructions 
  • Delivery Address 

 

Orders are matched to an Account Master Record using a unique identifier, usually an Account ShipTo Address. The Account Master Record is then appended with any new or additional Master Record Data that was included in the order.

 

The Appian database can accept basic order summary information, or line level detail.

 

See the Account Master Data Table for all required and optional fields included in the Account Master Record.

 

Options for Importing Orders

There are a variety of methods organizations can use to send (import) orders to the database, ranging from the simple passing of a text file, to the more complex, full Web Service integration.  

 

The methods used most often include:

  • Order Import Service (OIS) – Import daily orders (batch) from a text file (.csv, .ext) created by the ERP/WMS/OMS  
  • Legacy Import – Import data in a worksheet (.xls) or ASCII file (.csv, .ext) using DirectRoute™, Appian's installed automated fleet routing software
  • Web Services – Automatically push orders from the ERP/WMS/OMM in real time, or as a daily (batch) process

 

 Figure 1 – Import Methods

 

Web Services

Our Web Service is built using Microsoft Windows Communication Foundation framework. It is SOAP based and implements WS-Security standards.   Appian can accept order pushes or accounts utilizing our Web Service APIs.

 

Some benefits to using a Web Service integration include:

  • Seamless order import requiring no user interaction
  • Ability for near real time data exchange
  • Orders sent via Web Services can contain as much, or as little information as the ERP/WMS/OMS is capable of sending
  • Any missing information will automatically be appended from the Account Master Record

 

Description Language (WSDL)

The following Request Methods Table describes some (not all) of the import methods available via Web Services, and the expected return response.  The primary Web Service calls utilized by the vast majority of customers are ImportOrders and ImportAccounts.  You can access the WSDL (click to follow) at http://integration.appiangps.com/tracking.  

 

Name

Description

AddOrders

Add new order to an existing route.

BuildRouteFromOrderIds

Build routes from a list of orders.

ChangeAccountFrequency

Change Account delivery frequency

ImportAccounts

Import new Accounts for a specific Branch

ImportActuals

Import GPS data feed and sets the actual arrival and departure times for stops on dispatched routes within a Branch.

ImportBranches

Imports new Branches.

ImportDevices

Imports new Devices for a specific Branch.

ImportDrivers

Imports new Drivers for a specific Branch.

ImportOrders

Imports new orders for a Branch into the data base.

ImportRoutes

Imports new routes for a Branch into the data base.

Figure 2 – WSDL for Order Import

 

Figure 3 – Sequence for WSDL

 

Order Import Service

The Order Import Service (OIS) provides the ability to automate the process of inserting orders into the Appian software database using simple text file formats.  OIS is an Appian provided client application that polls a user-defined folder within your network for an order file (.csv or Tab Delimited) exported from an ERP/WMS/OMS.  The file is then processed by the service and automatically pushed to the database using Web Services.  

 

There are several benefits of using the OIS, including:

  • Text files are generally considered easier to generate than writing a full Web Service integration
  • The ability to deploy routing and dispatch tools quickly

 

Because the Account Master Record exists in the database, data elements that are required for routing aren’t necessarily required in the order file. Any information missing from the data will automatically populate from the Account Master Record information.  The order file can contain simple order summary data, or be detailed down to line level data.  See the Order File Data Table for the data elements that can be included in an Order File.

 

 Figure 4 – Order Import Service (OIS)

 

Figure 5 – Sequence for Order Import

 

Figure 6 – Sequence for Order Fetch

 

An .xml file format is another option.   The .xml Order Import Table lists the required and optional data elements that can be used in an order file.  Shown below are samples of an Order Import File; Sample .csv Import File and Sample .xlsx Import File.


Sample .CSV Import File 


Sample .xlsx Import File

 

Acct#

Name

Order

Address

City

State

Zip

Rt

Seq

Weight

Rev

Cube

Pallets

8102003

WINN DIXIE #2422

98798466

2060 W SPRING CREEK

PLANO

TX

75023

8

4

417

26

83

2

8102024

TOM THUMB 10

2948000

2300 E PARK BLVD

PLANO

TX

75074

8

2

179

64

36

1

8102025

TOM THUMB # 89

2947000

3320 AVE K

PLANO

TX

75074

8

3

200

75

40

1

8105024

KROGER #463

98798467

824 E CENTERVILLE RD

GARLAND

TX

75041

6

1

511

25

102

2

8106006

WINN DIXIE #2479

98798468

9310 FOREST LANE

DALLAS

TX

75243

9

8

203

28

41

1

8106007

TOM THUMB # 3

2604000

8060 SPRING VALLEY R

DALLAS

TX

75240

9

1

206

94

41

1

8106014

ALBERTSONS #4119

2951000

CENTENIAL AND AUDELIA

GARLAND

TX

75042

9

7

213

56

43

1

8107009

TOM THUMB #4613

3128000

HWY 289 AT FM720

FRISCO

TX

75034

8

5

393

97

79

2

8108006

KROGER #689

98798469

1122 W. CENTERVILLE

GARLAND

TX

75040

6

4

214

59

43

1

8108008

KROGER #434

2620000

4550 BUCKINGHAM RD

GARLAND

TX

75040

9

6

308

93

62

2

8108011

FOOD LION #1023

2618000

9661 AUDELIA/KINGSLEY

DALLAS

TX

75238

9

10

249

53

50

1

8108017

DIAMONDS #4184

2953000

212 MEDALLION CENTER

DALLAS

TX

75214

9

12

212

62

42

1

8108018

WINN DIXIE #2460

98798470

12400 LAKE JUNE RD

BLCH SPRNGS

TX

75180

6

7

327

63

65

2

8108020

K MART 7286 DEPT 2

98798471

HWY 80 & 205

TERRELL

TX

75160

2

9

173

58

35

1

8108021

K-MART 9256 DPT 2

98798472

12005 ELAM RD

BLCH SPRNGS

TX

75180

6

8

328

108

66

2

8108023

BROOKSHIRE #19

2619000

3212 JUPITER RD

GARLAND

TX

75042

9

4

264

110

53

1

8108027

KROGER #224

2617000

1736 E BELTLINE

RICHARDSON

TX

75081

9

5

165

70

33

1

 

See Attachment 2, Sample .xml Import File, and Attachment 4, Sample .xml Orders with Definitions for additional information.

 

Legacy File Import (DirectRoute)

The file import from DirectRoute allows import from Tab Delimited files (.txt, .xls).

 

Benefits of this import type include:

  • Simple (.txt, .xls) file format
  • Typically used for routing only deployments with a 3rd party dispatch/execution system

 

The order file generated from an ERP/WMS/OMS can contain as much, or as little information as the system is able to generate.  Any information missing from the order record will be populated from the Account Master Record.  Orders for new accounts will automatically create a new Account Master Record.

 

At a minimum, the order file should include

  • Account Number 
  • ShipTo Address
  • Order Number 
  • Order Volume (Qty) 
  • Special Instructions 
  • Delivery Address 

 

The Account Master Record can reside locally in a file, or can be stored in the database. To see what an Account Master Record might look like, refer to Attachment 5, Sample Account Master Record, and Attachment 1, URP Field Names Table, for all available fields that can be used to import.

 

    Sample .txt Import File

 

 

Options for Exporting Route Information 

After a routing solution has been completed, the resulting route information and statistics can be exported from the database to the OMS/ERP for processing.  This section of the document describes the different methods customers have to export that information.

 

The primary methods used to retrieve data from Appian  are:

  • Web Services – Automatically pull route and account information from Appian in near real time, or in a daily batch process
  • XML File – Exported with route and account detail; consumed by the ERP/WMS/OMS, or anywhere else .xml files can be read
  • Legacy Export – Files (.upl, .txt, or .xml) passed back to the ERP/WMS/OMS

 

   Figure 10 – Export to OMS/ERP 

 

Web Services

Appian has a full set of Web Service API’s for data regarding orders, accounts, and routes.

 

Benefits of using Web Services include:

  • Seamless data integration requires no user interaction
  • Ability for near real time data exchange
  • Ability to pull fields captured by the mobile device including pictures, signatures, etc. (device specific)

 

Description Language (WSDL) 

The following Request Methods Table describes some, but not all, of the import methods available via web services and the expected return response.  You can access the WSDL (click to follow) at http://integration.appiangps.com/tracking.

 

Name

Description

ExportAccounts

Exports Accounts by branches

GetAccountDetailsByBranch

Returns Account details for each account attached to a single branch.

GetAccountDetailsByModifiedDateAndBranch 

Returns Account details for each account attached to the Branch that have been modified within a date range.

GetBranches

Returns a list of all Branches

GetForms

Returns a list of forms.

GetMasterRoutes

Returns a list of Master Routes

GetMaxRouteDetailByBranchAndDispatchDate

Returns Route details by Branch for all routes dispatched within a date range.

GetOrderDetailByDate

Returns order details from a specific Branch within a date range.

GetOrderDetailByModifiedDate

Returns order details from a specific Branch that have been modified within a date range.

GetOrderDetailsAndEventsByOrderIDs

Returns order details from a specific Branch within a

GetOrderDetailsByOrderIds

Returns order details from a specific Branch

GetOrderEventsByTypeAndDate

Returns orders by events and date

GetRouteDetailByDateRange

Returns route details for each route within a Branch during a particular date range.

GetRouteDetailByModifiedDate

Returns route details for each modified route within a Branch during a particular date range.

GetRouteDetailByPlannedStartDate

Returns route details for each route within a Branch based off the planned start date.

GetRouteSummaryByPlannedStartDate

Returns a summary of all routes within a Branch based off the planned start date.

GetTruckProfiles

Returns truck details from a specific Branch

Figure 11 – WSDL for Order Export

 

 

 

 

 

 

 

 

XML File Export

Appian can create an .xml file export that contains the route information.   This allows the passing of pertinent information in an easy to consume format.  See Attachment 3 for a sample .xml export file.  Attachment 1, URP Field Names Table contains fields and attributes used in this process.

 

Benefits of using .xml export file are

  • Simple file integration
  • Contains most all routing fields

 

Figure 12 – .xml Export File

 

Legacy File Export (Direct Route)

Appian can also generate an Upload File (.upl, .txt, and .xml) to be exported from our legacy system (DirectRoute).  This enables control/selection of data fields to be included in the file being passed back to the ERP/WMS/OMS.

 

If planning to create and use an Upload File, the Routing Preferences in DirectRoute will need to be updated to specify an Upload File Name and an Upload File Path, as well as other pertinent upload options.  Creating a customized Upload File (.txt) allows you to select the data fields to be passed, and omit any fields not wanted.  Each field represents one piece of data from the routing project.  Refer to Attachment 1, URP Field Names Table for all available fields that can be used to export data in an Upload File.

 

Figure 13 – Sample .upl Upload File

 

 

 

Data Tables

 

Account Master Data Table

FIELD NAME

DESCRIPTION

REQUIRED OR OPTIONAL

Name

The name of the customer/business (stop) to be delivered.

Required

Contact

The name of a contact at the customer stop.

Optional

Phone

Telephone number at the stop location. If the Area code is included, The Legacy application can use it for geocoding.

Optional

ID1

Primary unique identifier for the customer/stop.     Example:  Account#, Customer#.   User defined field in Preferences/Configuration settings.     Used in the extract files process.

Required

ID2

Secondary unique identifier for the customer/stop.     

Example: Store#, Stop#. User defined field in Preferences/Configuration settings.

Optional

ID3

Tertiary unique identifier for the customer/stop. Example:  Line Item, SKU.  User defined field in Preferences/Configuration settings.

Optional

Address

Street Address for the customer. Address, along with City, State, and Zip are used to geocode by address. Also used by Address Cleanup.

Required

Address2

Additional Address information.  

Example:  Suite#, building#, Door#, Dock#.

Optional

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.

Required

State

2 letter state (Address) abbreviation.  

Example: WA, CA, OR.  Required to geocode.

Required

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.

Required

Longitude

The longitude and latitude fields are coordinates that define where a customer is located. Geocoding is the process used to identify these coordinates.

Required

Latitude

See Longitude.

Required

FixedTime

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 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 Legacy application, by adding these two fields together. 

Optional

SzRestriction

Size Restriction will inform The Legacy application 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 = load could only be put on trucks with a capacity of 20,000 or less in (Volume1 field) the Truck File.

Optional

EqCode

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 Legacy application 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. Can combine multiple codes (i.e. AJ-BH-HH-XX).  

Note:     There are also special EqCodes that can be utilized for Back Hauls, prioritizing and sequencing of stops, territory codes and exclusion codes.  

Optional

UnldRate 

Identifies the amount of time it takes to unload the volume1 value, in hours.  Note:     If Volume = cases, the field appears in the Stop File as ‘UnldCases’.  

Example:  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.).    

Optional

Open1

Earliest time of day s customer will accept delivery.     Military Time format (0000-2400). Multiple Time Windows can be used (up to ten), defined as Open1, Close1, Pattern1; Open2, Close2, Pattern2.  

Example:  Customer can receive deliveries between 800 and 1130 on Sunday, Wednesday, and Saturday.     Enter Open1=0800, Close1=1130, and Pattern1=SWA.

Required

Close1

Latest time of day that customer will accept delivery.  See Open1 for additional info.

Required

Pattern1

Days of the week when the customer will accept deliveries.  Each letter corresponds to the days of the week, beginning with Sunday (SMTWRFA).

Example:  Pattern1 = SWA; the customer can receive deliveries on Sunday, Wednesday, and Saturday.  

Required

EarlyBuffer

EarlyBuffer is used to activate the Soft TimeWindows function within The Legacy application, allowing stops to be loaded before the actual Open1 time window. A penalty cost is added if the buffer is engaged.  (MM/DD/YY) Used in conjunction with EarliestDate; determines the latest date 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. 

Optional

LateBuffer

LateBuffer is used to activate the Soft Time Windows function within The Legacy application. allowing stops to be loaded after the actual Close1 time window. A penalty cost is added if the buffer is engaged.EarlyBuffer is used to activate the Soft TimeWindows function within The Legacy application, allowing stops to be loaded before the actual Open1 time window. A penalty cost is added if the buffer is engaged.  

Optional

MaxSplits

Max Number of Splits Allowed for a Stop

Optional

PenaltyCost

The PenaltyCost (dollar amount per hour) is used in conjunction with the EarlyBuffer and LateBuffer to calculate and apply a penalty cost to stops that use the buffers, when egaged.     During the Optimization process, The Legacy application will try to move a stop with a penalty cost to another route in an attempt to eliminate the penalty (calculated per hour).

Optional

Rt

The Route # on which the customer is normally serviced.  When pre-populated, The Legacy application will place the stop on this Route.  If left blank, The Legacy application will determine which Route will service the stop.Max Number of Splits Allowed for a Stop

Optional

Seq

The delivery position of the stop on the Route.     If pre-populated, The Legacy application will place the stop in this position.  If left blank, The Legacy application will determine the position during the routing process.

Example:  A value of 3 indicates the customer is the third stop on the route.Max Number of Splits Allowed for a Stop

Optional

 

Order File Data Table

Because the Account Master Record 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 will auto-populate from the Account Master Record.  The order file can contain simple order summary data, or be as detailed as line level data.

 

FIELD NAME

DESCRIPTION

REQUIRED OR OPTIONAL

Name

The name of the customer/business (stop) to be delivered.

Optional

Contact

The name of a contact at the customer stop.

Optional

Phone

Telephone number at the stop location. If the Area code is included, the software can use it for geocoding.

Optional

ID1

Primary unique identifier for the customer/stop (Acct#, Customer#).   User defined (Preferences→Configuration) used in extract process.

Required

ID2

Secondary unique identifier for the customer/stop.     Example: Store#, Stop#. User defined field in Preferences→Configuration.

Required

ID3

Tertiary unique identifier for the customer/stop.     Example:  Line Item, SKU.  User defined field in Preferences→Configuration.

Optional

Address

Street Address for the customer. Address, along with City, State, and Zip are used to geocode by address. Also used by Address Cleanup.

Optional

Address2

Additional Address information.  Example:  Suite#, building#, Door#, Dock#.

Optional

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.

Optional

State

2 letter state (Address) abbreviation.  Example: WA, CA, OR.  Required to geocode.

Optional

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.

Optional

FixedTime

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.

Optional

SzRestriction

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.

Optional

EqCode

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.  

Optional

Qty Fields

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.

Required

UnldRate (UnldQty)

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).

Optional

CloseTW

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). 

Optional

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.  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.

Optional

AMStart

Set AM start time to adjust speed to account for heavier/lighter traffic.

Optional

AMEnd

Set AM end time to adjust speed to account for heavier/lighter traffic.

Optional

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 (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.

Optional

PMStart

Set PMStart to adjust speed to account for heavier or lighter traffic.

Optional

PMEnd

Set PMEnd to adjust speed to account for heavier or lighter traffic.

Optional

PMAdj

Set drive time adjustment for PMStart and PMEnd.     See AMAdj for additional info.

Optional

Open1

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.

Optional

Close1

Latest time a delivery can be made.  See Open1 for additional info.

Optional

Pattern1

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

Optional

EarliestDate

(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.

Optional

LatestDate

(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.

Optional

EarlyBuffer

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.

Optional

LateBuffer

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.

Optional

PenaltyCost

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.

Optional

 

.xml Order Import Table

The data fields in the .xml Order Import Table is divided into four data categories:  

  • General Fields Data – DRGeneralFields  Data  relays information related to delivery of an order
  • Volume Fields Data – DRVolumeFields  Data relays the type (named), quantity (amount), and the unload rate of material to be delivered.
  • Time Window Fields Data – DRTimeWindowFields Data relays authorized delivery times/days. 
  • User Fields – DRUserFields Data relays any optional information needed, as defined by the user. 

 

The following Fields (columns) are lissted in the XML Order Import Table:

  • Field Name
  • Field Type 
  • Enumeration (E)
  • String (S)
  • Numeric (N)
  • Duration (DU)
  • Date (D)
  • Time (T)
  • Boolean (B)
  • Field Width (Characters)
  • Required or Optional (R, O) 
  • Field Description
  • Sample Field Value

 

DRGeneralFields  Data 

Field Name

Field Type

Field Width

Req (R)

or Opt (O)

Description

Sample Field Value

Key

N

 

R

An unique identifier for each DRStop element

  1

Branch

S

20

R

The name of the branch the customer belongs

  MAIN, OKC or DALLAS

Name

S

50

R

The name of the customer

     Appian

Contact

S

50

O

The name of a contact at the customer site

  Joe

Phone

S

25

O

Telephone number of the customer

     800-893-1250

ID1

S

30

R

A unique identifier for this stop.  Typically, an account number

  A0001

ID2

S

25

R

A unique secondary ID normally used for order number 

  O0001

ID3

S

25

R

Third Identifier field normally used for a line item number or SKU.  Can be default value for all records 

  L0001

Address

S

100

R

Street address for the customer

  10317 Greenbriar Pl

Address2

S

100

O

Secondary address information (e.g. suite number, building, etc.)

  Ste 100

City

S

35

R

The name of the city for this customer

     Oklahoma City

State

S

2

R

2 character abbreviation for the state or province

  OK

Zip

S

10

R

The zip code or postal code of the customer

     73159-1514

FixedTime

DU

 

R

Number of minutes at this customer. Each customer can have a different fixed time.

Note:  Service Time at delivery locations are calculated based upon Fixed Time and UnldRate (time).  Setting the UnldRate to 0 will make the Fixed Time be the total service time.

  PT0H25M.     

RouteNumber

N

 

O

Route number that this stop is normally placed on

  1

Leg

N

 

O

Leg number that this stop is normally placed on

  1

Seq

N

 

O

Position of this customer within a route

  1

SizeRestriction

N

 

O

This field corresponds to the Capacity 1 field in the Truck file

  42000

EqCode

S

50

O

Equipment code for assigning account to particular vehicles

     @AB-BH

DRVolume (unlimited)

 

 

R

Volume to be delivered.  One field for each volume used (ie. weight, cube, pallets, etc.)

 See DRVolumeFields Data for details

DRTimeWindow

 

 

 

O

Open time and close time of delivery time window and the day of delivery.

 See DRTimeWindowFields Data for details 

Zone

N

 

O

Speed zones used to increase or decrease truck driving speed within a delivery area.     An example would be if the customer is located within a congested downtown area. A value of 125 increases driving time by 25%. Similarly, a value of 90 decreases the driving time by 10%.

  125

OrderType

E

 

R

If Modify is set as OrderType and if that order doesn’t exist in DRTrack then it will be added as a new order.

 Add – New Order, Modify – Update Order, Delete / Delete Order.

Longitude

N

 

O

Longitude of the customer (calculated by Application)

     -97.5225

Latitude

N

 

O

Latitude of the customer (calculated by Application)

     32.7545

DRUserFields

(Unlimited)

 

 

O

Optional data fields with additional information pertaining to the account.

 See DRUserFields Data for details

Symbol

S

10

O

The symbol which will be placed on the map when orders are downloded to the Legacy application

 Diamond

Size

N

 

O

The size of the symbol which is displayed on the map when orders are downloaded to The Legacy application

 16

Color

S

10

O

The color of the symbol which is displayed on the map

 Green

MaxSplits

N

2

O

Maximum number of times an order can be split

  0

EarlyBuffer

DU

 

O

The EarlyBuffer, in conjunction with the LateBuffer and PenaltyCost, is used to create Soft Time Windows. The Early Buffer applies a buffer, noted in hours, to the Time Windows. A buffer set to half-an-hour (.5) would stretch the front of the Time Windows by a half-an-hour. (I.e.: Time Windows of 07:00-11:00 would actually be computed as 06:30-11:00). When a stop uses the offered buffer, a penalty cost can be applied as set in the PenaltyCost Field

     PT1H25M30S

LateBuffer

DU

 

O

The LateBuffer, in conjunction with EarlyBuffer and PenaltyCost, is used to create Soft Time Windows. Late Buffer applies a buffer, noted in house, to the Time Windows. A buffer set to half-an-hour (.5) would stretch the back of the Time Windows by 30 minutes (I.e.: Time Windows of 07:00-11:00 would actually be computed as 07:00-11:30). When a stop uses the offered buffer, a penalty cost can be applied, as laid out in the PenaltyCost Field

  PT2H

PenaltyCost

N

 

O

The PenaltyCost column, used in conjunction with EarlyBuffer and LateBuffer, is used to apply a penalty to stops that use the buffers; penalty cost, applied in Cost per Hour. Penalty Cost is used to calculate not only penalty charges for a stop using the buffer, but also during optimization. DRTrack will attempt to move a stop with a penalty cost to another route, eliminating the penalty.

  50

Estimated

DeliveryDate

D

 

R

The delivery date time the order should be shipped

     2010-01-10T18:05:00

EarliestDate

D

 

O

When a Stop must be delivered within a certain timeframe, then Earliest Date may be used to ensure that the stop is completed within the restrictive time. 

     2010-01-08

LatestDate

D

 

O

Latest Date is used in conjunction with Earliest Date. This is the latest that a stop may be serviced. LatestDate may be the same as the Earliest Date, if there is only one day in which the stop may be serviced

     2010-01-12

CloseTW

B

 

O

If the customer's delivery must be completed (delivered, unloaded and out) by the late time window time, then set to TRUE.

  TRUE or FALSE

 

DRVolumeFields  Data 

1

2

3

4

5

6

No

N

 

R

ID

A number increment from 1

Name

S

25

R

Name of the Qty Field.

Weight, Cube, Pallet

Volume

N

 

R

The amount of material to be delivered to this stop

2000

UnldRate

N

 

R

The amount of time it will take to unload material per hour. It will take 2 hours to deliver 2000 units at an unld rate of 1000 units/hr

(Pass 0 to ignore unload rates)

1000.  Note:     Service Time at delivery locations are calculated based upon Fixed Time and UnldRate (time).  Setting the UnldRate to 0 will make the Fixed Time be the total service time.

 

DRTimeWindowFields Data

1

2

3

4

5

6

Open

T

 

R

 Open time of the delivery time window. (Seconds are ignored)

07:00:00

Close

T

 

R

Close time of the delivery time window. (Seconds are ignored)

13:30:00

Pattern

S

7

R

Day of the delivery.

Allowed Characters:

S – Sunday, M – Monday, T- Tuesday W – Wednesday, R- Thursday

F – Friday, A – Saturday

MWFA, SMF, RFA

 

DRUserFields Data 

1

2

3

4

5

6

No

N

 

R

ID

A number incremented from 1

Name

S

25

R

Name of the UserField

SalesPerson

Value

S

255

R

Value of the UserField

Bob

 

Attachment 1, URP Field Names Table

The URP Field Names Table is updated when new fields are added and/or identified, usually due to new features and/or capabilities.   As a result, the table listed in this document may not reflect the most recent information. To get an updated list, please contact your Sales Rep or Customer Support.   

 

ROUTE FIELDS

DESCRIPTION

RFARV_DATE

Arrival date at delivery location

RFARV_DAY

Arrival day at delivery location

RFARV_TIME

Arrival time at delivery location

RFBREAKTM

Break time for driver

RFCUM_DRV_TM

Cumulative drive time

RFCUM_WRK_TM

Cumulative work time on route

RFCUMQTY001

Cumulative Quantity1 of Order

RFCUMQTY002

Cumulative Quantity2 of Order

RFCUMQTY003

Cumulative Quantity3 of Order

RFCUMQTY004

Cumulative Quantity4 of Order

RFCUMQTY005

Cumulative Quantity5 of Order

RFCUMQTY006

Cumulative Quantity6 of Order

RFCUMQTY007

Cumulative Quantity7 of Order

RFCUMQTY008

Cumulative Quantity8 of Order

RFCUMQTY009

Cumulative Quantity9 of Order

RFCUMQTY010

Cumulative Quantity10 of Order

RFDEPDAY

Day of departure/dispatch day

RFDEPT_DATE

Route departure date

RFDEPT_TIME

Time of route departure

RFDIST_TO_PREV_STOP

Distance from previous stop

RFINCR_COST

Incremental cost of a stop; calculates difference in miles, drvtm; if a stop is added, applies mileage and hr cost 

RFLAYOVER_TM

Overnight layover time within a route

RFREMAINCAP001

Remaining Capacity1

RFREMAINCAP002

Remaining Capacity2

RFREMAINCAP003

Remaining Capacity3

RFREMAINCAP004

Remaining Capacity4

RFREMAINCAP005

Remaining Capacity5

RFREMAINCAP006

Remaining Capacity6

RFREMAINCAP007

Remaining Capacity7

RFREMAINCAP008

Remaining Capacity8

RFREMAINCAP009

Remaining Capacity9

RFREMAINCAP010

Remaining Capacity10

RFSEQ_NO

Sequence number of stop within a route

RFTIME_TO_PREV_STOP

Time to Previous Stop

RFUNLOAD_TIME

Unload Time

RFWAIT_TM_AT_STOP

Wait time at stop

RFWINDOW_VIOLATION

Window Violation

RT_NUM

Route Number

RT%_ABSCAP001_USED

Absolute value of Qty1 for each stop on route divided by Trk capacity * 2 (pickup, delivery)

RT%_ABSCAP002_USED

Absolute value of Qty2 for each stop on route divided by Trk capacity * 2 

RT%_ABSCAP003_USED

Absolute value of Qty3 for each stop on route divided by Trk capacity * 2 

RT%_ABSCAP004_USED

Absolute value of Qty4 for each stop on route divided by Trk capacity * 2

RT%_ABSCAP005_USED

Absolute value of Qty5 for each stop on route divided by Trk capacity * 2

RT%_ABSCAP006_USED

Absolute value of Qty6 for each stop on route divided by Trk capacity * 2 

RT%_ABSCAP007_USED

Absolute value of Qty7 for each stop on route divided by Trk capacity * 2 

RT%_ABSCAP008_USED

Absolute value of Qty8 for each stop on route divided by Trk capacity * 2 

RT%_ABSCAP009_USED

Absolute value of Qty9 for each stop on route divided by Trk capacity * 2 

RT%_ABSCAP010_USED

Absolute value of Qty10 for each stop on route divided by Trk capacity * 2 

RT%_CAP001_USED

Percent of cap1 used on route (10 cap fields avail)

RT%_CAP002_USED

Percent of cap2 used on route 

RT%_CAP003_USED

Percent of cap3 used on route 

RT%_CAP004_USED

Percent of cap4 used on route 

RT%_CAP005_USED

Percent of cap5 used on route 

RT%_CAP006_USED

Percent of cap6 used on route 

RT%_CAP007_USED

Percent of cap7 used on route 

RT%_CAP008_USED

Percent of cap8 used on route 

RT%_CAP009_USED

Percent of cap9 used on route (

RT%_CAP010_USED

Percent of cap10 used on route 

RTCAP001_USED

Route capacity1 used  (10 cap fields avail)

RTCAP002_USED

Route capacity2 used  

RTCAP003_USED

Route capacity3 used  

RTCAP004_USED

Route capacity4 used  

RTCAP005_USED

Route capacity5 used  

RTCAP006_USED

Route capacity6 used  

RTCAP007_USED

Route capacity7 used  

RTCAP008_USED

Route capacity8 used  

RTCAP009_USED

Route capacity9 used  

RTCAP010_USED

Route capacity10 used 

RTBACKHAUL001

Backhaul1

RTBACKHAUL002

Backhaul2

RTBACKHAUL003

Backhaul3

RTBACKHAUL004

Backhaul4

RTBACKHAUL005

Backhaul5

RTBACKHAUL006

Backhaul6

RTBACKHAUL007

Backhaul7

RTBACKHAUL008

Backhaul8

RTBACKHAUL009

Backhaul9

RTBACKHAUL010

Backhaul10

RTCOSTPERSTOP

Cost per Stop

RTDEL001

Total value of Qty1 delivered (Non negative quanties and excludes backhauls)

RTDEL002

Total value of Qty2 delivered

RTDEL003

Total value of Qty3 delivered 

RTDEL004

Total value of Qty4 delivered 

RTDEL005

Total value of Qty5 delivered 

RTDEL006

Total value of Qty6 delivered 

RTDEL007

Total value of Qty7 delivered 

RTDEL008

Total value of Qty8 delivered 

RTDEL009

Total value of Qty9 delivered 

RTDEL010

Total value of Qty10 delivered

RTCOSTPERQTY001

Cost per Quantity1

RTCOSTPERQTY002

Cost per Quantity2

RTCOSTPERQTY003

Cost per Quantity3

RTCOSTPERQTY004

Cost per Quantity4

RTCOSTPERQTY005

Cost per Quantity5

RTCOSTPERQTY006

Cost per Quantity6

RTCOSTPERQTY007

Cost per Quantity7

RTCOSTPERQTY008

Cost per Quantity8

RTCOSTPERQTY009

Cost per Quantity9

RTCOSTPERQTY010

Cost per Quantity10

RTEARLIESTLATEDATE

Shows the critical latest delivery date when Earliest/Latest Date is used.

RTENDDATE

End date of route

RTENDDAY

End day of route

RTENDTIME

Time route ends

RTSTARTDATE

Date route starts

RTSTART_DAY

Day route starts

RTSTARTTIME

Time route starts

RTFARTHESTSTOP

Distance to the farthest stop on the route

RTJULIANPLUSRT

Used to generate rt # for peoplenet day of year +Rt#     (ex. 050012 is rt 12 on the 50th day of the year)

RTNONSTEMDIST

None Stem distance

RTPENALTYCOST

Penalty Cost

RTPICKUP001

Total value of Qty1 delivered (shown as negative quantities)

RTPICKUP002

Total value of Qty2 delivered 

RTPICKUP003

Total value of Qty3 delivered 

RTPICKUP004

Total value of Qty4 delivered 

RTPICKUP005

Total value of Qty5 delivered 

RTPICKUP006

Total value of Qty6 delivered 

RTPICKUP007

Total value of Qty7 delivered 

RTPICKUP008

Total value of Qty8 delivered 

RTPICKUP009

Total value of Qty9 delivered 

RTPICKUP010

Total value of Qty10 delivered 

RTQTYPERHR001

Quantity1 per hour

RTQTYPERHR002

Quantity2 per hour

RTQTYPERHR003

Quantity3 per hour

RTQTYPERHR004

Quantity4 per hour

RTQTYPERHR005

Quantity5 per hour

RTQTYPERHR006

Quantity6 per hour

RTQTYPERHR007

Quantity7 per hour

RTQTYPERHR008

Quantity8 per hour

RTQTYPERHR009

Quantity9 per hour

RTQTYPERHR010

Quantity10 per hour

RTQTYPERMI001

Quantity1 per mile

RTQTYPERMI002

Quantity2 per mile

RTQTYPERMI003

Quantity3 per mile

RTQTYPERMI004

Quantity4 per mile

RTQTYPERMI005

Quantity5 per mile

RTQTYPERMI006

Quantity6 per mile

RTQTYPERMI007

Quantity7 per mile

RTQTYPERMI008

Quantity8 per mile

RTQTYPERMI009

Quantity9 per mile

RTQTYPERMI010

Quantity10 per mile

RTSTEMDIST

Route stem distance

RTSTOPSPERHR

Stops per hour on route

RTSTOPSPERMI

Stops per mile on route

RTTOAT_UNLD_TM

Route total unload time

RTTOT_DAYS

Total number of days on a route

RTTOT_DIST

Total distance of a route

RTTOT_DROPCOST

Total drop cost of a route

RTTOT_ELAPSED_TIME

Total elapsed time of a route

RTTOT_FIXEDCOST

Total fixed cost of a route

RTTOT_HRCOST

Total hourly pay cost of route

RTTOT_LAYOVERCOST

Total cost of layovers on a route

RTTOT_MICOST

Total mileage cost of a route

RTTOT_OTCOST

Total overtime cost of a route

RTTOT_PREPOST

Total pre and post time for a route

RTTOT_UNITCOST

Total unit cost on a route

RTTOT_UNLDHRCOST

Total unload hour cost on a route

RTTOT_WAITHRCOST

Total wait hour cost of a route

RTTOTAL_COST

Total cost of a route

RTTOTAL_DRV_TM

Total drive time

RTTOTAL_STOPS

Total stops serviced

RTTOTAL_WAIT_TM

Total wait time on a route

RTTOTAL_WRK_TM

Total work time on a route

RTVIOLATIONSYN

Violations yes or no

RTVIOLATIONSFULL

Violations (equip/capacity) on a route-Full

RTVIOLATIONSBRIEF

Violations (equip/capacity) on a route-Brief

RFEMPTYMILES

Empty Miles

RTTOTAL_HOURS_PERROUTEDAY

Total hours per route day

RTTOT_LAYOVERTIME

Total layover time of a route

RTTOTAL_MILES_PERROUTEDAY

Total miles per route day

RTTOT_LAYOVERS

Total no of layovers on a route

RTTOLLCOST

Toll cost per route

RTQTY001

Total Qty1 per route

RTQTY002

Total Qty2 per route

RTMILESPERQTY001

Route miles per QTY1

RTMILESPERQTY002

Route miles per QTY2

Stop Fields

Description of Field Info

SFADDRESS

Address of stop

SFADDRESS2

Extra address information

SFAMADJ

AM Rush Hour Speed Adjustment

RFBUFFERUSED

Total untilized buffer time

SFCITY

City the stop is located in

SFCOLOR

Color of stop displayed on the map

SFCONTACT

Contact name for stop

SFOPEN1

Earliest time for 1st delivery Time Window

SFCLOSE1

Latest time for 1st delivery Time Window

SFPATTERN1

Avail Del Days for first set of Time Windows

SFOPEN2

Earliest time for 2nd delivery Time Window

SFCLOSE2

Latest time for 2nd delivery Time Window

SFPATTERN2

Avail Del Days for 2nd set of Time Windows

SFDELQTY001

Quantity1 delivered to stop

SFDELQTY002

Quantity2 delivered to stop

SFDELQTY003

Quantity3 delivered to stop

SFDELQTY004

Quantity4 delivered to stop

SFDELQTY005

Quantity5 delivered to stop

SFDELQTY006

Quantity6 delivered to stop

SFDELQTY007

Quantity7 delivered to stop

SFDELQTY008

Quantity8 delivered to stop

SFDELQTY009

Quantity9 delivered to stop

SFDELQTY010

Quantity10 delivered to stop

SFEQCODE

Equipment code

SFFIXEDTIME

Fixed time for stop

SFEARLIESTDATE

EarliestDate for stop

SFID1

First Identifier for Customer/Acct (Account#)

SFID2

Second Identifier for Customer/Acct (Order#)

SFID3

Third Identifier for Customer/Acct (LineItem)

SFLATITUDE

Latitude coordinates of stop

SFLONGITUDE

Longitude coordinates of stop

SFLATESTDATE

LatestDate

SFNAME

Customer name

SFOUTPFROUTECOST

Out of Route cost for Stop

SFPHONE

Customer phone number

RFPENALTYCOST

Cost incurred for utilizing Early/Late Buffer 

SFPICKUPQTY001

Pickup quantity1 (negative number)

SFPICKUPQTY002

Pickup quantity2 (negative number)

SFPICKUPQTY003

Pickup quantity3 (negative number)

SFPICKUPQTY004

Pickup quantity4 (negative number)

SFPICKUPQTY005

Pickup quantity5 (negative number)

SFPICKUPQTY006

Pickup quantity6 (negative number)

SFPICKUPQTY007

Pickup quantity7 (negative number)

SFPICKUPQTY008

Pickup quantity8 (negative number)

SFPICKUPQTY009

Pickup quantity9 (negative number)

SFPICKUPQTY010

Pickup quantity10 (negative number)

SFQTY001

Quantity1 of order

SFQTY002

Quantity2 of order

SFQTY003

Quantity3 of order

SFQTY004

Quantity4 of order

SFQTY005

Quantity5 of order

SFQTY006

Quantity6 of order

SFQTY007

Quantity7 of order

SFQTY008

Quantity8 of order

SFQTY009

Quantity9 of order

SFQTY010

Quantity10 of order

SFROW

Row # in the spreadsheet for the stop

SFRT

Route number

SFRTONLY

Displays only the Rt#, not Rt and Leg

SFSELECTED

Stop selected

SFSEQ

Sequence number of stop

SFSIZE

Size restriction

SFSTATE

State where stop is located

SFSYMBOL

Symbol assigned to the Stop

SFUNLDRATE001

Unload rate1

SFUNLDRATE002

Unload rate2

SFUNLDRATE003

Unload rate3

SFUNLDRATE004

Unload rate4

SFUNLDRATE005

Unload rate5

SFUNLDRATE006

Unload rate6

SFUNLDRATE007

Unload rate7

SFUNLDRATE008

Unload rate8

SFUNLDRATE009

Unload rate9

SFUNLDRATE010

Unload rate10

SFUSERFLD001

Stop File user field1 (20 fields available)

SFUSERFLD002

Stop File user field2 

SFUSERFLD003

Stop File user field3 

SFUSERFLD004

Stop File user field4 

SFUSERFLD005

Stop File user field5 

SFUSERFLD006

Stop File user field6 

SFUSERFLD007

Stop File user field7 

SFUSERFLD008

Stop File user field8 

SFUSERFLD009

Stop File user field9 

SFUSERFLD010

Stop File user field10

SFUSERFLD011

Stop File user field11 

SFUSERFLD012

Stop File user field12 

SFUSERFLD013

Stop File user field13 

SFUSERFLD014

Stop File user field14

SFUSERFLD015

Stop File user field15 

SFUSERFLD016

Stop File user field16 

SFUSERFLD017

Stop File user field17 

SFUSERFLD018

Stop File user field18 

SFUSERFLD019

Stop File user field19 

SFUSERFLD020

Stop File user field20 

SFZIP

Zip code where stop is located

SFZONE

user defined zone of stop

SPDISTTODEPOT

dist from stop to depot

SPDISTTODEPOTSUM

sum of distance from stops to depot

SFDAYSBETWEENROUTES

Days between routes

SFFREQUENCY

Frequency for stop

SFGEORESULT

Geocode results

SFLEG

Leg number for stop

SFLTLCOST

LTL cost for the stop

SFMAXSPLITS

Max number of splits allowed per stop

SFAMSTART

Specifies start time of AM rush hour 

SFAMEND

Specifies end time of AM rush hour 

SFPMSTART

Specifies start time of PM rush hour 

SFPMEND

Specifies end time of PM rush hour 

SFPMADJ

Amount to adjust PM drive time

SFAMADJ

Amount to adjust AM drive time

RFTOLLCOST

Cost of toll for a stop

TW_GRAPH

Time window graph

RFCAPUSED001

Capacity1 used per stop (10 cap fields avail)

RFCAPUSED002

Capacity2 used per stop 

RFCAPUSED003

Capacity3 used per stop 

RFCAPUSED004

Capacity4 used per stop 

RFCAPUSED005

Capacity5 used per stop 

RFCAPUSED006

Capacity6 used per stop 

RFCAPUSED007

Capacity7 used per stop 

RFCAPUSED008

Capacity8 used per stop 

RFCAPUSED009

Capacity9 used per stop 

RFCAPUSED010

Capacity10 used per stop 

Truck Fields

Description of Field Info

TFCAP001

Vehicle capacity1

TFCAP002

Vehicle capacity2

TFCAP003

Vehicle capacity3

TFCAP004

Vehicle capacity4

TFCAP005

Vehicle capacity5

TFCAP006

Vehicle capacity6

TFCAP007

Vehicle capacity7

TFCAP008

Vehicle capacity8

TFCAP009

Vehicle capacity9

TFCAP010

Vehicle capacity10

TFDROPCOST

Drop Cost

TFEARSTART

Earliest time vehicle can be dispatched

TFEDATE

Earliest date vehicle may be dispatched

TFFIXEDCOST

Fixed cost for operating vehicle

TFHRCOST

Cost per hour to operate the vehicle

TFLATFINISH

Latest time vehicle can finish the route

TFLAYOVERCOST

Cost per layover of vehicle

TFLDATE

Latest date vehicle may be dispatched

TFLOCK

Lock route

TFMAXDRIVETM

Maximum drive time for the vehicle/driver

TFMAXLAYOVER

Maximum layover allowed

TFMAXWORKTM

Maximum work time for vehicle/driver

TFMICOST

Cost per mile to operate the vehicle

TFMINLAYOVER

Minimum layover required

TFOTCOST

Over time cost

TFSPEQ

Special equipment identifier (corresponds to equipment code in Stop File)

TFSTATUS

Vehicle utilized (Y or N)

TFTRKID

Unique identifier for vehicle

TFUNITCOST

Cost per unit on vehicle

TFUSERFLD001

user defined field1

TFUSERFLD002

user defined field2

TFUSERFLD003

user defined field3

TFUSERFLD004

user defined field4

TFUSERFLD005

user defined field5

TFUSERFLD006

user defined field6

TFUSERFLD007

user defined field7

TFUSERFLD008

user defined field8

TFUSERFLD009

user defined field9

TFUSERFLD010

user defined field10

TFUNLDHRCOST

Unload hour cost

TFWAITHRCOST

Wait time cost per hour

TFBREAKTM

Break time for driver

TRDIST

Total distance driven (all routes)

TRDROPCOST

Total drop cost

TRDRV_TM

Total drive time

TRELAPSED_TIME

Total elapsed time

TRFIXEDCOST

Total fixed cost

TRHRCOST

Total hourly pay cost

TRLAYOVERCOST

Total layover cost

TRMICOST

Total mileage cost

TROTCOST

Total over time cost

TRSTOPS

Total stops serviced

TRTOTCOST

Total overall cost

TRTOTTM

Total time used

TRUNITCOST

Total unit costs

TRUNLD_TM

Total unload time

TRUNLDHRCOST

Total unload hour cost

TRWAIT_TM

Total wait time

TRWAITHRCOST

Total wait time cost

TRWRK_TM

Total work time

TFCITY

City the truck is located in

TFLATITUDE

Truck latitude

TFLONGITUDE

Truck longitude

TFPRETRIP

Pre Trip

TFPOSTTRIP

Post trip

TFUNLDPERF

Unload performance

ResourcePro Fields

Description of Field Info

RPDRIVER

Driver assigend to route in ResourcePro

RPTRUCK

Truck assigned in ResourcePro

RPTRAILER

Trailer assigned in ResourcePro

RPSTARTINGDRIVETIME

Drive Time Start in ResourcePro

RPSTARTINGWORKTIME

Work Time Start in ResourcePro

RPWORKHOURSBEFORE

Work Hrs before next route (Hrs between routes)