MétaCan
Menu
Back to cohort
Record W2135338303 · doi:10.1002/sys.21262

The Applicability of Statistical Process Control to Systems Involving People Processes and Business Rhythms

2013· article· en· W2135338303 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

VenueSystems Engineering · 2013
Typearticle
Languageen
FieldDecision Sciences
TopicAdvanced Statistical Process Monitoring
Canadian institutionsLockheed Martin (Canada)
Fundersnot available
KeywordsControl chartStatistical process controlComputer scienceReliability engineeringProcess (computing)Reliability (semiconductor)Constraint (computer-aided design)Industrial engineeringEngineering

Abstract

fetched live from OpenAlex

ABSTRACT The operation and maintenance (O&M) activities of systems can account for 75% of total lifecycle cost. To effectively manage cost, optimize system “on” time, and mitigate defects/failures during the O&M phase of a system's lifecycle, the application of systems monitoring and control is encouraged. Statistical process control ( SPC ) in general, the control chart specifically, is the most common monitoring approach. The control chart provides alerts with respect to the behavior of systems and processes, as well as changes in process variability. Data applied to control charts is assumed to adhere to a normal distribution, a constraint often satisfied in manufacturing and similar industries where the natural variation in the process or system follows the Gaussian distribution. Systems involving people processes and business rhythms can compromise the normality assumption, reducing the reliability of SPC . Through the application of SPC , this paper proposes a novel approach to monitoring operational systems in the systems engineering O&M phase for the express purpose of reducing high costs by mitigating system discrepancies and uncovering inefficiencies. This paper focuses on processes that require 100% system data sampling due to the operational nature of the system.

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.018
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.924
Threshold uncertainty score0.990

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.018
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0010.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.022
GPT teacher head0.313
Teacher spread0.292 · 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