MétaCan
Menu
Back to cohort
Record W2040492074 · doi:10.1108/14637150810888064

Adoption and risk of ERP systems in manufacturing SMEs: a positivist case study

2008· article· en· W2040492074 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

VenueBusiness Process Management Journal · 2008
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicERP Systems Implementation and Impact
Canadian institutionsUniversité du Québec à Trois-Rivières
Fundersnot available
KeywordsEnterprise resource planningContext (archaeology)Process managementKnowledge managementProcess (computing)Business processOriginalityBusinessComputer scienceOperations managementMarketingQualitative researchEconomicsWork in process

Abstract

fetched live from OpenAlex

Purpose In order to deepen the knowledge and further advance theory on enterprise resource planning (ERP) implementation in small‐ to medium‐sized enterprises (SMEs), this paper seeks to explore the following question: what can be done to minimize the risk of ERP system implementation, from the adoption stage onwards, in a small manufacturing firm? Design/methodology/approach The research method is based on a positivist holistic single‐case design in order to perform an initial test of a process model of ERP system adoption by SMEs. The unit of analysis selected by purposeful sampling is a small manufacturing business. Findings In attempting to minimize the risk of ERP implementation, the small manufacturing firm applied three principles, eight policies and ten specific practices in adopting ERP. Research limitations/implications The research design, based upon a single‐case study, imposes care in generalizing the results of the study. This design, however, allowed the identification and understanding of the risk of ERP from a managerial/practical standpoint, as opposed to a research/theoretical standpoint. Practical implications In managerial terms, the results show that highly formalized management is not necessary to minimize ERP implementation risk in the context of SMEs. Originality/value Few studies have focused on the adoption process within the ERP implementation cycle. The proposed model, as validated empirically in this study, adds to the understanding of this process in small‐manufacturing firms, especially as regards the minimization of implementation risk from the adoption stage onwards.

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.001
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: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.048
Threshold uncertainty score0.900

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.002
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.029
GPT teacher head0.277
Teacher spread0.248 · 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