MétaCan
Menu
Back to cohort
Record W2911055565 · doi:10.1109/ieem.2018.8607699

Towards a Knowledge based Support for Risk Engineering When Elaborating Offer in Response to a Customer Demand

2018· article· en· W2911055565 on OpenAlexaff
Rania Ayachi, Delphine Guillon, François Marmier, Élise Vareilles, Michel Aldanondo, Thierry Coudert, Laurent Geneste, Yvan Beauregard

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsÉcole de Technologie Supérieure
FundersAgence Nationale de la Recherche
KeywordsComputer scienceRisk analysis (engineering)Knowledge baseRisk managementKnowledge engineeringCall for bidsKnowledge managementArtificial intelligenceBusinessProcurement

Abstract

fetched live from OpenAlex

This paper deals with the first ideas relevant to a knowledge based support for risk engineering when answering tenders or direct customer demands. Indeed, when an offer is defined, it becomes more and more important to analyze the possibilities of: risks occurrence, their consequences and their potential avoidance. Most of the time if it is done, this analysis is conducted manually thanks to a risk expert. In this paper, we propose to assist the expert with a risk engineering aiding tool that relies on a knowledge base and which allows to define and evaluate: (i) the risk and its probability, (ii) the main risk impacts and (iii) the interests of various corrective and preventive actions (impact and probability reductions). We first detail the problem. Then we identify risk knowledge and risk processing. This allows us proposing a knowledge model relevant to the risk engineering entities and some knowledge retrieval queries to support risk engineering.

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.006
metaresearch head score (Gemma)0.026
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: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.008
Threshold uncertainty score0.030

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0060.026
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.002
Bibliometrics0.0050.003
Science and technology studies0.0010.001
Scholarly communication0.0080.010
Open science0.0040.004
Research integrity0.0040.003
Insufficient payload (model declined to judge)0.0070.004

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.018
GPT teacher head0.295
Teacher spread0.277 · 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

Citations3
Published2018
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Engineering ResearchFrench-language works237,207