Every cold start a flexible plant absorbs costs far more than the fuel burned to ramp up. Thermal cycling drives low-cycle fatigue into rotors, headers, and HRSG tubing at a rate calendar-based maintenance schedules were never built to track. Plants running two-shifting or load-following duty accumulate equivalent operating hours three to four times faster than their run-hour counters suggest, which means fixed-interval PMs either inspect too late or waste outage time on components nowhere near their fatigue limit. Start tracking cycling-adjusted maintenance free with Oxmaint and replace the guesswork with a schedule built around the stress your assets actually absorb.
Why Calendar-Based PM Fails on a Cycling Unit
Fixed-Interval Schedule
TriggerCalendar date or raw run hours
Cold start impactNot counted separately
HP rotor inspectionSet at OEM baseload interval
ResultCracking found after the interval, not before
Equivalent Operating Hours
TriggerWeighted EOH counter per asset
Cold start impactCounted at configurable multiplier
HP rotor inspectionTriggers when EOH threshold is reached
ResultInspection lands ahead of the fatigue curve
What a Single Cold Start Actually Costs Your Rotor
100–200x
Run hours of equivalent fatigue damage inflicted by one cold start on hot-section components
3–4x
Faster EOH accumulation than run hours suggest on renewable-heavy, cycling grids
3–5x
Higher thermal fatigue rate in cycling HRSGs compared to baseload steam generators
Stop Scheduling Inspections by the Calendar
Oxmaint accumulates equivalent operating hours per asset using configurable multipliers for cold starts, warm starts, hot starts, and trips, then triggers your PM schedule against that counter instead of wall-clock time. Every cycling event your plant absorbs gets logged where it can actually change a maintenance date.
The Cycling Damage Map: Where Stress Lands First
Gas Turbine Hot Section
Combustor cans and transition pieces absorb the steepest temperature ramp on every start, making them the first component class to show cycling-driven wear ahead of baseload-rated intervals.
HP Turbine Rotor & Bore
Low-cycle fatigue accumulates at keyways and bore surfaces with every start-stop event, and a longer stop time before the next start increases the thermal stress generated at the following startup.
HRSG Headers & Tubing
HRSGs have no constant fire source to stabilize metal temperature, so every start, ramp, or trip imposes a thermal transient that fixed-interval boiler PM programs were never designed to catch.
Steam Chemistry & Economizer
Two-shifting challenges the plant's ability to hold water chemistry steady, accelerating corrosion-fatigue at economizer tubing bends, tees, and downstream of flow restrictors.
Building a Cycling-Adjusted Maintenance Schedule in Four Steps
1
Classify Every Start Type
Separate cold starts, warm starts, hot starts, and trips in your historical log, since each imposes a different magnitude of thermal stress on rotor and header components.
2
Assign EOH Multipliers
Use OEM guidance as a starting multiplier per start type, then refine it against your own inspection findings as plant-specific experience accumulates.
3
Run the EOH Counter Per Asset
Accumulate weighted EOH continuously against each rotor, header, and HRSG section rather than a single plant-wide hour total.
4
Re-Trigger PM Against EOH Thresholds
Move HP turbine inspections, HRSG tube thickness checks, and chemistry audits onto EOH-based triggers so the work order fires when fatigue damage warrants it, not when the calendar does.
Frequently Asked Questions
What is the difference between run hours and equivalent operating hours?
Run hours simply count the clock time a unit operates, while equivalent operating hours weight that time against the fatigue damage actually inflicted, applying multipliers to cold starts, warm starts, hot starts, and trips. A unit with 6,000 run hours but 200 cold starts a year can accumulate far more equivalent fatigue exposure than a baseload unit running continuously for the same period. See how Oxmaint calculates EOH per asset using your own start classification and multiplier settings.
How often should a cycling combined cycle unit get an HP turbine inspection?
Rather than a fixed calendar interval, the inspection should trigger once the EOH counter for that rotor crosses a threshold informed by OEM stress-life data, since a cycling unit can reach that fatigue exposure in a fraction of the wall-clock time a baseload unit would take. A unit running 200 cold starts a year at a typical multiplier may need that inspection well before three years of calendar time has passed.
Can a CMMS actually track cycling-adjusted maintenance automatically?
Yes, when the platform supports per-asset EOH accumulation rather than a single plant run-hour total. Book a planning session to walk through how multi-asset EOH tracking and outage planning fit your unit's specific cycling profile and start classification data.
Does longer downtime between starts make the next start worse for the rotor?
Yes, because natural cooling during an extended outage lowers the rotor's internal temperature, which increases the thermal stress generated when the unit starts back up and raises the lifetime consumption rate for that single start. This is why start classification needs to account for the preceding outage duration, not just start type alone.
What HRSG components fail first under frequent cycling?
High-pressure superheater headers experience creep-fatigue interaction that is a leading cause of unplanned HRSG outages in cycling combined cycle fleets, while economizer and LP evaporator tubing face accelerated flow-accelerated corrosion at bends and flow restrictors. Tracking cycle counts rather than relying on fixed-interval inspection catches both before they cause a forced outage.
Build the Schedule Your Cycling Profile Actually Demands
Oxmaint links cold start, warm start, hot start, and trip events to per-asset EOH counters and triggers preventive maintenance against fatigue exposure instead of the calendar. Every inspection lands where the stress actually is.
