Carl and Fred discussing the attributes of good reliability requirements, and how they can be used to improve the reliability requirements setting process.

Join Carl and Fred as they discuss the nature of reliability requirements, and how to assess their goodness.

Topics include:

Enjoy an episode of Speaking of Reliability. Where you can join friends as they discuss reliability topics. Join us as we discuss topics ranging from design for reliability techniques to field data analysis approaches.

Reliability requirements are stated as probability statements measurable by test or analysis during the product development timeframe. They are not goals or non-measurable allocated numbers.

Reliability requirements are benchmarked against target competition, when possible, so that requirements execution exceeds Best in Class.

Functional product requirements are well defined so that the measurable reliability requirements relate to their intended function .

A clear statement of time (such as hours, cycles, miles, etc.) must be specified as part of the reliability requirements.

The combined customer usage and operating environment profiles are adequately defined in product requirements, and the corresponding tests duplicate actual field failure modes.

The allowable degradation over time is defined in the requirements and represented by tests.

The requirements include a clear definition of product failure, and this definition is incorporated into tests. It is preferred that components or subsystems are tested to failure as part of Reliability demonstration.

All reliability requirements are balanced with other vehicle & subsystem performance objectives, and are agreed to by project management.

Assumptions about test-to-field correlation or failure distributions are valid.

Reliability Requirements are incorporated into technical specifications and thereby into subsystem & component validation plans.

The post SOR 608 Attributes of Reliability Requirements appeared first on Accendo Reliability.