The FWResource table is used to introduce the different resources that are available for building routes. The resource table provides specific instances of a physical unit that can actually perform the work (stops – the work that needs to be done). The resource creation process uses the specified route template to set many of the default settings needed by the different optimization engines. An external resource management system, or API request to create a resource record, may have certain attributes already set which will take precedence over the route template values.
Create: Resources can be created by themselves or several at a time. If a PreferredScheduleKey is specified, then the schedule and resource link (FWRoute) record needs to be created.
A special creation process will need to be created where one or more resources can be generated from a specific template.
Delete: When deleted, all associated FWRoute records are also deleted. There may be a need to delete location records of type temporary if they have no activities or templates associated with them.
Update: Individual record. Updates certain attributes that could have an impact on the schedule. It updates the FWRoute record associated to this Resource.
Attribute Name |
Type |
Field Size |
Description |
Required |
int |
4 |
Unique internal DB Identifier of the Resource table. |
Required | |
nvarchar |
50 |
Business key to identify the activity this Resource refers to. Must exist in the FWResource table. |
Required | |
int |
4 |
Unique internal DB Identifier of the Route Template table. |
| |
nvarchar |
50 |
Business key to identify the Route template this Resource refers to. Must exist in the FWRouteTemplate table. |
Required | |
nvarchar |
50 |
The initial location at which the route begins. ID of an entry in the FWLocation Table. The initial location attribute will determine the time zone for all the date saved on this record. If this value changes, all times will need to change to the new time zone. |
Must exist on the FWLocation table. | |
nvarchar |
50 |
The final location (Station) at which the route ends. ID of an entry in the FWLocation Table. |
Must exist on the FWLocation table. | |
nvarchar |
50 |
Business key to identify the Routing Parameter this Resource refers to. |
Must exist on the FWRoutingParameter table (default =Default). | |
int |
4 |
See ModifiedBy. |
| |
datetime |
8 |
See ModifyDate. |
| |
int |
4 |
See CreatedBy. |
| |
datetime |
8 |
See CreatedDate. |
| |
nvarchar |
500 |
See Comment. |
| |
nvarchar |
50 |
Company Name of this resource |
| |
nvarchar |
50 |
Business key to identify the Schedule this Resource refers to. This field is used to link a resource to a specific schedule during creation. |
If entered, it must exist on the FWSchedule table. | |
nvarchar |
255 |
This is a descriptive field used to identify this resource in a more user friendly way. It is not used for internal processing, but typically as output only. If parameter is not zero, displays blank if name and ID are identical. |
| |
nvarchar |
50 |
This attribute is used in the future to identify different resource status changes so that different processing can be performed based on status values, such as maintenance. |
| |
nvarchar |
50 |
The Preferred territory (zone). Must be validated against the FWCode table for a value territory. |
| |
nvarchar |
50 |
Must be validated against the FWCode table. |
| |
nvarchar |
50 |
Currently used as reference but is allocated for future processing. Must be validatedagainst the FWCode table. |
| |
nvarchar |
50 |
Currently used as reference, but is allocated for future processing. Must be validatedagainst the FWCode table. |
| |
datetime |
8 |
Earliest date and time resource can leave the base at the start of a route. Values of ”r;ScheduleDate + X” and ”r;Today + X” can be used to create relative dates. The default value comes from the RouteTemplateWindow EarliestDate and EarliestStartTime. Must be less than or equal to the LatestStartDate |
| |
datetime |
8 |
Latest date and time resource can leave the base at the start of a route. Values of ”r;ScheduleDate + X” and ”r;Today + X” can be used to create relative dates. The default value comes from the RouteTemplateWindow LatestDate and LatestStartTime. Must be greater than or equal to the EarliestStartDate and must be within the RouteTemplate time window range and frequency. |
Required | |
datetime |
8 |
Earliest date the resource can begin serving a job. Values of ”r;ScheduleDate + X” and ”r;Today + X” can be used to create relative dates. The default value comes from the RouteTemplateWindow EarliestDate and EarliestSeviceTime. Must be less than or equal to the LatestServiceDate. Must be greater than LatestStartDate. |
| |
datetime |
8 |
Latest date the resource can begin serving a job. Values of ”r;ScheduleDate + X” and ”r;Today + X” can be used to create relative dates. The default value comes from the RouteTemplateWindow LatestDate and LatestServiceTime. Must be greater than or equal to the EarliestServiceDate. Must be greater than LatestStartDate. |
| |
datetime |
8 |
Earliest date and time that a resource can end its route. If the resource reaches its final depot earlier, it must stop and wait, increasing the total elapsed time. The default value comes from the RouteTemplateWindow EarliestDate and EarliestEndTime. Must be less than or equal to the LatestEndDate. Must be greater than LatestStartDate. Must be greater than LatestServiceDate. |
| |
datetime |
8 |
Latest date and time that the resource can return to the final depot. Values of ”r;ScheduleDate + X” and ”r;Today + X” can be used to create relative dates. The default value comes from the RouteTemplateWindow LatestDate and LatestEndTime. Must be greater than or equal to the EarliestEndDate. Must be greater than LatestStartDate. Must be greater than LatestServiceDate. Must be within the RouteTemplateWindow time window range and frequency. |
| |
Float |
8 |
These values are applicable to the corresponding stop occurrence values used to manage capacity. For example: If the stop is a Drop-off type stop then this amount is reduced by the corresponding stop amounts (plus factor) to reflect additional capacity on this resource and save it in the ProjectedMesureCapacity on the route record. If the stop is a pickup then the corresponding amount is added to reduce this capacity. |
| |
Float |
8 |
When entered, the Measures1-9 occurrence must also be entered. This value provides the ability to reduce or increase the Measure values by this factor. This attribute is a percentage value used to adjust the measure value. For example: If the factor is less than one then the measure is reduced. If it is equal to one, then the measure will stay the same; and if the factor is more than one, then the measure is more. A negative value is not allowed. |
| |
Float |
8 |
When entered, the Measures1-9 occurrence must match the location supplied measure values; otherwise, recharge is ignored. The recharge rate is measured in units per second and is associated with the MeasureRechargeRate and Measure values of the location. |
| |
smallint |
2 |
This value is used to set the absolute threshold of the total number of stops that can be associated with this route. The stop types must be PICKUP (1), DROPOFF(0) or RECHARGE(4). |
| |
nvarchar |
255 |
Each specified code must exist on the FWCode table for the Requirement type. Multiple entries are possible and delimited by a comma or space. See route template for details. |
| |
float |
8 |
Used as a percentage of the capacity (measure amount) to apply the CompleteFullBonus and PartialFullPenalty values. Please see complete full bonus and partial full penalty for details. A value of 1.0 will require all measures to be at capacity before the Complete Full Bonus is applied and to avoid incurring the Partial Full Penalty. A value of 0.5 will require at least 50% capacity utilization on all measure to receive the Complete Full Bonus. If one of the measures is less than 50%, then the Partial Full Penalty is applied. A value of 0.0 (default) indicates that the bonus and penalty values is ignored. Percentage of full capacity that is acceptable for applying CompleteFullBonus and PartialFullPenalty. |
| |
float |
8 |
This attribute works in conjunction with the FullThreshold value. The CompleteFullBonus is added to the overall route profit when all measures are equal to or greater than the FullThreshold values. If not, then this value is ignored. Bonus for a route that has all measures filled above its FullThreshold. |
| |
float |
8 |
This attribute works in conjunction with the FullThreshold value. The PartialFullPenalty is subtracted from the overall route profit when one or more measures are less than the FullThreshold values. If not, then this value is ignored. Penalty applied to a route that has one or more measures filled more than the FullThreshold percentage, and one or more measures filled less than the FullThreshold percentage. |
| |
float |
8 |
This attribute is a set base profit value. It is cumulative where the template value is added to the Resource value whenever a route is created from this resource. Tells the Optimizer how important it is to schedule the job or item. |
| |
float |
8 |
This value is added to the overall profit of the route for every additional stop at a specific location. For example: If we have two stops at the same location, then the second stop will have the bonus applied once. If a third stop was also served at the same stop, then the bonus is applied twice, once for the second stop and again for the third stop. If we have two different locations with two serviceable stops at each location (type pickup or drop-off), then the bonus is applied twice, once for the second stop of the first pair and again for the second stop of the second pair. And so on. Bonus for a stop that has all measures filled above its FullThreshold. |
| |
float |
8 |
This value is used to discount the penalty of the initial leg of the route. It is a percent value used to reduce the cost of that leg. For example: a value of 1.0 will discount the full penalty of this leg and no penalty is incurred, a value of .6 will discount 60% of the penalty and apply 40% of the penalty. A value of .15 will discount 15% and apply 85% of the penalty. |
| |
float |
8 |
This value is used to discount the penalty of the final leg of the route. See the discount initial leg for details. |
| |
float |
8 |
This value is used to apply a penalty for every meter driven. Previous setting was in miles, so care should be taken when updating or using this value. Straight-line distance is used for this calculation. This amount is multiplied by the distance and deducted from the overall route profit. |
| |
float |
8 |
This value is used to apply a penalty for every order (type Pickup or Drop-off) serviced. Total penalty is multiplied by this value and the number of orders serviced. It is deducted from the overall route profit. If less than the MinPaidOrders have been assigned to this route, then the MinPaidOrders is used as the multiplier. See the MinPaidOrders for details. |
| |
smallint |
2 |
This value is used to set a minimum threshold of the number of orders that the PenaltyPerOrder is applied against. For example: if the number of orders serviced is three, and this value is set to 5, then the PenaltyPerOrder is applied against the minimum setting. If seven orders were serviced, then the penalty is applied against the actual value serviced and this setting is ignored. |
| |
float |
8 |
Per minute penalty for a missed time window. With values greater than zero, the Optimizer tends to keep unserved jobs close to their time windows instead of placing them geographically. |
| |
float |
8 |
This value is used to penalize a route that missed its LatestEndDate time. Regardless of how much the time window was missed, the same flat value is used. Should be set to a value roughly equal to the profit value for a job. |
| |
float |
8 |
This value is applied for every second that the resource waits to service the order. It is applied against every second of the route. WaitTime values are used. |
| |
float |
8 |
This attribute is based on using occurrence one first, then two, three, and so on. It is not possible to skip any occurrences. Occurrences two through seven must be empty if one is empty. Occurrences three through seven must be empty if two is empty and so on. This value is used in conjunction with the WorkDuration attribute where they must be applied in pairs. If one is entered, the other is required. These values are used to either increase or decrease the penalty as the route executes over time at different rates. This value is applied for every second duration. For example: if the WorkDuration is 7,200 seconds and the penalty value is 1.00, this route will insure a penalty of 7,200 points. If the second occurrence duration is 3600 and the penalty is 1.5, then the total penalty is 7,200 points from first occurrence and 5,400 points for the second occurrence and so on. Please note that the duration must be in seconds. |
| |
int |
4 |
This attribute is directly related to the Work1-7Penalty attribute and each Work1-7Penaty occurrence must have a corresponding Work1-7Duration value and must be in seconds. These values are used to either increase or decrease the penalty as the route executes over time at different rates. See Work penalty for more details. |
| |
int |
4 |
This attribute specifies the length of the break to be taken. If this attribute is empty the following must also be empty: · MaxElapsedTimeBeforeBreak · MaxDriviyTimeBeforeBreak · MaxNumberOfBreaks |
| |
int |
4 |
If entered, the BreakDuration must also be greater than 0. This attribute indicates how much time must pass before a break can be scheduled. Time is measured in seconds. If BreakDuration was entered, then this attribute must be greater than 0. |
| |
int |
4 |
If entered, the BreakDuration must also be greater than 0. This attribute indicates how much driving time must pass before a break can be scheduled. Time is measured in seconds. If BreakDuration was entered, then this attribute must be greater than 0. |
| |
tinyint |
1 |
If BreakDuration was entered, then this attribute must be greater than 0. This attribute indicates the maximum number of breaks allowed for a given work unit. A work unit is dependent on whether rests are being used. If rests are not being used, then the number of breaks is allowed for the duration of the route. If rests are specified, then this number of breaks is allowed between every rest. For example:When a rest occurs, the number of breaks taken is reset and the count starts again. The default value is zero, which represents an unlimited number of breaks. If BreakDuration was entered, then this attribute must be greater than 0. |
| |
bit |
1 |
Determines if time spent on break is counted as elapsed time between rests. |
| |
int |
4 |
This attribute specifies the length of the rest to be taken. If this attribute is empty the following must also be empty: · MaxElapsedTimeBeforeRest · MaxDrivingTimeBeforeRest · FirstStopTimeThreshold |
| |
int |
4 |
This attribute indicates how much time must pass before a break can be scheduled. Time is measured in seconds. If entered, then RestDuration must be greater than 0. |
| |
int |
4 |
This attribute indicates how much driving time must pass before a break can be scheduled. Time is measured in seconds. If entered, then RestDuration must be greater than 0. |
| |
float |
8 |
If entered, then RestDuration must be greater than 0. This attribute is very similar to the Early Rest Time Threshold attribute in that its value is applied against the maximum elapsed or driving time settings with the exception that it is only considered for the first stop on the route. This attribute allows users to have the first stop treated differently from other stops (e.g., only allow early rests to be scheduled for the first stop). The First Stop Time Threshold attribute is only evaluated if the Allow Early Rests setting is true. It is also represented as a percentage of the maximum elapsed or drive time. Note― Both the First Stop Time Threshold and the Early Rest Wait Threshold must be met for an early rest to be taken. |
| |
bit |
1 |
This attribute determines how the recuperation time is considered. If enabled, the entire recuperation time is considered to be off the clock and the clock is reset when work begins again. If disabled, then the clock will restart as soon as the recuperation time has elapsed. This is only significant if the idle time before a stop is larger than the Recuperation Time attribute. For example: If Use Full Wait As Rest were false, the idle time before a particular stop were eight (8) hours, and the Recuperation Time for the resource were six (6) hours, then the clock would restart two (2) hours before the idle time were completed (when work at the stop begins). |
| |
bit |
1 |
If set to true the following must also be greater than 0: · EarlyRestTimeThreshold · EarlyRestWaitThreshold This attribute indicates whether early rests are allowed. If yes, then rests can be scheduled before the maximum elapsed or drive time threshold values have been reached. If no, then the maximum elapsed or drive threshold values must be reached before a rest can be scheduled. |
| |
float |
8 |
If greater than 0, then the AllowEarlyRests must be set to true. This attribute indicates how much of the maximum elapsed or drive time threshold must be used before an early rest can be scheduled. The early rest time threshold is only evaluated when the Allow Early Rest indicator is enabled. The Early Rest Time Threshold value is represented as a percentage of the maximum elapsed or drive time. For example: if the Maximum Elapsed Time Before Rest attribute is set to four (4) hours and the Early Rest Time Threshold is set to .50 (50%), then the earliest that the rest can be scheduled would be two (2) hours into the route. Note― Both the Early Rest Time Threshold and the Early Rest Wait Threshold must be met for an early rest to be taken. |
| |
float |
8 |
If greater than 0, then the AllowEarlyRests must be set to True. This attribute indicates how much of the recuperation time must be available to schedule an early rest. It is represented as a percentage of the total recuperation time. In other words, the Early Rest Wait Threshold attribute works in conjunction with the Recuperation Time attribute. For example: if the Recuperation Time is eight (8) hours and the Early Rest Wait Threshold is set to .75 (75%) then an early rest can be taken only if there is a period of idle time that is greater than six (6) hours, 75% of the total recuperation time. The early rest wait threshold is only evaluated when the Allow Early Rest indicator is enabled. Note― Depending on the stop in question, both the Early Rest Time Threshold or First Stop Time Threshold and the Early Rest Wait Threshold must be met for an early rest to be taken. |
| |
bit |
1 |
Specifies whether or not an early rest should be taken whenever the wait time to serve a job is larger than the Resource's RecuperationTime. If false, early rests are entirely controlled by FirstStopTimeThreshold, EarlyRestTimeThreshold, and EarlyRestWaitThreshold. |
| |
int |
4 |
This attribute is used to set a consistent recharge duration in seconds for this resource. |
| |
int |
4 |
Restricts the "dwell" time for a route, which is the total elapsed time from the beginning of service for the first job (initial drive and parking time are ignored) through the final return to depot. A value of 00:00 places no restriction on the dwell time. |
| |
int |
4 |
Maximum elapsed time for the entire route. Elapsed time is measured from start of route through the return to final depot. |
| |
int |
4 |
This attribute is used to set an initial service duration for the first job for the same customer at the same location. It is added to the standard service duration once for each grouping of same stop orders. |
| |
float |
8 |
Service time "overhead" for the customer or depot. Added to the customer's first job. Useful in operations such as couriers, where several jobs may be performed in the same amount of time as a single job. This attribute is used to set a consistent service duration for this resource. |
| |
int |
4 |
This integer value (in seconds) is added to the post-service duration of the order, order lines, and location post duration when the activity is created. See the service duration attribute for more details. |
| |
float |
8 |
This attribute can be used to adjust and control how quickly a resource serves stops. It is used to calculate how long it takes a resource to service a stop by dividing the stop's total service duration (including pre and post values) by the resource's ServiceSpeedFactor value. A value less than 1.0 increases the time the resource requires to service stops, and a value greater than 1.0 decreases the time. For example: If stop X has a total service duration of 100 seconds. · A resource with a ServiceSpeedFactor of 1.0 needs 100 seconds to serve it (100/1.0 = 100). · A resource with a ServiceSpeedFactor of .50 needs 200 seconds to serve it (100/0.5 = 200). · A resource with a ServiceSpeedFactor of 1.5 needs 67 seconds to serve it (100/1.5 = 67). |
| |
float |
8 |
Used to offset the RoutingParameter speeds. Changes travel times without reconfiguring the Routing Parameter attributes or the speed attributes. Numbers greater than one create faster travel times; numbers less than one create slower travel times. The calculation is: adjusted time = calculated time multiplied by speed factor. For example: calculated time = 100, Speed factor = .75, resulting in an adjusted time of 75 (100 X .75 = 75). |
| |
float |
8 |
This attribute restricts the distance that this resource can travel in meters, not miles. |
| |
float |
8 |
This attribute is used to determine the distance at which two stops are considered separate stops. If the distance between two sequential stops is less than this value, it is assumed that the vehicle parks once to service both stops. Please note that the unit is meters not feet. |
| |
float |
8 |
This attribute is directly related to the Speed1-7 attribute and each Speed occurrence must have a corresponding Speed1-7Threashold value This attribute works in conjunction with the Speed Attribute where the speed is used for the corresponding speed threshold distance. Once the distance is reached, the second occurrence speed and distance is used. |
| |
float |
8 |
This attribute is directly related to the Speed1-7 attribute and each Speed occurrence must have a corresponding Speed1-7Threashold value. |
| |
float |
8 |
Distance in Meters: Allows Optimizer to make appropriate geographic decisions based on the current set of orders in the system. Unlike "static" zones (which must be pre-determined in the data set using the "Zone" attributes), Dynamic Zoning allows the set of Resources/Jobs allowed for any given optimization to change over time based on the current assignment of jobs and Distance value. |
| |
int |
4 |
The Requirement Set ID taken from the FWRequirementSet table. |
| |
float |
8 |
This attribute is used to set a base penalty value that is issued to deploy this resource. It is deducted from the overall route profit. Default is zero (0). |
| |
nvarchar |
500 |
User Defined Fields for Strings 1...9 |
| |
int |
4 |
User Defined Fields for integers 1..3 |
| |
float |
8 |
User Defined fields for numbers 1…3 |
| |
nvarchar |
512 |
This attribute is used to convey selection criteria from the Route Planner UI or other external applications. |
| |
int |
4 |
Unique Identifier of the Schedule record. Must exist on the FWSchedule table. |
| |
int |
4 |
Maximum Driving Time before a break. |
| |
float |
8 |
Multiplier that the advise will use to calculate nominal driving time. |
| |
datetime |
8 |
Date of the final day supplied in WorkWeekHistory. |
| |
int |
4 |
Number of days in a work week (e.g., 6 or 7). |
| |
int |
4 |
Number of hours that can be worked (e.g., 70:00). |
| |
int |
4 |
Idle time required to reset the work week (e.g., 34:00). |
| |
int |
4 |
Time of day marking the end of one ’r;day’ and the beginning of the next (e.g., midnight, entered as 00:00). |
| |
int |
4 |
Hours worked per day for each day from 1-WorkWeekLength. For any day without a history supplied zero (0) will be assumed. |
| |
int |
4 |
Indicates if this route is a Master Route. Valid values are: · 0 – Normal Route · 1 – Master Route |
| |
int |
4 |
Maximum number of redispatches that can occur during a route |
| |
int |
4 |
Maximum elapsed time that can pass between visits to the depot. |
| |
int |
4 |
Unique Identifier of the Driver record. Must exist on the FWDriver table. |
| |
int |
4 |
Unique Identifier of the Truck record. Must exist on the FWTruck table. |
| |
int |
4 |
Unique Identifier of the Trailer record. Must exist on the FWTrailer table. |
| |
nvarchar |
|
Allows RMPI to add a startup time at the beginning of a route. This time can be specified by resource and/or by location. If both exist, RMPI adds them together. |
| |
nvarchar |
|
Allows RMPI to add a shut down time at the end of a route. This time can be specified by resource and/or by location. If both exist, RMPI adds them together. |
| |
int |
4 |
This field specifies the day of the week to use when generating routes from this master route record. For example, this master route may apply to Monday/Wednesdays and Fridays |
| |
nvarchar |
50 |
This field is used to generate routes from master routes and use this field name to match the orders that come with this field. If no value is specified in this record, then the value will come from the MasterOrders assigned to this Master Route. |
| |
nvarchar |
512 |
This field is used when generating routes from this master route. This field value will be used as an extra criterion to match real orders to this route. |
| |
bit |
1 |
|
Enables Resources to start empty and allows them to load at their home or remote location. To activate this functionality on a schedule, the AllowEmptyStart property must be set to ”r;1”. | |
nvarchar |
|
Allows RMPI to add a startup time at the beginning of a route. This time can be specified by resource and/or by location. If both exist, RMPI adds them together. |
| |
nvarchar |
|
Allows RMPI to add a shut down time at the end of a route. This time can be specified by resource and/or by location. If both exist, RMPI adds them together. |
| |
|
|
Determines whether the Initial or Final Depot should be included in the dynamic zoning distance test. The attribute can have one of the following values: • 0: do not include initial or final depot in dynamic zoning (this was the behavior in previous versions) • 1: include only the initial depot in dynamic zoning • 2: include only the final depot in dynamic zoning • 3: include the initial and final depots in dynamic zoning This setting is defaulted to ‘0’. |
| |
datetime |
8 |
User-defined date/time fields |
| |
nvarchar |
50 |
The resource key of the master route which a resource was created from. If a resource was not created from a master route, this value will be null |
| |
float |
8 |
The route geofencing threshold |
| |
float |
8 |
The stop geofencing threshold |
| |
datetime |
8 |
Date and time resource can leave the base at the start of a route. |
| |
nvarcar |
500 |
User-defined URL fields |
| |
float |
8 |
This attribute works in conjunction with the FullThreshold value. The CompleteFullBonus is added to the overall route profit when all measures are equal to or greater than the FullThreshold values. If not, then this value is ignored. Default is zero (0). |
| |
float |
8 |
The maximum workload a resource can handle during the entire route duration, no matter how many recharge occurs in it. |
| |
float |
8 |
Used to determine when to perform reloads |
| |
bit |
1 |
Tells the optimizer if the recharge should be done to capacity or not. If this value is set to zero, then the recharge amount will only be required to fulfill the planned stops in the route. 1=Recharge to Capacity, 0=Recharge |
| |
int |
4 |
Integer that encodes indices of measures that a resource needs to fill up before closing out the route in preparation for next day's route. MeasureN is encoded into 2N-1. For example, the requirement to fill up Measure1, Measure3, and Measure6 are represented by EndVehicleMeasuresRequired=37 |
| |
bit |
1 |
Resource is allowed to recharge |
| |
float |
8 |
Used to calculate the time required to change commodities in a reload. |
| |
nvarchar |
100 |
Resource is allowed to recharge |
| |
datetime |
8 |
User-defined date/time fields |
| |
float |
8 |
Maximum as-the-crow-flies distance away from initial depot of resource |
| |
int |
4 |
The rest time for redispatch (reserved for future development) |
| |
bit |
1 |
RMPI has been configured to support this setting through the UseRoutePosition attribute. RMPI handles this new setting as follows: • If the setting is disabled at the schedule level, it will not be used by RMPI • If the setting is enabled at the schedule level, it will be used based on the value of resource setting • If the resource setting is null, RMPI will use the schedule setting • If the setting is enabled at the resource level, RMPI will use the resource setting • If the value of the setting at the resource level is 0, RMPI will not apply the UseRoutePosition setting to the particular resource |
| |
int |
1 |
When enabled, the resource will always be routed as if carrying hazardous materials. When disabled, the system will evaluate the onboard orders for hazardous materials. |
| |
int |
4 |
Select one of the following options from the drop-down menu to control recharges at depots: • Recharge at any depot • Recharge only at initial depot • Recharge only at final depot • Recharge at either initial or final depot |
| |
MinInterstopTravelTime |
|
|
This field allows Descartes Route Planner to handle “Interstop” service time values from Descartes Route Planner RS. |
|
nvarchar |
50 |
Business key to identify the Truck this Resource refers to. Must exist in the FWTruck table. |
|