MétaCan
Menu
Back to cohort
Record W2012499881 · doi:10.1111/poms.12033

Designing Service Level Agreements for Inventory Management

2013· article· en· W2012499881 on OpenAlex
Liping Liang, Derek Atkins

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

VenueProduction and Operations Management · 2013
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicSupply Chain and Inventory Management
Canadian institutionsUniversity of British Columbia
FundersLingnan University
KeywordsService levelIncentiveIntuitionOutsourcingOrder (exchange)Computer scienceService (business)Operations researchOperations managementBusinessMicroeconomicsEconomicsMarketingFinance

Abstract

fetched live from OpenAlex

Service level agreements (SLAs) are widely employed forms of performance‐based contracts in operations management. They compare performance during a period against a contracted service level and penalize outcomes exceeding some allowed deviation. SLAs have a number of design characteristics that need careful tuning to ensure that incentives are properly aligned. However, there is little theoretical research in this area. Using an example of an SLA for outsourcing inventory management, we make a number of recommendations. First it is preferable, if possible, that penalties be proportional to the underperformance rather than lump‐sum ones. This goes a long way towards mitigating strategic (“gaming”) behavior by the supplier. Second, it might be thought that giving “bonuses for good performance” rather than “penalties for bad performance” are essentially identical apart from the former being a more positive approach to management. This turns out to be incorrect in the case of large percentage service rate targets and that penalties will normally be preferred by the buying firm. Third, in order not to incorrectly penalize underperformance resulting purely from “noise” rather than supplier efforts, management might think it best to make allowed deviations from the target generous. Again intuition is not a helpful guide here: for proportional penalties, acceptable performance deviations should be close to the target. Although these results come from a particular inventory application, it is likely that the lessons are applicable to SLAs in general.

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 categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.621
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0010.000
Scholarly communication0.0010.002
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.001

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.053
GPT teacher head0.239
Teacher spread0.186 · 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