MétaCan
Menu
Back to cohort
Record W2948199369 · doi:10.5539/ijbm.v14n7p54

Critical Challenges in Enterprise Resource Planning (ERP) Implementation

2019· article· en· W2948199369 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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueInternational Journal of Business and Management · 2019
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicERP Systems Implementation and Impact
Canadian institutionsnot available
Fundersnot available
KeywordsEnterprise resource planningExploratory researchBusinessCritical success factorResource (disambiguation)Project managementProject teamKnowledge managementPetroleum industryProject planningSenior managementProcess managementManagementComputer scienceEngineeringPublic relationsSociologyPolitical science

Abstract

fetched live from OpenAlex

This research paper explores critical challenges in Enterprise Resource Planning (ERP) implementation based on insights from an exploratory qualitative single case study in the Canadian Oil and Gas Industry. The study was conducted in a Canadian case organization using twenty interviews from members of four project role groups of senior leaders, project managers, project team members, and business users. The study further collected and reviewed project documents from the ERP implementation for triangulation. The research evoked a comprehensive list of sixty critical challenges and out of which, the top twelve challenges discussed in detail were drawn from the responses of participants from all four project role groups. The study findings indicated that critical challenges were significant during ERP implementation. This research is one of first case studies in the Canadian oil and gas industry that focuses on critical challenges in ERP implementation projects.

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.416
Threshold uncertainty score0.460

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.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
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.042
GPT teacher head0.337
Teacher spread0.295 · 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