MétaCan
Menu
Back to cohort
Record W4399054801 · doi:10.3926/jiem.6045

Analysis of a new dynamic capacity management approach in DDMRP: Application on a real industrial case

2024· article· en· W4399054801 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

VenueJournal of Industrial Engineering and Management · 2024
Typearticle
Languageen
FieldDecision Sciences
TopicOperations Management Techniques
Canadian institutionsPolytechnique Montréal
Fundersnot available
KeywordsOriginalityWorkloadComputer scienceCapacity managementProduction (economics)Operations researchService levelIndustrial engineeringOperations managementEngineeringBusinessEconomicsMarketingMicroeconomics

Abstract

fetched live from OpenAlex

Purpose: Although the authors of the Demand Driven Material Requirements Planning (DDMRP) argue that the method DDMRP is the solution to the limitations of traditional production management methods, its capacity management system remains unclear. Since DDMRP operates at infinite capacity, it is important to consider a capacity management approach to avoid under- or overloading production workshops.Design/methodology/approach: We propose a new dynamic capacity management approach for the DDMRP method. Our approach is based on the calculation of the anticipated workload, using DDMRP stock buffers and considering customer order spikes. Considering a real industrial case, we compare the proposed approach to a static one and a dynamic approach from the literature.Findings: The analysis of the results, supported by a two-way ANOVA, indicates that the proposed capacity management approach outperforms the performance of the other two approaches by maximizing the resource loading rate while ensuring a high customer service level.Originality/value: The originality of the article comes on the one hand from the capacity adjustment module by calculating the anticipated workload, and on the other hand from the comparison of this approach with two others, one of which comes from the literature.

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.003
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.579
Threshold uncertainty score0.622

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0040.004
Science and technology studies0.0000.000
Scholarly communication0.0000.000
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.101
GPT teacher head0.339
Teacher spread0.238 · 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