Release 26.2
Summary
Addition of cover constraints for each warehouse in Regional Utilisation Module
Added an optional input to define the priority of warehouses in Regional Utilisation Module
Addition of cover constraints for each warehouse in Regional Utilisation Module
Currently, the days of cover to be maintained at a warehouse is an input parameter, and the same cover days constraint is used across all warehouses.
Going forward, cover days can be added for each warehouse in the Regional Warehouse Details file (previously called Regional Warehouse Capacity).
This will help you in having more control of the allocation process, especially when each warehouse has its own unique requirement.
Note: The existing cover day input parameter will be copied to the Regional Warehouse Details file for all warehouses once the release is deployed.
Added an optional input to define the priority of regional warehouses
This input gives you the flexibility in the Regional Utilisation module to assign priority to certain warehouses to meet your business needs. You can override the calculated warehouse-wise allocation split in the product using this input. Refer to the example, for more details.
A new optional input file has been added in the Regional Utilisation module, Regional Warehouse Priority. The Warehouse ID and a numerical priority of that warehouse need to be entered in the file.
UI:
Sample Regional Warehouse Priority Input File:
Note: 1 has the highest priority, then 2, and so on.
Example 1:
Let's take SKU A whose ideal allocation to 3 warehouses (WH1, WH2, WH3) are (5, 10, 5) units and Mother Warehouse stock is 4.
Previously, the stock would have been split in the ratio of the three warehouses. ie. the final allocation would have been (1, 2, 1) units.
But for certain business reasons, you want WH1 to be given a higher priority and its demands are to be met, regardless.
So, now you can assign a higher priority for WH1 by setting the priority as 1, in the new Regional Warehouse Priority file.
After assigning priority, the allocation will be (4, 0, 0) units.
| WH1 | WH2 | WH3 |
Priority | 1 | 2 | 2 |
Ideal Allocation as per sales and cover constraint | 5 | 10 | 15 |
Mother Warehouse Stock |
| 4 |
|
Allocation Without Priority | 1 | 2 | 1 |
Allocation With Priority | 4 | 0 | 0 |
Example 2:
Let's take SKU A whose ideal allocation to 3 warehouses (WH1, WH2, WH3) is (5, 10, 5) units and the stock available in Mother Warehouse is 4.
Previously, the stock would have been split in the ratio of the three warehouses. ie. the final allocation would have been (1, 2, 1) units.
But for certain business reasons, you want WH1 and WH3 to be given a higher priority and their demands are to be met, regardless.
So, now you can assign a higher priority for WH1 by setting the priority as 1, in the new Regional Warehouse Priority file.
After assigning priority, the allocation will be (2, 0, 2) units.
| WH1 | WH2 | WH3 |
Priority | 1 | 2 | 1 |
Ideal Allocation as per sales and cover constraint | 5 | 10 | 15 |
Mother Warehouse Stock |
| 4 |
|
Allocation Without Priority | 1 | 2 | 1 |
Allocation With Priority | 2 | 0 | 2 |
Product Versions
Artifact Name | Artifact version |
iris-algo | 3.1 |
iris-webapp | 7.5 |
iris-ui | 1.5 |