Determining appropriate data analytics for transformer health monitoring
Bibliographic record
Abstract
Transformers are vital assets for the safe, reliable and cost-effective operation of nuclear power plants. The unexpected failure of a transformer can lead to different consequences ranging from a lack of export capability, with the corresponding economic penalties, to catastrophic failure, with the associated health, safety and economic effects. Condition monitoring techniques examine the health of the transformer periodically, with the aim to identify early indicators of anomalies. However, many transformer failures occur because diagnostic and monitoring models do not identify degraded conditions in time. Therefore, health monitoring is an essential component to transformer lifecycle management. Existing tools for transformer health monitoring use traditional dissolved gas analysis based diagnostics techniques. With the advance of prognostics and health management (PHM) applications, we can enhance traditional transformer health monitoring techniques using PHM analytics. The design of an appropriate data analytics system requires a multi-stage design process including: (i) specification of engineering requirements; (ii) characterization of existing data sources and analytics to identify complementary techniques; (iii) development of the functional specification of the analytics suite to formalize its behavior, and finally (iv) deployment, validation, and verification of the functional requirements in the final platform. Accordingly, in this paper we propose a transformer analytics suite which incorporates anomaly detection, diagnostics, and prognostics modules in order to complement existing tools for transformer health monitoring.
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.003 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.004 | 0.005 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.004 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".