MétaCan
Menu
Back to cohort
Record W1988214716 · doi:10.1108/02635570910926627

Interactions between contingency, organizational IT factors, and ERP success

2009· article· en· W1988214716 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

VenueIndustrial Management & Data Systems · 2009
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicERP Systems Implementation and Impact
Canadian institutionsCape Breton University
Fundersnot available
KeywordsEnterprise resource planningContingencyContingency theoryKnowledge managementStructural equation modelingContext (archaeology)OriginalityInformation technologyResource (disambiguation)Critical success factorBusinessManufacturing resource planningInformation systemValue (mathematics)Resource-based viewComputer scienceMarketingPsychologyEngineeringCompetitive advantageSocial psychology

Abstract

fetched live from OpenAlex

Purpose The purpose of this paper is to examine the impact of some organizational information technology (IT) factors (i.e. IT assets, employees' IT skills, IT resources, and satisfaction with legacy IT systems) and their interacting effects with two contingency factors (i.e. organization's size and structure) on enterprise resource planning (ERP) system success. Design/methodology/approach Surveys were conducted in two European countries. Respondents came from diverse, private, and industrial organizations. Relevant hypotheses were developed and tested using a structural equation modeling technique. Findings The analysis supported – partially or fully – six of the eight hypotheses formulated. For example, the data indicated strong positive relationships between IT assets and IT resources, on the one hand, and ERP success, on the other. Organization's size and structure were also found to be moderators in some of the relationships. Also, the analysis revealed that satisfaction with legacy IT systems increased with ERP success, which was an unexpected finding. Originality/value This study contributes to the literature, being among the few to investigate the effects of organizational IT factors and their interacting effects with relevant contingency factors in the context of ERP system success. Methodologically, the study utilized a “non‐deterministic” model to facilitate deeper insights into the effects of variables.

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

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0020.003
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.176
GPT teacher head0.335
Teacher spread0.159 · 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