MétaCan
Menu
Back to cohort
Record W169915107

Business process monitoring and alignment: An approach based on the user requirements notation and business intelligence tools

2007· article· en· W169915107 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

VenueWER · 2007
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicBig Data and Business Intelligence
Canadian institutionsOttawa HospitalCarleton UniversityUniversity of Ottawa
Fundersnot available
KeywordsArtifact-centric business process modelBusiness process modelingBusiness Process Model and NotationProcess managementComputer scienceBusiness processBusiness process discoveryProcess (computing)Business ruleProcess modelingBusiness intelligenceBusiness process managementNotationBusiness requirementsKnowledge managementWork in processEngineeringOperations management
DOInot available

Abstract

fetched live from OpenAlex

Monitoring business activities using Business Intelligence (BI) tools is a well-established concept. However, online process monitoring is an emerging area which helps organizations not only plan for future improvements but also change and alter their current ongoing processes before problems happen. In this paper, we explore how monitoring process performance can help evolve process goals and requirements. We elaborate an approach that uses the User Requirements Notation (URN) to model the goals and processes of the organization, and to monitor and align processes against their goals. A BI tool exploiting an underlying data warehouse provides the Key Performance Indicators (KPI) used to measure the satisfaction of goals and process requirements. Feeding this information into the URN modeling tool, we can analyze the consequences of current business activities on desired business goals, which can be used for process and business activity alignment thereafter. We illustrate the approach with a case study from the healthcare sector: a hospital discharge process.

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.567
Threshold uncertainty score0.787

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
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.117
GPT teacher head0.317
Teacher spread0.200 · 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