Click here
      Home    DAG Tutorial    Search    Available Downloads     Feedback
 
The DAG does not reflect the changes in the DoDI5000.02. Work is in progress to update the content and will be completed as soon as possible.
 
.

4.3.18.19. Reliability and Maintainability Engineering

Topic

Previous and Next Page arrows

DEFENSE ACQUISITION GUIDEBOOK
Chapter 4 -- Systems Engineering

4.3.18.19. Reliability and Maintainability Engineering

4.3.18.19. Reliability and Maintainability Engineering

The purpose of Reliability and Maintainability (R&M) engineering (Maintainability includes Built-In-Test (BIT)) is to influence system design in order to increase mission capability and availability, and decrease logistics burden and cost over a system’s life cycle. Properly planned, R&M engineering reduces cost and schedule risks by preventing or identifying R&M deficiencies early in development. This early action results in increased acquisition efficiency and higher success rates during operational testing, and can even occur in the development process as early as the Engineering and Manufacturing Development (EMD) phase.

DoDI 5000.02 requires Major Defense Acquisition Program (MDAP) Program Managers to implement a comprehensive R&M engineering program as an integral part of the systems engineering (SE) process. The Systems Engineer should understand that R&M parameters have an impact on the system’s performance, availability, logistics supportability, and total ownership cost. To ensure a successful R&M engineering program, the Systems Engineer should integrate the following activities across the program’s engineering organization and processes:

  • Providing adequate R&M staffing
  • Ensuring R&M engineering is fully integrated into SE activities, Integrated Product Teams, and other stakeholder organizations (i.e., Logistics, Test, and ESOH)
  • Ensuring specifications contain realistic quantitative R&M requirements traceable to the Initial Capabilities Document (ICD)/Capability Development Document (CDD) /Capability Production Document (CPD)
  • Ensuring that R&M engineering activities and deliverables in the Request for Proposal are appropriate for the program phase and product type
  • Integrating R&M engineering activities and reliability growth planning curve(s) in the Systems Engineering Plan (SEP) at each milestone
  • Planning verification methods for each R&M requirement
  • Ensuring the verification methods for each R&M requirement are described in the TEMP, along with a reliability growth planning curve beginning at MS B
  • Ensuring data from R&M analyses, demonstrations, and tests are properly used to influence life-cycle product support planning, availability assessments, cost estimating, and other related program analyses
  • Identifying and tracking R&M risks and Technical Performance Measures.
  • Assessing R&M status during program technical reviews
  • Including consideration of R&M in all configuration changes and trade-off analyses

As part of the SE process, the R&M engineer should be responsible for the R&M activities by acquisition phase outlined in Table 4.3.18.19.T1.

Table 4.3.18.19.T1. R&M Activities by Acquisition Phase

Acquisition Phase

R&M Activities

Materiel Solution Analysis (MSA) Phase. During the Materiel Solution Analysis Phase, the R&M engineer, as part of the program SE team, should:

  • Analyze conceptual design approaches and estimate the feasibility with respect to R&M ICD performance capabilities
  • Perform AoA trade-off studies among R&M, availability, and other system performance parameters to arrive at a preferred system alternative. The studies should be performed in conjunction with product support, cost, and design personnel, using the DoD RAM-C Rationale Report Manual
  • Prepare the Reliability, Availability, Maintainability, and Cost (RAM-C) Rationale Report and attach it to the SEP
  • Translate ICD performance capabilities and draft CDD thresholds to R&M specification requirements based on system use conditions, mission profile, failure definitions, and utilization rates
  • Define contractor R&M engineering activities in the RFP and contract Statement of Work for the TD phase, which should include:

a. Allocations

b. Block diagrams and modeling

c. Predictions

d. Failure Mode, Effects, and Criticality Analysis (FMECA)

e. Subsystem and system-level reliability growth planning activities

f. R&M tests and demonstrations

g. Failure Reporting, Analysis, and Corrective Action System (FRACAS)

Technology Development (TD) Phase. During the Technology Development phase, the R&M engineer, as part of the program SE team, should:

  • Participate in trade studies during requirements analysis and architecture design
  • Review results of R&M engineering analyses, verification tests, design approach, availability assessments, and maintenance concept optimization to verify conformance to requirements, and to identify potential R&M problem areas
  • Contribute to integrated test planning to avoid duplication and afford a more complete utilization of all test data for R&M assessment. Comprehensive test planning should include subsystem reliability growth and maintainability and Built-In Test (BIT) demonstrations as appropriate
  • Verify that plans have been established for the selection and application criteria of parts, materials, and processes to limit reliability risks
  • Define contractor R&M engineering activities in the RFP and contract Statement of Work for the EMD phase, during which R&M quantitative requirements and verification methods are incorporated

Engineering and Manufacturing Development (EMD) Phase. During the EMD phase, the R&M engineer, as part of the program SE team, should:

  • Perform evaluations to assess R&M status and problems
  • Ensure that the product baseline design and required testing can meet the R&M requirements
  • Ensure the final FMECA identifies failure modes, and their detection methods, that could result in personnel injury and/or mission loss, and ensure they are mitigated in the design
  • Ensure that the detailed R&M prediction to assess system potential to meet design requirements is complete
  • Verify through appropriate subsystem/equipment-level tests the readiness to enter system-level testing at or above the initial reliability established in the reliability growth-planning curve in both the SEP and the TEMP
  • Verify system conformance to specified R&M requirements through appropriate demonstration and test
  • Implement a FRACAS to ensure feedback of failure data during test and to apply and track corrective actions
  • Coordinate with the Chief Developmental Tester (T&E Lead) and Operational Test Agencies (OTA) to ensure that the program office and OTA data collection agree on R&M monitoring and failure definitions, and that R&M and BIT scoring processes are consistent in verification of requirements through all levels of testing
  • Define contractor R&M engineering activities in the RFP and contract Statement of Work (SOW) for the P&D phase to ensure adequate R&M engineering activities take place during P&D, and to ensure the RFP and contract SOW provide adequate consideration of R&M in re-procurements, spares, and repair parts
  • Verify that parts, materials, and processes meet system requirements through the use of a management plan detailing reliability risk considerations and evaluation strategies for the intended service life. Include flow of requirements to subcontractors and suppliers. See MIL-STD-1546, Parts, Materials, and Processes Control Program for Space and Launch Vehicles, and MIL-STD-1547, Electronic Parts, Materials, and Processes for Space and Launch Vehicles

Production and Deployment (P&D) Phase. During the P&D phase, the R&M engineer, as part of the programs SE team should:

  • Verify initial production control of R&M degradation factors by test and inspection, production data analysis, and supplemental tests
  • Verify R&M characteristics, maintenance concept, repair policies, Government technical evaluation, and maintenance procedures by T&E
  • Identify R&M and production-related BIT improvement opportunities via FRACAS and field data assessment
  • Review Engineering Change Proposals (ECP), operational mission/deployment changes, and variations for impact on R&M
  • Update R&M predictions and FMECAs based on field results and apply them to the models previously developed to assess impacts on spares, manpower, missions, and availability
  • Verify that parts, materials, and processes management requirements for limiting reliability risk and “lessons learned” are utilized during all design change efforts including change proposals, variations, substitutions, product improvement efforts, or any other hardware change effort

Operations and Support (O&S) Phase. During the O&S phase, the R&M engineer, as part of the program SE team should:

  • Assess operational data to determine the adequacy of R&M and BIT characteristics performance, maintenance features and procedures, and provisioning plans
  • Identify problem areas for correction through ongoing closed-loop FRACAS and field data assessment
  • Monitor availability rates and respond to negative trends and data anomalies

Previous and Next Page arrows

Previous Page Next Page

List of All Contributions at This Location

No items found.

Popular Tags

Browse

https://acc.dau.mil/UI/img/bo/minus.gifWelcome to the Defense Acquisition...
https://acc.dau.mil/UI/img/bo/plus.gifForeword
https://acc.dau.mil/UI/img/bo/plus.gifChapter 1 -- Department of Defense...
https://acc.dau.mil/UI/img/bo/plus.gifChapter 2 -- Program Strategies
https://acc.dau.mil/UI/img/bo/plus.gifChapter 3 -- Affordability and...
https://acc.dau.mil/UI/img/bo/minus.gifChapter 4 -- Systems Engineering
https://acc.dau.mil/UI/img/bo/plus.gif4.0. Overview
https://acc.dau.mil/UI/img/bo/plus.gif4.1. Introduction
https://acc.dau.mil/UI/img/bo/plus.gif4.2. Systems Engineering Activities in...
https://acc.dau.mil/UI/img/bo/minus.gif4.3. Systems Engineering Processes
https://acc.dau.mil/UI/img/bo/plus.gif4.3.2. Technical Planning Process
https://acc.dau.mil/UI/img/bo/plus.gif4.3.3. Decision Analysis Process
https://acc.dau.mil/UI/img/bo/plus.gif4.3.4. Technical Assessment Process
https://acc.dau.mil/UI/img/bo/plus.gif4.3.5. Requirements Management Process
https://acc.dau.mil/UI/img/bo/plus.gif4.3.6. Risk Management Process
https://acc.dau.mil/UI/img/bo/plus.gif4.3.7. Configuration Management Process
https://acc.dau.mil/UI/img/bo/plus.gif4.3.8. Technical Data Management Process
https://acc.dau.mil/UI/img/bo/plus.gif4.3.9. Interface Management Process
https://acc.dau.mil/UI/img/bo/plus.gif4.3.10. Stakeholder Requirements...
https://acc.dau.mil/UI/img/bo/plus.gif4.3.11. Requirements Analysis Process
https://acc.dau.mil/UI/img/bo/plus.gif4.3.12. Architecture Design Process
https://acc.dau.mil/UI/img/bo/plus.gif4.3.13. Implementation Process
https://acc.dau.mil/UI/img/bo/plus.gif4.3.14. Integration Process
https://acc.dau.mil/UI/img/bo/plus.gif4.3.15. Verification Process
https://acc.dau.mil/UI/img/bo/plus.gif4.3.16. Validation Process
https://acc.dau.mil/UI/img/bo/plus.gif4.3.17. Transition Process
https://acc.dau.mil/UI/img/bo/minus.gif4.3.18. Design Considerations
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.1. Accessibility (Section 508...
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.2. Affordability – Systems...
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.3. Anti-Counterfeiting
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.4. Commercial-Off-the-Shelf
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.5. Corrosion Prevention and...
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.6. Critical Safety Item
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.7. Demilitarization and Disposal
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.8. Diminishing Manufacturing...
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.9. Environment Safety and...
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.10. Human Systems Integration
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.11. Insensitive Munitions
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.12. Intelligence (Life-Cycle...
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.13. Interoperability and...
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.14. Item Unique Identification
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.15. Open Systems Architecture
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.16. Operational Energy
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.17. Packaging Handling Storage...
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.18. Producibility Quality and...
https://acc.dau.mil/UI/img/bo/minus.gif4.3.18.19. Reliability and...
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.20. Spectrum Management
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.21. Standardization
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.22. Supportability
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.23. Survivability and...
https://acc.dau.mil/UI/img/bo/plus.gif4.3.18.24. System Security Engineering
https://acc.dau.mil/UI/img/bo/plus.gif4.3.19. Tools Techniques and Lessons...
https://acc.dau.mil/UI/img/bo/plus.gifChapter 5 -- Life-Cycle Logistics
https://acc.dau.mil/UI/img/bo/plus.gifChapter 6 -- Human Systems Integration...
https://acc.dau.mil/UI/img/bo/plus.gifChapter 7 -- Acquiring Information...
https://acc.dau.mil/UI/img/bo/plus.gifChapter 8 -- Intelligence Analysis...
https://acc.dau.mil/UI/img/bo/plus.gifChapter 9 -- Test and Evaluation (T&E)
https://acc.dau.mil/UI/img/bo/plus.gifChapter 10 -- Decisions Assessments and...
https://acc.dau.mil/UI/img/bo/plus.gifChapter 11 -- Program Management...
https://acc.dau.mil/UI/img/bo/plus.gifChapter 12 - Defense Business System...
https://acc.dau.mil/UI/img/bo/plus.gifChapter 13 -- Program Protection
https://acc.dau.mil/UI/img/bo/plus.gifChapter 14 -- Acquisition of Services
https://acc.dau.mil/UI/img/bo/plus.gifDoD Directive 5000.01
https://acc.dau.mil/UI/img/bo/plus.gifDoD Instruction 5000.02
https://acc.dau.mil/UI/img/bo/plus.gifRecent Policy and Guidance
https://acc.dau.mil/UI/img/bo/plus.gifCurrent JCIDS Manual and CJCSI 3170.01 I
https://acc.dau.mil/UI/img/bo/plus.gifDefense Acquisition Guidebook Key...
ACC Practice Center Version 3.2
  • Application Build 3.2.9
  • Database Version 3.2.9