At one time or another all of us have been the “new” reliability engineer on the block. You have been given a set of expectations from your boss to either ensure that your product is 1)”good enough” and ready for production or 2) will meet the expected “reliability”. So as the “newly” minted reliability engineer where do you start?
In this blog we will discuss tools/best practices for the “new or seasoned” reliability guru to guide you on your journey. So, to get things started just what exactly is reliability engineering anyway?
One definition is as follows: Reliability engineering is the function of analyzing the expected or actual reliability of a product, process or service, and identifying actions to reduce failures or mitigate their effect. In addition to this definition, reliability engineering can be done by reliability engineers, design engineers, quality engineers, or system engineers.
The overall goal of reliability engineering is to make your product more reliable in order to reduce repairs, lower costs, and to maintain your company’s reputation. In essence reliability engineering should be done at all levels across the product development life cycle.
Any and all opinions are welcome as we kick-off this blog on “Best Practices” and if you have a differing view on what is reliability engineering I’d be glad to hear from you on this site.