Reliability, maintainability, and supportability : best practices for systems engineers / Michael Tortorella.

"Provides exercises in each chapter, allowing the reader to try out some of the ideas and procedures presented in the chapter"--

Saved in:
Bibliographic Details
Main Author: Tortorella, Michael, 1947-
Format: eBook
Language:English
Published: Hoboken, New Jersey : John Wiley & Sons, Inc., [2015]
Subjects:
Online Access:Click for online access
Table of Contents:
  • Machine generated contents note: 1. Systems Engineering and the Sustainability Disciplines
  • 1.1. Purpose of this Book
  • 1.1.1. Systems Engineers Create and Monitor Requirements
  • 1.1.2. Good Requirements are a Key to Success
  • 1.1.3. Sustainability Requirements are Important Too
  • 1.1.4. Focused Action is Needed to Achieve the Goals Expressed by the Requirements
  • 1.2. Goals
  • 1.3. Scope
  • 1.3.1. Reliability Engineering
  • 1.3.2. Maintainability Engineering
  • 1.3.3. Supportability Engineering
  • 1.4. Audience
  • 1.4.1. Who Should Read This Book?
  • 1.4.2. Prerequisites
  • 1.4.3. Postrequisites
  • 1.5. Getting Started
  • 1.6. Key Success Factors for Systems Engineers in Reliability, Maintainability, and Supportability Engineering
  • 1.6.1. Customer-Supplier Relationships
  • 1.6.2. Language and Clarity of Communication
  • 1.6.3. Statistical Thinking
  • 1.7. Organizing a Course Using this Book
  • 1.7.1. Examples
  • 1.7.2. Exercises
  • 1.7.3. References
  • 1.8. Chapter Summary
  • References
  • 2. Reliability Requirements
  • 2.1. What to Expect from this Chapter
  • 2.2. Reliability for Systems Engineers
  • 2.2.1. "Reliability" in Conversation
  • 2.2.2. "Reliability" in Engineering
  • 2.2.3. Foundational Concepts
  • 2.2.4. Reliability Concepts for Systems Engineers
  • 2.2.5. Definition of Reliability
  • 2.2.6. Failure Modes, Failure Mechanisms, and Failure Causes
  • 2.2.7. Stress-Strength Model
  • 2.2.8. Competing Risk Model
  • 2.3. Reliability, Maintainability, and Supportability are Mutually Reinforcing
  • 2.3.1. Introduction
  • 2.3.2. Mutual Reinforcement
  • 2.4. Structure of Reliability Requirements
  • 2.4.1. Reliability Effectiveness Criteria
  • 2.4.2. Reliability Figures of Merit
  • 2.4.3. Quantitative Reliability Requirements Frameworks
  • 2.5. Examples of Reliability Requirements
  • 2.5.1. Reliability Requirements for a Product
  • 2.5.2. Reliability Requirements for a Flow Network
  • 2.5.3. Reliability Requirements for a Standing Service
  • 2.5.4. Reliability Requirements for an On-Demand Service
  • 2.6. Interpretation of Reliability Requirements
  • 2.6.1. Introduction
  • 2.6.2. Stakeholders
  • 2.6.3. Interpretation of Requirements Based on Effectiveness Criteria
  • 2.6.4. Interpretation of Requirements Based on Figures of Merit
  • 2.6.5. Models and Predictions
  • 2.6.6. What Happens When a Requirement is Not Met?
  • 2.7. Some Additional Figures of Merit
  • 2.7.1. Cumulative Distribution Function
  • 2.7.2. Measures of Central Tendency
  • 2.7.3. Measures of Dispersion
  • 2.7.4. Percentiles
  • 2.7.5. Central Limit Theorem and Confidence Intervals
  • 2.8. Current Best Practices in Developing Reliability Requirements
  • 2.8.1. Determination of Failure Modes
  • 2.8.2. Determination of Customer Needs and Desires for Reliability and Economic Balance with Reliability Requirements
  • 2.8.3. Review All Reliability Requirements for Completeness
  • 2.8.4. Allocation of System Reliability Requirements to System Components
  • 2.8.5. Document Reliability Requirements
  • 2.9. Chapter Summary
  • 2.10. Exercises
  • References
  • 3. Reliability Modeling for Systems Engineers
  • 3.1. What to Expect from this Chapter
  • 3.2. Introduction
  • 3.3. Reliability Effectiveness Criteria and Figures of Merit for Nonmaintained Units
  • 3.3.1. Introduction
  • 3.3.2. Life Distribution and the Survivor Function
  • 3.3.3. Other Quantities Related to the Life Distribution and Survivor Function
  • 3.3.4. Some Commonly Used Life Distributions
  • 3.3.5. Quantitative Incorporation of Environmental Stresses
  • 3.3.6. Quantitative Incorporation of Manufacturing Process Quality
  • 3.3.7. Operational Time and Calendar Time
  • 3.3.8. Summary
  • 3.4. Ensembles of Nonmaintained Components
  • 3.4.1. System Functional Decomposition
  • 3.4.2. Some Examples of System and Service Functional Decompositions
  • 3.4.3. Reliability Block Diagram
  • 3.4.4. Ensembles of Single-Point-of-Failure Units: Series Systems
  • 3.4.5. Ensembles Containing Redundant Elements: Parallel Systems
  • 3.4.6. Structure Functions
  • 3.4.7. Path Set and Cut Set Methods
  • 3.4.8. Reliability Importance
  • 3.4.9. Non-Service-Affecting Parts
  • 3.5. Reliability Modeling Best Practices for Systems Engineers
  • 3.6. Chapter Summary
  • 3.7. Exercises
  • References
  • 4. Reliability Modeling for Systems Engineers
  • 4.1. What to Expect from this Chapter
  • 4.2. Introduction
  • 4.3. Reliability Effectiveness Criteria and Figures of Merit for Maintained Systems
  • 4.3.1. Introduction
  • 4.3.2. System Reliability Process
  • 4.3.3. Reliability Effectiveness Criteria and Figures of Merit Connected with the System Reliability Process
  • 4.3.4. When is a Maintainable System Not a Maintained System?
  • 4.4. Maintained System Reliability Models
  • 4.4.1. Types of Repair and Service Restoration Models
  • 4.4.2. Systems with Renewal Repair
  • 4.4.3. Systems with Revival Repair
  • 4.4.4. More-General Repair Models
  • 4.4.5. Separate Maintenance Model
  • 4.4.6. Superpositions of Point Processes and Systems with Many Single Points of Failure
  • 4.4.7. State Diagram Reliability Models
  • 4.5. Stability of Reliability Models
  • 4.6. Software Resources
  • 4.7. Reliability Modeling Best Practices for Systems Engineers
  • 4.7.1. Develop and Use a Reliability Model
  • 4.7.2. Develop the Reliability-Profitability Curve
  • 4.7.3. Budget for Reliability
  • 4.7.4. Design for Reliability
  • 4.8. Chapter Summary
  • 4.9. Exercises
  • References
  • 5. Comparing Predicted and Realized Reliability with Requirements
  • 5.1. What to Expect from this Chapter
  • 5.2. Introduction
  • 5.3. Effectiveness Criteria, Figures of Merit, Metrics, and Predictions
  • 5.3.1. Review
  • 5.3.2. Example
  • 5.3.3. Reliability Predictions
  • 5.4. Statistical Comparison Overview
  • 5.4.1. Quality of Knowledge
  • 5.4.2. Three Comparisons
  • 5.4.3. Count Data from Aggregates of Systems
  • 5.4.4. Environmental Conditions
  • 5.5. Statistical Comparison Techniques
  • 5.5.1. Duration Requirements
  • 5.5.2. Count Requirements
  • 5.6. Failure Reporting and Corrective Action System
  • 5.7. Reliability Testing
  • 5.7.1. Component Life Testing
  • 5.7.2. Reliability Growth Testing
  • 5.7.3. Software Reliability Modeling
  • 5.8. Best Practices in Reliability Requirements Comparisons
  • 5.8.1. Track Achievement of Reliability Requirements
  • 5.8.2. Institute a FRACAS
  • 5.9. Chapter Summary
  • 5.10. Exercises
  • References
  • 6. Design for Reliability
  • 6.1. What to Expect from this Chapter
  • 6.2. Introduction
  • 6.3. Techniques for Reliability Assessment
  • 6.3.1. Quantitative Reliability Modeling
  • 6.3.2. Reliability Testing
  • 6.4. Design for Reliability Process
  • 6.4.1. Information Sources
  • 6.5. Hardware Design for Reliability
  • 6.5.1. Printed Wiring Boards
  • 6.5.2. Design for Reliability in Complex Systems
  • 6.6. Qualitative Design for Reliability Techniques
  • 6.6.1. Fault Tree Analysis
  • 6.6.2. Failure Modes, Effects, and Criticality Analysis
  • 6.7. Design for Reliability for Software Products
  • 6.8. Robust Design
  • 6.9. Design for Reliability Best Practices for Systems Engineers
  • 6.9.1. Reliability Requirements
  • 6.9.2. Reliability Assessment
  • 6.9.3. Reliability Testing
  • 6.9.4. DFR Practices
  • 6.10. Software Resources
  • 6.11. Chapter Summary
  • 6.12. Exercises
  • References
  • 7. Reliability Engineering for High-Consequence Systems
  • 7.1. What to Expect from this Chapter
  • 7.2. Definition and Examples of High-Consequence Systems.
  • -- 7.2.1. What is a High-Consequence System?
  • 7.2.2. Examples of High-Consequence Systems
  • 7.3. Reliability Requirements for High-Consequence Systems
  • 7.4. Strategies for Meeting Reliability Requirements in High-Consequence Systems
  • 7.4.1. Redundancy
  • 7.4.2. Network Resiliency
  • 7.4.3. Component Qualification and Certification
  • 7.4.4. Failure Isolation
  • 7.5. Current Best Practices in Reliability Engineering for High-Consequence Systems
  • 7.6. Chapter Summary
  • 7.7. Exercises
  • References
  • 8. Reliability Engineering for Services
  • 8.1. What to Expect from this Chapter
  • 8.2. Introduction
  • 8.2.1. On-Demand Services
  • 8.2.2. Always-On Services
  • 8.3. Service Functional Decomposition
  • 8.4. Service Failure Modes and Failure Mechanisms
  • 8.4.1. Introduction
  • 8.4.2. Service Failure Modes
  • 8.4.3. Service Failure Mechanisms
  • 8.5. Service Reliability Requirements
  • 8.5.1. Examples of Service Reliability Requirements
  • 8.5.2. Interpretation of Service Reliability Requirements
  • 8.6. Service-Level Agreements
  • 8.7. SDI Reliability Requirements
  • 8.8. Design for Reliability Techniques for Services
  • 8.8.1. Service Fault Tree Analysis
  • 8.8.2. Service FME(C)A
  • 8.9. Current Best Practices in Service Reliability Engineering
  • 8.9.1. Set Reliability Requirements for the Service
  • 8.9.2. Determine Infrastructure Reliability Requirements from Service Reliability Requirements
  • 8.9.3. Monitor Achievement of Service Reliability Requirements
  • 8.10. Chapter Summary
  • 8.11. Exercises
  • References
  • 9. Reliability Engineering for the Software Component of Systems and Services
  • 9.1. What to Expect from this Chapter
  • 9.2. Introduction
  • 9.3. Reliability Requirements for the Software Component of Systems and Services
  • 9.3.1. Allocation of System Reliability Requirements to the Software Component.
  • Note continued: 9.3.2. Reliability Requirements for Security and Other Novel Areas
  • 9.3.3. Operational Time and Calendar Time
  • 9.4. Reliability Modeling for Software
  • 9.4.1. Reliability Growth Modeling for the Sequence of Failure Times
  • 9.4.2. Other Approaches
  • 9.5. Software Failure Modes and Failure Mechanisms
  • 9.5.1. Software Failure Modes
  • 9.5.2. Software Failure Mechanisms
  • 9.6. Design for Reliability in Software
  • 9.6.1. Software Fault Tree Analysis
  • 9.6.2. Software FME(C)A
  • 9.6.3. Some Software Failure Prevention Strategies
  • 9.7. Current Best Practices in Reliability Engineering for Software
  • 9.7.1. Follow Good Software Engineering Practices
  • 9.7.2. Conduct Design Reviews Focused on Reliability
  • 9.7.3. Reuse Known Good Software
  • 9.7.4. Encourage a Prevention Mindset
  • 9.8. Chapter Summary
  • 9.9. Exercises
  • References
  • 10. Maintainability Requirements
  • 10.1. What to Expect from this Chapter
  • 10.2. Maintainability for Systems Engineers
  • 10.2.1. Definitions
  • 10.2.2. System Maintenance Concept
  • 10.2.3. Use of Maintainability Effectiveness Criteria and Requirements
  • 10.2.4. Use of Preventive Maintenance
  • 10.2.5. Levels of Maintenance
  • 10.2.6. Organizational Responsibilities
  • 10.2.7. Design Features
  • 10.2.8. Maintenance Environment
  • 10.2.9. Warranties
  • 10.2.10. Preventive Maintenance and Corrective Maintenance
  • 10.2.11. Maintainability for Services
  • 10.3. Maintainability Effectiveness Criteria and Figures of Merit
  • 10.3.1. Products and Systems
  • 10.3.2. Services
  • 10.4. Examples of Maintainability Requirements
  • 10.5. Maintainability Modeling
  • 10.5.1. Duration and Labor-Hour Effectiveness Criteria and Figures of Merit
  • 10.5.2. Count Effectiveness Criteria and Figures of Merit
  • 10.6. Interpreting and Verifying Maintainability Requirements
  • 10.6.1. Duration Effectiveness Criteria and Figures of Merit
  • 10.6.2. Count Effectiveness Criteria and Figures of Merit
  • 10.6.3. Cost and Labor-Hour Effectiveness Criteria and Figures of Merit
  • 10.6.4. Three Availability Figures of Merit
  • 10.7. Maintainability Engineering for High-Consequence Systems
  • 10.8. Current Best Practices in Maintainability Requirements Development
  • 10.8.1. Determine Customer Needs for Maintainability
  • 10.8.2. Balance Maintenance with Economics
  • 10.8.3. Use Quantitative Maintainability Modeling to Ensure Support for Maintainability Requirements
  • 10.8.4. Manage Maintainability by Fact
  • 10.9. Chapter Summary
  • 10.10. Exercises
  • References
  • 11. Design for Maintainability
  • 11.1. What to Expect from this Chapter
  • 11.2. System or Service Maintenance Concept
  • 11.3. Maintainability Assessment
  • 11.3.1. Maintenance Functional Decomposition and Maintainability Block Diagram
  • 11.3.2. Quantitative Maintainability Modeling
  • 11.4. Design for Maintainability Techniques
  • 11.4.1. System Maintenance Concept
  • 11.4.2. Level of Repair Analysis
  • 11.4.3. Preventive Maintenance
  • 11.4.4. Reliability-Centered Maintenance (RCM)
  • 11.5. Current Best Practices in Design for Maintainability
  • 11.5.1. Make a Deliberate Maintainability Plan
  • 11.5.2. Determine Which Design for Maintainability Techniques to Use
  • 11.5.3. Integration
  • 11.5.4. Organizational Factors
  • 11.6. Chapter Summary
  • 11.7. Exercises
  • References
  • 12. Support Requirements
  • 12.1. What to Expect from this Chapter
  • 12.2. Supportability for Systems Engineers
  • 12.2.1. Supportability as a System Property
  • 12.2.2. Factors Promoting Supportability
  • 12.2.3. Activities Included in Supportability Engineering
  • 12.2.4. Measuring and Monitoring Supportability
  • 12.2.5. Developing and Interpreting Support Requirements
  • 12.3. System or Service Support Concept
  • 12.4. Support Effectiveness Criteria and Figures of Merit
  • 12.5. Examples of Support Requirements
  • 12.5.1. Support Elapsed Time (Duration) Requirements
  • 12.5.2. Support Count Requirements
  • 12.6. Interpreting and Verifying Support Requirements
  • 12.7. Supportability Engineering for High-Consequence Systems
  • 12.8. Current Best Practices in Support Requirements Development
  • 12.8.1. Identify Support Needs
  • 12.8.2. Balance Support with Economics
  • 12.8.3. Use Quantitative Modeling to Promote Rationally Based Support Requirements
  • 12.8.4. Manage Supportability by Fact
  • 12.9. Chapter Summary
  • 12.10. Exercises
  • References
  • 13. Design for Supportability
  • 13.1. What to Expect from this Chapter
  • 13.2. Supportability Assessment
  • 13.2.1. Quantitative Supportability Assessment
  • 13.2.2. Qualitative Supportability Assessment
  • 13.3. Implementation of Factors Promoting Supportability
  • 13.3.1. Diagnostics and Fault Location
  • 13.3.2. Tools and Equipment
  • 13.3.3. Documentation and Workflow Management
  • 13.3.4. Staff Training
  • 13.3.5. Layout of Repair Facility and Workstation Design
  • 13.3.6. Design of Maintenance Procedures
  • 13.3.7. Spare Parts, Repair Parts, and Consumables Inventory
  • 13.3.8. Transportation and Logistics
  • 13.4. Quantitative Design for Supportability Techniques
  • 13.4.1. Performance Analysis of a Maintenance Facility
  • 13.4.2. Staff Sizing: The Machine Servicing Model
  • 13.5. Current Best Practices in Design for Supportability
  • 13.5.1. Customer Needs and Supportability Requirements
  • 13.5.2. Team Integration
  • 13.5.3. Modeling and Optimization
  • 13.5.4. Continual Improvement
  • 13.6. Chapter Summary
  • 13.7. Exercises
  • References.