Shipment Management

Logic Configuration - Container Optimization

Logic configuration container optimization parameters are accessed via the Logic Configuration page if you select a logic configuration type of Container Optimization.

The options you select determine how Oracle Transportation Management optimizes containers. You can choose to minimize the number of containers used, maximize the overall utilization for all containers, or minimize cost. You then specify if you want to optimize containers based on weight, volume, or a combination of weight and volume. You must select at least one container optimization metric and at least one container optimization objective.

The property glog.business.ConoptConverter.CheckOrderDates determines if OTM should skip the time window checks in container optimization.

By default, the 3D load configuration view uses built in 3D functionality.

Note: The Cortona VRML plugin has been deprecated. If necessary, you can configure the OTM Load Config action to use Cortona via the property glog.webserver.loadconfig.useCortona. The 3D viewer available in the Workbench does not support Cortona.

To display the 3D load configuration using Cortona, a VRML plugin is required for Microsoft Internet Explorer for 3D load configuration view. Cortona is not supported in Safari or in newer versions of Chrome.

Pattern Based Load Configuration

Pattern based load configuration uses the following parameters:

  • EMPTY SPACE SORT CRITERIA
  • EVALUATION DEPTH
  • ITEM SORT CRITERIA - except the value = Stacking Index. OTM does not stack different ship units on top of each other in a pattern-based load configuration. The higher the value, the lower it will be placed.
  • LOAD PLACEMENT ITERATION CRITERIA

The following parameters are not used with pattern based load configuration as they are irrelevant for pattern based:

  • IS LENGTHWISE ORIENTATION FIRST
  • MAX OVERHANG PERCENT
  • ROTATION SORT CRITERIA

The following parameters work differently with pattern based load configuration:

  • EMPTY SPACE SORT CRITERIA: Pattern based load configuration ignores where HEIGHT is. OTM is just concerned about the order or LENGTH and WIDTH. Also, it works differently from 3D. For example, if we have WIDTH, LENGTH, we first try to fill in remnant area first and then fill the non-remnant area. If it is LENGTH, WIDTH, then we fill non-remnant area first and then fill remnant areas at the end. However, the placement of items within the pattern always ends up minimizing the length.
  • LOAD PLACEMENT ITERATION CRITERIA: The rotation is ignored as we look at all the patterns at once and so there is no need to look at individual orientations. In essence, there are two options, SPACE, ITEM and ITEM, SPACE. The position of ROTATION is ignored.

Container Optimization Algorithms

See the Container Optimization Algorithms topic to see how the Container Optimization algorithms interact. Column generation algorithm works with some other algorithms but is incompatible with others.

Parameters

The parameters are in alphabetical order and list the group they are in.

Parameter

Group

New in Version

Functional Description

3D SCORING MAXIMUM ITERATIONS WITHOUT IMPROVEMENT

Container Optimization 3D Scoring

6.4.2

This parameter limits how many iterations the 3D scoring mechanism will try without seeing improvement. Then OTM will stop the iteration process and return the best resource obtained until that point.

See also the '3D SCORING NUMBER OF ITERATIONS' parameter.

3D SCORING NUMBER OF ITERATIONS

Container Optimization 3D Scoring

6.4.2

This parameter limits the number of times the 3D scoring mechanism will try packing equipment with items. Then OTM will stop the iteration process and return the best resource obtained till that point. The higher the value, the more performance will be impacted. The number of items being packed also affects performance.

See also the '3D SCORING MAXIMUM ITERATIONS WITHOUT IMPROVEMENT' parameter.

ALLOW PARTIAL CONOPT SOLUTION Container Optimization 24C This parameter is used to control bulk plan for providing successfully planned orders when some of the orders fail to plan in Container Optimization

CHECK COMMODITY COMPATIBILITY

Container Optimization Tuning Parameters

6.1

Set this parameter On to have Oracle Transportation Management check the commodity compatibilities during container optimization. The commodity compatibility checks involve checking for compatibility between the equipment group and the commodity, compatibility between two commodities and the "allow commodity mixing" checkbox on the equipment group compartments.

CONOPT COLUMN GENERATION NUMBER OF ITERATIONS

Container Optimization Tuning Parameters

6.1

Column Generation algorithm invokes a seed algorithm repetitively to generate container optimization solutions. This number sets the limit on the number of times it calls into the seed algorithm. It is possible that the column generation algorithm finds a desired solution before it hits this limit. This limit is placed so as to control the run time.

CONSIDER CAPACITY LIMITS

Container Optimization Tuning Parameters

 

Set this parameter to have Oracle Transportation Management check equipment capacity. If set, the availability of equipment is considered within the processing of each order bundle. If setting this, also set the Optimize Cost parameter. Capacity will also be checked across days depending on the time window. Multi-day resource planning only works for single leg itineraries.

The Optimize Cost and Rate Shipment Inside Conopt parameters also factor in to container optimization rating. See the topic Rating for Container Optimization to see how the three parameters work together.

If rating inside container optimization, see the parameter DRIVE WHILE RATING SHIPMENT IN CONOPT.

CONSIDER COMMITMENT ALLOCATIONS

Container Optimization Tuning Parameters

6.3.2

Set this to true to turn on the capability to have container optimization consider capacity commitment allocations when making decisions to pack equipment.

Note: When considering allocation groups on orders and matching them with the correct allocation while making routing decisions, the parameter 'APPLY ALLOCATION GROUP ON PRIMARY LEG ONLY' is taken into consideration if the leg in question is not a primary leg.

This is off (false) by default.

For some use cases, see Considering Allocations in Shipment Building.

CONSIDER SCORING LOGIC IN 3D PLACEMENT

Container Optimization 3D Scoring

6.4.2

This parameter is used to turn on/off the 3D scoring mechanism in 3D Load Configuration Container Optimization Algorithm.

When scoring is turning on, OTM will perform the following two steps of packing.

Step 1: packing without scoring mechanism.

Step 2: packing with scoring mechanism. Note that the following parameters are not considered in this step:

EMPTY SPACE SORT CRITERIA

EVALUATION DEPTH

ITEM SORT CRITERIA

LOAD PLACEMENT ITERATION CRITERIA

The default is false.

Note: In addition to setting this parameter to true, the property "glog.optimization.packingparameters.scoringInMultistop" needs to be set to "1" to enable the 3D scoring mechanism inside the Multistop logic.

CONSIDER SPACES ABOVE PLACED ITEMS SEPARATELY

Container Optimization Load Placement

6.3.2

During container optimization, there is a step (amalgamation) that looks at all the spaces at the current iteration and looks to consolidate them and make larger spaces. If there are two spaces on top of two placed objects that are of same height, there is a chance to expand the first one. This may allow placement of larger items.

If they are combined totally, the second space is removed. This may cause problems if there are stacking constraints. If an object cannot be placed on top of the first object but can be placed on the second one, the ability to place on the second one is lost since there is only space.

If set to true, OTM expands/combines the two spaces into a larger space but does not remove the second space. Then there is a larger space and a second space to try placing the next item. If there is a constraint so an item cannot be placed in the first space, the second space is still available to try placement.

Default is false (second stop is removed).

CONTAINER OPTIMIZATION BUNDLING CRITERIA

Container Optimization Tuning Parameters

24A

This parameter is used to bundle the items within Container Optimization. If the parameter is enabled, items are organized within Container Optimization based on the below bundling criteria.

The parameter will try to keep the items (by defined bundling criteria) together if this setting is used along with PACK FULL CONTAINERS WITH LARGE ORDERS FIRST to true.

The values are:

  • 0. None (default)
  • 1. Bundle by Transport Handling Unit
  • 2. Bundle by Packaged Item
  • 3. Bundle by Packing Unit

DESIRED UTILIZATION PERCENTAGE

Container Optimization Tuning Parameters

 

Specify the Desired Utilization % (Enumerative Algorithm Only) to indicate the desired utilization of how tightly you want your shipments packed. By setting this to a low value, the system will run faster, but will try and produce containers with that utilization. This setting does not guarantee the specified level of packing utilization, but rather serves as a recommendation to the solver. Running at higher utilization levels results in longer solving times. The valid range is 0-100. This is valid for the Enumerative algorithm only.

DRIVE WHILE RATING SHIPMENT IN CONOPT

Container Optimization Tuning Parameters

6.3.5

This parameter determines if only feasible rates, such as time window feasibilities, are returned when rating inside container optimization. Having this parameter set to true can impact processing time.

To use this parameter, the following parameters must also be true:

Optimize Cost

Rate Shipment Inside Conopt  

If false, the default, OTM will find the cheaper rate but it may not be feasible and could fail later during bulk planning.

For example, suppose there are two equipment options: one is cheaper but will not satisfy time windows; the other is more expensive but will satisfy time windows. With this parameter off, OTM will choose the cheaper equipment option, but the shipment will fail later during bulk plan steps where time windows are checked. This parameter ensures only feasible rates are found, but will have additional processing time.

EMPTY SPACE SORT CRITERIA

Container Optimization Load Placement

6.1

Sorting criteria for sorting the empty spaces in the equipment. This will influence how the empty spaces are chosen.

The space sorting is usually done based on the distance of the space from the nose of the trailer (length), left of the trailer (width) or the floor (height) of the trailer.

See the Pattern Based Load Configuration section above for how this works with pattern based load configuration.

This parameter will not be considered if 3D Scoring Placement is used (CONSIDER SCORING LOGIC IN 3D PLACEMENT parameter set to true).

EQUIPMENT COMPARTMENT SORT CRITERIA

Container Optimization Load Placement

6.4.2

This specifies sorting criteria used to sort the equipment compartments when using multi-compartment equipment. Valid values are:

0.Use Compartment Item Compatibility (default)

1.Use Compartment Number

2.Largest Volume

3.Largest Weight

4.Smallest Volume

5.Smallest Weight

This allows you to choose how to sort compartments. You can sort more restrictive compartments first and then less restrictive compartments. If no restrictions are specified (such as commodity compatibility and temperature control), OTM will pack compartments based on compartment number.

Alternatively, you can specify to sort based solely on compartment number, regardless of compartment restrictions by choosing the option "1.Use Compartment Number".

EVALUATION DEPTH

Container Optimization Load Placement

6.1

As the logic iterates through spaces, items and rotations, this parameter determines if the logic should return the first feasible combination or the best rotation for a given space and item and so on. A High value will involve extensive computations and hence adversely affect the performance.

This parameter will not be considered if 3D Scoring Placement is used (CONSIDER SCORING LOGIC IN 3D PLACEMENT parameter set to true).

GENERATE DOUBLE ITEM PATTERNS

Container Optimization Pattern Based Packing

6.3.3

When true, OTM generates patterns where each pattern can contain at most two items (or ship units) in various orientations to fill the width of the container as much as possible. The stacked items are assumed to be the same item with the same orientation. The pattern contains at most two of the longest item dimensions along the length, or "z", axis of the equipment. All the items in a pattern would either be all upright, all prone or all on-side (not mixed).

When this parameter as well as the GENERATE SINGLE ITEM PATTERNS parameter are turned on, OTM skips single item pattern logic because the double item pattern logic considers generating single item patterns in its logic. So, you do not need to turn on both parameters at the same time. You can select one or the other.

With this, only 2 items will be used but all combinations of all items will be checked. For example, if you have 4 items A, B, C and D, OTM will check the combinations of AB, AC, AD, BC, BD, and CD. Since single item patterns are also allowed, all A's, all B's, etc, would also be considered.

NOTE: The parameter USE PATTERNS IN 3D (also a logic configuration - container optimization parameter) must be true for this parameter to be used.

This enables you to terminate the bulk plan when using auto-generated pattern logic and also to log a warning when there is an excessive number of ship units sent in when creating the patterns. The property glog.optimization.packingsolver.LoadConfigPackingMethod.MaxItemsForDoubleAuto GeneratedPatterns allows you to define what is considered excessive. If the number of different types of items exceeds this number, OTM will skip the logic that generates patterns and will place the items using item-by-item 3D load configuration placements.

The default is false.

GENERATE SINGLE ITEM PATTERNS

Container Optimization Pattern Based Packing

6.3.3

When true, OTM generates patterns where every pattern generated contains at most one item or ship unit. OTM attempts to find patterns with different orientations of the item and fill the width of the equipment group as much as possible. The stacked items are assumed to have the same orientation as the one below. The pattern contains at most two of the ship units in its longest dimension along the length, or "z", axis of the equipment. All the items in a pattern would either be all upright, all prone or all on-side (not mixed).

When this parameter as well as the GENERATE DOUBLE ITEM PATTERNS parameter are turned on, OTM skips single item pattern logic because the double item pattern logic considers generating single item patterns in its logic. So, you do not need to turn on both parameters at the same time. You can select one or the other.

NOTE: The parameter USE PATTERNS IN 3D (also a logic configuration - container optimization parameter) must be true for this parameter to be used.

This enables you to terminate the bulk plan when using auto-generated pattern logic and also to log a warning when there is an excessive number of ship units sent in when creating the patterns. The property glog.optimization.packingsolver.LoadConfigPackingMethod.MaxItemsForSingleAuto
GeneratedPatterns
allows you to define what is considered excessive. If the number of different types of items exceeds this number, OTM will skip the logic that generates patterns and will place the items using item-by-item 3D load configuration placements.

The default is false.

IS LENGTHWISE ORIENTATION FIRST

Container Optimization Load Placement

6.1

This works in tandem with the Rotation Sort Criteria parameter (below). If two orientations have same priority based on rotation sort criteria, then this parameter takes precedence.

This parameter is not used with pattern based logic configuration.

ITEM GROUPING CRITERIA

Container Optimization Tuning Parameters

20A

This provides an option for grouping items by a specified criteria and packs every group of items in continuum in the container. The options are:
"0. None" (the default)
"1. Group by Order": ship units from the same order are put together
"2. Group by Ship Unit": ship units with the same dimension across different order releases are put into one group.

"3.Group by Order and Ship Unit": ship units within the same order release are put into one group.

This parameter is applicable to all the heuristic packing algorithms, but is not applicable to Multicontainer MIP and Column Generation packing algorithms.

ITEM SORT CRITERIA

Container Optimization Load Placement

6.1

Sorting criteria used to sort the item types (ship unit specifications or ship units).

This parameter will not be considered if 3D Scoring Placement is used (CONSIDER SCORING LOGIC IN 3D PLACEMENT parameter set to true).

ITEM TOLERANCE HEIGHT INCREMENT FOR 3D PATTERNS

ITEM TOLERANCE HEIGHT OFFSET FOR 3D PATTERNS

ITEM TOLERANCE LENGTH INCREMENT FOR 3D PATTERNS

ITEM TOLERANCE LENGTH OFFSET FOR 3D PATTERNS

ITEM TOLERANCE WEIGHT INCREMENT FOR 3D PATTERNS

ITEM TOLERANCE WEIGHT OFFSET FOR 3D PATTERNS

ITEM TOLERANCE WIDTH INCREMENT FOR 3D PATTERNS

ITEM TOLERANCE WIDTH OFFSET FOR 3D PATTERNS

Container Optimization Pattern Based Packing

6.3.4

 

These parameters allow you to group THUs that are slightly different for loading purposes. You may have several THUs that are slightly different from one another. Normally, you define ship unit specifications in exact dimensions and OTM considers all of those as different when it comes to placing them in a container. With these parameters, you can indicate what tolerances to apply to determine if dimensions of two ship units are the "same" for packing and placement purposes.

With tolerances defined, packing algorithms will be based on your defined tolerances. The alternate dimensions and alternate weight will be used in creating patterns. These dimensions are not used in the actual dimensions of the objects, so there is a possibility of "gaps" showing up in Cortona since OTM uses the alternate dimensions in placements while using the exact original dimensions to represent the ship unit pieces.

For every dimension, height, length, width and weight, you can define an increment and an offset. Based on these two values, the entire dimension is divided into multiple bands or ranges. Any ship unit dimension in a band is mapped to the upper end of the range. For example, lets say the range is 10 cm and offset is 5 cm. This means that the ranges are: 5-15, 15-25, 25-35 and so on. That is, the ranges start at the offset, 5 cm, with increments of 10 cm each. Now, if the ship unit dimension is 22 cm, we see that it falls in the 15-25 range.

To use these the following parameters need to be set as follows:

USE TOLERANCES IN 3D PATTERN CONFIGURATION = true

USE WEIGHT TOLERANCE IN 3D PATTERN = true

These tolerances only apply for auto generated patterns so one of the following parameters must also be set:

GENERATE DOUBLE ITEM PATTERNS

GENERATE SINGLE ITEM PATTERNS

LOAD CONFIG GROUP SHIP UNITS WITH SAME THU

Container Optimization Load Placement

 

This controls if load configuration will keep like items together. Valid values are True and False.

This has been renamed in 6.2 from LOAD CONFIG KEEPS LIKE ITEMS TOGETHER.

LOAD CONFIG IGNORE MAX TOP WEIGHT CONSTRAINT

Container Optimization Tuning Parameters

6.3.2

If true, the weight distribution logic and max top weight will be ignored. For the weight distribution and max top weight constraint check to be invoked, this must be set to false. The default is true.

If set to false, the property glog.optimization.packingsolver.PackingParameters.loadBearingCheckDirectUnitBelowOnly can be set to true, if your load bearing weight is zero or unlimited, to save run time within 3D load configuration.

LOAD CONFIG MULTISTOP MIXING RULE

Container Optimization Load Placement

 

The valid values are:

0 - NO MIXING ALLOWED - No widthwise mixing of units from different stops is allowed.

1- WIDTHWISE MIXING ALLOWED - Units from different stops is allowed.

2 - WIDTHWISE AND STACKING MIXING ALLOWED - Units from different stops can be stacked on each other. Units loaded earlier cannot stack on top of units loaded later.

3 - WIDTHWISE AND STACKING MIXING ALLOWED FOR LAST ROW ONLY - If set to 3, it is allowed to place items of a stop on top of (stacking) or to the side of (widthwise) the previous stop's items but only up to a depth corresponding to the depth of the last row placement of the previous stop, so the items of a stop cannot be placed so deep that they are unreachable when unloading/loading. In other words, if they are placed very close to the nose of the trailer, on top of the previous stop's items, there is no way to reach them but to climb on top of the previous stop's items. This is avoided when this is set to this value.

LOAD CONFIG MULTISTOP RELOAD TYPE

Container Optimization Load Placement

 

This is used in multi-stop shipment builder. The options are "RELOAD CONFIG AT EACH ITERATION" and "RELOAD CONFIG AT END OF PROCESS" (default).

This will go through load configuration at the end of the process unless the volume utilization (total rolling volume/remaining capacity of equipment) of ship units being placed in the equipment is more than the volume threshold. Note that it will always go through load configuration at the end if LOAD CONFIG ENGINE TYPE is either 3D PLACEMENT, PATTERN BASED or PATTERN BASED OPTIMIZE.

LOAD CONFIG RULE

Container Optimization

6.3

This parameter is used to designate which load configuration rule is to be applied. Values are Use Most Specific Setup Only, and Use Most Specific With Additional Values.

Default = Use Most Specific Setup Only

LOAD CONFIG RULE SEARCH LEVEL 1

Container Optimization

6.3

This parameter controls how the system will sort through load configuration setup rules. Values are:

  • Use THU then PI: use the rules defined on the transport handling unit and then the rules on the packaged item.
  • Use PI then THU: use the rules defined on the packaged item and then the rules defined on the transport handling unit.

Default= Use THU then PI

LOAD CONFIG RULE SEARCH LEVEL 2

Container Optimization

6.3

This parameter tells the system how to use By Location and By Equipment loading rules. The values are:

  • Use Location and then Equipment Group: This setting specifies that the location level setup is the most specific.
  • Use Equipment Group and then Location: This setting specifies that the equipment level setup is the most specific.

Default= Use Equipment Group and then Location

LOAD PLACEMENT ITERATION CRITERIA

Container Optimization Load Placement

6.1

In order to place the individual pieces in the equipment, the logic iterates through empty spaces, remaining items and possible orientations. This parameter lets you select which of these three dimensions spaces, item types, and rotations should be chosen first, second and third respectively.

See Pattern Based Load Configuration section above for how this works with pattern based load configuration.

This parameter will not be considered if 3D Scoring Placement is used (CONSIDER SCORING LOGIC IN 3D PLACEMENT parameter set to true).

When this parameter is set to any of the values mentioned below (if rotation comes first and then item), the constrained orientations in the Load Configuration Setup is ignored, as the CONOPT logic iterates through empty spaces, remaining items, and possible orientations to find the feasible placement. System identifies only the item first, and then the configured orientations for that item to iterate.
1.    Space, Rotation, Item
4.    Rotation, Space, Item
5.    Rotation, Item, Space
If the value of this parameter is set to any of the values mentioned below, the constrained orientations in the Load Configuration Setup will be honored.
0.    Space, Item, Rotation
2.    Item, Rotation, Space
3.    Item, Space, Rotation

MAXIMIZE CONTAINER UTILIZATION

Container Optimization Objectives

 

Set this to true if you want to maximize the overall utilization for all the containers. For example, if you want to try to load everything into one container. If you do not care how many containers it uses, as long as they are each fully optimized, then select Maximize Container Utilization.

If both this and MINIMIZE NUMBER OF CONTAINERS are true, Oracle Transportation Management will find solutions using both methods and use the one that is least expensive.

Also, see the property glog.business.conopt.useOneConoptObjectiveInEquipmentAssigner. It can impact the runtime performance of container optimization when called from Multistop.

MAX OVERHANG PERCENT

Container Optimization Load Placement

6.1

Specifies the amount of overhang in both length and width dimensions. Zero (0) percent indicates that no overhang is allowed. 100% mean that there is no restriction (items can hang in space). 50% indicates that the supported dimension and overhang are the same. This works in conjunction with Max Unsupported Area specified on the Ship Unit Spec.

There is a parameter CONSIDER SPACES ABOVE PLACED ITEMS SEPARATELY. If this parameter is set too high and that parameter is true, items can stick out of the container. Set to true, it can take a long time. It is quicker when set to false. Default is false.

This parameter needs to be wisely used. It should not set it to 100% (meaning it can hang in air). A value of 20-25% seems reasonable.

Default is 0. Note that this is different in behavior from pre 6.1 which assumed 100% overhang.

This parameter is not used with pattern based logic configuration.

MAX VARIABLES IN MULTICONTAINER MIP

Container Optimization Tuning Parameters

6.4.1

This parameter specifies the maximum number of variables allowed in Multicontainer MIP. The multicontainer MIP will fail and return no solution when this limit is exceeded. Though setting a considerably large value for this parameter could allow large problem instances to solve, it would affect run-time performance.

The default value is 10000.

MAX WEIGHT FOR BOX SIZE LOADING HEIGHT CRITERIA

Container Optimization 3D Scoring

6.4.2

This parameter works together with the other max and min parameters to determine the priority of the criteria for placement by 3D scoring mechanism.

MAX WEIGHT FOR BOX SPACE DIMENSION MATCH CRITERIA

Container Optimization 3D Scoring

6.4.2

This parameter works together with the other max and min parameters to determine the priority of the criteria for placement by 3D scoring mechanism.

MAX WEIGHT FOR COLUMN BUILDING CRITERIA

Container Optimization 3D Scoring

6.4.2

This parameter works together with the other max and min parameters to determine the priority of the criteria for placement by 3D scoring mechanism.

MAX WEIGHT FOR LOAD BEARING CRITERIA

Container Optimization 3D Scoring

18D

This parameter works together with the other max and min parameters to determine the priority of the criteria for placement by 3D scoring mechanism.

MAX WEIGHT FOR SPACE DEFRAGMENTATION CRITERIA

Container Optimization 3D Scoring

18D

This parameter works together with the other max and min parameters to determine the priority of the criteria for placement by 3D scoring mechanism.

MAX WEIGHT FOR UNUSABLE SPACE CRITERIA

Container Optimization 3D Scoring

6.4.2

This parameter works together with the other max and min parameters to determine the priority of the criteria for placement by 3D scoring mechanism.

MINIMIZE NUMBER OF CONTAINERS

Container Optimization Objectives

 

Use this parameter if you want to minimize the total number of containers used.

If both this and MAXIMIZE CONTAINER UTILIZATION are true, Oracle Transportation Management will find solutions using both methods and use the one that is least expensive.

Also, see the property glog.business.conopt.useOneConoptObjectiveInEquipmentAssigner. It can impact the runtime performance of container optimization when called from Multistop.

MIN WEIGHT FOR BOX SIZE LOADING HEIGHT CRITERIA

Container Optimization 3D Scoring

6.4.2

This parameter works together with the other max and min parameters to determine the priority of the criteria for placement by 3D scoring mechanism.

MIN WEIGHT FOR BOX SPACE DIMENSION MATCH CRITERIA

Container Optimization 3D Scoring

6.4.2

This parameter works together with the other max and min parameters to determine the priority of the criteria for placement by 3D scoring mechanism.

MIN WEIGHT FOR COLUMN BUILDING CRITERIA

Container Optimization 3D Scoring

6.4.2

This parameter works together with the other max and min parameters to determine the priority of the criteria for placement by 3D scoring mechanism.

MIN WEIGHT FOR LOAD BEARING CRITERIA

Container Optimization 3D Scoring

18D

This parameter works together with the other max and min parameters to determine the priority of the criteria for placement by 3D scoring mechanism.

MIN WEIGHT FOR SPACE DEFRAGMENTATION CRITERIA

Container Optimization 3D Scoring

18D

This parameter works together with the other max and min parameters to determine the priority of the criteria for placement by 3D scoring mechanism.

MIN WEIGHT FOR UNUSABLE SPACE CRITERIA

Container Optimization 3D Scoring

6.4.2

This parameter works together with the other max and min parameters to determine the priority of the criteria for placement by 3D scoring mechanism.

OPTIMIZE COST

Container Optimization Objectives

 

Set this parameter to indicate if optimizing cost is one of the objectives. Cost is considered when more than one equipment option is available.

The Consider Capacity Limit and RATE SHIPMENT INSIDE CONOPT parameters also factor in to container optimization rating. See the topic Rating for Container Optimization to see how the three parameters work together.

Also, see the property glog.business.conopt.useOneConoptObjectiveInEquipmentAssigner It can impact the runtime performance of container optimization when called from multistop.

PACK FULL CONTAINERS WITH LARGE ORDERS FIRST

Container Optimization Tuning Parameters

20A

This provides the option to pack full containers with large orders first (i.e. orders that will fill more than a full container). The default is false.

This parameter applies to all heuristic packing algorithms, except Multicontainer MIP and Column Generation packing algorithms.

This works along with the parameter ITEM GROUPING CRITERIA.

PRIORITY FACTOR IN 3D PATTERNS

Container Optimization Pattern Based Packing

6.3.4

The parameter affects the solution to use priorities. The value should be between 0 and 999. If the value is zero (the default), only the volume packed using patterns in maximized. If 999 is used, only priorities are considered in order to pack in order to pack the patterns and actual volumes packed are ignored (which means all highest priority items are packed and the fill rate is ignored). Values set between 0 and 999 will have considerations for fill rate and priority.

RAIL AXLE WEIGHT AWARE PACKING Container Optimization 24C

This parameter is used to enable the axle weight aware packing algorithm. When the parameter is set to true, the equipment packing algorithm will try to honour the axle weight threshold and axle imbalance ratio threshold constraints if possible. When this is set to false, the equipment packing algorithm will not try to honour the constraints.

By default this is set to false.

RATE SHIPMENT INSIDE CONOPT

Container Optimization Tuning Parameters

6.2

If true, the rate engine is called inside Container Optimization. The default is false.

Along with this one being true, OPTIMIZE COST must be true. The Consider Capacity Limit Parameter also factors in to container optimization rating. See the topic Rating for Container Optimization to see how the three parameters work together.

REMOVE FRAGMENT SPACE IN GROUP PACKING

Container Optimization Tuning Parameters

20A

When group packing is used with a 3D load configuration based packing algorithm, this parameter provides the option to eliminate the possibility of using the constricted space atop a packed group of items. This helps improve the arrangement of the group load placement. The default is false.

This works along with the parameter ITEM GROUPING CRITERIA.

ROTATION SORT CRITERIA

Container Optimization Load Placement

6.1

Criteria for sorting the rotations or orientations. If an item has preferred orientation, the preferred orientations will take precedence over these sort criteria.

This parameter is not used with pattern based logic configuration.

SPLIT BEHAVIOR Container Optimization 26B

This parameter is used to split orders only across compartments within an equipment. By default, the application follows the original split logic, allowing items to be split across both different compartments and different shipments

SPLIT OPTION

Container Optimization Tuning Parameters

 

This parameter influences the aggressiveness with which the algorithm attempts to split the orders. It is only applicable for Enumerative Algorithm, Quick Packing Algorithm and Single Container MIP. Valid options are:

0.Optimize - Evaluates the options and selects the best solution. The best solution has the lowest overall objective (cost or least containers or max utilization). However, if multiple solutions are found with the same objective, the choice will go with the solution that has the fewest number of splits.

1.Favor splitting - This is an aggressive splitting logic, in which it will try the splitting in order to pack the items into containers. It will not consider keeping the ship units or ship unit counts together. As long as the splittable flag is on, anything is allowed.
OTM considers the Splittable checkbox on the order. If it is off, it will not split, even if this option is set to Favor split.

2.Splitting Only If Required - This is the default. This option tries to keep the items together first, and only splits if required.

SPLIT PENALTY

Container Optimization Tuning Parameters

6.2

This parameter is only used with column generation algorithm. If an order gets split into multiple pieces of equipment, a temporary cost equal to the split penalty times the number of splits is added to the equipment option. Thus, if two equipment options of equal cost exist, one with splitting and the other without splitting, the column generation algorithm will select the one without splits. Higher values of split penalty will influence formation of shipments without any splits even if a cheaper option exists with splitting. The default setting is 0.1.

Note: This parameter is also used when the USE LOAD POINT PENALTIES IN PACKING parameter is turned on.  In this case, it is used in the column generation algorithm in order to discourage a shipment having to visit multiple load points.  A temporary cost computed using the split penalty and the number of splits (i.e., number of extra load points) is added to the equipment packing option.  Thus, if two equipment packing options of equal cost exist, one with splitting and the other without splitting, the column generation algorithm will select the one without splits. Higher values of split penalty will influence formation of shipments without any splits even if a cheaper option exists with splitting.

TREE SEARCH ITEMS TO PLACE PER EVALUATION

Container Optimization Load Placement

6.2

This parameter is used when using the USE TREE SEARCH LOAD CONFIGURATION algorithm. At any given iteration of the algorithm, an item, its orientation and a space to place the item is chosen. The quality of this placement is evaluated by placing certain number of other items (specified by this parameter). The logic uses an estimated loading length to determine the goodness of placement.

See Use Tree Search Load Configuration algorithm.

TREE SEARCH NUM SOLUTIONS PER LEVEL

Container Optimization Load Placement

6.2

This parameter is used when using the USE TREE SEARCH LOAD CONFIGURATION algorithm. Out of all the explored combinations of placing items in various orientations and at various positions, the best "n" combinations are kept. This parameter determines "n".

See Use Tree Search Load Configuration algorithm.

TREE SEARCH NUM SOLUTIONS TO EXPLORE

Container Optimization Load Placement

6.2

This parameter is used when using the USE TREE SEARCH LOAD CONFIGURATION algorithm. Different items/orientations and placement positions are evaluated and for each, the estimated loading length is calculated. The number of such combinations to evaluate is controlled by this parameter. The higher the number, more combinations that will be explored and hence the chance of finding better solution is enhanced.

See Use Tree Search Load Configuration algorithm.

VOLUME METRIC

Container Optimization Metrics

 

Set this to true to optimize containers based on volume. If your goal is to optimize the cubic capacity of the containers, then set this to true.

USE 3D BASED LOAD CONFIGURATION

Container Optimization Algorithm

6.1

True indicates 3D Based Load Configuration. If this parameter is On, the logic will discard other algorithms that are on, with the exception of USE COLUMN GENERATION ALGORITHM (see below). Additionally, the Load Config Engine Type parameter needs to be set to No Load Config to enable 3D placement load configuration.

If this parameter is set to true as well as the parameter 'CONSIDER SCORING LOGIC IN 3D PLACEMENT', then ITEM SORT CRITERIA will not be used (the value of the item sort criteria will not be considered if populated).

See the Container Optimization Algorithms topic to see how the Container Optimization algorithms interact.

See also Bulk Plan Tuning Container Optimization Logic.

USE 3D IN MULTICONTAINER HEURISTIC

Container Optimization Tuning Parameters

6.4.2

This determines whether the Multicontainer Heuristic algorithm  will use 3D based load configuration to pack items.

When true, the algorithm will use 3D based load configuration to pack items. The default is false.

Note: To use this parameter, the following parameter must also be true: USE MULTICONTAINER HEURISTIC ALGORITHM.

USE BULK EQUIPMENT GROUP LOGIC

Container Optimization Tuning Parameters

6.4.2

This parameter determines whether you can mix bulk items in equipment during equipment packing. They can be mixed if all the following are true:

The default for this parameter is false.

USE BULK PACKING MIP Container Optimization Algorithm 26B

This parameter enables the Bulk Packing MIP algorithm to efficiently pack bulk compartments and bulk equipment groups. It is specifically designed for scenarios with multiple non-mixable bulk items and equipment featuring multiple bulk compartments of unequal sizes.

When set to true, this parameter enables Container Optimization to use the Bulk Packing MIP.  The default value is false.

Note: To use this parameter, the following parameter must be false: USE QUICK PACKING ALGORITHM.

USE COLUMN GENERATION ALGORITHM

Container Optimization Algorithm

6.1

True indicates the use of column generation based multi-container optimization.

If ON,you have 2 options:

1 - If this parameter is on, the column generation algorithm will work with other algorithms to zero in on a solution. It works like a manager, runs an algorithm, alters input and runs it again and then repeats the process. The other algorithms that it works with are Quick Packing, Enumerative or Single Container. You can use one or more of these. The disadvantages are a long run time and more resources used. The benefits are a better solution is found.

2 - You can select 3D Based Load Configuration or Pattern Based load configuration. You can use either or both of these. The above three are ignored even if they are on (see 1 above).

If this is on and no other algorithm is selected, then Single Container MIP algorithm is used.

Note: Multi-container MIP is not compatible so will not be used even if On.

Note: The use of column generation with any 3D based algorithm (e.g. 3D load configuration, pattern based load configuration, tree search based load configuration) is not recommended.

See the Container Optimization Algorithms topic to see how the Container Optimization algorithms interact.

See also Bulk Plan Tuning Container Optimization Logic.

USE ENHANCED CYLINDER PACKER

Container Optimization Pattern Based Packing

23C

When set to true, this parameter enables stacking of different ship units (cylindrical items) with the same diameter within a pattern-based load configuration algorithm. This parameter is applicable only for ship units with:

The default value of this parameter is false.

Note: This parameter will take effect ONLY if the parameter "USE PATTERN BASED LOAD CONFIGURATION" is set to true.

USE ENUMERATIVE ALGORITHM

Container Optimization Algorithm

 

This algorithm works by enumerating several packing options and selecting the option that best uses a given piece of equipment.

The algorithm evaluates different equipment by tightly packing each equipment and selecting the resource that results in the best packing. This process of evaluating and selecting the best equipment continues until all the orders are completely packed into the equipment.

This algorithm typically produces very tightly packed equipment, but does not necessarily optimize across equipment.

Note: The Single Container MIP algorithm is recommended instead of the Enumerative algorithm as it produces an equivalent quality solution with lower run times.

See the Container Optimization Algorithms topic to see how the container optimization algorithms interact.

See also Bulk Plan Tuning Container Optimization Logic.

USE LAST CONTAINER PRIORITY HEURISTIC

Container Optimization 3D Scoring

20A

This parameter impacts packing when scoring and priority are both enabled.

When this parameter is false (the default), OTM performs a "last container" algorithm, and only makes sure the last equipment is just packing the relatively low priority algorithm.

When set to true, OTM packs items priority group by priority group.

See also Heuristics Algorithms – 3D Based.

USE LOAD POINT PENALTIES IN PACKING Container Optimization Tuning Parameters 24A

This parameter allows orders to consolidate onto the same shipment, even when they have different load points at the same source location. When this parameter is set to true, the Container Optimization logic will use Load Point Penalties to determine how to consolidate orders with different load points.  When this parameter is false, orders from different load points will not be bundled together, and Container Optimization logic will not consolidate them onto the same shipment.

 By default, the parameter is set to false.  

USE MULTICONTAINER HEURISTIC ALGORITHM

Container Optimization Algorithm

6.4.2

The Multicontainer Heuristic algorithm is designed to select the least-cost equipment combination while avoiding greedy decisions as much as possible.

When this parameter is set to true, Multicontainer Heuristic algorithm will be used. The default is false. To use 3D load config in this algorithm, set the parameter USE 3D IN MULTICONTAINER HEURISTIC to true.

USE MULTICONTAINER MIP

Container Optimization Algorithm

 

This algorithm evaluates all the containers simultaneously and selects the best set of equipment (and the compartments therein) resulting in the optimized objective. Since it evaluates all the containers simultaneously, it does not scale too well for large problems; so generally for small sets of orders such as less than 10 orders per bundle and a limited number of equipment choices. This algorithm is not recommended if the number of containers/equipment is high. This algorithm also uses FICO XPRESS OPTIMIZER.

This does not honor the split option parameter. It always aggressively splits order releases or ship units if they can be split. However, when this algorithm is used, splitting bulk shipment ship units is currently not allowed during multistop shipment consolidation.

If there are multiple solutions resulting in the same cost, the output can be any one of the "alternate optimal solutions".

The parameter MAX VARIABLES IN MULTICONTAINER MIP specifies the maximum number of variables allowed in Multicontainer MIP.

Note:  The multi-container MIP is limited in functionality as it cannot 3D load configuration, order priorities and various item-to-resource and item-to-item incompatibilities. For shipment planning in these situations, use column generation algorithm instead.

See the Container Optimization Algorithms topic to see how the Container Optimization algorithms interact.

See also Bulk Plan Tuning Container Optimization Logic.

USE FULL USER DEFINED PATTERNS FIRST

Container Optimization Pattern Based Packing

21C

USE MULTI-OBJECTIVE VALUE FUNCTION

Container Optimization Pattern Based Packing

21A

USE PATTERN BASED LOAD CONFIGURATION

Container Optimization Algorithm

6.2

TRUE invokes the pattern-based load configuration.

See the Container Optimization Algorithms topic to see how the container optimization algorithms interact.

See also Bulk Plan Tuning Container Optimization Logic.

USE PATTERNS IN 3D

Container Optimization Pattern Based Packing

6.3.3

This is the main parameter to turn on logic configuration 3D pattern based logic for 3D load configuration. This must be true for any of the following parameters to be used:

  • USE USER PATTERNS IN 3D

  • GENERATE DOUBLE ITEM PATTERNS

  • GENERATE SINGLE ITEM PATTERNS

The default is false.
See also Load Configuration Engine Type.

USE QUICK PACKING ALGORITHM

Container Optimization Algorithm

 

This is generally the fastest algorithm and produces reasonably high quality solutions. It takes into account costs, resources, equipment reference units and splittability.

See the Container Optimization Algorithms topic to see how the Container Optimization algorithms interact.

See also Bulk Plan Tuning Container Optimization Logic.

USE SIMILARITY SORTING IN GROUP PACKING

Container Optimization Tuning Parameters

20A

When group packing is used with a 3D load configuration based packing algorithm, this parameter can be set to true to keep item groups containing similar sized ship unit items close to each other in the group packing sequence. This improves the consistency in item placement and also helps increase equipment utilization. The default is false.

This works along with the parameter ITEM GROUPING CRITERIA.

USE SINGLE CONTAINER MIP

Container Optimization Algorithm

 

This is an optimization algorithm that results in tightly packed containers. This uses FICO XPRESS OPTIMIZER. This produces solutions that are as good as or better than the Enumerative algorithm. Compared to the Enumerative algorithm, the run time is quicker.

See the Container Optimization Algorithms topic to see how the Container Optimization algorithms interact.

See also Bulk Plan Tuning Container Optimization Logic.

USE TOLERANCES IN 3D PATTERN GENERATION

Container Optimization Pattern Based Packing

6.3.4

This turns on tolerances in pattern generation in load placement. See the item tolerance parameters above.

USE TREE SEARCH LOAD CONFIGURATION

Container Optimization Algorithm

6.2

The Tree Search engine has the potential of producing higher quality load placements than 3D LOAD CONFIG or PATTERN BASED LOAD CONFIG algorithms by exploring many more placement combinations. The increased solution quality does come at the expense of increase run times.

At any given iteration of the algorithm, an item, its orientation and a space to place the item is chosen. The quality of this placement is evaluated by placing certain number of other items (specified by the logic configuration parameter TREE SEARCH ITEMS TO PLACE PER EVALUATION). The logic uses an estimated loading length to determine the goodness of placement.

The above step is repeated for different items/orientations and placement positions and for each, the estimated loading length is calculated. The number of such combinations to evaluate is controlled by the logic configuration parameter TREE SEARCH NUM SOLUTIONS TO EXPLORE. The higher the number, the more combinations that will be explored and hence the chance of finding better solution is enhanced.

Out of all the explored combinations of placing items in various orientations and at various positions, the best n combinations are kept. The number n is controlled by a third logic configuration parameter - TREE SEARCH NUM SOLUTIONS PER LEVEL.

The three parameters are in the Container Optimization Load Placement section.

See also Bulk Plan Tuning Container Optimization Logic.

USE USER PATTERNS IN 3D

Container Optimization Pattern Based Packing

6.3.3

When on (true), OTM looks at the user defined load configuration 3D patterns and uses those that are appropriate for the ship units that need to be placed.

The property glog.optimization.containerloading.CheckPlacementPositionsfor3DPatterns can impact user patterns.

NOTE: The parameter USE PATTERNS IN 3D (also a logic configuration - container optimization parameter) must be true for this parameter to be used.

The default is false.

USE WEIGHT TOLERANCE IN 3D PATTERN GENERATION

Container Optimization Pattern Based Packing

6.3.4

Turns on the weight tolerance. See the item tolerance weight parameters above.

USER DEFINED PATTERN HEIGHT TOLERANCE PERCENT

USER DEFINED PATTERN LENGTH TOLERANCE PERCENT

USER DEFINED PATTERN WIDTH TOLERANCE PERCENT

Container Optimization Pattern Based Packing

6.4.3

These parameters enable you to define tolerances for items so they can be considered similar for use in user defined patterns. The tolerances are defined as percentages (0-100). The default for each is zero, meaning no tolerance. Hundred (percent) means any dimension, smaller or equal in size, can match the pattern item dimension.

USER DEFINED PATTERN LENGTH METRIC WEIGHT

USER DEFINED PATTERN VOLUME METRIC WEIGHT

USER DEFINED PATTERN WEIGHT METRIC WEIGHT

Container Optimization Pattern Based Packing

21A

These parameters allow you to enable the knapsack MIP formulation for user-defined pattern based packing to optimize multi-different objectives, namely, weight, volume and load length. You can configure the weighting for each criteria: load length, volume, and weight.

These are only enabled if the parameter  USE MULTI-OBJECTIVE VALUE FUNCTION is set to true.

WEIGHT AND VOLUME METRIC

Container Optimization Metrics

 

Set Weight and Volume Metric to true to optimize containers using a density calculation. When this is true, Oracle Transportation Management adds the weight and volume and divides the answer by 2. This provides a density number that it uses to optimize containers.

If you want Oracle Transportation Management to consider both weight and volume, then set both Weight Metric and Volume Metric to true, but leave Weight and Volume Metrics unselected. This finds a solution based on weight and a solution based on volume, and then uses the one that is least expensive.

WEIGHT METRIC

Container Optimization Metrics

 

Select Weight Metric to optimize containers based on weight if your goal is to load the most amount of weight into the containers as possible.

Related Topics