General Info Table settings that are used by Fuel Dispatch

These General Info Table settings are used by Fuel Dispatch, and are saved within the TMWSuite database.

CityLatLongUnits

Applies to

TMWSuite V.2005; TMW Operations 14.10

Description

Use this setting to specify whether city latitude/longitude values in the city table are in seconds or decimal degrees.

String1

D (default)
The value is in decimal degrees.
S
The value is in seconds.

DistanceCacheByState

Applies to

TMWSuite, Fuel Dispatch, TMW Operations: 15.30.074

Description

When the system creates a new route entry in the mileage database, this setting determines whether the mileage database records the states passed through on the route.

Note: This setting is valid only when String1 in the DistanceLookupVersion General Info Table setting is set to 2004.

String1

N (default)
When creating a new route entry, the mileage database does not record the states passed through on the route.
Y
When creating a new route entry, the mileage database records the states passed through on the route.

Additional Notes

To use this setting, TMWSuite must be set up to use ALK’s PC*MILER|Streets version 17 or higher.

This setting is required to use the Permitting feature in TMWSuite. The Permitting feature is a licensed add-on that must be purchased separately.

DistanceCacheOneWay

Applies to

TMWSuite, Fuel Dispatch, TMW Operations: 15.30.074

Description

This setting determines how the system will calculate the mileage for each stop on a trip.

String1

N (default)
When calculating the mileage for a stop, the system sorts the origin and destination in alphabetical order by city/state name.

For example, a trip includes a pickup at Columbus, Ohio, and drop at Beachwood, Ohio. The system calculates the mileage between Beachwood and Columbus, not between Columbus and Beachwood.
Y
When calculating the mileage for a stop, the system sorts the origin and destination according to the order specified for the trip.

For example, a trip includes a pickup at Dayton, Ohio, and drop at Cincinnati, Ohio. The system calculates and stores the mileage between Dayton and Cincinnati.

Additional Notes

To use this setting, TMWSuite must be configured to use ALK’s PC*MILER|Streets version 17 or higher.

This setting is valid only if the String1 value of the DistanceLookupVersion key is 2004.

DistanceLookupVersion

Applies to

TMWSuite: 2005.04_10.0211, Fuel Dispatch, TMW Operations: 15.30.074

Description

When stop locations are entered or modified on an order, this setting determines how the system chooses the location information used for mileage lookups, i.e., whether lookups are based on street addresses, latitude and longitude data, ZIP Codes/postal codes in TMWSuite company profiles, or each city’s primary ZIP Code/postal code in the mileage application.

String1

OLD (default)
The system will use [MileageInterface]DefaultLookupBy option to determine the location information for all mileage lookups.
2004
The system determines the location information for mileage lookups on a company-by-company basis.

The Distance SearchLvl field displays in the General section of the Company File Maintenance window. The option in this field determines the location information used for mileage lookups involving that company.

The available options in the Distance SearchLvl field are:
- A (address)
  Mileage lookups will be based on the company’s street address.
- L (latitude and longitude)
  Mileage lookups will be based on the company’s latitude and longitude data.
- Z (ZIP Code)
  Mileage lookups will be based on the company’s ZIP Code/postal code.
- C (city)
  Mileage lookups will be based on the primary ZIP Code/postal code for the company’s city in ALK.

Notes for TMWSuite users

To use the 2004 option TMWSuite must be set up to use either:
- ALK’s PC*MILER|Streets version 17 or higher, or
- RAND MileMaker with Intelliroute 18 or higher.
  This option is first available in 2014.13_07.0644.
You cannot use the 2004 option with any other mileage application.
If a company’s Distance SearchLvl field is blank, mileage lookups will be based on the company’s city in ALK.
The 2004 option overrides the [MileageInterface]DefaultLookupBy setting.
The 2004 option is required to enable any of the following optional features:
- Storing separate entries in the mileage database for each direction of the same route
  For more information on this feature, see the description of the DistanceCacheOneWay setting.
- Saving travel directions for routes in the mileage database
  For more information on this feature, see the description of the DistanceCacheRouting setting.
- Recording the states traveled through on a route in the mileage database
  For more information on this feature, see the description of the DistanceCacheByState setting.
  
  Note: To use the Permitting feature in TMWSuite, you must enable the state cached mileage feature. The Permitting feature is a licensed add-on that must be purchased separately.
- Specifying a company ID as the origin point for calculations performed by the Calc Distance button in Company File Maintenance
  For more information on this feature, see the description of the DistanceValidateCmpID setting.

Notes for Fuel Dispatch users

You can use the 2004 option with ALK’s PC*MILER|Streets version 17 or higher.
You can use the 2004 option with RAND MileMaker SP32 and RAND IntelliRoute version 18 or greater.
If a company’s Distance SearchLvl field is blank, mileage lookups will be based on the company’s city.
The 2004 option overrides the [MileageInterface]DefaultLookupBy setting.
The following optional features are available when you have a value of 2004 or OLD in the String1 field.
- Storing separate entries in the mileage database for each direction of the same route
  For more information on this feature, see the description of the DistanceCacheOneWay setting.
- Saving travel directions for routes in the mileage database (available only for ALK)
  For more information on this feature, see the description of the DistanceCacheRouting setting.
- Recording the states traveled through on a route in the mileage database (available only for ALK)
  For more information on this feature, see the description of the DistanceCacheByState setting.
  
  Note: To use the Permitting feature in TMWSuite, you must enable the state cached mileage feature. The Permitting feature is a licensed add-on that must be purchased separately.
- Specifying a company ID as the origin point for calculations performed by the Calc Distance button in Company File Maintenance
  For more information on this feature, see the description of the DistanceValidateCmpID setting.

String2

First available in V. 2006.05_10.1071

String 2 is applicable only when the String1 field has a value of 2004.

TMWSuite

It is possible for the mileage on some trips to be incorrect because of the lookup used for the companies on the trip segments. For example, if a company has its Distance SearchLvl field set to A (Address), but the address is not valid according to ALK, the system will perform the lookup as city-to-ZIP Code. However, the company’s SearchLvl field remains set to A. You can use the String2 field to specify the search method that will be used when the one specified in a company’s profile fails. The options are:
Fuel Dispatch

String2 options are used only when the system validates the company’s address in the company profile.
- Blank, that is, no entry (default)
  Base the lookup on the company’s address. If the address is not a valid ALK address, no other lookup will be made.
- A
  Base the lookup on the company’s address. If the address is not a valid ALK address, base the lookup on the company’s city location.
- C
  Base the lookup on the company’s city location. If the city is not a valid ALK city, base the lookup on the company’s ZIP Code.
- L
  Base the lookup on the company’s location, as defined by the lat/long entries in its profile. If no lat/long data is recorded in the company’s profile, base the lookup on the company’s ZIP Code.
- Z
  Base the lookup on the company’s ZIP Code.

String3

First available in V. 2011.10_08.1029

String3 options are valid only for TMWSuite.

String3 is applicable only when the String1 field has a value of 2004.

When you are using a manual mileage interface and a company on an order has the Distance SearchLvl field set to Z (ZIP Code) in its profile, the system does not return saved Zip-to-Zip lookup miles. Instead, it returns miles equal to the option recorded in the [MileageInterface]DefaultIntraCityMileage setting in your TTS50.

You can force the system to perform a new lookup, and base it on the company’s ZIP Code, or its ZIP Code and its city/state location. The options are:

N (default)
When the company’s Distance SearchLvl field is set to Z, return miles equal to the value record in the [MileageInterface]DefaultIntraCityMileage INI setting.
Y
When the company’s Distance SearchLvl field is set to Z, the company’s city and state will be added after the ZIP Code to provide more information to the mileage system for the mileage lookup.

FingerPrintAudit

Applies to

TMWSuite: 2003 and later; Fuel Dispatch; TMW Operations

Description

Determines whether the Activity Audit feature is enabled. The Activity Audit feature allows you to view a list of the changes to:

An order
Invoice details
An invoice header
Pay details associated with a trip
A pay header
A billing rate or pay rate schedule

Changes are logged to the expedite_audit table, which also is known as the fingerprint audit table.

String1

N (default)
The Activity Audit feature is disabled.
Y
The Activity Audit feature is enabled.

Notes:
1. Only changes made while the feature is enabled will be tracked.
2. When you use this option, changes can be viewed in these applications:
  - TMWSuite
    
    Changes are listed in the Load Activities window. The window is available in Order Entry, the Dispatch Trip Folder, Rate Schedules, Invoicing, and Settlements. You access it by selecting Reports > Activity Audit. The command is accessible only when the feature is enabled.
  - Fuel Dispatch
    
    You view changes tracked by the Activity Audit feature in the Audit Log section of the Order Audit Log window. The window is available in Call On Demand Order Entry. You access it by selecting Dispatch > Audit Log. The window is always available, but the Audit Log section is populated only when the feature is enabled.
    
    You cannot view changes to a billing rate or pay rate in Fuel Dispatch.
  - TMW Operations
    
    Changes are listed on the Activity Audit tab, available in Order Maintenance and the Trip Folder. The tab is always available in the Trip Folder, but changes are shown only when the feature is enabled. The tab is not shown in Order Maintenance when the feature is disabled.
    
    You cannot view changes to a billing rate or pay rate in TMW Operations.

FleetLicense

Applies to

Fuel Dispatch, TMWSuite, TMW Operations: 15.30.074

Description

The system uses fleet licensing information to determine whether the assets on a trip belong to a fleet that is licensed for hauling loads in the jurisdictions on a trip. You record fleet licensing information based on jurisdiction, license expiration date, and gross vehicle weight. Entries are made in the Fleet Licensing window.

This setting activates the fleet licensing feature. When it is enabled, you access the window in TMWSuite File Maintenance. You use the Edit >Fleet Licensing command to do so.

String1

N (default)
The system does not validate licensing compliance for fleet vehicles. The Fleet Licensing window is not accessible.
Y
The system validates licensing compliance for fleet vehicles. Access to the Fleet Licensing window is enabled.

Int1

This field is applicable when String1 has a value of Y.

Enter the default gross vehicle weight to be displayed in the Fleet Licensing window when you add a fleet license record. This weight can be changed on a fleet-by-fleet basis.

Additional Notes

This setting is used only for the Auto-fill Autoloading method in Fuel Dispatch and the Autoloading and Fleet Licensing features in TMW Operations. It is not used for the Learned Autoloading method in Fuel Dispatch.

GRACE

Applies to

TMWSuite: 2003 and later; Fuel Dispatch; TMW Operations

Description

Grace period refers to the number of days the system is to continue showing inactive companies and carriers; and terminated tractors, trailers, and drivers in drop-down lists. It affects drop-down lists in Order Entry, Dispatch, Invoicing, and Settlements. The system automatically updates this setting based on two things:

The [Misc]GracePeriod setting in your TTS50 file.
Whether the Show Retired Items check box in the Set List Box Properties window is selected or cleared.

You can override the grace period temporarily. You do this by selecting the Show Retired Items check box in the Set List Box Properties window. To access the window, go to Tools > Set List Box Property in any core TMWSuite application. The check box is cleared by default.

When the Show Retired Items check box is cleared:

The [Misc]GracePeriod setting in your TTS50 determines the number of days allowed.
This setting has these values:
- String1 is set to GracePeriod. This indicates that the [Misc]GracePeriod setting is to be used.
- The number in the Int1 field matches the number of days specified in the [Misc]GracePeriod setting.

When the Show Retired Items check box is selected:

The [Misc]GracePeriod setting is not used.
The system automatically updates this setting’s values.
- String1 is set to Apocalypse. Users in any base application can select IDs of inactive companies and carriers, and terminated drivers, tractors, and trailers in fields that use a drop-down list.
- The Int1 field is set to 999. This is the number of days allowed.

Selecting the Show Retired Items check box does not change the [Misc]GracePeriod setting in your TTS50. The original entry is retained. Clearing the check box resets the grace period. The system reads the entry for the [Misc]GracePeriod setting and writes that entry in this setting’s Int1 field.

String1

GracePeriod (default)
This value is based on the presence of the default value of 90 for the [Misc]GracePeriod setting in your TTS50.

Int1

-90 (default)
This value is based on the presence of the default value of 90 for the [Misc]GracePeriod setting in your TTS50.

Additonal Notes

If this setting is set to GracePeriod in String1, TMW Operations will only use the [Misc]GracePeriod TTS50 values.
It’s recommended that the [Misc]GracePeriod TTS50 setting value and the GRACE General Info Table values be kept in sync for TMWSuite.

GVWMarginOfError

Applies to

TMWSuite, Fuel Dispatch 14.40.26, TMW Operations: 15.30.074

Description

Use this setting to specify the maximum amount by which a load’s total weight can exceed the maximum gross weight.

When you save a load in the Trailer Autoload window in Fuel Dispatch and TMW Operations, the system compares the amounts in the Max Gross and Total Gross fields. If the Total Gross amount exceeds the Max Gross amount, a warning is displayed.

Int1

0 (default)
The maximum margin of error is 0 (zero). The actual gross weight cannot be more than the maximum gross weight.

Note: When the total weight for a load exceeds the maximum gross weight, the system will display a warning when you attempt to save the Trailer Autoload window.

"The Total Gross (#####) has exceeded the Max Gross (#####) + margin (###). Please adjust the order."

You cannot save the order until you change the compartment amounts.

User-specified number

Enter the maximum number of pounds or kilograms by which the total weight for a load can exceed the maximum gross weight.

Note: When the total weight for a load exceeds the maximum gross weight, the system will display a warning when you attempt to save the Trailer Autoload window.
If the difference is more than the tolerance amount, this warning is displayed:

"The Total Gross (#####) has exceeded the Max Gross (#####) + margin (###). Please adjust the order."

You cannot save the order until you change the compartment amounts.
If the difference is less than the tolerance amount, this warning is displayed:

"The Total Gross (#####) has exceeded the Max Gross (#####) but is within margin (###). Continue save?"

You can save the order without changing the compartment amounts.

Additional Notes

In the Fuel Dispatch Trailer Autoload window, total vehicle weight is calculated as:

Tractor Tare + Lead Trailer Tare + Pup Tare + Driver/Cushion + Total Commodity Weight
Use the [Order]DefaultWgtVolCount setting in your TTS50 to specify the weight, volume, and count measurement units used by your system.

HazMatMileageLookups

Applies to

TMWSuite, Fuel Dispatch

Description

This setting determines if the HazMat Mileage feature is active. This feature allows you to create routes and calculate mileages based on ALK’s hazardous material classifications. The HazMat Mileage feature also allows you to filter trips in TMWSuite’s Available Trips grid based on hazardous material classifications.

String1

N (default)
The HazMat Mileage feature is not active.
Y
The HazMat Mileage feature is active.

Note: In versions earlier than V.2014.13_07.0242, this setting was valid only if the String1 value of the DistanceLookupVersion General Info Table setting was OLD. Starting with version 2014.13_07.0242, the 2004 value is also supported.

Additional Notes

To create routes and calculate mileages based on hazardous material classifications, you must have ALK’s HazMat add-on module and either PC*MILER V.18 or PC*MILER|Streets V.18.

JurisdictionLicense

Applies to

Fuel Dispatch, TMWSuite, TMW Operations: 15.30.074

Description

Jurisdictions (states/provinces) use road restrictions to specify the maximum gross vehicle weight for a road class. This setting activates functionality that allows you to record:

Record weight limits for jurisdictions
Record weight limits for axle groups
Record restrictions for an equipment configuration

Using this information, the system can validate that the equipment assigned on a trip complies with the road restrictions in place for all jurisdictions the trip’s route passes through.

You record the information in the Jurisdiction Restrictions window.

TMWSuite

The Jurisdiction Road Restrictions window is in the File Maintenance application.

When the functionality is activated, the Jurisdiction Road Restrictions command appears in the Edit menu. It opens the window .
TMW Operations

The Jurisdiction Road Restrictions window in TMW Operations. When the functionality is activated, the Jurisdiction Road Restrictions command appears in the Tools menu’s Tools Maintenance sub menu. It opens the window.

String1

N (default)
The system cannot be set up to use jurisdictional road restrictions. The menu command is unavailable.
Y
The system can be set up to use jurisdictional road restrictions. The menu command is available.

Note: Using this option requires that:
- The DistanceCacheByState General Info Table setting has a String1 field value of Y.
- The DistanceLookupVersion General Info Table setting has a String1 field value of 2004.

Int1

If String1=Y, enter the default axle group weight.

Your entry appears in the Jurisdiction Road Restrictions window’s Weight field. You use the window to add an axle group to a jurisdictional road restriction record.

Int2

If String1=Y, enter the default maximum permissible gross weight.

Your entry appears in the Jurisdiction Road Restriction window’s GVW field. You use this window to add an equipment configuration to a jurisdictional road restriction record.

Additional Notes

This setting is used:

Only for the Auto-fill Autoloading method in Fuel Dispatch
Note: It is not used for the Learned Autoloading method in Fuel Dispatch.
The jurisdictional features in TMW Operations

MaxDailyOnDutyHours

Applies to

TMWSuite, Fuel Dispatch, TMW Operations

Description

In TMWSuite, this setting specifies the maximum number of available on-duty hours that can be displayed, regardless of the calculated estimate. It applies to these locations:

Dispatch Trip Folder Log Date fields
Day 1, Day 2, and Day3 fields on the Driver tab. The tab is located in the Planning Worksheet’s Available Resources grid
The Find Drivers window Day1 Hrs, Day2 Hrs, and Day3 Hrs fields

In Fuel Dispatch and TMW Operations, this setting determines the maximum number of available working hours during a 24-hour period. These hours appear in the Driver Hours of Service window.

String1

14 (default)
The driver has a maximum of 14 hours per day.
User-defined number of hours
Enter the maximum number of working hours per day.

Note: You must enter a whole number. Entering a decimal point causes an error.

Additional Notes

CRM Right does not support this feature.

NumberOfDaysForNoteExp

Applies to

TMWSuite: 2005.04_10.0281 and later, CRM Right, Fuel Dispatch

Description

By default, when new notes are created, the value in the note’s Note Expires field is the apocalypse date of 12/31/2049. You can enter a specific expiration date for a note, or you can use this setting to specify the number of days until a note expires.

In versions prior to V. 2010.09_08.0990, this setting used only the Int1 field. To specify the number of days until a note’s expiration, you entered a number from 1 to 9999. The same method of calculating the expiration date was used for all note types (i.e., notes attached to orders, companies, resources, Pay To’s, movements, invoices, settlements, and commodities). Also, the adjusted expiration date did not display until you closed and reopened the Notes window.

Int1

Starting with V.2010.09_08.0990, TMW added options for the String1 fields. These options allow you to set a different numbers of days for order type notes than you set for other note types. Entries are allowed in the String1 and Int1 fields.

When String1 is:

Blank (no entry)
The expiration date is based on your entry in the Int1 field. When Int1is set to:
0 (or blank)
The expiration date will be the system’s apocalypse date of 12/31/2049.
1 to 9999
The note expires the specified number of days after the date it was first saved.
C
The note’s expiration date is based on the date/time it was first saved.

In the Int1 field enter the number of days that you want the system to add to the date/time the note was first saved. Values from 0 to 9999 are acceptable.
E
The note’s expiration date is based on the whether the note is order-based.
- Order type notes
  The note’s expiration date is based on the date/time recorded in the order’s Latest date/time field for the last drop.
  
  In the Int1 field enter the number of days that you want the system to add to the date/time recorded in the order’s Latest date/time field for the last drop. Values from 0 to 9999 are acceptable.
- All other note types
  The note’s expiration date is based on the date/time it was first saved.
  
  In the Int1 field enter the number of days that you want the system to add to the date/time the note was first saved. Values from 0 to 9999 are acceptable.

Additional Notes

Do not enter a decimal point in the Int1 field.
This setting affects notes for companies, resources (drivers, tractors, trailers, carriers) Pay To’s, commodities, orders, movements, invoices, and settlements.
Regardless of the options set in this key, you can manually set a different expiration date for a note in the Note Expires field.
By default, the Int1 field is blank. Once an entry is made in the field, you cannot delete the value to return the field to its blank state. You must save a value between 0-9999. The value 0 (zero) has the same meaning as blank.

OilFieldOrderSources

Applies to

Fuel Dispatch V.2023.4 and later

Description

In previous versions, orders with an order source of “OFOE” would open in Oil Field Order Entry instead of Call On Demand Order Entry when the TTS50 setting ShowOilFieldOrderEntry=Y. All other order sources would open in Call On Demand Order Entry. Use this setting to enter a comma-separated list of order source codes for orders that should open in Oil Field Order Entry.

String1

User- specified list
Enter the order source code as a comma-separated list.
For example: OFOE,OIL
Note: String1 is case sensitive. When entering order source codes, matching case sensitivity is required.

Additional Notes

The TTS50 setting ShowOilFieldOrderEntry must still be set to ‘Y’ to open orders in Oil Field Order Entry.

SERVICERULE

Applies to

TMWSuite, TMW Operations

Description

This setting determines the default service rule.

String1

7/60 (default)
This option sets the 7-day/60-hour service rule.
User-defined label option
Enter the value in the Abbr field of the desired ServiceRule label.

ShowExpiredNotes

Applies to

TMWSuite: 2003 and later, CRM Right, Fuel Dispatch, TMW Operations

Description

Determines whether the system will show expired notes in the Notes window.

String1

Y (default)
The system will show all notes, including those that have expired.
N
The system will not show expired notes.

ShowExpiredNotesGrace

Applies to

TMWSuite: 2003 and later, CRM Right, Fuel Dispatch

Description

This setting instructs the system to allow notes to display in the Notes window for a set number of days past their expiration date. After the grace period ends, the system hides the expired note.

Int1

0 (default)
The system will show all notes, including those that have expired.
Value
Enter the number of days you want expired notes to display.

Additional Notes

To use this setting, you must have ShowExpiredNotes=N in the General Info Table.

TrlConfigurationMgtOn

Applies to

TMWSuite, Fuel Dispatch, TMW Operations: 15.30.074

Description

This setting determines if:

Tractor and trailer profiles display the fields needed to define equipment configurations
You can specify a default equipment configuration for a company in its profile
The system saves trailer autoloading history or equipment configurations for the autoloading feature
The Loading by Compartment feature is available in the TMWSuite Dispatch Trip Folder

String1

N (default)
Display the default fields in tractor and trailer profiles.

Save trailer loading history (commodities, tank loading sequences, and volumes) in the Trailer_Autoloading table. Use this information in Fuel Dispatch’s Trailer Autoload Maintenance and Trailer Compartment History windows.

Notes:
1. When you use this option:
  - The Tractor File Maintenance window displays the default fields in the Tractor year/Make Model section.
  - The Trailer File Maintenance window displays the default fields in the Vehicle Details section.
  - The Edit > Loading by Compartment option and Compartment Loading icon are grayed out in the Dispatch Trip Folder.
2. To use this option, you must have these settings in the [FuelDispatch] section of your TTS50.
  - AutoloadMethod=1
    This setting allows you to use the Learned Autoloading method.
  - DisplayAutoload=Y
Y
Display the fields for setting up axle loading configurations.

Save equipment configurations in the Freight_By_Compartment table. Use this information in the Fuel Dispatch Trailer Compartment History window.

Notes:
1. When you use this option:
  - The Tractor File Maintenance window displays axle loading configuration fields instead of the Tractor year/Make/Model section.
  - The Trailer File Maintenance window displays axle loading configuration fields instead of the default fields in the Vehicle Details section.
  - You can specify a default equipment configuration for a company. It is used for pickups and/or deliveries for that company. You use the TrlConfiguration field in the Additional Details window to identify the configuration.
  - The Edit > Loading by Compartment option and Compartment Loading icon are activated in the Dispatch Trip Folder.
2. This option is required for setting up these types of autoloading:
  - Autoloading feature in TMW Operations
  - Auto-fill Autoloading method in Fuel Dispatch
    
    Note: The [Misc]CompanyProductsRule setting in your TTS50 determines whether commodity sub codes are used with the Auto-Fill Autoloading method in Fuel Dispatch. When your system is set up this way, the density values entered for a seasonal blend are used to calculate the weight of each loaded compartment and the total commodity weight loaded on the trailer.
3. To use this option, you must have these settings in the [FuelDispatch] section of your TTS50.
  - AutoloadMethod=2, 3, or 4
  - DisplayAutoload=Y

TruETALimitTrips

First available in

Fuel Dispatch, TMW Operations

Description

Identifies the number of hours in the past to use when determining if a trip should be calculated.

Note: This setting was designed to limit old or incomplete trips from being calculated.

Int1

Blank, that is, no entry
No hours specified, all trips will be calculated.
User-specified value
Number of hours in the past to use when determining if a trip should be calculated.

Examples:
- 24 (one day)
  Any trip created more than one day in the past will not be calculated using TruETA.
- 720 (30 days)
  Any trip created more than 30 days in the past will not be calculated using TruETA.