MétaCan
Menu
Back to cohort
Record W4386997967 · doi:10.30813/jiems.v16i2.4722

Inventory Lot Sizing Decisions for Material Requirements Planning to Minimize Inventory Costs

2023· article· en· W4386997967 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueJIEMS (Journal of Industrial Engineering and Management Systems) · 2023
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicManagement and Optimization Techniques
Canadian institutionsBrock University
Fundersnot available
KeywordsEconomic order quantitySizingMaterial requirements planningInventory controlOperations managementOperations researchInventory costInventory valuationInventory managementValue (mathematics)Exponential smoothingComputer scienceEconomicsBusinessProduction (economics)MathematicsStatisticsMicroeconomicsMarketing

Abstract

fetched live from OpenAlex

<p><em>Inventory control is one of the most important factors in achieving optimal organizational performance. Material Requirement Planning (MRP) is a common method used by businesses to manage inventories. This study focuses on a hydraulic firm that has been in operation since 2016. This research examines the planning of eleven components to get the best planning for the company. This study contributes to the integration of Moving Average (MA) and Exponential Smoothing (ES) forecasting techniques alongside the MRP and three lot sizing techniques, such as LFL, EOQ, and LUC. T</em><em>he minimum error value</em><em>s</em><em> </em><em>between MA and ES are evaluated and followed by the comparison between three lot sizing techniques. The result shows that ES (α=0.1) is selected as the best forecasting technique, and LUC presents the lowest total inventory cost. However, LUC is only 0.05 percent lower than what LFL presents. A larger difference is shown by EOQ with 14.57 percent higher than LUC which makes EOQ unlikely to be selected.</em></p>

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.352
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0020.001
Science and technology studies0.0000.000
Scholarly communication0.0010.001
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.075
GPT teacher head0.271
Teacher spread0.196 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it