IBM Support

Pickup Window Calculation in Optimization

Question & Answer


Question

Pickup Window Calculation in Optimization

Answer

Pickup Window Calculation in Optimization

When you submit orders to the optimizer each order includesthe planned departure window that was originally assigned to the order.If your organization plans orders far in advance you might want theoptimizer to ignore the original pickup window and calculate a newpickup window based on the following criteria:

  • The pickup window duration you define in the optimization run
  • The transit time needed to deliver the shipment
  • The delivery window that was submitted with the original order

To have the optimizer calculate the pickup window definethe following settings on the Shipping Data tabof the Optimization Parameters page:

  • Select Ignore Pickup Windows.
  • Set Pickup Window Duration to the numberof hours you want Sterling TMS toassign as the planned departure window.

When you select the Ignore Pickup Windows option Sterling TMS uses the followingprocess to calculate the planned departure window:

Planned Departure Window End

Sterling TMS calculatesthe transit time needed to deliver the shipment and subtracts thetime from the start of the planned arrival window.

For example:

  • The shipment is scheduled to be delivered on 15 June from 8 a.m.to 5 p.m.
  • The transit time from the origin to the destination is 2 days.
  • The end of the planned departure window is calculated as 13 Juneat 8 a.m.
Planned Departure Window Start

Sterling TMS subtractsthe Pickup Window Duration from the end ofthe planned departure window.

For example:

  • The end of the planned departure window is calculated as 13 Juneat 8 a.m.
  • The Pickup Window Duration is 24 hours.
  • The start of the planned departure window is calculated as 12June at 8 a.m.

The following example shows how Sterling TMS calculatesthe planned departure window when the Pickup Window Duration isset to 4 days:

  1. You plan to optimize this order:
    • The planned departure window is 20 July to 21 July.
    • The planned arrival window is 22 July to 23 July.
    • The transit time from the origin to the destination is 1 day.
  2. You set up the optimization run to ignore the pickup window. Youset Pickup Window Duration to 4 days.
  3. You submit the optimization run on 10 July which is 10 days beforethe start of the original planned departure window.
  4. Sterling TMS calculatesthe planned departure window:
    • Planned Departure Window End = 21 July(the 22 July start of the planned arrival window minus 1 day of transittime)
    • Planned Departure Window Start = 17 July(the 21 July end of the planned departure window minus the 4-day pickupduration)

Whenyou use Sterling TMS tocalculate the pickup window you can have the system take into accountthe location hours of the origin. Sterling TMS will adjustthe pickup window so the shipment departs when the location is open.

Forexample:

  1. Set Use Location Hours to Pickups whenyou define an optimization run.
  2. A shipment is being picked up at a warehouse that is open Mondaythrough Friday.
  3. You have Sterling TMS calculatethe pickup window. The system calculates the departure as Saturday16 May.
  4. Sterling TMS changesthe pickup window from Saturday 16 May to Friday 15 May becausethe warehouse is closed on Saturday.
Notes:
  • You can use the Planning Horizon feature to calculate the pickupwindow. The optimizer creates the planned departure window based onthe date and time of the optimization run.
  • You can use the Pickup Window Offset feature to calculate thepickup window. The optimizer calculates the start of the planned departurewindow based on the end of the planned departure window.
"

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SS73G6","label":"Sterling Total Payments for Financial Services"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
08 December 2018

UID

ibm10753913