MétaCan
Menu
Back to cohort
Record W2964576056 · doi:10.5539/ibr.v12n8p124

Benefits and Process Improvements for ERP Implementation: Results from an Exploratory Case Study

2019· article· en· W2964576056 on OpenAlexvenueaboutno aff
Sreekumar Menon

Bibliographic record

VenueInternational Business Research · 2019
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicERP Systems Implementation and Impact
Canadian institutionsnot available
Fundersnot available
KeywordsEnterprise resource planningProcess managementStandardizationBusinessProcess (computing)Key (lock)Exploratory researchResource (disambiguation)Business processKnowledge managementOperations managementComputer scienceMarketingWork in processEngineering

Abstract

fetched live from OpenAlex

This exploratory qualitative single case study discusses the benefits and process improvements pertinent to enterprise resource and planning (ERP) projects. The study was conducted in a Canadian case organization in the oil and gas industry that includes twenty participants from four project role groups of senior leaders, project managers, project team members, and business users. The results of the study revealed twenty-two key benefits and four process improvements from which organizations can draw value while planning for ERP projects. The top six benefits include: standardization of common business processes, single integrated system, standardized reporting, improved key performance indicators (KPI), all countries in one system, and easy access to data. Knowing and maximizing these key benefits may prove beneficial for organizations, while planning for major investments in ERP systems.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.033
metaresearch head score (Gemma)0.096
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: Qualitative
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.033
Threshold uncertainty score0.175

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0330.096
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0020.002
Science and technology studies0.0050.003
Scholarly communication0.0040.004
Open science0.0020.003
Research integrity0.0020.002
Insufficient payload (model declined to judge)0.0030.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.154
GPT teacher head0.456
Teacher spread0.302 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designQualitative
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations23
Published2019
Admission routes2
Has abstractyes

Explore more

Same venueInternational Business ResearchSame topicERP Systems Implementation and ImpactFrench-language works237,207