MétaCan
Menu
Back to cohort
Record W2740735422 · doi:10.1287/msom.2017.0648

Simple Policies for Managing Flexible Capacity

2018· article· en· W2740735422 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

VenueManufacturing & Service Operations Management · 2018
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicSupply Chain and Inventory Management
Canadian institutionsUniversity of British Columbia
Fundersnot available
KeywordsComputer scienceSimple (philosophy)Product (mathematics)Economic shortageScarcityService (business)Operations researchNewsvendor modelRange (aeronautics)AppealService levelMathematical optimizationMicroeconomicsBusinessEconomicsSupply chainMarketingMathematics

Abstract

fetched live from OpenAlex

In many scenarios, a fixed capacity is shared flexibly between multiple products. To manage such multiproduct systems, firms need to make two sets of decisions. The first one requires setting an inventory target for each product, and the second requires dynamically allocating the scarce capacity among the products. It is not known how to make these decisions optimally. In this paper, we propose easily implementable policies that have both theoretical and practical appeal. We first suggest simple and intuitive allocation rules that determine how such scarce capacity is shared. Given such rules, we calculate the optimal inventory target for each product. We demonstrate analytically that our policies are optimal under two asymptotic regimes represented by high service levels (i.e., high shortage costs) and heavy traffic (i.e., tight capacity). We also demonstrate that our policies outperform current known policies over a wide range of problem parameters. In particular, the cost savings from our policies become more significant as the capacity gets more restrictive. The online appendix is available at https://doi.org/10.1287/msom.2017.0648 .

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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Scholarly communication, Insufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.844
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

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

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.037
GPT teacher head0.255
Teacher spread0.217 · 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