Optimization Request Fields

Note: Optimization requests can be accessed in Update mode only when the Status is Wait or Hold.

Plan

Plan ID: The Plan ID for the optimization request. This will default based on the Current Plan ID for the current user when the optimization request is created and can never be modified.
Description: The description for the load plan. This is not updatable from this context. It can be updated by authorized users from the List of Plans.

Parameters

Request ID: The system-assigned identifier for the optimization request. This ID is never editable. Presented only in Update and View modes.
Status: The status for the optimization request. Supported statuses are: Wait, Processed, Failed, Completed, Canceled, Hold. Status can be controlled using explicit operations from the List of Optimization Requests when in Wait or Hold status. Status changes will also occur when the optimization process is initiated and terminated. Presented only in Update and View modes.
Scheduled Date/Time: The scheduled date and time to be used when optimization is performed for this request. Expressed in time zone context of the system. It is editable when the optimization request is accessed in Update mode. If the Earliest Scheduled Date Source in the Optimizer Server Configuration is “MANAGER_DATE”, Optimizer uses the Scheduled Date/Time as the earliest time that a carrier can depart from the first stop for any load created by the optimization request.
Submitted Date/Time: The date and time when the optimization request was submitted from the UI or via API. This is expressed in the time zone of the system and cannot be modified in Update mode. Presented only in Update and View modes.
Constraints Override File: This refers to the optimizer constraints file that will be used during optimization. Eligible entries are defined by the optimizer constraints table. This field is editable when the optimization request is accessed in Update mode. The optimizer constraints table in Transportation Manager refers to a location where the actual file is located. This will default to the value previously assigned during the current session. If the current plan specifies an optimizer constraints group ID, only the constraint override files attached to that optimizer constraint group will be displayed during optimization request creation. See List of Optimizer Constraints (Employee) / List of Optimizer Constraints Group (Employee).
Resource Project ID: The CEA resources having the same value as the request's selected resource project ID will be used to evaluate loads and trips during optimization. All loads and trips that are created or modified by the optimization will be set to the Resource Project ID (RPID) associated with the optimization request. When creating an optimization request, the RPID associated with the Plan is assigned to the optimization request, by default. For loads assigned to a trip, the RPIDs on loads do not have to be the same across all loads and also does not have to be the same as for the trip. Trip level RPID will be honored when assigning CEA Resources to a trip. A load level RPID that is different from a trip level value would be used only if the load is subsequently removed from the trip. Similarly, a booking may contain loads having different RPIDs although the booking itself does not refer to a RPID.
Optimizer Instance Group: Specifies the group of optimizer instances that should be used when optimizing. One instance from the group will be selected. A default will be established based on the optimizer instance group where the “Is Default” flag is True. At any time, a maximum of one optimizer instance can be designated as the default. This can be modified when the optimization request is accessed in Update mode. Transportation Manager will not dynamically determine which optimizer instances are available at the moment when an optimization request is created. Any active Optimizer Instance Group ID will be accepted. Only active optimizer instance groups will be available for selection when triggering an optimization request. This field will be mandatory when active optimizer instance groups have been configured in Transportation Manager. See Optimizer Instance Groups.
Request Type: User-defined type for an optimization request. The default value is established from the current plan.
Include Eligible Loads: Indicates whether eligible loads should be selected to be used by optimizer's re-planning, trip and booking building strategies. If filter criteria are specified on the Create Optimization Request – Select Loads page, only the loads that satisfy the selection criteria and meet predetermined eligibility requirements will be selected. Not editable in Update mode.
Include Eligible Trips: Indicates whether eligible trips should be selected to be used by optimizer's re-planning and trip building strategies. If filter criteria are specified on the Create Optimization Request – Select Trips page, only the trips that satisfy the selection criteria and meet predetermined eligibility requirements will be selected. Not editable in Update mode.
Include Eligible Bookings: Indicates whether eligible bookings should be selected to be used by optimizer’s re-planning and booking strategies. If filter criteria are specified on the Create Optimization Request - Select Bookings page, only the bookings that satisfy the selection criteria and meet predetermined eligibility requirements are selected. Not editable in Update mode.