MétaCan
Menu
Back to cohort
Record W4402669414 · doi:10.1016/j.omega.2024.103196

Strategic expansion of freight transportation hub networks under demand uncertainty

2024· article· en· W4402669414 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

VenueOmega · 2024
Typearticle
Languageen
FieldEngineering
TopicVehicle Routing Optimization Methods
Canadian institutionsUniversity of Waterloo
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsTraffic managementBusinessTransport engineeringIndustrial organizationOperations researchEngineering

Abstract

fetched live from OpenAlex

We focus on freight transportation carriers that transport shipments that are small relative to vehicle capacity and incur transportation costs that exhibit economies of scale. For such carriers, profitability is driven by shipment consolidation, which is achieved by routing shipments through a network of hubs. We consider a carrier that seeks to expand its network into new regions by merging with carriers that already operate in those regions. We focus on how, and by how much, the network that results from such a merger should be redesigned to maximize profitability. We perform a case study based on operations from a multi-regional United States Less-than-truckload freight transportation carrier to derive insights into the profitability of different redesign strategies. We derive insights into how a network that results from a merger should be redesigned. We also study how uncertainty in shipment sizes impacts the structure of the redesigned networks. • Studies redesign of merged transportation hub networks for maximum profitability. • Introduces three profit-maximizing capacitated hub location models. • Transportation costs between hubs are modeled on a per-vehicle basis. • Two different stochastic models address the impacts of shipment size uncertainty. • A case study is presented based on a multi-regional freight transportation carrier.

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.713
Threshold uncertainty score0.388

Codex and Gemma teacher scores by category

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