Draft TOI - General Conopt Enhancements

<Insert Picture Here>
General Conopt Enhancements

Release 6.2
Table of Contents
• Rating within Conopt
• Allow zero cost rates in Pre Rate API
• Cleanup of L/C Parameters
• Rename of Like Item Parameter
• Move P/B to L/C for config.
• Load Config to be invoked from SPA
• Logic Config Sets
• Tree Search
• Column Generation
© 2009 Oracle Corporation – Proprietary and Confidential

Rating Within Conopt
• The enhancement for rating within Conopt was needed because pre-
rating set costs for equipment that were fixed for the duration of the
Conopt processing run.
• Equipment costs that were variable based such as weight based
rates did not vary by the actual quantity placed in the equipment.
• Equipment costs with variable rates were estimate with the lesser of
the equipment capacity or the order size.
• The cost of the particular equipment option at each decision point
within Conopt changes dynamically by the rating calls within Conopt.
• Partially loaded equipment is the most susseptable to bad rating
when the costs were established as fully loaded.
• Equipment that carried light, fluffy materials were also poorly rated.
• The result was that poor equipment choices were made prior to the
enhancement.

Examples Tested
• Navy Beans Bulk – Weight Based

• PPS is ERU with Quick Pack
• Detergent – Weight Based
• PPS is 3D-Both
• Dog Food – Load Length Based
• PPS is 3-D - Widthwise
• Wheat Crackers – Per ERU Based
• PPS is 3-D
• Empty Drums - Per SU Count Based
• PPS is 3-D

Navy Beans – Compartments
Pre-Rate
ERU - QP
Order
Units = 1300
Weight = 59,800
Volume = 1618
(59800/2000 * 40 = $1196
Internal Rating
Full Truck
Conner Miles 519.28 MI * $2.00/MI = $1038.56
Kellogg 55,936/2,000*40 = $1118.72
Part Truck
Kellogg 3,864/2,000 * $40/TON = $77.28

Detergent – Weight Based
Pre-Rate
3-D
Order
Units = 44
Weight = 66,264
Volume = 2909
Internal Rating (66,264/100 * 2.3/CWT = $1524

Full Truck
Kellogg 43,674/100*2.30/CWT = $1004.50
Part Truck
Kellogg 22,590/100 * $2.30/CWT = $519.57

Dog Food – Load Length Based
Pre-Rate
3-D widthwise
Order
Units = 38
Weight = 43,776
Volume = 21111
Internal Rating
Full Truck
Kellogg 60.00ft * $20.00/Load Ft = $1,000
Part Truck
Kellogg 13.33 ft * $20.00/Load Ft = $266.67

Wheat Crackers – ERU Usage Based
Pre-Rate
3-D - width
Order
Units = 90
Weight = 32,400
Volume = 4800
Internal Rating
45 ERU * $35/ERU = $1575
Full Truck
Kellogg 30 ERU * $35.00/ERU = $990
Part Truck
Kellogg 15 ERU * $35.00/ERU = $495

Empty Drums – Num Ship Unit
Pre-Rate
P/B L/C
Order
Units = 500
Weight = 17,500
Volume = 3797
Internal Rating 500 SU * $3.00/SU = $15.00

Full Truck
Kellogg 384 SU * $3.00/SU = $1,152
Part Truck
Kellogg 116 SU * $3.00/SU = $348

Allow zero cost rates in Pre Rate API
• The purpose of Conopt- Pre Rate is to find all rates that are authorized to
be used in solving the Conopt problem.
• Each asset type (Equipment Group) will be assigned as a constraint to the
Order Bundle and compatibel rates will be returned. This will for the basis
of the resources to be used in the solution when Cost is to be considered.
• In version 6.1 the cost search sometimes filtered out good candidate
equipment when no rates were found.
• The reason was that the rate was dependent on a measure that was not
known during pre-rating. The best example is Loaded Length which is
zero because no cargo has been packed.
• However, if more than one carrier had valid rates for the equipment,
only that carrier would be filtered out from Conopt.
• However, re-rate after shipment building would sometimes restore
that carrier, but the decision making was made without that carrier.
• This made the issue hard to diagnose.

Test Example
• Rates for a specific item from Baltimore to Lexington

are provided by 2 carriers.
– Conner has a mileage based rate for a 53 ft Dry Van.
– Kellogg has a loaded length based rate for a 53 ft Reefer.
• The order provides for a full truck and a partial.
– The best price for the full truck is by miles.
– The best prince for the part truck is by Loaded Length.

Dog Food – Load Length Based
Pre-Rate
3-D
Order
Units = 38
Weight = 43,776
Volume = 21111
Internal Rating Work-around

Full Truck $1/equipment weighted cost
Kellogg 60.00ft * $20.00/Load Ft = $1,000
Part Truck
Kellogg 13.33 ft * $20.00/Load Ft = $266.67

Distance Based Rate – 53 Ft Dry
This is the full truckload price and does not require loading length.
If the part truck rate failed, the results would be 2 trucks based on this rate.

Loading Length Rate – 53 Ft Reefer
Work-around

Results without pre-rating
Order Release is BALT_LEX_DOG FOOD 01

Results after enhancement

Pre-Rate for Loaded Length

Why is Pre-Rate so important?
• Pre rate finds all of the available rates for each size of
equipment.
• The equipment and the service provider are now considered
a “resource” for Conopt.
• If you use Capacity Limits, the quantity of that equipment is
also considered by Conopt.
• If the Pre-rate was turned off
• You could not use capacity limits.
• You could not perform cost analysis in Conopt.

Cleanup of Parameters for L/C
• Most parameters for Conopt that were in the Planning

Parameter set in 6.1 were moved to Logic Config as L/C
parameters.
• In 6.2, 3-D can only be invoked through the L/C
configuration.
• In 6.2, Pattern Based can be invoked from either the PPS
or the L/C.
• Properties were also converted into parameters.

CONOPT – Planning Parameter Set 6.2

Change in Planning Parameters for 6.2
• Parameter from 6.1 • Parameter for 6.2
• ADJUSTED EQUIPMENT CAPACITY PERCENT • No Change
• ALLOW SMALL DIRECT ORDERS TO BE • No Change
SPLITTABLE
• CONTAINER OPT CONFIG ID • No Change
• CONTAINER OPT SEARCHING WINDOW DAYS • No Change
• DRNAMIC PROGRAMMING MAX RECURSION • No Change
DEPTH
• DYNAMIC PROGRAMMING TIME OUT LIMIT • No Change
• LOAD CONFIG 3D PLACEMENT ALGORITHM • Removed
TYPE • Limited Selection
• LOAD CONFIG ENGINE TYPE • Removed
• LOAD CONFIG IS SWAP ALGORITHM USED • Renamed and Moved to L/C
• LOAD CONFIG KEEPS LIKE ITEMS TOGETHER • Moved to L/C
• LOAD CONFIG MULTISTOP MIXING RULE • Moved to L/C
• Removed
• LOAD CONFIG MULTISTOP RELOAD TYPE
• No Change
• LOAD CONFIG PERCENT IMPROVEMENT
• LOAD CONFIG STACKING HEIGHT DIFF
• No Change
TOLERANCE
• New in 6.2
• LOAD CONFIG VOLUME THRESHOLD
• No Change
• LOGIC CONFIG SET ID
• USE PRIORITY IN CONOPT SORTING

Change in Parameters for 6.2
Parameter from 6.1 Parameter for 6.2
ADJUSTED EQUIPMENT CAPACITY PERCENT No Change
ALLOW SMALL DIRECT ORDERS TO BE SPLITTABLE No Change
CONTAINER OPT CONFIG ID No Change
CONTAINER OPT SEARCHING WINDOW DAYS No Change
DYNAMIC PROGRAMMING MAX RECURSION DEPTH No Change
DYNAMIC PROGRAMMING TIME OUT LIMIT No Change

Changes to the Logic Config
• Move Parameters
• Bugs for cleanup
• New Parameters
• New features

6.2 Container Optimization Algorithm
Parameter in 6.2 Notes

• USE 3D BASED LOAD • NO CHANGE
CONFIGURATION
• USE COLUMN GENERATION • NO CHANGE
ALGORITHM
• USE ENUMERATIVE • NO CHANGE
ALGORITHM • NO CHANGE
• USE MULTICONTAINER MIP
• USE PATTERN BASED LOAD • NEW IN 6.2
CONFIGURATION • NO CHANGE
• USE QUICK PACKING
ALGORITHM • NO CHANGE
• USE SINGLE CONTAINER MIP
• NO CHANGE
• USE TREE SEARCH LOAD
CONFIGURATION • NEW IN 6.2

6.2 Container Optimization Load Placement

• EMPTY SPACE SORT CRITERIA • NO CHANGE
• EVALUATION DEPTH
•
• NO CHANGE
IS LENGTHWISE ORIENTATION FIRST
• ITEM SORT CRITERIA • NO CHANGE
• LOAD CONFIG GROUP SHIP UNITS WITH SAME • NO CHANGE
THU
• LOAD CONFIG MULTISTOP MIXING RULE • RENAMED FROM 6.1 PPS
• LOAD CONFIG MULTISTOP RELOAD TYPE • FROM 6.1 PPS
• LOAD CONFIG VOLUME THRESHOLD • FROM 6.1 PPS
• LOAD PLACEMENT ITERATION CRITERIA
• MAX OVERHANG PERCENT
• NO CHANGE
• ROTATION SORT CRITERIA • NO CHANGE
• TREE SEARCH ITEMS TO PLACE PER • NO CHANGE
EVALUATION
• TREE SEARCH NUM SOLUTIONS PER LEVEL • NO CHANGE
• TREE SEARCH NUM SOLUTIONS TO EXPLORE • NEW IN 6.2
• NEW IN 6.2
• NEW IN 6.2

6.2 Container Optimization Tuning
Parameters

• CHECK COMMODITY • NO CHANGE
COMPATIBILITY
• CONOPT COLUMN
GENERATION NUMBER OF • NO CHANGE
ITERATIONS
• CONSIDER CAPACITY • NO CHANGE
LIMITS
• NO CHANGE
• DESIRED UTILIZATION
PERCENTAGE
• RATE SHIPMENT INSIDE • NEW IN 62
CONOPT • NO CHANGE
• SPLIT OPTION • NEW IN 6.2
• SPLIT PENALTY

Removed Properties
glog.business.loadconfig.loadConfig3DPlacementEngine.LoadConfigIterationNumberForPctImprovement=0
glog.business.loadconfig.loadConfig3DPlacementEngine.LoadConfigNumberOfInfeasibleSequencesEvaluated=5
glog.business.loadconfig.loadConfig3DPlacementEngine.LoadConfigMaxPctWastedAreaWhilePlacing=100
glog.business.loadconfig.loadConfig3DPlacementEngine.LoadConfigSpaceUtilizationFlag=false
glog.business.loadconfig.loadConfig3DPlacementEngine.LoadConfigFloorAreaToLengthPct=30
glog.business.loadconfig.loadConfig3DPlacementEngine.LoadConfigTryNextPieceIfPointInfeasible=true
Remaining Properties
glog.optimization.containerloading.AddAdditionalPointsForStacking=false


Keep Like Items Together
• The idea that items with the same THU are considered to
be alike is default behavior.
• However, when different items share the same THU such
as a generic pallet THU.
• The same Ship Unit Line items are not kept together.
• The parameter to specify this was named
• Load Config Keeps Like Items Together
• This was confusing
• In 6.2, the parameter was renamed
• Load Config Group Ship Units with Same THU
• The default is true

Test of Keeping Like Items Together
• 1 Item – Range
• 3 Brands that each have unique carton (THU)
• 3 Brands that share a generic carton (THU)
• Keep Like items together parameter
• By THU
• By Ship Unit
• 2 Orders
• 1 with unique THU
• 1 with Generic THU

Parameter is True
Assumes that Ship Units with the same THU are identical.
Order – Range 01 Specific THU
Order – Range 02 Generic THU

Range Specifications
Shipping Dimensions
L = 32, W = 31, H = 50
Weight = 285 lbs

Packaged Items
6 Packaged Items
3 Packaged Items
With unique THU
3 Packaged Items
With generic THU



Parameter is False
Ship Unit data is used in preference to THU data.
Layer building.

Parameter is False
Wall building across nose.

Move P/B to L/C Sets
• The main reason to move P/B to L/C is to unify the

structure of the “placement algorithms” to a common
platform so that they can share the same control
parameters.
• P/B and 3-D now can be influenced by
• The Load Placement Parameters
• For example Space, vs Items
• Obstructions and other new features as they are developed
• The old way of using P/B through the PPS will remain
in 6.2 until it is removed in a later release.

SPA, Compartments and Conopt
• SPA now calls Conopt when there is a multi-

compartment shipment or a shipment that was built
with Load Config.
• Previously, it did not and this was the cause of the
problem.

Example of SPA rebuilding without Conopt

After the Fix – Compartments are Filled

Logic Config Sets
• There are shipments that are best built with the items placed
lengthwise and there are shipments where that are best built
when the items are widthwise.
• OTM will place the first item based on
• The parameter “Is Lengthwise Orientation First”.
• This is a greedy placement which
• Will not change
• Will influence the rest of the load.
• A L/C set will allow the user to configure multiple ways to solve a
Conopt Run.
• All results will be kept and evaluated for the best solution.
• The lengthwise/widthwise example only brought this to light. There are many
other possible combinations which may be used depending on the situation.

Logic Config Set

BEST SOLVED BY
LENGTHWISE

Fig 2 – Greedy – 2 comp - L
710 mm Ctn – ELX Appliance B
258 Pcs
42 Pcs
Order Release is ELX DBL COMP 03 B ONLY – 300 Pcs

Fig 2 Greedy – 2 comp - W
710 mm Ctn – ELX Appliance B
234 Pcs
66 Pcs
Order Release is ELX DBL COMP 03 B ONLY – 300 Pcs

BEST SOLVED BY WIDTHWISE

Fig 23 Dbl Comp - Greedy - L
Inefficient Solution by Lengthwise
Compartment 1
72 ctn Green 645 x 925 x 960
Compartment 2
30 ctn Red 710 x 565 x 955
60 ctn Green 645 x 925 x 960
Compartment 1
Order Release is ELX DBL COMP 01 39 ctn Red 710 x 565 x 955

Fig 23 Dbl Comp - Greedy - W
Combined compartment totals

69 ctn Red 710 x 565 x 955
132 ctn Green 645 x 925 x 960
Order Release is ELX DBL COMP 01

Changes to Algorithms
• The Tree Search Algorithm was introduced as a
solution that looks ahead. The idea is that instead of
just placing the next item based on the evaluation of
that item, the algorithm places several items in
different possible solutions. The best solution path is
picked and the immediate item is placed based on that
decision. Then the next item’s placement is examined
in the same manner.
• Tree search uses 3-D for placement.
• You do not also need to enable 3-D.
• The Column Generation Algorithm was enhanced with
the ability to evaluate splitting decisions by means of a
weighting factor.

Split Penalty Tuning Parameter
• This parameter allows the configuration of a weighting

factor to control splitting when using Column
Generation.
• An scenario was designed to test this parameter.
– Order was larger than 2 trucks but smaller than 1 boxcar.
– The cost of the 2 trucks were cheaper than the cost of the
boxcar.
– The factor will control the solution.

Column Generation – Split Penalty Results

Column Generation – Split Penalty Results

Draft TOI - General Conopt Enhancements

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Draft TOI - General Conopt Enhancements

Uploaded by

Copyright:

Available Formats

<Insert Picture Here>

General Conopt Enhancements

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

• Navy Beans Bulk – Weight Based

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

Internal Rating (66,264/100 * 2.3/CWT = $1524

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

Internal Rating 500 SU * $3.00/SU = $15.00

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

• Rates for a specific item from Baltimore to Lexington

© 2009 Oracle Corporation – Proprietary and Confidential

Internal Rating Work-around

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

Order Release is BALT_LEX_DOG FOOD 01

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

• Most parameters for Conopt that were in the Planning

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

Parameter from 6.1 Parameter for 6.2

ADJUSTED EQUIPMENT CAPACITY PERCENT No Change

ALLOW SMALL DIRECT ORDERS TO BE SPLITTABLE No Change

CONTAINER OPT CONFIG ID No Change

CONTAINER OPT SEARCHING WINDOW DAYS No Change

DYNAMIC PROGRAMMING MAX RECURSION DEPTH No Change

DYNAMIC PROGRAMMING TIME OUT LIMIT No Change

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

Parameter in 6.2 Notes

© 2009 Oracle Corporation – Proprietary and Confidential

Parameter in 6.2 Notes

© 2009 Oracle Corporation – Proprietary and Confidential

Parameter in 6.2 Notes

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

Order – Range 01 Specific THU

Order – Range 02 Generic THU

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

© 2009 Oracle Corporation – Proprietary and Confidential

Ship Unit data is used in preference to THU data.

Order – Range 01 Specific THU

Order – Range 02 Generic THU

© 2009 Oracle Corporation – Proprietary and Confidential

Order – Range 01 Specific THU

Order – Range 02 Generic THU

Wall building across nose.

© 2009 Oracle Corporation – Proprietary and Confidential

• The main reason to move P/B to L/C is to unify the

© 2009 Oracle Corporation – Proprietary and Confidential