Using the RRA^® to Manage Requirements Risk

Objectives

The Requirements Definition Process fails any time a Customer Requirement or Product Design Requirement (Product Design Requirements are Customer Requirements translated into language of design engineers) is released for design that results in a product being designed that does not meet the Customer Requirements.  When this happens both the company who designed the product and the Customer are exposed to risk.  Unfortunately, due to the volume of Customers and Customer Requirements for a product and the fact that some Customer Requirements may compete, it is often impossible to define Customer Requirements and Product Design Requirements that define a product that will meet all the Customer Requirements.

Although meeting all Customer Requirements is the goal, the Customer Requirements and Product Design Requirements must be optimized to define a product that does not exceed a failure rate that is acceptable to the Customer and the Company who designed the product. The RRA^® (Requirements Risk Assessment^®) provides a systematic methodology to allow companies to define Customer Requirements and Product Design Requirements that minimize risk while providing products with best in class benefits.  Using a product of the classes choice, attendees will learn how to use the Requirements Risk Assessment^® (RRA^®) and Design Validation Plan to “risk optimize” Customer Requirements and Product Design Requirements.

The Key role that the RRA^® plays in meeting the risk-based thinking requirements of ISO 9001:2015 and IATF 16949 will also be explained.

If material is presented using a multi-day Workshop, the goal is to provide RRA® and Design Validation Plan of “Customer Delivery Quality” as well as educate attendees on the fundamentals of their use and creation.

Who Should Attend:

All personnel who are responsible for the creation and maintenance of Customer Requirements and Product Design Requirements should attend the class.

Prerequisites

Students must have knowledge of the product that they choose to use for the class exercises. If they exist, Customer Requirements documents and Product Design Requirements for product that documents will be developed for must be brought to the session.

Duration:

Class (One Day); Workshop (Two to four Days depending on product complexity).

Overview

1. Key Concepts Covered:

   1. Why the RRA^® is the most important process a company can implement to reduce risk;
   2. The role of the Requirements Risk Assessment^® (RRA^®), Design FMEA (System, Subsystem, Component), Process FMEA, Design Validation Plan, Design Verification Plan and Process Control Plan in Risked Based PLM^®;
   3. Linkages between RRA^®, Design FMEA, Process FMEA, Design Validation Plan, Design Verification Plan and Process Control Plan;
   4. Common mistakes made when capturing the voice of the customer;
   5. Detecting and defining “undefined customer requirements”;
   6. High cost of incorrect or undefined customer requirements;
   7. Common mistakes made when defining design requirements;
   8. High cost of incorrect or undefined design requirements;
   9. How the customer type affects the RRA^® methodology to be used;
   10. Step by step method for performing RRA^®.

Get Training!