This standard requires the developers and customer/users working as a team to plan and implement a reliability program that provides systems/products that satisfy the userÂ¿Â¿Â¿s requirements and expectations. The userÂ¿Â¿Â¿s requirements and needs are expressed in the form of the following four reliability objectives:
- The developer shall solicit, investigate, analyze, understand and agree to the userÂ¿Â¿Â¿s requirements and product needs. The developer, working with the customer and user, shall include the activities necessary to ensure that the userÂ¿Â¿Â¿s requirements and product needs are fully understood and defined, so that a comprehensive design specification and Reliability Program Plan can be generated.
- The developer shall use well-defined reliability- and systems-engineering processes to develop, design, and verify that the system/product meets the userÂ¿Â¿Â¿s documented reliability requirements and needs. The developer shall implement a set of engineering activities (included in this standard as normative activities and informative activities, refer to Section 3) so that the resulting system/product satisfies the customerÂ¿Â¿Â¿s documented requirements and needs.
- The multifunctional team shall verify during production that the developer has met the userÂ¿Â¿Â¿s reliability requirements and needs prior to fielding. The developer shall include activities that assure the customer that the reliability requirements and product needs have been satisfied.
- The multifunctional team shall monitor and assess the reliability of the system/product in the field. The team is responsible for identifying the data elements to assess the reliability of the system/product in the field and to ensure the data collected are accurate and complete. The team will establish a closed-loop feedback method to flow recommended improvements (corrective actions) for monitoring reliability growth.
- Number of Pages:
- File Size:
- 1 file , 940 KB
- Redline File Size:
- 2 files , 4.8 MB