| QG3: Prioritizing Requirements: NUDs and ECOs |
| CPD&M has two categories to distinguish the risk profile of requirements and their fulfilling parameters through a given technology/system/product architecture: high-risk is NUD, low-risk is ECO.
Requirements or a set of design/process control and noise parameters are categorized as NUD if they are:
- New to you and to all who work in your field or compete in your market. No one is able to prove, with data, that they can fulfill it. Risk is due to both a lack of knowledge (judgment) and experience.
- Unique to you. These are currently being fulfilled in your field or market, but you are not fulfilling it. It presents significant risk because you are not yet proving with data that you, too, can fulfill it. You lack both knowledge (judgment) and experience, but your competitor or peers do not - they are ahead of you and may have this risk well in-hand.
- Difficult for you to fulfill. These may or may not be New or Unique, but they are challenging for you to fulfill. This is the most common source of significant risk. You may have data as a result of attempts to fulfill this difficult requirement showing you are incapable of fulfilling it. The risks may be due to lack of data and/or well-known gaps from actual data.
If a requirement or set of design/process control and noise parameters is new, unique or difficult (NUD), then it is a candidate for critical status, until proven otherwise. It takes time and money to gain judgment and experience around these candidate NUD requirements and the parameters that will fulfill them.
Requirements or a set of design/process control and noise parameters are categorized as ECO if they are:
- Easy for you to fulfill. You have both knowledge and experience on how to do it. Risk is manageable and low for you in this area because you have the hard data to prove it.
- Common to your field or competitive market. Everybody is pretty much at parity over fulfilling this requirement. It is well known to all and all are capable of meeting this requirement.
- Old; it has been around for a long time and a great deal is known about its subtleties and nuances relative to fulfilling it. There is a lot of literature and insight that is readily available to fulfill this requirement.
ECO requirements and their fulfilling parameters are proven to be worthy of our trust because they are well characterized and possess sufficient data to prove that their use in a new technology or product design is reasonably the same as previous applications. Because of this, the team needs far less development work on ECO parameters as they do on NUD parameters.
|
| QG4: The Design Guide |
| A responsible development project team documents what they have learned in a Design Guide. The Design Guide is a resource for all future development or production teams that will leverage or manage the design through its life. This includes an explanation of how the design works and what parameters (Xs) control its various outputs (Ys) across and within the system. It also explains what sources of unwanted variation (noise factors) are statistically significant as they affect the mean and standard deviation of the measured Y outputs. All Y-as-a-function-of-x relationships and parameters that cannot pass the Big 7 metrics should be characterized for the risk they carry, along with recommendations to mitigate the risks as the design is transferred into product development or production operations. The Design Guide is the repository for all data acquisition system, measurement instrumentation design, and critical parameter learning as it unfolded during the development project.
Recommended Design Guide TOC
A Design Guide should contain the following documentation:
- Voice of Customer and Voice of Stakeholder Needs statements
- Classified as NUD or ECO, Grouped/Affinitized, Ranked and Prioritized
- Product and Sub-level Technical Requirements documents
- Requirements classified as NUD or ECO, Grouped/Affinitized, Ranked and Prioritized
- Each requirement must have a documented measurement method to prove it can be met
- Alternative Design Concepts and the final Design Concept
- Pugh Process Documents that illustrate how the final superior concept was selected.
- Functional Flow Diagrams, Input-Output-Constraint Diagrams, Basic Parameter Diagrams, Robust Design Parameter Diagrams, Tolerance Parameter Diagrams, and System Integration and Performance Balancing Diagrams
- A set of related functional diagrams that illustrate each function within the design and how they occur in time sequence (hierarchy of serial-parallel flows)
- A set of parameter diagrams that illustrate the parameters (Xs) that govern the functional performance (Ys) of the design
- A set of Noise Diagrams and their points of noise transmission across the integrated system
- All major tolerance parameter relationships and stacks that limit variation such that the design can meet required functional and assembly performance goals
- A final system integration and performance balance model that illustrates how the subassemblies and subsystems parametrically interface / integrate to meet all system level performance and assembly requirements
- Modeling and Simulation information and summary results
- Summary of all analytical math models and simulation analysis; software used and location of code
- Designed Experimentation and Robust Design information and summary results
- Summary of all DOEs, analysis results (ANOVA Tables, Main Effects, Interaction and Response Surface Plots)
- Tolerance Analysis and Experimentation information and summary results
- Summary of all Computer and DOE-based analysis results (tolerance stack model, Monte Carlo simulation and ANOVA results from DOEs)
- System Performance Analysis and Experimentation and summary results
- Summary of all Computer and DOE-based analysis results (ANOVA results from DOEs)
The Design Guide should conclude with summary recommendations and guidance on all parameters that are "at risk" because they failed or had weak fulfillment of one or more of the Big 7 metrics. The down-stream recipients of the Design Guide should be able to use it to understand how the design works at a parametric level, apply it for product, production and service/maintenance diagnostics, problem solving and technical change management and decision making.
|
| Links to Prior CPD&M Quick Guide Newsletter Issues |
|
Below are links to each of the prior newsletters with CPD&M Quick Guides:
The CPD&M Quick Guide TOC (Nov 2013)
CPD&M Intro & Process (Jan 2014)
|
| |
Is there a topic you'd like us to write about? Have a question? We appreciate your feedback and suggestions! Simply "reply-to" this email. Thank you!
Sincerely,
|
Carol Biesemeyer
Business Manager and Newsletter Editor Product Development Systems & Solutions Inc. |
