Reliability engineers rarely lose a combined cycle plant's efficiency to one dramatic event — they lose it a fraction of a percentage point at a time. A one degree rise in turbine inlet temperature deviation here, a 15°F stack temperature creep there, a compressor pressure ratio that drifts 2% below design, and by the time the monthly heat rate report lands on your desk, the plant has been quietly burning 2 to 5% more fuel per megawatt for weeks without a single alarm firing. None of these deviations individually crosses a trip threshold, which is exactly why they survive so long inside a control room that is built to watch for hard limits, not slow drift. Reliability teams working to close this gap are finding it useful to book a demo and see what their last quarter of heat rate data would have flagged in week one instead of month three.
Recover the 2–5% Heat Rate Loss Hiding in Everyday Operations
iFactory tracks turbine inlet temperature, HRSG effectiveness, steam cycle efficiency, and heat rate deviation together in real time — so performance loss shows up as a trend, not a surprise at month-end.
The Five Points Where a Combined Cycle Plant Loses Efficiency Without Anyone Noticing
Combined cycle efficiency is a chain — gas turbine topping cycle, HRSG heat transfer, and steam turbine bottoming cycle all feeding into one heat rate number. A loss anywhere in that chain shows up in the same place: a higher heat rate at the same load. The five points below account for most of the recoverable efficiency loss reliability teams find once they start trending continuously instead of monthly.
TIT is the single strongest lever on combined cycle efficiency — both gas turbine and steam turbine output rise with it, but the rate of gain flattens at higher temperatures while heat loss keeps climbing. A control system running a few degrees below its optimal firing curve, often to protect margin after a sensor recalibration, quietly gives up output and efficiency that never shows up as an alarm.
Gas turbines are designed for one specific ambient temperature, pressure, and humidity profile, and every deviation from that design point costs efficiency even when power output looks unaffected. Heat rate rises as ambient temperature falls even though output increases, which is counterintuitive enough that many operators misread the trend entirely.
As HRSG tube surfaces foul and pinch and approach points widen, heat transfer effectiveness falls and stack temperature rises — exhaust heat that should have become steam instead goes up the stack. This degradation is gradual and almost invisible on a single shift's data, but compounds significantly over an operating season.
Condenser backpressure creep, steam path seal wear, and feedwater heater fouling erode the bottoming cycle independently of anything happening on the gas turbine side, and because the steam turbine team and gas turbine team often track different reports, this loss category is the easiest to miss entirely.
Fouling and erosion on early compressor stages reduce pressure ratio, which reduces both power output and thermal efficiency together — a double loss that is easy to attribute to ambient conditions unless it is trended against a clean baseline built from the unit's own history.
What Continuous Tracking Typically Recovers Per Loss Category
The recoverable value in each loss category depends on how early it is caught. Deviations trended daily and corrected within a shift recover far more value than the same deviation caught three weeks later on a monthly report.
| Loss Category | Typical Undetected Impact | Primary Tracked Signal | Correction Window |
|---|---|---|---|
| Turbine inlet temperature drift | 0.5–1.5% heat rate | TIT vs firing curve deviation | Same shift |
| HRSG pinch/approach creep | 1–3% HRSG effectiveness | Stack temperature, pinch trend | Days to weeks |
| Condenser backpressure creep | 0.5–2% cycle efficiency | Backpressure vs design curve | Weeks |
| Compressor pressure ratio decay | 1–3% output and efficiency | Pressure ratio, polytropic efficiency | Scheduled wash window |
Find Out Which of the Five Leaks Is Costing You the Most Right Now
A short walkthrough of your DCS historian data against these five categories usually surfaces at least one recoverable loss most teams didn't know was active.
Our monthly heat rate test always told us we had lost efficiency, but never when it started or which unit caused it. Once we had daily trending on TIT deviation and HRSG pinch point side by side, we found a stack temperature creep on unit one that had been building for six weeks and nobody had connected it to the heat rate number, because the two reports lived in different spreadsheets owned by different teams.
Combined Cycle Performance Optimization — Frequently Asked Questions
Stop Finding Efficiency Loss in a Monthly Report
iFactory turns turbine inlet temperature, HRSG effectiveness, and steam cycle data your plant already produces into a daily heat rate breakdown — so a 2% loss gets caught this week, not next quarter.
