KPI calculation for rescheduled orders

An order can be scheduled multiple times within IBM Order Management due to modifications such as a backorder, the addition of new items, changes to the requested ship date, or changes to the requested delivery date. When these order modifications occur, an order may be sent multiple times to Fulfillment Optimizer. An entire order or only a portion of it may be re-optimized during the reschedule based on the type of order modification.

An order that is sent multiple times to Fulfillment Optimizer within 7 calendar days is considered a "rescheduled" order. The Key Performance Indicators (KPIs) are then updated accordingly.

For more information about these KPIs, see IBM Developer.

The following examples demonstrate how rescheduled orders are re-optimized in Fulfillment Optimizer through the number of orders, packages, and shipping costs.

Consider order ORD0010 with 2 order lines.

Table 1. ORD0010
LineID ItemID Quantity Weight
L0001 Item0001 1 1.2
L0002 Item0002 1 1.1

On 4 October, the order is optimized and the optimization result is a single ship node (store ST0001), a package weight of 2.3 pounds, and a shipping cost of $9.

Table 2. Net KPI values on 4 October
KPI Value
Total orders 1
Total order lines 2
Total packages 1
Total weight (lbs.) 2.3
Total shipping cost (USD) 9
Entire order is rescheduled
On 5 October, ORD0010 is scheduled and optimized completely.
Table 3. ORD0010
LineID ItemID Quantity Weight
L0001 Item0001 1 1.2
L0002 Item0002 1 1.1
The optimization result has a different ship node (ST0002) based on the data at the time of optimization, and the shipping cost is $8. The KPIs have negative adjustments for the optimization result on 4 October and positive adjustments for the data on 5 October.
Table 4. Comparison of net KPI values on 4 October and 5 October
KPI Value on 4 October Value on 5 October
Total orders 1 1
Total order lines 2 2
Total packages 1 1
Total weight (lbs.) 2.3 2.3
Total shipping cost (USD) 9 8
Part of the order is rescheduled

On 6 October at 08:00, ORD0010 is scheduled and partially optimized. Only Item0002 is sent for optimization.

Table 5. ORD0010
LineID ItemID Quantity Weight
L0002 Item0002 1 1.1

The optimization result is ship node ST0003 based on the data at the time of optimization. The shipping cost of the package of Item0002 is $4. The KPIs have negative adjustments for the optimization results at 4 October and 5 October, and positive adjustments for the data on 6 October at 08:00.

Since the entire order is not rescheduled and Item0001 is part of a package from ST0002, a shipping cost of $6 is determined at ST0002 for the package weight of 1.2lbs.
Table 6. Comparison of net KPI values at 4 October, 5 October, and 6 October at 08:00
KPI Value on 4 October Value on 5 October Value on 6 October at 08:00
Total orders 1 1 1
Total order lines 2 2 2
Total packages 1 1 2
Total weight (lbs.) 2.3 2.3 2.3
Total shipping cost (USD) 9 8 10
A newly added order line is scheduled
On 6 October at 10:00, a new order line (L0003) is added to ORD0010, scheduled, and optimized.
Table 7. ORD0010
LineID ItemID Quantity Weight
L0001 Item0001 1 1.2
L0002 Item0002 1 1.1
L0003 Item0003 1 0.5
The optimization result is ship node ST0002 based on the data at the time of optimization. The shipping cost of the package of Item0003 is $3.50 for a package weight of 0.5lbs. Since a new order line is optimized, there is no negative adjustment. Instead, a positive adjustment takes place for the KPIs based on the optimization result on 6 October at 10:00.
Table 8. Comparison of net KPI values at 4 October, 5 October, 6 October at 08:00, and 6 October at 10:00
KPI Value on 4 October Value on 5 October Value on 6 October at 08:00 Value on 6 October at 10:00
Total orders 1 1 1 1
Total order lines 2 2 2 3
Total packages 1 1 2 3
Total weight (lbs.) 2.3 2.3 2.3 2.8
Total shipping cost (USD) 9 8 10 13.5