MétaCan
Menu
Back to cohort

Measurement and Verification of Energy Efficiency Savings in Industrial Facilities: The flaw of using energy intensities to determine savings

2010· article· en· W2149064954 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

VenueEnergy Engineering · 2010
Typearticle
Languageen
FieldEnergy
TopicEnergy Efficiency and Management
Canadian institutionsCybernet Systems Corporation (Canada)
Fundersnot available
KeywordsEfficient energy useEnergy intensityEnergy (signal processing)Energy accountingEnergy engineeringEnvironmental economicsProcess (computing)EngineeringOperations managementEnvironmental scienceAutomotive engineeringComputer scienceEconomicsElectrical engineeringStatisticsMathematics

Abstract

fetched live from OpenAlex

ABSTRACT Energy intensities have widely been used as a key performance indicator to track and report on the overall energy performance of an industrial plant or facility. The same energy intensity figures have then also been used to determine the energy savings over time. Energy managers have used reduction in energy intensities over time to determine energy savings. This is a method that has been widely applied across all types of industries and has worked very well over the last number of years, with the world economy booming and growing each year. However, with the slow-down in the economy, industrial plants suddenly started to experience drops in overall efficiency. All the savings they accrued over these years were “lost,” although no changes were made to the plants and facilities. The energy intensities of the plants started to increase. This article focuses on and describes the flaw of using energy intensities to determine energy efficiency savings. It describes how the physical characteristics of industrial plants are influenced by controllable and uncontrollable energy drivers and how these drivers should be incorporated into the measurement and verification process. The methodology is also applied to a case study.

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.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: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.284
Threshold uncertainty score0.994

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
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.024
GPT teacher head0.199
Teacher spread0.175 · 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