MétaCan
Menu
Back to cohort
Record W2893199289 · doi:10.1109/tem.2018.2868716

An In-Depth Analysis of Contingent Sourcing Strategy for Handling Supply Disruptions

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

VenueIEEE Transactions on Engineering Management · 2018
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicSupply Chain Resilience and Risk Management
Canadian institutionsWilfrid Laurier University
FundersFundamental Research Funds for the Central UniversitiesNational Natural Science Foundation of China
KeywordsStrategic sourcingBusinessIndustrial organizationComputer scienceStrategic planningMarketing

Abstract

fetched live from OpenAlex

In this paper, we consider a make-to-stock producti-on-inventory system where a manufacturer's production may be entirely interrupted due to a supply disruption. Customers react dynamically to the subsequent inventory shortage, depending on factors including market condition, customer characteristic, and behavioral interaction. The manufacturer can adopt contingent sourcing to manage the disruption. Consequently, the postdisruption demand and inventory exhibit complicated dynamics in terms of customer behavior, demand recovery, and the adoption of contingent sources. We first model and forecast the postdisruption customer behavior. Customers are classified into two types based on brand loyalty and the interaction is captured as “demand learning” within each type. Using differential models, we analytically characterize customers' postdisruption behavior in five possible scenarios, depending on customers' constitution, transient reaction, brand loyalty, and competition intensity. Next, we propose dynamic contingent sourcing strategies to mitigate the supply disruption, and the optimal sourcing time is derived. Finally, by conducting numerical analysis, we obtain further managerial insights on how to adapt dynamic contingent sourcing strategies according to various contributing factors.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.789
Threshold uncertainty score0.997

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0020.002
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.017
GPT teacher head0.258
Teacher spread0.241 · 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