MétaCan
Menu
Back to cohort
Record W1987581148 · doi:10.1108/14637150910960620

ERP implementation through critical success factors' management

2009· article· en· W1987581148 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 · 2009
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicERP Systems Implementation and Impact
Canadian institutionsPolytechnique Montréal
Fundersnot available
KeywordsImplementationComputer scienceScope (computer science)GRASPCritical success factorDelphi methodEnterprise resource planningProcess managementKnowledge managementOriginalityWork (physics)Management scienceBusinessSoftware engineeringQualitative researchEngineering

Abstract

fetched live from OpenAlex

Purpose The purpose of this paper is to identify practical activities that are essential for managing enterprise resource planning (ERP) implementation projects and that answer to the expectations of the widely recognized critical success factors (CSFs). Design/methodology/approach This work is based on an extensive literature review on CSF, which has been followed by a Delphi survey with a panel of ERP experts. For each CSF, it obtained a range, validated by experts, of practical actions to perform, supported by the resolution of the problems usually encountered in these areas. Findings The work carried out has a practical scope: the principles of the proposed method directly affect all actors in ERP projects and gives them practical results that they can apply immediately. When applied in the framework of the methodology the paper suggests, these actions will result in better oversight over the requirements of each area of expertise. In this way, overall grasp of the project is facilitated, reducing the inherent uncertainties. Research limitations/implications Findings may be limited by the small number of respondents, but each one had participated in several implementations. Moreover, no industry sector was specifically targeted; thus, the results apply a priori to most implementations. Originality/value This research helps to draw the academic and professional domains together by proposing, for the first time, a way for theoretical findings to be translated into practical actions. These results will allow all actors in an ERP implementation to understand the project imperatives faster and more accurately.

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, Insufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.591
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.002
Science and technology studies0.0010.000
Scholarly communication0.0020.007
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0020.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.037
GPT teacher head0.360
Teacher spread0.323 · 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