Combined cycle gas turbine plants lose an average of 12–18 equivalent operating days per year to unplanned outages when maintenance is scheduled by calendar alone. Runtime-based maintenance replaces arbitrary time intervals with actual fired hours, start counts, and thermal cycle data—targeting inspections precisely when turbine components reach their true service limits. Plants that shift to runtime-driven strategies consistently cut forced outage rates by 35% and extend hot gas path intervals by thousands of equivalent operating hours. Sign up for Oxmaint to track fired hours, start counts, and component life across every turbine in your fleet from a single dashboard.
35%
Reduction in forced outage rate with runtime-based scheduling
4,000+
Additional equivalent operating hours between major inspections
$2.8M
Average annual savings per unit from optimized outage timing
Why Calendar-Based Maintenance Fails CCGT Plants
Most combined cycle plants still schedule combustion inspections, hot gas path overhauls, and major inspections at fixed calendar intervals—regardless of how the unit actually operates. A peaking unit with 800 fired hours per year receives the same maintenance schedule as a baseload unit running 7,500 hours. The result is either premature maintenance that wastes budget and availability, or delayed interventions that risk catastrophic turbine damage. Runtime-based strategies eliminate this mismatch by tying every maintenance action to measurable operating parameters that reflect actual component degradation.
Core Runtime Tracking Parameters
A runtime-based strategy depends on tracking the right data continuously. These four parameters form the foundation of every turbine life management program. Oxmaint captures all of them automatically from your plant historian—no spreadsheets, no manual entry. Create your free Oxmaint account and start tracking turbine runtime parameters in minutes.
Runtime Engine — Central tracking of fired hours, starts, trips, and thermal transients
FH
Fired Hours Tracking
Continuous accumulation of actual turbine firing time feeds combustion inspection intervals and hot gas path replacement schedules with precision unavailable from calendar methods.
SC
Start Count Analysis
Each turbine start imposes thermal stress equivalent to multiple fired hours. Factored starts convert cold, warm, and hot starts into equivalent operating hours for accurate life consumption tracking.
TC
Thermal Cycle Monitoring
Trip events, fast ramps, and load swings cause disproportionate component fatigue. Cycle-weighted algorithms adjust maintenance intervals based on actual thermal severity, not just hours.
CL
Component Life Modeling
Individual parts—blades, vanes, transition pieces, combustion liners—each consume life at different rates. Part-level tracking prevents blanket replacements and enables targeted swaps during planned outages.
Key Insight
Factored Hours Change Everything
A single emergency trip on an F-class gas turbine can consume the equivalent of 20 normal fired hours in component life. Plants that track only raw fired hours systematically underestimate degradation on cycling units—leading to blade failures that cost $1.5M–$4M per event. Factored-hour tracking inside a CMMS captures these severity multipliers automatically, giving planners the true picture of remaining component life. Start tracking factored hours in Oxmaint and align your maintenance intervals to real turbine condition.
Runtime Maintenance Intervals for CCGT Major Components
Every gas turbine OEM publishes recommended maintenance intervals based on equivalent operating hours and equivalent starts. The table below consolidates typical intervals for F-class and H-class heavy-duty gas turbines. Actual intervals depend on fuel type, ambient conditions, and operating profile—which is exactly why a CMMS like Oxmaint must track these variables continuously.
+ Lower annual fired hours can extend time between major inspections
+ Revenue from ancillary services and peak pricing offsets cycling costs
− High start counts consume component life at accelerated rates
− Thermal transients increase LCF cracking risk on blades and vanes
− Trip frequency multiplies factored hours, often surprising planners
Track Every Fired Hour, Start, and Trip Automatically
Oxmaint connects to your control system historian and continuously calculates equivalent operating hours, factored starts, and remaining component life—so your planners always know exactly when the next outage should happen. Your maintenance team deserves real-time visibility into turbine health, not spreadsheets that are outdated the moment they are saved.
Transitioning from calendar schedules to runtime-based maintenance requires structured data collection, clear ownership, and a CMMS capable of handling factored-hour calculations. Here is the proven sequence that power generation teams follow.
01
Establish Baseline Operating Data
Extract 3–5 years of historical fired hours, start counts, trip logs, and fuel quality records from your DCS historian. Categorize starts by type and calculate cumulative factored hours for each turbine.
02
Map Component Life Limits to OEM Guidelines
Cross-reference baseline data against OEM-published interval limits for combustion inspections, hot gas path overhauls, and major inspections. Identify units where factored hours exceed recommended thresholds.
03
Configure CMMS for Automated Runtime Tracking
Set up automated data feeds from your plant historian into Oxmaint. Configure factored-hour multipliers for start types, trip events, and fuel penalty factors. Create your Oxmaint account and configure runtime triggers in minutes.
04
Implement Condition Monitoring Overlays
Layer borescope inspection findings, vibration trends, exhaust gas temperature spreads, and compressor performance maps onto runtime data to justify interval extensions or trigger early interventions.
05
Optimize Outage Timing with Predictive Scheduling
Align maintenance windows with seasonal demand troughs, parts availability, and crew scheduling. Use CMMS forecasting to project when each unit hits its next inspection threshold.
CMMS Features That Power Runtime Maintenance
Automated EOH Counters
Real-time equivalent operating hour accumulators pull data directly from plant historians. Factored-hour multipliers for starts, trips, and fuel types update automatically.
Auto-CalculationHistorian Integration
Threshold-Triggered Work Orders
When a turbine reaches 90%, 95%, or 100% of its next inspection interval, the CMMS automatically generates work orders with correct scope, parts list, and labor hours.
Auto Work OrdersConfigurable Alerts
Component Life Dashboards
Visual displays show remaining life for every tracked component—blades, vanes, liners, bearings—across the entire fleet, updated in real time as data flows in.
Fleet VisibilityPart-Level Tracking
Outage Planning Forecasts
Projection algorithms estimate when each unit will hit its next CI, HGP, or MI threshold based on current dispatch patterns for scenario modeling.
Predictive SchedulingScenario Modeling
Critical Runtime Parameters Every CCGT Plant Must Track
Fired Hours (FH)
Total hours with flame present in the combustion section. The primary driver for combustion hardware degradation and coating consumption rates.
Factored Fired Hours (FFH)
Fired hours adjusted by severity multipliers for fuel type, peak firing temperature, water/steam injection, and off-design operation.
Equivalent Starts (ES)
Start events weighted by thermal severity. A cold start after 72+ hours offline carries a higher factor than a hot restart.
Trip Events
Emergency shutdowns impose severe thermal shock. Each trip adds 20x or more factored hours to component life counters.
Exhaust Temp Spread
Variation in exhaust thermocouple readings signals combustion system health—liner damage, nozzle degradation, or crossfire tube failures.
Vibration Amplitude
Bearing vibration trends correlate with rotor balance, alignment, and bearing wear, accelerating degradation beyond normal rates.
Common Runtime Maintenance Mistakes
Ignoring Start-Type Weighting
Treating all starts equally underestimates life consumption on cycling units by 30–50%, leading to blade cracking between inspections.
Configure cold/warm/hot start multipliers in your CMMS and validate against OEM technical letters quarterly.
Tracking Gas Turbine Only
HRSG tube failures and steam turbine seal degradation cause 40% of CCGT forced outages. Tracking only the GT misses half the plant.
Extend runtime triggers to HRSG tube bundles, attemperators, bypass valves, and steam turbine components inside Oxmaint's asset hierarchy.
Spreadsheet-Based Tracking
Manual calculations introduce errors, miss trip events, and become obsolete the moment someone forgets to update them.
Migrate to an automated CMMS with historian integration. Book a demo to see how Oxmaint replaces spreadsheets with live runtime dashboards.
The plants that get runtime maintenance right are the ones that stopped treating the CMMS as a work order system and started treating it as a turbine life management platform. When fired hours, starts, trips, and condition data all live in one place, every outage decision becomes defensible.
— CCGT Fleet Maintenance Director, Independent Power Producer
Move Your CCGT Plant to Runtime-Based Maintenance
Oxmaint gives power generation teams the runtime tracking, automated work orders, component life dashboards, and outage forecasting they need to eliminate calendar-based guesswork and run turbines to their actual service limits—safely and profitably. Stop managing turbine life on spreadsheets that nobody trusts.
What is the difference between fired hours and equivalent operating hours?
Fired hours count only the time the gas turbine has flame present in the combustion section. Equivalent operating hours add factored hours from start events, trips, fuel penalties, and peak firing adjustments to create a composite number that better represents actual component life consumption.
How does a CMMS automate runtime-based maintenance scheduling?
A properly configured CMMS connects to your plant historian via automated data feeds, continuously accumulating fired hours and factored starts. When a component approaches its OEM-defined interval threshold, the system generates work orders with correct inspection scope, parts requirements, and labor estimates. Sign up for Oxmaint to set up automated runtime triggers for every turbine in your fleet.
Can runtime-based maintenance extend intervals beyond OEM recommendations?
Yes, when supported by condition monitoring data. Borescope inspections showing clean coatings, stable exhaust temperature spreads, and healthy vibration trends can justify extensions of 10–20%. The CMMS must document the condition data supporting any extension for regulatory compliance.
What runtime data should we track for the HRSG and steam turbine?
For the HRSG, track thermal cycles, attemperation spray hours, and tube wall thickness trends. For the steam turbine, track operating hours, start cycles, and hours at off-design conditions. All parameters should feed into your CMMS alongside gas turbine data.
How quickly can we transition from calendar to runtime-based maintenance?
Most CCGT plants complete the transition in 8–12 weeks. Extracting historical data and configuring CMMS runtime counters takes 2–3 weeks. Validation runs 4–6 weeks. Full cutover follows once data accuracy is confirmed. Book a demo to get a customized transition timeline.
