MétaCan
Menu
Back to cohort
Record W2126105410 · doi:10.1186/s40165-014-0009-8

A goal-oriented, business intelligence-supported decision-making methodology

2014· article· en· W2126105410 on OpenAlexafffund
Alireza Pourshahid, Iman Johari, Gregory Richards, Daniel Amyot, Okhaide Akhigbe

Bibliographic record

VenueDecision Analytics · 2014
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicBig Data and Business Intelligence
Canadian institutionsWilfrid Laurier UniversityUniversity of OttawaIBM (Canada)
FundersUniversity of Ottawa
KeywordsIntuitionComputer scienceBusiness intelligenceProcess managementKey (lock)Knowledge managementBusiness decision mappingBusiness ruleTask (project management)Artifact-centric business process modelManagement scienceDecision support systemBusiness processData scienceBusiness process modelingBusinessArtificial intelligenceEngineeringWork in processSystems engineeringMarketing

Abstract

fetched live from OpenAlex

In many enterprises and other types of organizations, decision making is both a crucial and a challenging task. Despite their importance, many decisions are still made based on experience and intuition rather than on evidence supported by rigorous approaches. Decisions are often made this way because of lack of data, unknown relationships between data and goals, conflicting goals, and poorly understood risks. This research presents a goal-oriented, business intelligence-supported methodology for decision making. The methodology, which is iterative, allows enterprises to begin with limited data, discover required data to build their models, capture stakeholders goals, and model threats, opportunities, and their impact. It also enables the aggregation of Key Performance Indicators and their integration into goal models. The tool-supported methodology and its models aim to enhance the user’s experience with common business intelligence applications. Managers can monitor the impact of decisions on the organization's goals and improve both decision models and business processes. The approach is illustrated and evaluated through a retail business scenario, from which several lessons were learned. One key lesson is that once an organization has a goal model, data can be added iteratively. The example, tool support, and lessons suggest the feasibility of the methodology.

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.030
metaresearch head score (Gemma)0.021
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.030
Threshold uncertainty score0.158

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0300.021
Meta-epidemiology (narrow)0.0020.001
Meta-epidemiology (broad)0.0010.003
Bibliometrics0.0050.005
Science and technology studies0.0030.006
Scholarly communication0.0110.008
Open science0.0050.005
Research integrity0.0030.004
Insufficient payload (model declined to judge)0.0030.001

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.103
GPT teacher head0.362
Teacher spread0.259 · 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 designTheoretical or conceptual
Domainnot available
GenreMethods

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

Citations31
Published2014
Admission routes2
Has abstractyes

Explore more

Same venueDecision AnalyticsSame topicBig Data and Business IntelligenceFrench-language works237,207