Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B8CCF200CEC for ; Mon, 21 Aug 2017 12:10:15 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B7A27164E1A; Mon, 21 Aug 2017 10:10:15 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B9135164E14 for ; Mon, 21 Aug 2017 12:10:14 +0200 (CEST) Received: (qmail 15356 invoked by uid 500); 21 Aug 2017 10:10:13 -0000 Mailing-List: contact notifications-help@ofbiz.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ofbiz.apache.org Delivered-To: mailing list notifications@ofbiz.apache.org Received: (qmail 15269 invoked by uid 99); 21 Aug 2017 10:10:13 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Aug 2017 10:10:13 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 949271806C0 for ; Mon, 21 Aug 2017 10:10:12 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id IfRQaXCCUkre for ; Mon, 21 Aug 2017 10:10:09 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id D8A495FE5F for ; Mon, 21 Aug 2017 10:10:08 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 37742E0D85 for ; Mon, 21 Aug 2017 10:10:08 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id BCFB125389 for ; Mon, 21 Aug 2017 10:10:07 +0000 (UTC) Date: Mon, 21 Aug 2017 10:10:07 +0000 (UTC) From: "Swapnil Shah (JIRA)" To: notifications@ofbiz.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (OFBIZ-7355) OFBIZ-6964: Document finalized business requirements to support replenishment planning through any intra-company facility MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 21 Aug 2017 10:10:15 -0000 [ 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 intra-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 following use case (Please refer to attached screenshot for reference) !screenshot-1.png|width=800px! : * A retail chain has multiple stores and say a given physical store 'Store_01' and is strategically located near two warehouse in the region say Whse_01 & Whse_02, * One centralized warehouse(Main/buffer) say 'Backup_Whse' that supplies material to all the stores and regional warehouse * Any retails store e.g. Store_01 shouldn't raise purchase order from any outside vendor directly. * As Store_01 is strategically located near Whse_01 & Whse_02, so system should always suggest to replenish any product shortfall by first looking up and pulling up available supply from Whse_01 & Whse_02 and then from Backup_Whse in that order of priority. * Banckup_Whse mostly works on push system and supplies the products to all regional warehouse and physical stores. Now we could design an OFbiz based replenishment planning that : * Could allow to associate and rank the facilities(physical store/warehouse) that could replenish the material at any other facility (physical store/warehouse) * Could suggest the "*Transfer Requirement*" by gauging the product shortfall within any given facility product-facility at any given point of time by * Could allow to configure and manage the setting at facility(ProductStore or ProductFacility) level, to let planning engine know whether given facility could replenish stock via Transfer Requirement from any other facility. If not then it could take normal route of replenishment via Purchase Order or Production Order route. was: 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 following use case (Please refer to attached screenshot for reference) !screenshot-1.png|width=800px! : * A retail chain has multiple stores and say a given physical store 'Store_01' and is strategically located near two warehouse in the region say Whse_01 & Whse_02, * One centralized warehouse(Main/buffer) say 'Backup_Whse' that supplies material to all the stores and regional warehouse * Any retails store e.g. Store_01 shouldn't raise purchase order from any outside vendor directly. * As Store_01 is strategically located near Whse_01 & Whse_02, so system should always suggest to replenish any product shortfall by first looking up and pulling up available supply from Whse_01 & Whse_02 and then from Backup_Whse in that order of priority. * Banckup_Whse mostly works on push system and supplies the products to all regional warehouse and physical stores. Now we could design an OFbiz based replenishment planning that : * Could allow to associate and rank the facilities(physical store/warehouse) that could replenish the material at any other facility (physical store/warehouse) * Could suggest the "*Transfer Requirement*" by gauging the product shortfall within any given facility product-facility at any given point of time by * Could allow to configure and manage the setting at facility(ProductStore or ProductFacility) level, to let planning engine know whether given facility could replenish stock via Transfer Requirement from any other facility. If not then it could take normal route of replenishment via Purchase Order or Production Order route. > OFBIZ-6964: Document finalized business requirements to support replenishment planning through any intra-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 > Attachments: screenshot-1.png > > > Here are the most common set of business requirement to support product level replenishment within a given facility(store/warehouse) via any intra-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 following use case (Please refer to attached screenshot for reference) > !screenshot-1.png|width=800px! > : > * A retail chain has multiple stores and say a given physical store 'Store_01' and is strategically located near two warehouse in the region say Whse_01 & Whse_02, > * One centralized warehouse(Main/buffer) say 'Backup_Whse' that supplies material to all the stores and regional warehouse > * Any retails store e.g. Store_01 shouldn't raise purchase order from any outside vendor directly. > * As Store_01 is strategically located near Whse_01 & Whse_02, so system should always suggest to replenish any product shortfall by first looking up and pulling up available supply from Whse_01 & Whse_02 and then from Backup_Whse in that order of priority. > * Banckup_Whse mostly works on push system and supplies the products to all regional warehouse and physical stores. > Now we could design an OFbiz based replenishment planning that : > * Could allow to associate and rank the facilities(physical store/warehouse) that could replenish the material at any other facility (physical store/warehouse) > * Could suggest the "*Transfer Requirement*" by gauging the product shortfall within any given facility product-facility at any given point of time by > * Could allow to configure and manage the setting at facility(ProductStore or ProductFacility) level, to let planning engine know whether given facility could replenish stock via Transfer Requirement from any other facility. If not then it could take normal route of replenishment via Purchase Order or Production Order route. -- This message was sent by Atlassian JIRA (v6.4.14#64029)