MétaCan
Menu
Back to cohort
Record W3124088161 · doi:10.1287/mnsc.2016.2632

The Impact of Supply Chains on Firm-Level Productivity

2017· article· en· W3124088161 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

VenueManagement Science · 2017
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicSupply Chain and Inventory Management
Canadian institutionsUniversity of British ColumbiaMcGill University
Fundersnot available
KeywordsProductivitySupply chainBusinessIndustrial organizationUpstream (networking)Asset (computer security)PortfolioSample (material)MicroeconomicsEconomicsMarketingComputer scienceFinance

Abstract

fetched live from OpenAlex

Firms in a vertical relationship are likely to affect each other’s productivity. Exactly how does productivity spill over across this type of relationship (i.e., through which mechanisms)? Additionally, how does the relative importance of these mechanisms depend on the structure of the supply chain? To answer these questions, we decompose the channels of upstream productivity spillovers—from customers to suppliers—by developing a structural econometric model on a sample of approximately 22,500 supply chain dyads. We find that the “endogenous channel” (i.e., the effect of the customer’s own productivity on the supplier’s productivity) is by far the most important source of spillovers. This is especially true if (i) the supplier has a concentrated customer base, (ii) the supplier and the customer have similar operational characteristics, and (iii) the relationship has medium maturity. In the converse scenarios, we find, it is more important to have a partner with a portfolio of favorable “contextual” characteristics (high inventory turnover, financial liquidity, and asset turnover) than to have a productive partner. The online appendix is available at https://doi.org/10.1287/mnsc.2016.2632 . This paper was accepted by Serguei Netessine, operations management.

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.002
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies, Scholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.796
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0030.001
Scholarly communication0.0010.002
Open science0.0030.001
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.052
GPT teacher head0.295
Teacher spread0.243 · 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