A 500 MW gas turbine that takes 18 hours to repair instead of 6 doesn't just cost the difference in labour — it costs 12 additional hours of lost generation revenue at $15,000–$40,000 per hour. A boiler feed pump that fails every 8 months instead of every 24 months doesn't just triple bearing costs — it triples the number of forced outage events, each carrying its own startup risk and thermal stress penalty. MTTR and MTBF are the two metrics that define whether a power plant's maintenance programme is creating reliability or just responding to breakdowns. Yet most plants track these numbers reactively — calculating them from historical data that is already months old and too aggregated to drive specific improvement actions. iFactory measures MTTR and MTBF per equipment, per failure mode, per craft — in real time — and connects each metric to the specific maintenance actions, spare parts decisions, and workforce allocations that move the number. Book a free MTTR/MTBF baseline assessment for your plant.
Quick Answer
iFactory tracks MTTR and MTBF per equipment, per failure mode, and per maintenance craft — not as plant-wide averages but as actionable metrics tied to specific improvement levers. AI-driven root cause analysis identifies why MTTR is high (parts delays, craft skill gaps, diagnostic time) and why MTBF is low (inadequate PM intervals, wrong lubrication, operating condition changes). Average result across deployed plants: 38% MTTR reduction within 6 months, 2.1x MTBF improvement on targeted critical equipment within 12 months.
Why Plant-Wide MTTR and MTBF Averages Hide the Real Problems
Most power plants report MTTR and MTBF as single numbers — "our plant MTTR is 6.2 hours" or "MTBF for rotating equipment is 14 months." These averages are mathematically correct and operationally useless. They mask the specific equipment, failure modes, and maintenance process failures that actually drive downtime.
Plant-wide MTTR average — updated quarterly
MTBF by equipment class (all pumps, all fans)
No breakdown by failure mode or root cause
No link between MTTR drivers and specific actions
Historical only — no predictive trajectory
MTTR per equipment, per failure mode, per craft — real-time
MTBF per component with age-adjusted failure rate curves
MTTR decomposition: diagnostic time, parts wait, active repair, testing
Each metric linked to the specific lever that improves it
Predictive trajectory — MTBF trend forecasted from condition data
MTTR/MTBF Assessment
Know Exactly Where Your Downtime Hours Go — and Which Actions Recover Them
iFactory decomposes your MTTR into its component time blocks and your MTBF into its failure mode drivers — so every improvement action targets the specific bottleneck that matters most.
2.1x
Avg MTBF Improvement
MTTR Decomposition — Where Repair Time Actually Goes
MTTR is not a single number — it is the sum of four distinct time blocks, each with its own improvement lever. iFactory measures each block separately so improvement efforts target the actual bottleneck, not the average. Talk to an expert about MTTR decomposition for your plant.
Time from fault detection to confirmed root cause. In most plants, this is the largest MTTR component — technicians troubleshooting without data, running multiple diagnostic tests, waiting for engineering support.
iFactory lever: AI fault diagnostics provide probable root cause and recommended diagnostic sequence before the technician arrives at the equipment — reducing diagnostic time by 40–60%.
Time waiting for the correct spare part — either retrieving from stores, confirming the right part number, or emergency procurement when the part is not in stock.
iFactory lever: RUL-linked spare parts procurement ensures parts are on the shelf before the failure occurs. NLP work orders automatically check stock at creation — zero parts-wait for predicted failures.
Hands-on wrench time — the actual physical repair. This is typically the smallest component of MTTR, yet it's the only one most plants measure or attempt to improve.
iFactory lever: Digital work instructions with equipment-specific procedures, torque specs, and clearance values — reducing rework from incorrect assembly. Craft skill gap analysis identifies where targeted training reduces active repair time.
T4 — Testing & Return to Service
Post-repair testing, vibration checks, operational verification, and return-to-service procedures. Delays here are often caused by waiting for operations staff or test equipment.
iFactory lever: Automated post-repair vibration and temperature baseline comparison — confirming repair quality against pre-fault condition data without waiting for a vibration analyst to attend.
MTBF Improvement — The Five Failure Mode Drivers iFactory Targets
MTBF doesn't improve by doing more maintenance — it improves by doing the right maintenance at the right time on the equipment that is actually degrading. iFactory identifies the specific failure mode drivers that are shortening MTBF for each critical asset and recommends targeted interventions.
01
Inadequate PM Intervals
PM schedules based on OEM recommendations or calendar time rather than actual equipment condition. A bearing replaced every 12 months may fail at 9 months because operating conditions (temperature, load, contamination) differ from OEM assumptions.
iFactory adjusts PM intervals from condition data — extending intervals when equipment is healthy, shortening when degradation is detected.
02
Repeat Failures — Same Root Cause
The same bearing fails on the same pump every 6–8 months because the root cause (misalignment, contaminated lubrication, incorrect bearing specification) is never addressed — only the symptom is repaired each time.
iFactory's failure pattern recognition identifies repeat failures per asset and triggers root cause investigation when MTBF falls below threshold for any equipment-failure mode combination.
03
Operating Condition Changes
Equipment MTBF drops after operational changes — increased load, different fuel quality, seasonal temperature variation — that the maintenance programme hasn't accounted for. The PM schedule stays the same while the equipment operates harder.
iFactory correlates failure rates with operating parameters — flagging when load, temperature, or process changes require adjusted maintenance strategies.
04
Age-Related Degradation Not Tracked
Equipment reliability follows a bathtub curve — but most plants don't track where each asset sits on that curve. A 15-year-old gas turbine combustion system needs fundamentally different maintenance than the same system at 5 years.
iFactory models age-adjusted failure rate curves per equipment class — recommending maintenance strategy changes as equipment transitions from useful life to wear-out phase.
05
Maintenance-Induced Failures
10–15% of failures in power plants are introduced during maintenance — incorrect reassembly, contamination during oil changes, overtorqued fasteners, or damage during inspection. These failures are invisible in standard MTBF reporting because they look like normal equipment failures.
iFactory tracks MTBF for the period immediately following each PM or corrective action — identifying maintenance activities that consistently reduce MTBF rather than improve it.
MTTR & MTBF Improvement Timeline
The timeline below shows the typical MTTR and MTBF trajectory across iFactory's four deployment phases — based on measured outcomes across deployed power plant sites.
Phase 1
Baseline & Decomposition
Weeks 1–4
Baseline established. MTTR decomposed into T1–T4 per equipment. MTBF drivers identified per critical asset. No improvement yet — measurement only.
Phase 2
Quick Wins — Diagnostic & Parts
Months 2–3
AI diagnostics reduce T1 by 40%. RUL-linked parts procurement eliminates T2 for predicted failures. Repeat failure investigations launched for top 10 worst-MTBF assets.
Phase 3
Root Cause & PM Optimisation
Months 4–6
Root causes addressed for top repeat failures. PM intervals adjusted from condition data. Maintenance-induced failure tracking activated. MTBF improvement accelerates as systemic issues are resolved.
Phase 4
Continuous Optimisation
Month 7+
Dynamic MTTR and MTBF targets per equipment. Age-adjusted failure curves operational. Craft skill gaps closed through targeted training. Continuous improvement cycle self-sustaining.
Platform Capability Comparison — MTTR/MTBF Analytics
SAP PM, IBM Maximo, and GE APM calculate MTTR and MTBF from work order history. iFactory differentiates on real-time MTTR decomposition, failure mode-level MTBF tracking, AI-driven root cause linkage, and predictive MTBF trajectory modelling — capabilities that require predictive analytics integration, not retrospective reporting. Book a comparison demo.
| Capability |
iFactory |
SAP PM |
IBM Maximo |
GE APM |
Generic CMMS |
| MTTR Analytics |
| MTTR decomposition (T1–T4 time blocks) |
Per equipment, real-time |
Total MTTR only |
Manual breakdown |
Total MTTR only |
Total MTTR only |
| AI diagnostic time reduction |
Fault diagnosis before arrival |
Not available |
Not available |
Condition alerts only |
Not available |
| Parts-wait time tracking per WO |
Linked to inventory system |
MRP reporting |
Materials reporting |
Not tracked |
Not tracked |
| MTBF Analytics |
| MTBF per failure mode (not just per asset) |
Per component + failure mode |
Per equipment class |
Per equipment class |
Per equipment class |
Plant-wide only |
| Repeat failure pattern detection |
Auto-flagged + RCA trigger |
Manual analysis |
Report-based |
Alert-based |
Not available |
| Age-adjusted failure rate curves |
Per equipment age cohort |
Not available |
Not available |
Basic degradation models |
Not available |
| Improvement Tracking |
| Maintenance-induced failure identification |
Post-PM MTBF tracking |
Not available |
Not available |
Not available |
Not available |
| Predictive MTBF trajectory |
RUL-based forecasting |
Historical only |
Historical only |
Condition-based estimates |
Historical only |
Based on publicly available product documentation as of Q1 2025. Verify current capabilities with each vendor before procurement decisions.
Measured Outcomes Across Deployed Plants
38%
MTTR Reduction Within 6 Months
2.1x
MTBF Improvement on Targeted Equipment
52%
Diagnostic Time Reduction (T1)
Zero
Parts-Wait Delays for Predicted Failures
68%
Repeat Failures Eliminated via RCA
Real-Time
MTTR/MTBF Tracking Per Equipment
Reliability Engineering
Your MTTR Is High Because You're Measuring the Wrong Thing. Your MTBF Is Low Because You're Fixing Symptoms.
iFactory decomposes MTTR into its four time blocks and MTBF into its five failure mode drivers — so every improvement action targets the specific bottleneck driving your downtime.
52%
Diagnostic Time Saved
68%
Repeat Failures Eliminated
From the Field
"We had been reporting plant-wide MTTR of 6 hours for years and nobody could explain why availability wasn't improving. iFactory decomposed the number and showed us that 42% of our MTTR was diagnostic time — technicians troubleshooting without sensor data. Another 30% was parts wait time because our storeroom accuracy was 71%. Active repair was only 18% of total MTTR. Once we knew where the time was going, improvement was straightforward. Our MTTR on critical rotating equipment dropped from 8.4 hours to 3.8 hours in five months — and it's still coming down."
Reliability Engineering Manager
1,200 MW Gas-Fired Combined Cycle Plant — Gulf Coast USA
Frequently Asked Questions
QHow does iFactory calculate MTTR decomposition without timestamped work order phases in our existing CMMS?
iFactory uses a combination of work order status timestamps, technician mobile app check-in/check-out data, and parts issue transaction times to reconstruct the T1–T4 breakdown. Where gaps exist, the system uses statistical estimation from similar work orders and refines over time as more data is captured through the mobile workflow.
Book a scoping call to assess your current data availability.
QCan iFactory track MTBF for equipment that has only failed once or twice — limited failure history?
Yes. For equipment with limited failure history, iFactory uses fleet-level failure data from similar equipment types across your portfolio and industry benchmarks to establish initial MTBF estimates. As condition monitoring data accumulates, the MTBF model transitions from fleet-based to equipment-specific — typically within 6–12 months of sensor data.
QHow does iFactory distinguish maintenance-induced failures from normal wear-out failures?
iFactory tracks a "post-maintenance MTBF window" — monitoring equipment condition and failure events in the 30–90 day period following each maintenance intervention. If MTBF in the post-maintenance window is statistically shorter than the pre-maintenance baseline, the system flags a potential maintenance-induced failure and triggers investigation.
See this analysis in a live demo.
QWe already have an OEM digital twin that provides MTBF estimates — what does iFactory add?
OEM digital twins model design-condition MTBF based on operating parameters. iFactory adds actual failure history, maintenance quality data, parts consumption patterns, and technician-reported observations — producing MTBF estimates that reflect your plant's real-world conditions, not the OEM's design assumptions. The two data sources are complementary; iFactory can ingest OEM digital twin outputs as additional input.
Continue Reading
Decompose Your MTTR. Target Your MTBF Drivers. Make Every Improvement Action Measurable.
iFactory tracks MTTR and MTBF per equipment, per failure mode, and per craft — connecting every metric to the specific maintenance action, spare parts decision, and workforce allocation that moves the number.
MTTR Decomposition (T1–T4)
Failure Mode MTBF Tracking
Repeat Failure Detection
Age-Adjusted Failure Curves
Maintenance-Induced Failure ID
