MétaCan
Menu
Back to cohort
Record W4410324073 · doi:10.52783/jisem.v10i45s.8889

Real-Time Data Processing in ERP Systems: Benefits and Challenges

2025· article· en· W4410324073 on OpenAlexaff
Chandra Bonthu

Bibliographic record

VenueJournal of Information Systems Engineering & Management · 2025
Typearticle
Languageen
FieldComputer Science
TopicCloud Computing and Resource Management
Canadian institutionsEVERSANA (Canada)
Fundersnot available
KeywordsComputer scienceEnterprise resource planningReal-time computingEmbedded systemKnowledge management

Abstract

fetched live from OpenAlex

Enterprise Resource Planning (ERP) systems are very necessary, and it is only important to find how real-time data processing can be used to handle business processes more efficiently. ERP combines all disparate business functions into one system, combining finance, supply chain, and customer service to coordinate department activities and performance. Timely insights from real-time data processing help companies make informed decisions about operational efficiency. This involves how real-time data is utilized to support Multi-Domain Master Data Management (MDM) to ensure the Data is accurate and consistent across Domains such as customers and product SVC providers. This real-time synchronization removes the differences among departments and errors in decisions and execution of operations. The article also discusses the advantages of Data Quality as a Service (DaaS). It automates data cleansing, validation, and error resolution so the data stays in good shape. It illuminates the business of data latency, challenges to real-time processing, and the scope and level of security. Advanced data streaming technologies and cloud platforms are used to overcome these challenges, and solutions are discussed. The article also considers AI, machine learning, edge computing, and 5G technology in the future, which will power the next round of ERP real-time data processing. In the fast-changing data-driven market, the competitive edge comes about from the real-time processing of the data.

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 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.002
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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.906
Threshold uncertainty score0.479

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.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.0010.001
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.017
GPT teacher head0.218
Teacher spread0.202 · 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 teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designSimulation or modeling
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

Citations1
Published2025
Admission routes1
Has abstractyes

Explore more

Same venueJournal of Information Systems Engineering & ManagementSame topicCloud Computing and Resource ManagementFrench-language works237,207