MétaCan
Menu
Back to cohort
Record W2117842718 · doi:10.1177/1094670513481108

The Service Delivery Network (SDN)

2013· article· en· W2117842718 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

VenueJournal of Service Research · 2013
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicService and Product Innovation
Canadian institutionsUniversity of Victoria
Fundersnot available
KeywordsService providerService (business)Service delivery frameworkComputer scienceSet (abstract data type)Customer Service AssuranceKnowledge managementProcess managementCustomer advocacyService designBusinessService level objectiveMarketingService quality

Abstract

fetched live from OpenAlex

In this article, we introduce the concept of the service delivery network (SDN) defined as two or more organizations that, in the eyes of the customer, are responsible for the provision of a connected overall service experience. This responds to calls for frameworks recognizing that dyadic service encounters are embedded in the series of experiences customers have with complementary providers as part of the journey to achieve their desired goals. Adopting an SDN perspective presents a dramatically different set of challenges for managers and provides research opportunities challenging the current view of established service concepts. Managers must recognize that to better serve the customer they need to understand the role that they play in the customer-defined service journey and be prepared to coordinate their activities with complementary providers. Participating in helping build and manage the SDN for the customer, or understanding how they fit into customer’s self-designed SDN, becomes a central challenge, often requiring firms to develop a new set of capabilities. The SDN also challenges the way we view many of the core concepts in service research, which are anchored in the dyadic view. This provides considerable opportunity for future inquiry. We present a series of research questions, inspired by the SDN, organized into categories including building cooperative and collaborative networks, customer cocreation, systems thinking, customer relationship management, managing service failure and recovery, building capabilities, and customer-to-customer interactions.

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.005
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScholarly communication, Insufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.179
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

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

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.082
GPT teacher head0.313
Teacher spread0.231 · 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