MétaCan
Menu
Back to cohort
Record W2027768301 · doi:10.1016/j.procir.2014.01.125

Capacity Scalability in Robust Design of Supply Flow Subject to Disruptions

2014· article· en· W2027768301 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

VenueProcedia CIRP · 2014
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicSupply Chain Resilience and Risk Management
Canadian institutionsConcordia University
Fundersnot available
KeywordsSupply chainRobust optimizationRisk analysis (engineering)Safety stockScalabilitySupply chain risk managementBackupComputer scienceBusinessOperations researchReliability engineeringOperations managementSupply chain managementService managementEngineeringMathematical optimization

Abstract

fetched live from OpenAlex

Within the last decade, several cases of the supply chain vulnerability to major disruptions have been observed. The typical mitigation strategies such as safety inventory and excess capacity are inadequate to cover the major disruptions. Furthermore it is not economical to invest in such costly proactive strategies to recover from infrequent disruptions. The objective of this paper is to provide a decision making tool achieving robust supply flow by incorporating strategic stock and reconfigurable back-up supplier in mitigating disruptions. We consider a firm with two suppliers where the main supplier is cost-effective but prone to disruptions and the back-up supplier is reliable but expensive due to re-configurability characteristics. We present a multi-stage robust optimization model to determine optimal strategic stock levels and layout configuration of the back-up supplier for a supply chain subject to random realization of disruptions and available capacity during the ramp-up time. Furthermore, the partial available capacity of the backup supplier during the response time has been modelled using queuing theoretical models. The results show the optimality of highly scalable configuration as the decision maker becomes more risk averse.

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.001
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.120
Threshold uncertainty score0.619

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.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.028
GPT teacher head0.227
Teacher spread0.199 · 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