top of page

You need to do reliability engineering with confidence.

There are hundreds of reliability engineering activities...
and hundreds of ways of doing each of them wrong!


(24 hours)

  • Virtual (synchronous) delivery

  • Video lessons recorded with 12 month access

  • Downloadable INTERACTIVE PDF workbook

  • Includes ONE on ONE interaction with instructor

  • Can be delivered specifically to your ORGANIZATION

  • Scope for TAILORING content 


Louise B.

... I usually find probability and statistics hard, but the way it is taught on this course made it as easy as possible for me to understand ...

Kat B.

... we used to just follow the standard approach for testing – we won’t
anymore  ...

Haley S.

...This is not just relevant for reliability engineering … it is relevant for all engineering ...

Tim N.

... If you don’t know this stuff, you can’t call yourself a reliability engineer ...


This course is all about planning and implementing the vital few reliability engineering activities that will ultimately create reliable systems, products, machines, services or processes. This includes an overview of probability, statistics, test planning, key Design for Reliability (DfR) activities and several other related topics.

This course teaches how to identify which reliability engineering activity best informs key decisions associated with the reliability design and asset management cycles. This includes reliability (goal) allocation to provide direction and guidance at the subcomponent level. It includes system reliability modelling to analyze overall reliability performance based on component reliability characteristics. We teach data and statistical analysis that includes Weibull probability plotting to interpret failure data into meaningful information. Baseline activities like Failure Mode and Effects Analyses (FMEAs) and Root Cause Analysis (RCA) are also introduced. We also discuss maintainability and how reliability interfaces with logistics engineering.

Students will be taught to focus on the ‘vital few’ ways our product, system, service or process can fail. Which means we only need to worry about the ‘vital few’ things we need to do to increase reliability quickly and cheaply. The key focus is being able to understand the probabilistic nature of reliability performance and analyse failure data to inform key decisions. This includes understanding key probability distributions (such as the Weibull distribution) and being able to use this knowledge to do things like design reliability tests.


The course is broken down into 6 modules. Each module is made up of 4 x 1-hour lessons delivered over a period of two weeks. But don't forget ... you will have access to the recorded lessons for 12 months.

The fundamental aim is to introduce students to reliability practice. This allows you to implement all the reliabiltiy engineering activities your overall strategy demands.

​Module 1 - How do we stop failure happening? 
Which is the opposite of 'dumb design.'  Here we talk about design activities and how we deal with the (unfortunate) uncertainty we always see when we talk about RAM.

Module 2 - How do we tolerate things not being perfect? 
Where we start to look at designing (and modelling) systems with redundancy and other tricky little things that mean it won't stop working when something bad happens.

Module 3 - How do we describe (random) failure?
Where we start to think about how we describe the random nature of failure in a way that helps us. Oh, and this is where we talk about probability distributions.

Module 4 - How do our components fail?
Where we use some of the things we have learned to try and describe what we think is happening.
Which means we can then fine-tune what we think when we get data.

Module 5 - How reliable are our components, and our system?
Where gather data to create information - remembering that we need to understand how confident we are
in the outcomes.

Module 6 - How do we keep our things working?
Where we make sure our 'thing' is easy to maintain, manufactured or coded in a way that minimizes defects, and helps inform how much support it needs. And then go do it!


We have more more stuff for you below if you need a more formal understanding of how this course can help you.

bottom of page