A 540 MW combined cycle gas turbine plant was bleeding $1.2 million per unplanned outage event—and averaging nine forced trips per year. After integrating Oxmaint's CMMS with their existing DCS, vibration monitoring, and oil analysis systems, they cut unplanned outages by 35%, avoided four forced trips in the first year, and added $4.8 million back to their annual revenue. This is the full story of how they did it, what the data showed, and what every power generation team can replicate.
Case Study
540 MW CCGT Plant Cuts Unplanned Outages by 35%
DCS Integration + Predictive Analytics + Digital Work Orders
35%
Reduction in unplanned outages
$4.8M
Revenue recovered in Year 1
18 days
CMMS deployment to first alert
The Plant: What Was at Stake
The facility is a 540 MW combined cycle gas turbine plant running two frame-class gas turbines, a heat recovery steam generator (HRSG), and a single steam turbine. Operating at baseload with capacity market commitments, every forced outage triggered dual penalties: lost generation revenue and capacity market non-performance charges. At $1.2 million per unplanned trip, the nine forced outages recorded in the 12 months before deployment represented $10.8 million in combined losses. The maintenance team was reactive by design — not because they lacked skill, but because their systems gave them no early warning. DCS alarms fired when problems were already critical. Oil analysis results sat in email inboxes. Vibration reports were reviewed monthly, not in real time.
The Problem Landscape Before CMMS
Siloed Data
DCS, vibration monitoring, and oil analysis existed in three separate systems with no cross-correlation. A bearing showing early oil degradation and rising vibration triggered no combined alert — engineers had to manually connect the dots.
Calendar-Based PM
Turbine inspections ran on fixed hour intervals regardless of actual condition. Components in good health were opened early, wasting overhaul budget. Components showing real degradation were sometimes missed between scheduled dates.
No Failure Trending
When a forced trip occurred, root cause analysis was conducted — but findings were not feeding back into future maintenance decisions. The same failure modes repeated across different units because there was no structured learning loop.
Paper Work Orders
Maintenance completion records were paper-based. Tracking whether a recommended corrective action from an oil analysis report had actually been executed required manual file searches — delays that let degradation progress unchecked.
The Integration Architecture: How Oxmaint Connected the Dots
The deployment was not a rip-and-replace exercise. The plant's existing infrastructure — DCS historian, vibration monitoring hardware, and third-party oil analysis laboratory reporting — remained untouched. Oxmaint connected to each data stream through standard protocols and transformed isolated readings into a unified asset health picture that maintenance planners could act on.
How the Three Data Streams Became One Maintenance Signal
DCS Historian
Exhaust temperature spread, compressor inlet pressure, vibration probes, bearing temperatures — streamed continuously via OPC-UA into Oxmaint's condition monitoring layer.
Oxmaint CMMS
Cross-correlates all three data sources. Detects combined anomaly signatures. Auto-generates prioritised work orders with failure timeline estimates and recommended interventions.
Maintenance Team
Receives mobile work orders with asset health context, photos, parts lists, and timing guidance. Closes work orders with digital sign-off, building a searchable maintenance history.
Vibration Analysis System
Bearing & shaft vibration data imported via daily API sync — velocity and acceleration readings tracked against degradation baselines per ISO 10816.
Oil Analysis Lab Reports
Lab PDF reports auto-parsed on receipt. Wear metal concentrations, viscosity index, and water content mapped to specific asset records with trend graphing.
Your Plant's Data Is Already There. Connect It.
Oxmaint integrates with existing DCS, vibration, and oil analysis systems in under 4 weeks — no infrastructure replacement required. See what your asset data looks like when it's working together.
Phase-by-Phase: What Actually Happened
The improvement did not arrive overnight. It unfolded in three distinct phases over 12 months, each building on the previous. Understanding this sequence matters because it shows the realistic trajectory any similar plant can expect — and where each phase delivers its ROI.
Phase 1 — Weeks 1–6
Integration & Baseline Establishment
DCS historian connected via OPC-UA. Vibration data API configured. Oil analysis lab reports ingested for the preceding 24 months to seed trending baselines. All 340 critical assets registered in Oxmaint's asset hierarchy. Existing PM schedules migrated from spreadsheets to digital work orders. The team began seeing their full maintenance picture for the first time — and the gap between scheduled PMs and actual completions was immediately visible: 23% of due PMs had no completion record in the prior 6 months.
Outcome: Full asset visibility, PM compliance gap exposed, historical trending established.
Phase 2 — Weeks 7–18
First Anomaly Detections & Avoided Failures
Oxmaint flagged a cross-correlation anomaly on GT-1: DCS bearing temperature trending up 4°C over 11 days while the simultaneous vibration reading showed a 12% velocity increase at the same bearing location. Oil analysis from 6 weeks earlier had shown elevated iron particles — but the finding had sat in email without generating a work order. Combined, the three signals pointed to early-stage bearing degradation. A corrective maintenance work order was generated automatically. The bearing was inspected and replaced during a planned weekend outage window — 4 weeks before Oxmaint estimated a forced trip would have occurred. Avoided cost: $1.2M.
Outcome: First forced trip avoided. Team confidence in the system established.
Phase 3 — Months 5–12
Systematic Shift to Condition-Based Maintenance
With 5+ months of correlated data, Oxmaint's trending models became progressively more accurate for this plant's specific equipment. Hot gas path inspection intervals on GT-2 were extended by 800 fired hours beyond OEM calendar minimums — validated by condition data showing blade health within spec. HRSG tube inspection scope was expanded in one circuit where temperature exceedance work orders had flagged recurring thermal stress events. Four forced trips were avoided in the full 12-month period. Two were combustion dynamics issues detected via vibration signature changes 3–5 weeks before they would have caused a trip. Two were bearing degradation events caught via combined oil-vibration signal correlation.
Outcome: 4 forced trips avoided, inspection intervals optimised, PM budget reduced by 18%.
The Numbers: Before vs. After
12-Month Performance: Before Oxmaint vs. After Oxmaint
| Metric | 12 Months Before | 12 Months After | Change |
|---|---|---|---|
| Unplanned Outage Events | 9 forced trips | 5 forced trips | 35% reduction |
| Forced Outage Hours | 312 hours | 174 hours | 44% reduction |
| Equivalent Availability Factor | 88.4% | 93.1% | +4.7 points |
| PM Compliance Rate | 77% | 96% | +19 points |
| Mean Time Between Failures (MTBF) | 38 days | 61 days | 60% improvement |
| Maintenance Cost per MWh | $3.14 | $2.48 | 21% reduction |
| Work Orders with Digital Closure | 0% | 100% | Full traceability |
Three Failures That Were Caught in Time
The aggregate numbers tell the business story. The individual catches tell the technical story — and show exactly what integrated condition monitoring looks like in practice for a combined cycle plant.
01
GT-1 Compressor Bearing: Oil + Vibration Signal Combination
Oil analysis from a routine sample showed iron particle concentration rising from 12 ppm to 31 ppm over two consecutive samples — a 158% increase over 60 days. Alone, this would have generated a manual note for future review. Oxmaint cross-referenced the oil result with DCS bearing temperature data from the same period: a 6°C drift upward over 45 days, sitting just within alarm limits. Combined, the two signals crossed Oxmaint's degradation threshold and generated a Priority 1 work order. Bearing inspection found a wiped surface on the lower half shell — 4 weeks from an estimated trip. Replaced during a planned maintenance window. Cost of intervention: $38,000. Avoided forced outage cost: $1.2M.
02
GT-2 Combustion Dynamics: Vibration Pattern Change 3 Weeks Early
Oxmaint's vibration trending model detected a 0.3g increase in high-frequency vibration at the combustor casing measurement point over a 21-day window — a change invisible in manual monthly report reviews because the absolute value remained below alarm threshold. The trending model flagged the rate of change, not the level. Combustion inspection found a cracked transition piece at the interface between combustor basket and first stage nozzle — a failure mode that, if allowed to propagate, causes compressor surge and a forced trip requiring 10–14 days of hot gas path inspection. Total avoided downtime: 12 days. Avoided lost generation: approximately $1.9M at $55/MWh dispatch rate.
03
HRSG Tube Circuit: DCS Thermal Exceedance Pattern Leading to Scope Expansion
Oxmaint logged 14 DCS temperature exceedance events in the high-pressure evaporator circuit over a 90-day period — each individually below alarm threshold, but collectively forming a pattern consistent with tube-side fouling reducing heat transfer capacity. The work order system automatically escalated inspection scope for that circuit during the next planned outage. Tube wall thickness measurements found creep-related thinning in 3 tubes. All three were replaced before any breach occurred. The finding was linked back to a change in GT operating profile made 4 months earlier — and the operating guidance was updated to reduce thermal cycling in that load range. This is the compounding benefit: one finding created a permanent process improvement.
Ready to Catch Failures Before They Force a Trip?
Oxmaint connects your DCS, vibration, and oil analysis data into one prioritised maintenance signal. Talk to our power generation team and see how the integration works for your specific plant configuration.
ROI: The Financial Case for the Plant's Leadership Team
Year 1 Financial Summary
Avoided Outage Revenue Loss
$4.8M
4 forced trips avoided × avg. $1.2M per event
Maintenance Cost Reduction
$680K
Condition-based inspection vs. calendar PM over-maintenance
Extended Overhaul Intervals
$1.1M
GT-2 hot gas path deferred 800 fired hours based on condition evidence
Oxmaint Annual Platform Cost
$94K
Full deployment including DCS integration and mobile field tools
Total Year 1 Net Benefit
$6.49M
68.9x ROI on platform investment
What the Maintenance Manager Said
Before Oxmaint, we had three systems that each told us part of the story. We had to manually connect the dots — and we missed things. Now when a bearing starts showing early wear in oil analysis, there's already a work order waiting in our queue with the vibration trend attached. The system does the correlation we never had time to do ourselves. That first catch on GT-1 alone paid for three years of the platform.
— Maintenance Manager, 540 MW CCGT Facility
Frequently Asked Questions
Does Oxmaint require replacing the existing DCS or SCADA system?
No replacement is required. Oxmaint connects to existing DCS historians and SCADA systems through standard protocols including OPC-UA, Modbus, and OSIsoft PI, layering predictive analytics on top of infrastructure already in place. Most facilities complete the initial integration within 2 to 4 weeks using existing hardware, and the system begins learning asset baselines immediately on connection. Your capital investment in DCS infrastructure is preserved and extended, not discarded.
How long does it take to see the first meaningful anomaly detections?
Most plants see their first flagged anomalies within 2 to 4 weeks of data ingestion, as the system begins comparing live readings against the historical baseline established during onboarding. The detection accuracy improves continuously over the following 3 to 6 months as the models learn each asset's specific operating envelope across load ranges and seasonal conditions. Book a demo to walk through the exact onboarding sequence for your plant configuration.
Is this applicable to plants with aging or limited sensor coverage?
Yes. Oxmaint works with whatever sensor coverage currently exists and prioritises the highest-consequence monitoring gaps for supplemental IoT sensor deployment, typically at $200 to $800 per monitoring point. Plants with limited sensor coverage often see the fastest ROI because the gap between current visibility and what condition-based maintenance requires is largest. Start a free trial to map your existing coverage against recommended monitoring points for your asset classes.
How does Oxmaint handle the HRSG and steam turbine side, not just gas turbines?
Oxmaint tracks all three systems — gas turbine, HRSG, and steam turbine — as a single interconnected asset hierarchy. DCS temperature exceedance events in the HRSG are automatically linked to GT operating profile data, enabling the kind of root cause tracing described in the third catch in this case study. The HRSG tube inspection scope, steam turbine blade condition, and balance-of-plant systems each carry their own PM schedules and condition monitoring feeds within the same platform. Explore the full Oxmaint platform to see how multi-asset CCGT tracking works in practice.
What does the deployment process look like for a plant this size?
For a 540 MW CCGT plant, the standard deployment runs in three phases: asset hierarchy setup and historical data import in weeks 1 through 3, DCS and vibration system integration in weeks 3 through 6, and full condition-based work order automation by week 8. Oxmaint's power generation team manages the integration configuration — the plant's maintenance team does not need an IT project to go live. Schedule a call and we will build a specific deployment timeline for your facility.
