A date field is already mapped into “JobDate” field of Locus but currently not being used at Locus end. This date value need to be used to hold the jobs in Loucs if the date/day anniversary is not reached and should be excluded from the Locus algorithm for workload and printing labels via API. Only consider those jobs when the date/day anniversary is reached and follow the normal process from then on. These jobs that are not yet due need to be separated in a application UI so that Ops know what is real workload and what is not. Subsequently, these jobs also need to be excluded from all the dashboard calculations displaying workload of the day. However, would still need to display next days workload via some visual indicator on screen for Ops to better manage next day’s workload.
This functionality should not impact any other agreed processes and configuration or functionalities.
|
Problem/opportunity trying to be solved
The DHL HP6 team has an issue with linking replenishment tasks to a sales order. Stock being moved for one channel is subsequently allocated to a B2C order where the replenishment was initially triggered for B2C. With the shorter SLA of the B2C orders, the B2B orders don’t end up being allocated to the orders that triggered the replenishment task. Also, running short waves and multiple replenishments immediately after is affecting productivity. With this feature, Ops can run waves knowing that they have longer time to fulfill those replenishments since it is for next day’s orders and thus, they can do bit of bulk replen and be better prepared for next morning/day. |
|
|
Quantify the problem/opportunity
Customer orders for B2B miss out on the stock being replenished for their orders as the B2C orders come in on a shorter lead time. Running shorter waves and subsequent replenishments can be prevented with this functionality. |
|
|
What is the root cause of the problem/opportunity
The customer has conflicting SLAs so short lead-time orders (B2C) take the stock intended for longer lead-time orders (B2B). Thus resulting in constant replenishment activity which stops the picking activity and thus productivity and consistency loss. |
|
| Customer need date | Dec 31, 2025 |
| Urgent request | No |
| Report Tag | CSM |