By Fred Schenkelberg
A reasonable model helps you make informed decisions. In many cases, a simple reliability block diagram provides the insights your team needs to prioritize and achieve the desired reliability performance. Let’s create, populate and use RBDs effectively.
RBDs comprise of a few simple elements and arrangements, yet are capable of describing a wide range of products and systems. There are a few assumptions to keep in mind, and a few basic ways to create a useful model for your system.
Let’s discuss the elements that make up a useful reliability model and how you can craft a model to get you and your team started talking about reliability. Drawing the model is one step, populating the RBD with reliability targets is another. Adding reliability estimates brings power to the model.
The RBD model is just a model. It allows you and your team to identify reliability improvement priorities, focus resources where they will make the most difference, and permit tracking of reliability progress toward a goal. The model itself is not the objective, as with many reliability tools, it’s what you do with the model that matters.
Let’s discuss a few best practices for effective use of your RBD model.