Critical Success Factors for ERP Projects: Recommendations from a Canadian Exploratory Study
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.
Bibliographic record
Abstract
This research paper discusses key recommendations for improving future Enterprise Resource Planning (ERP) implementations based on insights from an exploratory qualitative single case study in the Canadian Oil and Gas Industry. The study was conducted using a semi-structured interview guide from twenty participants belonging to four project role groups of senior leaders, project managers, project team members, and business users. The research evoked a comprehensive list of forty-two critical success factors (CSFs) and out of which, top ten CSFs discussed include: Know your data, longer and more integrated testing, utilization of the right people, longer stabilization period (hyper-care), communication, address legal and fiscal requirements, hyper-care must be longer, early buy-in from business, have a Lean Agile program, less customization and more vanilla out of the box, and project must be business-driven and not IT-driven. This study is one of first ERP case studies in the Canadian oil and gas industry and the research recommendations can prove to be beneficial for organizations when undertaking ERP implementations.
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 imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.002 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it