When secondary supply temperature sags during heating season, an opened plate heat exchanger often reveals scale and biofilm. This article explains four degradation mechanisms of the heat transfer coefficient K, presents four early-warning criteria (K-ratio decline, narrowing temperature difference, rising plate differential pressure, rising valve opening), and closes with a quick-reference signal table and a six-step governance checklist.

A boiler plant runs at part load for over ninety percent of the year: one unit crawls at low load, two units starve each other, gas consumption per unit of heat stays high, cycling is frequent and low-temperature condensation corrosion accumulates. This article focuses on the core question of group control — how many units to run and how much each carries: the inverted-U efficiency curve of boilers, peaking at eighty-to-ninety percent load ratio and collapsing below thirty with condensation risk; a comparison of three load distribution strategies — equal, master-slave and efficiency-first — with their trade-offs; staging by hysteresis control and load forecasting; three remedies for return water temperature management; the metering data foundation and a six-step implementation checklist. A tertiary hospital retrofit: gas consumption down about nine to twelve percent year on year, start-stop cycles down roughly sixty percent, payback within two heating seasons.

Every heating season, buildings overheat near the plant while far-end rooms stay cold no matter how hard the pumps run — the culprit is usually not the heat source but hydraulic imbalance in the network. This article proceeds through understanding imbalance, three-step diagnosis, balancing commissioning and continuous monitoring: static versus dynamic imbalance and horizontal versus vertical imbalance; a three-step diagnostic method of temperature survey, flow confirmation and pressure verification with a criteria table; the division of labor between digital locking balancing valves and dynamic differential pressure valves, and the commissioning order; and a continuous monitoring architecture with savings verification. A university residential retrofit: room temperature compliance rose from about seventy percent to ninety-seven percent, pump frequency fell from fifty to forty-two hertz, pump electricity dropped by roughly sixteen percent, and heating complaints went to zero.

Most energy monitoring systems track only kilowatt-hours and miss power quality, an invisible source of extra consumption and cost. Harmonics heat transformers and cables for nothing, and a low power factor brings a recurring reactive adjustment penalty. This article proceeds in four parts: reference limits for voltage deviation, harmonic distortion, power factor and three-phase imbalance; how variable-frequency drives and switch-mode supplies generate characteristic harmonics and how harmonics steal energy through eddy-current loss and resonance; the economics of reactive power, the power factor assessment and capacitor bank trade-offs; and a monitoring architecture of circuit-level metering plus edge computing, with common pitfalls. A retrofit case at an industrial park: total harmonic distortion fell from twelve percent to within five percent, monthly average power factor rose from 0.82 to above 0.95, the reactive adjustment charge turned from penalty into reward, and transformer running temperature dropped by more than ten degrees.

Once energy monitoring goes live, alarms are what actually consume the duty team's attention: loose thresholds miss leaks, tight ones flood everyone into apathy. This article designs alarm rules in three tiers. Tier one keeps fixed thresholds for safety alarms but adds three engineering details: deadband and hysteresis against alarm chatter, persistence confirmation so momentary crossings never wake anyone, and prioritization mapping each level to notification channels and response deadlines. Tier two writes calendar and operating knowledge explicitly into time-of-day and mode-based rules, often eliminating over half of false alarms. Tier three uses forecast values as moving thresholds; an alarm condition is written as three parameters - baseline source, bandwidth (start at plus or minus ten to twenty percent) and run length (three to five consecutive points). At one commercial complex chiller plant, this cut monthly false alarms from over forty to single digits and acknowledgement time from two hours to under twenty minutes. The chain matters too: zero-filled gaps are the worst source of phantom crossings, maintenance mode suppresses invalid alarms during service, and dry-contact devices such as the ZYH-WFS water flow switch and the ZYH-100 freeze-protection switch corroborate electrical alarms. Deploy in order: safety thresholds, time-of-day rules, dynamic-baseline pilots; then review false alarms monthly, attach a playbook to every alarm, and clean up unhandled rules quarterly.

Energy monitoring answers what happened; energy forecasting answers what will happen. The payoffs are concrete and tiered: monthly budgets tolerate 5 to 10 percent error while daily dispatch needs 3 to 5 percent. The entry path climbs three model tiers: first, degree-day regression, which condenses weather's influence on consumption into heating degree days (HDD) and cooling degree days (CDD) for a univariate linear regression that typically reaches R-squared above 0.8 on public buildings, with a worked example (18,000 kWh constant, 320 kWh per degree day, R-squared 0.86) generating next month's forecast; second, multivariable regression adding three to five business variables such as occupancy, foot traffic and calendar features, whose coefficient signs must make engineering sense; third, machine learning (gradient-boosted trees, LSTM) which only justifies its complexity in control-grade applications and multi-building portfolio forecasting, evaluated horizontally by MAPE (5 to 10 percent passing on monthly, 3 to 5 percent good). The ceiling of forecast quality sits on the data side: temporal granularity from monthly down to fifteen-minute, interrupted or missing data interpolated or excluded whole months, and metering boundaries kept consistent. Three deployment scenarios: demand warnings, dynamic-threshold anomaly alerts around forecast values, and heating and chiller dispatch scheduling.

Verifying energy retrofit savings often ends in dispute: the contractor announces twenty percent savings while the owner points at a rising utility bill. Consumption fluctuates with weather, business volume and operating hours, and a direct before-after subtraction mixes real savings with external changes. A subtler trap is regression to the mean: retrofits launched after an abnormally high-consumption year will see consumption fall back on its own. The scientific answer is the baseline regression model: fit the relationship between consumption and driving factors such as degree days and business volume using at least twelve months of pre-retrofit data, feed actual post-retrofit weather into the model to compute hypothetical no-retrofit consumption, and the difference between actual and predicted values is the real savings. This article explains the whole-building route of IPMVP, presents three model forms chosen by data availability (single-variable degree-day, multivariable, high-frequency), lists the R-squared and CV-RMSE double thresholds of ASHRAE Guideline 14, organizes a five-step baseline workflow, and warns about three frequent failure points: a too-short baseline period, omitted variables, and construction-period data leaking into baseline or reporting periods.

When an owner asks “is our building's energy use high?” and the vendor answers “we used X ten-thousand kWh last month,” the comparison is meaningless — absolute consumption is not comparable across buildings. What the industry needs is a common ruler: Energy Use Intensity (EUI). This article provides EUI reference ranges and consumption profiles for eleven building types including offices, commercial complexes, hotels, hospitals, schools, libraries, gymnasiums, metro stations and data centers; stresses that benchmarking must first be adjusted for climate zone, functional density and service depth; notes that a high EUI is only a symptom to be decomposed system by system down to equipment-level efficiency; and offers a three-step continuous improvement path of baseline building, benchmarking and anomaly catching. A baseline without a clear caliber is worse than none, and a figure notably below the lower bound should trigger suspicion of under-metering rather than celebration.

At acceptance, every energy monitoring platform shows smooth curves and complete reports, yet three months later the doubts arrive: absurd lighting consumption at two in the morning, a calculated chiller COP close to nine, and a weekend curve missing for a whole day. Eighty percent of such problems trace back to data quality. This article provides actionable cleaning methods: a four-layer funnel for outlier detection covering physical range checks, rate-of-change checks, the boxplot method and the Hampel filter, and energy balance verification; graded imputation strategies by gap length, with interpolation for short gaps, same-period analogy corrected by degree days for medium gaps, and honest missing flags instead of forced patching for long gaps; and a reminder that the number one source of false outliers is sensor drift rather than algorithms. A copy-ready cleaning rules checklist and three daily inspection indicators of completeness, validity and timeliness turn data cleaning from a pre-launch cleanup into a daily routine.