MétaCan
Menu
Back to cohort
Record W4246666722 · doi:10.1109/28.845068

Development of transmission system reliability performance benchmarks

2000· article· en· W4246666722 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

VenueIEEE Transactions on Industry Applications · 2000
Typearticle
Languageen
FieldEngineering
TopicPower System Reliability and Maintenance
Canadian institutionsUniversity of Alberta
Fundersnot available
KeywordsReliability (semiconductor)Reliability engineeringElectricity marketElectricityTransmission systemElectric utilityTransmission (telecommunications)Competition (biology)Risk analysis (engineering)Computer scienceElectric power industryService (business)EngineeringBusinessTelecommunicationsMarketing

Abstract

fetched live from OpenAlex

The reliability of an electric utility transmission system is a measure of its ability to continuously meet the demands of all its customers (i.e., points of delivery). Enhancing the supply reliability is one of planning and design targets of any utility within the constraints of capital investments, intense free-market competition, variable and higher level of customer preferences, and safety and environmental considerations. The utilization of transmission system facilities is changing from its traditional role in this new deregulated era and raising significant concerns about the possible erosion of the reliability of utility transmission facilities. It has been recognized that, with the movement toward a deregulated and competitive electricity market, decisions to improve reliability will be heavily influenced by industrial and commercial customer preferences requiring service level benchmarks to be defined. This paper presents an approach to establish realistic transmission system reliability performance benchmarks that provide a measure against which the different planning and design procedures can be evaluated to assist in achieving the primary objective of providing reliable electricity with competitive rates to utility customers.

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: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.691
Threshold uncertainty score0.693

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.001
Insufficient payload (model declined to judge)0.0010.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.008
GPT teacher head0.203
Teacher spread0.195 · 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