Your Reliability Engineering Professional Development Site
A listing in reverse chronological order of articles by:
In my last article the high level goal of lean product development was established as follows:
Develop products that maximize customer value and minimize product cost, in the least amount of time, and at the least amount of product development cost.
Let’s analyze this goal statement and establish some high-level objectives. [Read more…]
Lean product development might mean different things to different organizations, but let’s start with the 5 principles of lean manufacturing and see how it can be applied to the product development process. [Read more…]
Hey Ash,
I have a question about whether I should stay in my current engineering job or pursue other options.I work for an engineering firm that does contract work for other companies. We have recently lost a big contract. With this lull, I have been told that much of my work over the next several months will basically be document control.
As a new engineer, I am concerned that I will be missing out on valuable experience if I am not working on strong engineering projects.
So my question is, should I stick it out or look for another job?
Thanks,
-Anonymous
One of several reasons for emphasizing product requirements includes enabling modeling and simulations of designs, as well as ensuring adequate verification and validation testing.
Recall the fundamental framing of a requirement as:
Note the framing (within the requirement) of a mathematical and/or experimental relationship where “Y” is the output as a function of “(x)” as the input….Y = f(x) or as a function of multiple inputs Y = f (x1, x2, x3…xn). Let’s expand on this for a moment:
While previous articles focused on requirements writing, another element of products requirements is design constraints.
A design constraint might not be a requirement in the purest sense, but must be accommodated in product requirements (and, ideally, identified as such). Design constraints almost always make their way into product requirements.
Let’s use a simple example whereby a specific housing material is specified (a polyester thermoplastic elastomer).
The requirement might simply be: “The housing material shall be made of a polyester thermoplastic elastomer”. The PRD is then provided to the designer, essentially telling him he must use this material.
I’ve teamed up with Skylar Wooden, a Technical Writer, and Katie Butler, a CPA, the ladies behind Pare and Flourish to bring you some technical writing tips for engineers. 
Engineers are incredibly knowledgeable people. You understand how to design and build the most complex of structures. You analyze and evaluate intricate data. But, many engineers miss one of the most important aspects of any profession—explaining your work to others. Whether it’s to tell someone how to perform a task, or report on a project to a superior, relaying information is just as critical as knowing the information.
As an engineer, you can offer your expertise in two ways: verbal or written communication. You likely deal with the verbal aspect of this on a daily basis when you answer questions, explain a process, or even talk about your job with your friends. So, how often are you writing? [Read more…]
Managing requirements for complex systems can be challenging, however, establishing a hierarchical framework of key questions (answered at each layer of the hierarchy) can be quite helpful.
While some regulatory authorities (such as the FAA) may require various layers of documentation and traceability, this article isn’t necessarily advocating a bureaucratic development process. The process can be scaled based on the complexity of your system, your ability to model it’s (system) design performance and/or based on the amount of product development risk the organization is willing to assume. [Read more…]
In this article we’ll explore the topic of requirements, and attitudes about identifying requirements before the design work begins.
In my experience, I’ve had design resources literally state “I hope there are no requirements”. (Unconstrained design and no requirements certainly made this designer’s job much easier.)
There are several other reasons requirements are sometimes neglected:
One of the best pieces of career advice that I have ever heard is to treat your career as a company, of which you are the CEO. And like any company, your career will need a guiding principle that will help you stay focused on your purpose. Companies today would not think of operating without a mission statement to guide them. However, too many of us skip this critical aspect of running our own careers. [Read more…]
In recent articles I focused on a ‘linear’ approach to product development by understanding customer needs, establishing requirements (“what the design provides”), establishing a conceptual design, etc.
In this article, I’ll discuss a framework whereby an idea for a product or design might kick-off the process.
Also, rather than a commercialized product, we will assume our goal is to successfully demonstrate the idea’s feasibility. (This is common for a start-up company, where the business model might be to demonstrate product success with a goal of obtaining more venture capital, or to sell the intellectual property. Alternatively, a large company might want a separate idea development process that takes invention off the critical path.)
The Hot Shot Rule is a way to be your own coach in seeing what is possible and what needs improving.
Basically, you ask yourself, “If a hot shot took over my job today, what is one thing they would think is unacceptable?” And then go address that one thing. [Read more…]
I am a parent of two young children. As a result of my experiences as a mom, I feel that parents make great Reliability Engineers because there are so many shared skill sets. Please enjoy this lighthearted comparison to start your week out with a little humor.
First, I have to point out the development of a brand new Reliability Engineer requires the same skills of lubrication and vibration that the conception of a child requires. [Read more…]
Significant savings in product development costs can be realized with robust validation processes, starting with requirements validation. Validation confirms the product meets customer needs for the products intended use, and answers the question “are we designing the right product?” The “right product” therefore starts with the “right” product requirements. Even a product designed with detailed requirements, but incorrect specification limits, can be considered the “wrong product” (since the product would be rejected by the customer.) [Read more…]
Quality Function Deployment (QFD) is an excellent tool to ensure linkage of customer needs to product requirements. This article will provide a high-level overview on creating a ‘first-level’ QFD and how it can be used to guide design optimization.
(There are many additional features of QFD , however, and readers of this article are encouraged to research the methodology further.)
As stated above, we use the QFD matrix (similar to a cause-effect matrix) to ensure linkage of customer needs to product requirements using the critical thinking / questions as follows: [Read more…]
If a manufacturing plant was a human brain: Maintenance would be the repairing blood flow, Operations would be the electricity sparking between synapses, and Reliability would be the conscience. [Read more…]
