MétaCan
Menu
Back to cohort
Record W1990619572 · doi:10.1080/00207543.2014.986299

An optimised target-level inventory replenishment policy for vendor-managed inventory systems

2014· article· en· W1990619572 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

VenueInternational Journal of Production Research · 2014
Typearticle
Languageen
FieldEngineering
TopicVehicle Routing Optimization Methods
Canadian institutionsHEC MontréalUniversité Laval
Fundersnot available
KeywordsVendorBenchmark (surveying)Context (archaeology)Vendor-managed inventoryOperations researchInventory theoryPerpetual inventoryOrder (exchange)Inventory managementBusinessInventory controlComputer scienceEconomic order quantityOperations managementSupply chainMarketingEconomicsSupply chain managementEngineering

Abstract

fetched live from OpenAlex

In vendor-managed inventory (VMI) systems the supplier is responsible for replenishing customers and for deciding when and how much to deliver. One of two inventory policies is typically employed by the supplier. The first one, called the maximum level (ML) policy, gives full freedom to the supplier to deliver any quantity as long as it respects customer inventory capacities. The alternative, which is more constrained, is called the order-up-to (OU) policy. It states that the supplier has to bring the customer inventory up to its maximum capacity level upon delivery. We propose a new tactical policy in the context of VMI systems, called optimised target-level (OTL), under which when the supplier visits a customer, the quantity delivered is such that the final inventory will always be at the same customer-dependent OTL. We perform a computational evaluation of this new policy against both traditional strategies on benchmark instances. We show that it yields lower costs and inventory levels than the OU policy, and is only marginally more expensive than the ML policy, while being easier to implement.

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.008
metaresearch head score (Gemma)0.003
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.757
Threshold uncertainty score0.548

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0080.003
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.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.121
GPT teacher head0.417
Teacher spread0.296 · 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