MétaCan
Menu
Back to cohort
Record W1499809638 · doi:10.1108/14637150110392647

Organizational memory and the completeness of process modeling in ERP systems

2001· article· en· W1499809638 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 · 2001
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicERP Systems Implementation and Impact
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsComputer scienceEnterprise resource planningProcess (computing)Scope (computer science)Variety (cybernetics)Knowledge managementOrganizational memoryProcess managementProcess modelingBusiness processData scienceOrganizational learningWork in processBusinessArtificial intelligenceMarketing

Abstract

fetched live from OpenAlex

Enterprise resource planning (ERP) systems not only have a broad functional scope promising to support many different business processes, they also embed many different aspects of the company’s organizational memory. Disparities can exist between those memory contents in the ERP system and related contents in other memory media, such as individuals’ memories, and the organizational structure and culture. It is our contention that, in general, these disparities or memory mismatches, as we will refer to them, lead to under‐performance of ERP systems. In this paper we focus on potential memory mismatches that may arise with respect to the embedding of process knowledge within ERP packages. Packages such as SAP provide a varied and rich environment for process modeling. However, we suspect that there are still many instances where process knowledge is either lost or represented in different ways in different parts of the organization. As we will discuss, the results of such memory mismatches will often not become evident until the system is in use. The overall thrust of the paper is to identify a variety of concerns, intriguing questions and avenues for future research.

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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.400
Threshold uncertainty score0.693

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.002
Science and technology studies0.0000.000
Scholarly communication0.0010.002
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.038
GPT teacher head0.269
Teacher spread0.231 · 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