[
https://issues.apache.org/jira/browse/OFBIZ-13249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17983682#comment-17983682
]
Pierre Smits commented on OFBIZ-13249:
--------------------------------------
We have to differentiate between 'Build-To-Order' and 'Build-To-Stock'. But we
also have to factor in forecasts delivered by the sales department/account
managers for upcoming periods.
In 'Build-To-Order' we're often talking high-value products, where there is a
1-1-1 relation between SO, ProdRun and PO.
In 'Build-To-Stock', given multiple SOs in a given period, companies are
looking to forecasts (and ad-hoc sales activities like promotions) to ensure an
optimized planning regarding warehouse capacity (both space and workers) and
ProdRuns scheduling (re availability of equipment and workers) and PO
initiation (factoring in delivery constraints), to cater for cost optimization.
In OFBiz, forecasting is catered for through functionalities regarding the
SalesForecast entity. utilizing those would help ProdRun scheduling and PO
initiation.
Anyway, there seems to be more aspects to this ticket than the stated
description...
> Add a configurable ARDO window to the MRP engine to consolidate multiple
> small material requirements for a near tenure into single combined
> requirements.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-13249
> URL: https://issues.apache.org/jira/browse/OFBIZ-13249
> Project: OFBiz
> Issue Type: Improvement
> Components: manufacturing
> Affects Versions: Upcoming Branch
> Reporter: Yashwant Dhakad
> Priority: Minor
>
> Currently, in the Manufacturing module, the MRP engine currently creates
> separate material requirements for each demand date without any aggregation.
> For example, daily demands for the same product generate individual
> requirements instead of being consolidated. This leads to a long & confusing
> list of requirements thus complicating scheduling for procurement and
> production. In real-world business scenarios, this aspect makes it harder to
> coordinate with suppliers and increases the risk of missed or delayed orders.
> For example, the system has the following orders for skateboards:
> * Order 101: 10 units placed on May 15, with a Delivery Date of June 15.
> * Order 102: 10 units placed on May 28, with a Delivery Date of June 16.
> * Order 103: 10 units placed on May 30, with a Delivery Date of June 17.
> Now, if MRP is run on June 1 without ARDO, it creates separate requirements
> of 10 units for each order.
> However, if the MRP engine is executed with ARDO set to 20 days, the MRP
> engine consolidates all those requirements whose delivery date lies between
> June 1 to June 20 into a single requirement of 30 units on June 1. This
> simplifies planning by consolidating demand, ensuring efficient inventory
> management.
> There is no configuration option or UI field (such as an “Aggregate
> Requirements Days Offset” window/field) to define a time span within which
> requirements could be combined. As a result, procurement and production teams
> must manage multiple small orders, increasing administrative overhead, error
> risk, and increasing operational inefficiency.
> The system should support a configurable ARDO window that aggregates all
> material requirements within the specified number of days into a single
> consolidated requirement on the earliest date. This aggregation should be
> clearly indicated to the user through UI messages or logs and properly
> reflected in procurement and production planning screens and reports.
> This change would simplify procurement and production planning, reduce
> fragmented orders, and improve operational efficiency for manufacturing
> businesses.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
