MétaCan
Menu
Back to cohort
Record W2074954868 · doi:10.1057/jit.2010.34

Managing Erp System Risk in SMEs: A Multiple Case Study

2011· article· en· W2074954868 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 Information Technology · 2011
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicERP Systems Implementation and Impact
Canadian institutionsUniversité du Québec à Trois-RivièresHEC Montréal
Fundersnot available
KeywordsVendorContext (archaeology)Soft systems methodologyRisk managementEnterprise resource planningProcess (computing)Process managementBusinessInformation systemSmall and medium-sized enterprisesOrder (exchange)Knowledge managementComputer scienceBusiness processRisk analysis (engineering)Management information systemsMarketingWork in processFinance

Abstract

fetched live from OpenAlex

ERP systems are increasingly accessible to small and medium-sized enterprises (SMEs). If the potential benefits of these systems are significant, the same applies to the risk associated with their implementation. A number of authors emphasize that IS risk management is most effective when it is initiated at the earliest possible moment in the system's lifecycle, that is, at the adoption phase. But how do SMEs actually manage the risk of ERP implementation during the ERP adoption process? The research objectives are (1) to identify and describe the influence of the SMEs’ context on their implementation risk exposure, and (2) to understand whether and how, within the adoption process, SMEs actually manage the risk of implementing an ERP system supplied by an ERP vendor, with open source software, or through in-house development. In order to do so, four case studies of SMEs having implemented an ERP system were undertaken. The study shows that to manage risk at the adoption stage, SMEs can proceed in a rather intuitive, informal and unstructured manner, that is explicitly based however upon an architecture of basic principles, policies and practices.

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

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0020.001
Science and technology studies0.0000.000
Scholarly communication0.0000.003
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.026
GPT teacher head0.261
Teacher spread0.235 · 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