Mechanical System Reliability Engineering

Predicting failures in complex systems composed of multiple subsystems is a core responsibility for reliability engineers, maintenance planners, and logistics teams. Each subsystem within a product or machine exhibits its own failure probability, typically captured as a reliability curve that quantifies the chance of survival over time. By analyzing these subsystem reliability curves, engineers can anticipate potential points of breakdown, plan for spare parts, and proactively schedule maintenance—helping ensure system uptime and avoiding costly unplanned outages. In practical terms, failure prediction leverages both reliability curves and real-world operational data. For any subsystem, such as SYS1, engineers evaluate the probability of failure at specific points along its operational timeline using the complement of reliability: 1 - Re(t). Aggregating this probability across all deployed units—each with its own service hours—yields a data-driven estimate of how many failures to expect within a fleet. This methodology not only supports logistical preparedness but also provides development teams with a reality check, highlighting discrepancies between predicted and observed field behavior and guiding design refinements for enhanced system reliability.

Reliability Engineering is More Than Just MTBF | MDBF – Here’s Why In many projects, I’ve seen MTBF (Mean Time Between Failures) and MDBF (Mean Distance Between Failures) being treated as the benchmark for reliability performance — a convenient number to report and track. But here’s the hard truth MTBF/MDBF often hides more than it reveals. Let me share a real example from a rolling stock project: The Scenario: On paper, the project was performing well — MDBF targets were being met. But in reality, the trains were frequently experiencing failures in: 1. PA/PIS (Passenger Information Systems) 2. Propulsion subsystems Yet these failures didn’t count toward MDBF because they weren’t always classified as service-affecting. 1. Many issues were reset by the onboard staff or flagged as minor — leading to under reporting. 2. As a result, MDBF stayed high, but reliability on the ground suffered — frustrating passengers, operators, and maintainers. The Real Insight: ✅ MDBF only tracks failures that stop or delay the train — not the ones that hurt the passenger experience or stress maintenance staffs. ✅ Frequent low-impact failures, like intermittent PIS screen blackouts or propulsion resets, still degrade trust and increase OPEX. ✅ These issues often stem from design-stage gaps (like interface assumptions or inadequate software logic) and insufficient testing under real conditions. What We Must Do as Reliability Engineers: 1. Stop relying solely on service-affecting MDBF numbers. 2. Integrate RAMS thinking early in the design process — define what reliability means from a functional and user-experience perspective. 3. Advocate for rigorous testing – including edge cases, interface stress, and operational duty cycling. 4. Combine MDBF with failure frequency trends, Weibull modeling, and failure mode severity to get the full picture. Takeaway: Don’t be fooled by a clean-looking MDBF report. True reliability comes from design maturity, operational transparency, and attention to even the smallest failures that impact system confidence. #ReliabilityEngineering #RAMS #MTBF #MDBF #RollingStock #PAFailures #Propulsion #DesignForReliability #TestingMatters #RailwayEngineering #PredictiveMaintenance #TCMS #RealWorldReliability #FMECA #SystemDesign

What if we treated equipment reliability like an insurance policy? Most maintenance strategies still behave like co-pays and deductibles: we react, we mitigate, we absorb losses. But with today’s PM optimization methods and predictive technologies, we can design something far more powerful: 👉 A whole-equipment Asset Health Insurance Policy — one that intentionally covers 100% of an asset’s dominant failure modes. Here’s what that looks like in practice: 1️⃣ Start with failure modes, not tasks Build (or refresh) your component failure mode library using real failure data, not templates. Rank dominant failure modes by risk, consequence, and detectability. If a failure mode isn’t explicitly addressed, it’s effectively uninsured. 2️⃣ Optimize PM like an underwriter, not a scheduler Modern PM Optimization tools let you: ·      Eliminate low-value, time-based tasks ·      Align intervals to actual failure characteristics ·      Assign the right tactic: condition-based, predictive, run-to-failure, or redesign Every PM task should map to a specific failure mode and risk reduction outcome. 3️⃣ Layer predictive technologies where risk justifies the premium Vibration, ultrasound, oil analysis, process data, AI/ML models — these are not “nice to have.” They are risk transfer mechanisms that convert unknown failures into detectable, manageable conditions. 4️⃣ Close the gap with execution discipline An insurance policy only works if claims are processed correctly. That means: ·      High-quality work identification ·      Planned and scheduled execution ·      Feedback loops to update failure data and models 5️⃣ Measure coverage, not activity Stop asking “Did we do the PMs?” Start asking: “Which failure modes are fully covered, partially covered, or still exposed?” When done right, this approach: ·      Reduces unplanned downtime ·      Improves asset availability and safety ·      Lowers total cost of risk — not just maintenance cost Reliability isn’t about doing more maintenance......It’s about intentionally insuring your assets against how they actually fail. #AssetManagement #ReliabilityEngineering #PredictiveMaintenance #PMOptimization #AssetHealth #DigitalFactory #MaintenanceStrategy

🔴 Reliability is NOT a formula. It is the behavior of a system. A large part of the industry still analyzes reliability like this: R(t) = e⁻ˡᵗ MTBF = 1 / λ The math is correct. The assumption behind it often is not. 1️⃣ Reliability calculated with λ (Exponential model) This model assumes something critical: 👉 Constant failure rate Which implies: ❌ No aging ❌ No wear ❌ No infant mortality ❌ No operational changes In practice, it only represents: • Random failures • Time-independent failures Typical cases: 🔹 Electronic components 🔹 Software 🔹 Protection relays 🔹 Some control systems 📌 λ-based reliability does NOT explain why equipment fails. It only says how often it failed on average. 2️⃣ Reliability calculated with Weibull (3 parameters) R(t) = (see Weibull curve) Where: • β (beta) → failure behavior • η (eta) → characteristic life • γ (gamma) → failure-free period 3️⃣ What Weibull adds 🔹 β – The physics of failure • β < 1 → Infant mortality (design, installation, quality) • β = 1 → Random failures (exponential case) • β > 1 → Wear, fatigue, corrosion, aging 👉 This is where math connects with operational reality. 🔹 η – Life, not just frequency • Time when 63.2% of the population has failed • Enables: • PM optimization • Replacement strategies • Lifecycle decisions 🔹 γ – The reality no one talks about • Period where failure cannot occur • Commissioning • Warranty • Protected operating window 👉 The exponential model cannot represent this. 4️⃣ The key difference 🔹 λ says: “On average, this fails every X hours.” 🔹 Weibull says: “This fails for a reason, in a phase, and at a predictable point in its life.” 5️⃣ Why using only λ is dangerous in maintenance Because it assumes: ❌ The system does not learn ❌ Maintenance does not change behavior ❌ Aging does not exist ❌ Decisions do not matter 👉 That’s why we hear this so often: “Our MTBF is good, but availability is terrible.” 6️⃣ The truth • λ is a result • β explains the system • η enables decisions • γ reflects reality The exponential model is just a special case of Weibull: Weibull with β = 1 Using only λ is like: 📉 Driving while looking only at average speed 📈 Ignoring curves, traffic, and road conditions 🔹 λ tells you how often you failed. 🔹 Weibull tells you why, when, and what to do about it. Welcome to reality-centered reliability. #ReliabilityEngineering #Weibull #RCM

What does a Reliability Engineer do?  We know proper fitment of shafts and coupling hubs along with the key for items like gearboxes.  From experience we know how loose fits can quickly damage seals and bearings, break the key or the shaft.  Also proper sizing of the key to not create an imbalance which would also put extra burden on the seals and bearings causing them to wear faster.  Small subtle details including rounding of the key edges to not induce cracks.  I've seen far too often untrained mechanics who are not able to read the drawings, understand the tolerances, proper procedure for mounting the hub, and proper sizing of the key.  All of these details add up to ensuring the reliability of the bearings and seals and they will provide optimal service life without issue.  Many of the ongoing issues at a plant could be attributed to the knowledge and skills of the mechanics along with their willingness to ask for help.  After a number of years it becomes routine that repairs are made and may or may not last and require followup without understanding how the original repair may have had flaws that led to one or more failure modes.  If mechanics are too proud to ask an engineer for help; then at least they could learn to use AI and learn, it is good enough to take an image of a drawing and explain what the numbers mean.  From there with a bit more research one could learn ISO tolerances like we did in engineering University. #reliabilityengineering #mechanicalengineering #manufacturing

Why Every Mechanical Engineer in Oil & Gas Must Master Them In the oil & gas industry, rotating equipment is not just machinery — it is the heartbeat of production, safety, and reliability. Pumps, compressors, turbines, and auxiliary systems operate continuously under extreme pressures, temperatures, and corrosive environments. This is where API Standards become essential. The American Petroleum Institute (API) standards are not “guidelines to read later” — they are engineering languages that define how equipment is designed, manufactured, installed, operated, and maintained. 🔧 Why API Standards Matter Ensure equipment reliability and availability Reduce unplanned shutdowns Improve process safety Standardize best practices across global oil & gas operations Protect people, assets, and the environment 🔹 Core API Standards for Rotating Equipment Professionals 🟦 Pumps API 610 – Centrifugal Pumps The backbone standard for refinery and petrochemical pumps. Covers hydraulic design, materials, bearings, seals, testing, and reliability expectations. API 674 / 675 / 676 – Positive Displacement Pumps Essential for reciprocating, controlled-volume, and rotary pumps used in chemical injection, dosing, and high-pressure services. API 682 – Mechanical Seals One of the most critical standards for pump reliability, seal plans, and leakage prevention. API RP 691 – Risk-Based Machinery Management A powerful approach to prioritizing maintenance based on risk rather than time alone. 🟦 Compressors API 617 – Axial & Centrifugal Compressors Widely used in gas processing and LNG facilities. API 618 – Reciprocating Compressors Covers design, pulsation control, and vibration — vital for long-term reliability. API 619 – Rotary-Type Positive Displacement Compressors API 672 – Packaged Integrally Geared Compressors API 692 – Dry Gas Sealing Systems Critical for compressor sealing integrity and emissions control. 🟦 Installation, Reliability & Maintenance API RP 686 – Machinery Installation & Installation Design One of the most underrated but most powerful standards. Poor installation = guaranteed failure. API RP 687 – Repair of Rotating Equipment Ensures repairs restore equipment to original or improved condition. API 684 – Rotor Dynamics & Balancing API 688 – Pulsation & Vibration Control API RP 697 – Pump Repair A must-read for maintenance and workshop engineers. API standards don’t just tell you what the equipment is — they teach you how to think like a reliability engineer. 🎯 Final Thought If you are a mechanical engineer, technician, maintenance supervisor, or reliability engineer in oil & gas: 📌 Studying API standards is not optional 📌 Understanding them is a career accelerator 📌 Applying them on-site is what separates average engineers from trusted experts Rotating equipment excellence starts with knowledge, grows with discipline, and is sustained by API standards.

In reliability engineering, strategy improvement success hinges on identifying and resolving failure causes. However, a critical step that often determines the investigation's success is data collection. Collecting inaccurate or insufficient data risks addressing only symptoms—not the root cause—leading to persistent problems. 🛠️ Key Factors for Effective RCAs: Comprehensive Data Collection: Viewing the system holistically and gathering insights from all angles—historical data, environmental conditions, failure patterns, and operator input—prevents narrow conclusions and illuminates the root of the problem. Strong Cross-Functional Relationships: Collaboration between reliability engineers and maintenance/operations teams is essential. Reliability engineers bring analytical depth, while maintenance and operations teams offer practical, on-the-ground knowledge. This partnership fosters mutual trust and more complete investigations, as each team provides insights that would be overlooked if working in silos. Objective, In-Depth Interviews: Facilitating open discussions with maintenance and operations team members creates a safe space for honest feedback. In-depth knowledge from experienced team members can reveal critical failure insights that aren't evident in the data alone. Cross-Departmental Input: Bridging operations and maintenance perspectives builds a unified approach to RCAs. Operations may have specific knowledge about workload changes or procedural adjustments that affect outcomes, making their contributions invaluable to reliable, actionable RCAs. Holistic Analysis Techniques: Tools like 5-Why, Fishbone, and FMEA ensure comprehensive cause analysis. Validating findings with real operational data ensures that we address the core issues rather than just the surface symptoms. 📊 Data as the Backbone of Effective Actions: Accurate data and strong relationships translate into actions that address the true failure mechanisms, leading to reduced downtime, increased asset reliability, and optimized maintenance costs. In contrast, incomplete data or lack of cooperation can cause RCA efforts to miss the mark, leading to temporary fixes and higher costs. 🔹 The Role of Management Buy-In 🔹 For RCAs to drive sustainable change, management buy-in is essential. Leaders need to support the RCA process fully, holding teams accountable for actions across Operations, Maintenance, and Reliability. This commitment builds a reliability-centered culture, ensuring that RCA findings lead to lasting improvements. Our success as reliability engineers depends not only on precise data but also on strong relationships with maintenance and operations teams. These connections, combined with data-driven insights, allow us to implement solutions that address root issues, creating sustainable improvements that enhance equipment performance and team success. #RootCauseAnalysis #ReliabilityEngineering #Maintenance #Operations #TeamCollaboration #Data

“Didn’t we fix that pump 6 months ago?” Most plants deal with recurring failures that feel impossible to solve. Sure, we can use Root Cause Analysis to systemically go after these Bad Actors. We can ensure that when something fails, we fix it and improve it so that it won’t fail again. But let’s be a bit more proactive. There is a powerful tool you can use to pre-empt these bad actors. 🟢It's called Failure Modes and Effects Analysis (FMEA). An FMEA is often one of the first steps you would undertake to analyse and improve the reliability of a system or piece of equipment. By using FMEAs on installed equipment that is already operational, we can pre-empt failure. We identify the credible failure modes and determine the best method to address them. During an FMEA, you break the selected equipment down into systems, subsystems, assemblies, and components… and determine how these could fail. You analyse why the failure would happen and what the consequence would be. And the analysis is completed by assigning preventive or corrective actions to improve reliability. An FMEA analysis helps you identify how a piece of equipment might fail. You do this based on experience with similar types of equipment. Or in some cases purely based on sound engineering logic. The main elements of an FMEA are: →The potential failure mode that describes how the item fails to perform as intended; →the cause(s) of the potential failure mode. →The effect of the failure. Either on the system the item is part of or the people using it; Want to know more about FMEA? Want a step-by-step process? Want an editable template? Check out our article, “Why the FMEA is my equipment not reliable?” and download a copy of our FMEA template. Link is in the first comment. #maintenance #reliability #ReliabilityAcademy