Optimization of Meat and Poultry Farm Inventory Stock Using Data Analytics for Green Supply Chain Network

Abstract

The traditional meat and poultry farms use a fixed quantity of supply, which creates an imbalance between demand and supply. Due to this imbalance, a huge amount is spent on balancing the requirements. There is an inequality among demand and supply since typical meat and poultry farms use a fixed amount of supply. A lot of money is spent trying to balance the requirements because of this mismatch. In addition, when connecting and building the meat and poultry farm system, the procedure ignores the impact on the environment. The owner’s primary goals are to retain massive profits and raise reliability. The classical method neglects the effect on the environment while linking and designing the meat and poultry farm system. The main aim of the owner is to increase the quality and maintain the maximum profit. This paper deals with the meat and poultry farms in two folds. In the first step, the IoT based system is implemented for the traceability and demand‐supply monitoring. The second steps include optimization of the supply network to reduce the carbon emission from the transportation. Both steps take data analytics as an input to process the final result for the farm to run and optimize. Effective inventory optimization algorithms have been shown to be able to evaluate a significant portion of previous sales data and anticipate inventory future demand by taking seasonality and lead times into account. Revenue, productivity, and customer satisfaction are just a few of the business variables that these strategies may affect. Finally, the comparison is done with the traditional farm and supply chain on the points of demand‐supply balance, cost, carbon emission, and wastage. It is found that the farms using data analytics to optimize the overall system perform better and with 37% more efficient than the traditional systems.

Cite this work

No public copy is stored for this record, so only the metadata is cited.

Stored only when both papers are in the corpus — 51 citations exist upstream.

Papers that cite the same references — the relational fallback while embeddings are still backfilling.