MétaCan
Menu
Back to cohort

Implementing Off-peak Deliveries in the Greater Toronto Area: Costs, Benefits, Challenges

2015· article· en· W2268154704 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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueTransportation Journal · 2015
Typearticle
Languageen
FieldEngineering
TopicUrban and Freight Transport Logistics
Canadian institutionsUniversity of Waterloo
Fundersnot available
KeywordsTruckProcurementSustainabilityTransport engineeringBusinessTraffic congestionOperations managementComputer scienceMarketingEngineeringAutomotive engineering

Abstract

fetched live from OpenAlex

Abstract Nestle Canada currently uses 32 routes that serve over 4,500 customers in the Greater Toronto Area (GTA). This study aims to quantify Nestlé's costs and benefits of modifying their ice cream supply chain to incorporate night-time deliveries, while providing a framework for the regulatory, conceptual, and inertial obstacles to implementation. Employing Nestlé's customer data set, we created routing software to determine the proportion of customers who must be willing to accept deliveries outside of normal working hours so that the change would be financially feasible. Based upon a literature review we found that, before proceeding, the following qualitative factors should be considered: safety, sustainability, regulatory concerns, truck noise, traffic, and congestion. Reduction of 3–10 percent in the number of routes may result from switching a suitable proportion of deliveries to night-time, achieving the minimum fleet size when 50–60 percent of locations are served on night routes. The operation of both night-time and daytime deliveries would enable an increase in truck utilization, thus decreasing the number of vehicles required. Recommendations for success of night-time deliveries include preparation of a safety plan, procurement of plate trucks, noise-abatement techniques, and the development of a noise-monitoring program.

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: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.623
Threshold uncertainty score0.875

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.075
GPT teacher head0.229
Teacher spread0.154 · 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