MétaCan
Menu
Back to cohort
Record W2107858363 · doi:10.1504/ijor.2010.036289

A two-stage stochastic programming method for designing multi-stage global supply chains with stochastic demand

2010· article· en· W2107858363 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueInternational Journal of Operational Research · 2010
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicSustainable Supply Chain Management
Canadian institutionsUniversity of Windsor
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsOutsourcingStochastic programmingSupply chainComputer scienceService levelOperations researchInteger programmingProduction (economics)Stage (stratigraphy)Service (business)Mathematical optimizationBusinessMicroeconomicsEconomicsMathematicsMarketing

Abstract

fetched live from OpenAlex

This paper encompasses the design of a multi-stage global supply chain with stochastic demand. The network consists of manufacturing sites, distribution centres and retail zones situated at both domestic and international locations. Tactical level decisions to be made are the selection of international outsourcing partners, transportation modes and the capacity of each facility. To provide a practical decision support tool for the design of global supply chains, we consider the existence of exchange rate variations and the presence of economies of scale in production which lead to different capacity expansion and outsourcing policies. We formulate the problem as a mixed-integer programming (MIP) model with the objective of minimising the overall costs and maximising the expected average service level. A two-stage stochastic programming method is used to handle the stochasticity in demand. Finally, the proposed model is applied to various cases to demonstrate its applicability in facilitating decision making for managers.

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.006
metaresearch head score (Gemma)0.004
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.760
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0060.004
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0020.002
Open science0.0010.000
Research integrity0.0000.001
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.073
GPT teacher head0.417
Teacher spread0.344 · 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