MétaCan
Menu
Back to cohort
Record W4404932772 · doi:10.2514/1.i011331

Clarifying Ambiguity in Aircraft Regulatory Documentation: A Review of Modeling Approaches

2024· review· en· W4404932772 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueJournal of Aerospace Information Systems · 2024
Typereview
Languageen
FieldEngineering
TopicSafety Systems Engineering in Autonomy
Canadian institutionsRoyal Military College of CanadaConcordia University
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsDocumentationAmbiguityAeronauticsComputer scienceSystems engineeringEngineeringProgramming language

Abstract

fetched live from OpenAlex

Aircraft design and development programs must comply with many certification requirements described in natural language provided in a complex collection of document-based regulations and associated guidance material. As a result, individual design organizations develop internal processes detailing how regulatory requirements should be met within their aircraft design programs. Subject matter experts develop these processes, which are subjective interpretations of the regulations and can vary significantly between development programs and organizations. Model-based approaches are increasingly used to manage the complexity of the aircraft design and development process. Regulatory documentation, however, remains document-based, making certification a costly component of the design process. This paper reviews three approaches to modeling regulatory documentation of process mapping, ontological modeling, and Unified Modeling Language (UML) and compares their utility in the context of reducing ambiguity, reflecting complexity, and leveraging subject matter expertise. A case study is presented using the advisory circular AC 21.101-1B Establishing the Certification Basis of Changed Aeronautical Products to illustrate the comparison.

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.003
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Systematic review · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.522
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0030.001
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.002
Open science0.0000.000
Research integrity0.0000.001
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.058
GPT teacher head0.288
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