7.4 System Safety and Reliability

7.4 System Safety and Reliability

1. Fundamental Concepts

1.1 System Safety

1. Definition: The application of engineering and management principles to achieve an acceptable level of risk throughout a system's lifecycle.

2. Objective: To identify, evaluate, and eliminate or control hazards before they result in accidents or failures.

3. Key Principle: Safety should be designed into systems, not added as an afterthought.

1.2 Reliability

1. Definition: The probability that a system or component will perform its required function under stated conditions for a specified period of time.

2. Mathematical Definition: $R(t) = P(T > t)$ Where $R(t)$ is reliability at time $t$, and $T$ is time to failure.

3. Reliability vs Safety:

   • Reliability: Focuses on functional performance.

   • Safety: Focuses on prevention of accidents/harm.

   • A system can be reliable but unsafe, or safe but unreliable.

1.3 Key Terms

1. Hazard: A condition with potential to cause harm (e.g., high voltage, toxic chemical).

2. Risk: Combination of probability and severity of harm from a hazard. $Risk = Probability \times Severity$

3. Failure: Termination of a system's ability to perform required function.

4. Fault: Abnormal condition that may cause failure.

5. Error: Human mistake that creates faults.

2. Failure Modes

2.1 Classification of Failure Modes

1. By Timing:

   • Early Failures: Occur during initial operation (infant mortality).

   • Random Failures: Constant failure rate during useful life.

   • Wear-out Failures: Increasing failure rate as components age.

2. By Effect:

   • Catastrophic: Complete, sudden loss of function.

   • Degraded: Gradual deterioration of performance.

   • Intermittent: Sporadic failures.

3. By Cause:

   • Hardware Failures: Physical component breakdown.

   • Software Failures: Bugs, logic errors.

   • Human Error: Operator mistakes, maintenance errors.

   • Environmental: Temperature, humidity, vibration.

2.2 Failure Mode and Effects Analysis (FMEA)

1. Purpose: Systematic method to identify potential failures and their consequences.

2. Process Steps:

   1. Identify components/functions.

   2. List potential failure modes.

   3. Determine effects of each failure.

   4. Identify causes of failures.

   5. Determine current controls.

   6. Calculate Risk Priority Number (RPN).

3. Risk Priority Number (RPN): $RPN = Severity \times Occurrence \times Detection$

   • Severity: Impact of failure (1-10).

   • Occurrence: Probability of occurrence (1-10).

   • Detection: Ability to detect before effect (1-10).

2.3 Common Failure Mechanisms

1. Mechanical:

   • Fatigue cracking.

   • Wear and abrasion.

   • Corrosion and erosion.

   • Creep deformation.

2. Electrical:

   • Short circuits.

   • Open circuits.

   • Insulation breakdown.

3. Electronic:

   • Thermal cycling damage.

   • Electromigration.

   • Electrostatic discharge.

4. Software:

   • Logic errors.

   • Memory leaks.

   • Race conditions.

3. Mean Time Between Failures (MTBF)

3.1 Definition and Calculation

1. MTBF Definition: Average time between consecutive failures of a repairable system. $MTBF = \frac{Total \ Operational \ Time}{Number \ of \ Failures}$

2. For Constant Failure Rate:

   • Assuming exponential distribution: $R(t) = e^{-\lambda t}$

   • Where $\lambda$ is failure rate (failures per unit time).

   • $MTBF = \frac{1}{\lambda}$

3. Units: Typically expressed in hours.

3.2 Applications and Interpretation

1. Reliability Prediction:

   • Probability of no failure in time $t$: $R(t) = e^{-t/MTBF}$

   • For $t = MTBF$: $R(MTBF) = e^{-1} \approx 0.368$ (36.8% reliability)

2. Maintenance Planning:

   • Determines inspection intervals.

   • Guides spare parts inventory.

3. System Comparison:

   • Higher MTBF indicates more reliable system.

   • Used in procurement specifications.

3.3 Related Metrics

1. Mean Time To Failure (MTTF):

   • For non-repairable items.

   • Average time until first failure.

2. Mean Time To Repair (MTTR):

   • Average time to restore system after failure.

3. Availability: $Availability = \frac{MTBF}{MTBF + MTTR}$

   • Percentage of time system is operational.

3.4 Limitations of MTBF

1. Assumes Constant Failure Rate: Not valid for wear-out periods.

2. Doesn't Consider Failure Severity: Treats all failures equally.

3. Population Statistic: Not a guarantee for individual units.

4. Data Quality Dependent: Requires accurate failure data.

4. Fault Tree Analysis (FTA)

4.1 Overview

1. Purpose: Top-down, deductive analysis method.

2. Approach: Starts with undesired top event, works downward to identify root causes.

3. Visual Representation: Boolean logic tree with gates and events.

4.2 Symbols and Notation

1. Events:

   • Top Event: Undesired system failure.

   • Basic Event: Lowest level, requires no further development.

   • Intermediate Event: Result of logic gate combination.

2. Logic Gates:

   • AND Gate: Output occurs if ALL inputs occur.

   • OR Gate: Output occurs if ANY input occurs.

3. Transfer Symbols: Connect different parts of large trees.

4.3 Analysis Process

1. Define System: Boundaries, assumptions, success/failure criteria.

2. Identify Top Event: Specific system failure to analyze.

3. Construct Tree: Develop logic relationships downward.

4. Evaluate Tree: Qualitative and quantitative analysis.

5. Interpret Results: Identify critical paths, recommend improvements.

4.4 Quantitative Analysis

1. Probability Calculation:

   • AND Gate: $P_{output} = \prod P_{input}$

   • OR Gate: $P_{output} = 1 - \prod (1 - P_{input})$

2. Cut Sets: Minimal combinations of basic events causing top event.

3. Importance Measures:

   • Birnbaum Importance: Sensitivity of top event to component.

   • Criticality Importance: Accounts for component reliability.

4.5 Applications and Benefits

1. Design Evaluation: Identify weak points in system design.

2. Risk Assessment: Quantify probability of hazardous events.

3. Root Cause Analysis: Systematic investigation of failures.

4. Safety Verification: Demonstrate compliance with safety requirements.

5. Event Tree Analysis (ETA)

5.1 Overview

1. Purpose: Forward-looking, inductive analysis method.

2. Approach: Starts with initiating event, works forward through possible outcomes.

3. Visual Representation: Tree branching at decision points.

5.2 Analysis Process

1. Identify Initiating Event: Starting point for analysis.

2. Define Safety Functions: Systems responding to initiating event.

3. Construct Tree: Branch for success/failure of each function.

4. Assign Probabilities: To each branch point.

5. Calculate Outcome Probabilities: Multiply along paths.

5.3 Quantitative Analysis

1. Path Probability: Product of probabilities along path. $P_{path} = P_{IE} \times \prod P_{branch}$

2. Outcome Probability: Sum of probabilities for all paths leading to same outcome.

3. Risk Calculation: Combine probability with consequence severity.

5.4 Applications

1. Accident Sequence Analysis: How initiating events escalate.

2. Safety System Effectiveness: Evaluate protective systems.

3. Emergency Planning: Identify critical response sequences.

4. Regulatory Compliance: Demonstrate risk control measures.

5.5 FTA vs ETA Comparison

Aspect	Fault Tree Analysis (FTA)	Event Tree Analysis (ETA)
Direction	Top-down (deductive)	Forward-looking (inductive)
Starting Point	Undesired top event	Initiating event
Focus	Causes of specific failure	Consequences of initiating event
Logic	Boolean (AND/OR gates)	Sequential branching
Best For	Root cause analysis, design weakness	Accident progression, safety system evaluation

6. Hazard Analysis

6.1 Types of Hazard Analysis

1. Preliminary Hazard Analysis (PHA):

   • Early in design phase.

   • Identifies potential hazards.

   • Recommends design changes.

2. System Hazard Analysis (SHA):

   • Detailed analysis of system interactions.

   • Identifies interface hazards.

3. Operating and Support Hazard Analysis (OSHA):

   • Focuses on operational phase.

   • Human-machine interface hazards.

4. Job Hazard Analysis (JHA):

   • Task-specific analysis.

   • Identifies step-by-step hazards.

6.2 Hazard Identification Techniques

1. Checklists: Standardized lists of potential hazards.

2. What-If Analysis: Brainstorming potential abnormal situations.

3. Hazard and Operability Study (HAZOP):

   • Systematic examination of deviations from design intent.

   • Uses guide words (NO, MORE, LESS, etc.).

4. Failure Modes, Effects, and Criticality Analysis (FMECA):

   • Extension of FMEA with criticality ranking.

6.3 Risk Assessment Matrix

1. Severity Categories:

   • Catastrophic

   • Critical

   • Marginal

   • Negligible

2. Probability Levels:

   • Frequent

   • Probable

   • Occasional

   • Remote

   • Improbable

3. Risk Ranking: Combine severity and probability.

6.4 Risk Control Hierarchy

1. Elimination: Remove hazard completely.

2. Substitution: Replace with less hazardous alternative.

3. Engineering Controls: Physical changes (guards, ventilation).

4. Administrative Controls: Procedures, training, supervision.

5. Personal Protective Equipment (PPE): Last line of defense.

7. Reliability Engineering Principles

7.1 Design for Reliability

1. Derating: Operate components below rated capacity.

2. Redundancy:

   • Active: Multiple components operate simultaneously.

   • Standby: Backup activates when primary fails.

   • k-out-of-n: System works if k of n components work.

3. Fault Tolerance: Continue operation despite component failures.

4. Fail-Safe Design: System fails to safe state.

7.2 Reliability Modeling

1. Series Systems:

   • All components must work for system success.

   • $R_{system} = \prod R_i$

   • System reliability ≤ weakest component.

2. Parallel Systems:

   • System works if any component works.

   • $R_{system} = 1 - \prod (1 - R_i)$

3. Combined Systems: Series-parallel combinations.

7.3 Reliability Testing

1. Life Testing: Operate until failure.

2. Accelerated Life Testing: Apply stress to hasten failures.

3. Environmental Stress Screening: Eliminate early failures.

4. Burn-in Testing: Operate before delivery to remove infant mortality.

7.4 Reliability Data Analysis

1. Weibull Analysis: Models various failure patterns.

   • Shape parameter (β) indicates failure pattern.

2. Exponential Distribution: Constant failure rate assumption.

3. Normal Distribution: Wear-out failures.

4. Data Collection: Failure times, operating conditions, maintenance records.

8. Safety Instrumented Systems (SIS)

8.1 Safety Integrity Levels (SIL)

1. Definition: Quantitative target for safety system performance.

2. SIL Levels 1-4: Increasing reliability requirements.

3. Probability of Failure on Demand (PFD):

   • SIL 1: 0.1 to 0.01

   • SIL 2: 0.01 to 0.001

   • SIL 3: 0.001 to 0.0001

   • SIL 4: 0.0001 to 0.00001

8.2 Safety Lifecycle

1. Hazard and Risk Assessment

2. Allocation of Safety Functions

3. Safety Requirements Specification

4. Design and Engineering

5. Installation and Commissioning

6. Operation and Maintenance

7. Modification and Decommissioning

9. Implementation Considerations

9.1 Organizational Factors

1. Safety Culture: Management commitment, employee involvement.

2. Competence: Training and qualification of personnel.

3. Documentation: Procedures, records, analysis reports.

4. Continuous Improvement: Learn from incidents and near-misses.

9.2 Cost-Benefit Analysis

1. Direct Costs: Analysis time, implementation of controls.

2. Benefits: Reduced accidents, lower insurance, regulatory compliance.

3. Return on Investment: Often significant for safety improvements.

9.3 Regulatory Framework

1. Standards and Codes: ISO 31000 (Risk management), IEC 61508 (Functional safety).

2. Industry Specific: Process industry, aerospace, automotive.

3. Legal Requirements: Occupational safety, environmental protection.

10. Summary of Key Points

1. Proactive Approach: Identify and mitigate risks before incidents occur.

2. Systematic Methods: Use structured techniques (FTA, ETA, FMEA).

3. Quantitative Analysis: Support decisions with data and probabilities.

4. Lifecycle Perspective: Consider all phases from design to decommissioning.

5. Integrated Approach: Combine safety, reliability, and maintainability.

6. Continuous Process: Regular review and update of analyses.

7. Documentation: Maintain records for verification and improvement.

Effective system safety and reliability engineering requires a balanced approach combining technical analysis with organizational commitment and continuous improvement culture.