OTM Planning (Order Bundling Logic) Does Not Maximize the Utilization Based on the ERU (Equipment Reference Unit) Capacity.
(Doc ID 2586135.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Operational Planning - Version 4.0 and laterOracle Transportation Operational Planning Cloud Service - Version 6.3.4 and later
Information in this document applies to any platform.
Symptoms
OTM Planning (Order Bundling Logic) does not maximize the utilization based on the ERU (Equipment Reference Unit).
Example:
- Orders:
ORDER_01 (ERU count: 0.56)
ORDER_02 (ERU count: 3)
ORDER_03 (ERU count: 2)
ORDER_04 (ERU count: 2.09)
ORDER_05 (ERU count: 27.17)
- Planning Parameters:
CHECK EQUIPMENT CAPACITY IN REFERENCE UNITS = TRUE
PERFORM ORDER BUNDLE SPLITTING USING CONTAINER OPT = true
WEIGHT AND VOLUME METRIC = false
MAXIMUM VOLUME PER BUNDLE = 1,000,000.00 CUMTR
MAXIMUM WEIGHT PER BUNDLE = 1,000,000.00 KG
- ERU capacity constraint on the Equipment Group is 33.
- Planning result:
ORDER_01 524.29 0.7 0.56 Shipment-1
ORDER_02 695.84 2.17 3 Shipment-1
ORDER_03 1304.54 3.22 2 Shipment-1
ORDER_04 6741.92 38.75 27.17 Shipment-1
ORDER_05 866.96 1.86 2.09 Shipment-2
This is nearly optimal solution, notice the total ERU count for shipment-1 is (32.73) is almost at full 33 ERU capacity.
However, this is still not optimal since the order ORDER_03 (2 ERU) alone should have been in a different bundle and then planned to Shipment-2.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |