MétaCan
Menu
Back to cohort
Record W2896702585 · doi:10.2478/mape-2018-0027

Applying the Anticipatory Failure Determination at a Very Early Stage of a System’S Development: Overview and Case Study

2018· article· en· W2896702585 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.

fundA Canadian funder is recorded on the work.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueMultidisciplinary Aspects of Production Engineering · 2018
Typearticle
Languageen
FieldEngineering
TopicTechnology Assessment and Management
Canadian institutionsnot available
FundersIndependent Electricity System OperatorUniwersytet Szczeciński
KeywordsHullProcess (computing)Set (abstract data type)Computer scienceTRIZReliability engineeringSystems engineeringStage (stratigraphy)EngineeringOperations researchIndustrial engineeringArtificial intelligence

Abstract

fetched live from OpenAlex

Abstract Anticipatory Failure Determination (AFD) is a tool used in the TRIZ (Theory of Inventive Problem Solving) methodology. This article introduces its concept and describes the process of AFD in different versions of the method. The article presents the application of the AFD method at a very early state of a system’s development, i.e. its concept formulation stage, which corresponds to a technology readiness level (TRL) equal to 2. The system under analysis is a set of devices used to reduce displacement ship hull resistance. The system was modelled using functional analysis. An analysis of system resources was then carried out. Possible direct, indirect, and accident-related failures were identified. A multi-criteria analysis of the causes of system failures was conducted from which the top 10 potential failures were selected. Observations were made on the applicability of AFD in respect to systems not yet implemented.

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.000
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: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.172
Threshold uncertainty score0.616

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
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.021
GPT teacher head0.261
Teacher spread0.240 · 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