[jira] [Updated] (OFBIZ-7355) OFBIZ-6964: Document finalized business requirements to support replenishment planning through any inter-company facility

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Updated] (OFBIZ-7355) OFBIZ-6964: Document finalized business requirements to support replenishment planning through any inter-company facility

Nicolas Malin (Jira)

     [ https://issues.apache.org/jira/browse/OFBIZ-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Swapnil Shah updated OFBIZ-7355:
--------------------------------
    Description:
Here are the most common set of business requirement to support product level replenishment within a given facility(store/warehouse) via any inter-company facility (preferred warehouse/stocking facility) before raising the purchase order from an outside vendors/suppliers.

In current standard OFbiz workflow there are essentially two basic types of material requirements generated at product-facility level. Both of these can be created manually or could be suggested by MRP engine:
* First, is "Product Requirement" which suggests that the given product is going to be low or out of stock within any given facility in a given time frame based on upstream demand signals within the supply chain and hence can more commonly be treated as Purchase Requirement that need to be eventually transformed as Purchase Orders to be raised from a given vendor/supplier
* Second, is "Internal Requirement" which suggests that the given product is going to be low or out of stock within any given facility in a given time frame based on upstream demand within the supply chain. But such products can be internally manufactured(produced) and hence can more commonly be treated as Production Requirement that need to be eventually transformed as Production Order (Production Run).

*Gap*
Currently the OFbiz planning algorithm (aka MRP) generate the requirement by only considering the supply available within the given facility. But there is no planning logic built into the system which can support and look up the supply availability in a complex supply chain setup where business could be run using multiple facilities spread geographically. A more common examples could be brick and mortar retail stores chain having multiple stores spread across geographically. Or any manufacturing business that own multiple production facilities and warehouse spread across geographically.

*Requirement*
There are many instances, where material visibility in a multi-facility setup within an organization or company is not very accurately gauged. We would need to start building an intelligent planning system that could gauge such material availability across facilities and honor them while furnishing the requirements around any product within any given facility.
Let's consider a simple use case as follows:



  was:Let's use this ticket to post the finalized business requirement to support product level replenishment within a given facility(store/warehouse) via any inter-company facility (preferred warehouse/stocking facility) before raising the purchase order from an outside vendors/suppliers.


> OFBIZ-6964: Document finalized business requirements to support replenishment planning through any inter-company facility
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-7355
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-7355
>             Project: OFBiz
>          Issue Type: Sub-task
>          Components: manufacturing, order, product
>    Affects Versions: 15.12.01
>            Reporter: Swapnil Shah
>            Assignee: Swapnil Shah
>             Fix For: Upcoming Branch
>
>
> Here are the most common set of business requirement to support product level replenishment within a given facility(store/warehouse) via any inter-company facility (preferred warehouse/stocking facility) before raising the purchase order from an outside vendors/suppliers.
> In current standard OFbiz workflow there are essentially two basic types of material requirements generated at product-facility level. Both of these can be created manually or could be suggested by MRP engine:
> * First, is "Product Requirement" which suggests that the given product is going to be low or out of stock within any given facility in a given time frame based on upstream demand signals within the supply chain and hence can more commonly be treated as Purchase Requirement that need to be eventually transformed as Purchase Orders to be raised from a given vendor/supplier
> * Second, is "Internal Requirement" which suggests that the given product is going to be low or out of stock within any given facility in a given time frame based on upstream demand within the supply chain. But such products can be internally manufactured(produced) and hence can more commonly be treated as Production Requirement that need to be eventually transformed as Production Order (Production Run).
> *Gap*
> Currently the OFbiz planning algorithm (aka MRP) generate the requirement by only considering the supply available within the given facility. But there is no planning logic built into the system which can support and look up the supply availability in a complex supply chain setup where business could be run using multiple facilities spread geographically. A more common examples could be brick and mortar retail stores chain having multiple stores spread across geographically. Or any manufacturing business that own multiple production facilities and warehouse spread across geographically.
> *Requirement*
> There are many instances, where material visibility in a multi-facility setup within an organization or company is not very accurately gauged. We would need to start building an intelligent planning system that could gauge such material availability across facilities and honor them while furnishing the requirements around any product within any given facility.
> Let's consider a simple use case as follows:



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)