top of page

Want to become the best reliability engineer you can as fast as possible?

KNOWING the purpose of reliability engineering activities and then being able to go and do them makes YOU a valuable asset to your organization.


(40 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 


The logo for "Ed Virtus" our partner in Reliability Engineering programs.

Acuitas has partnered with Australian systems engineering training provider edVirtus to deliver this and a number of other courses. This course will be delivered with edVirtus starting in the morning of your timezone. Please check out edVirtus to learn about this and lots of other fantastic courses for managers, project managers, systems engineers and technologists in general. 


Sydney S.


... fantastic introduction to the things you need to consider when managing an organization that designs or manufactures equipment ...

David R.

... this is much better than my high school probability and statistics lessons ... this course actually makes sense and I now feel confident using probability and statistics on my own ...

Florian R.

... I will never use the mean time between failure (MTBF) as a reliability metric ever again because now I realize that we need to focus on reliability ...

Toby S.

... the link between reliability engineering and reducing production budgets and schedules was something I never realized - but I can now make the case for my own team to do it ...


You can't talk about reliability without also talking about availability and maintainability. Or RAM. Which is what you want when you are designing a new 'thing.' Or purchasing that 'thing' from someone else. You need to know how valuable RAM is, how your organization needs to be postured to get it, and how you make sure you end up with it when you have done all that other stuff. 

This course was developed to help everyone ranging from an engineer in a start-up trying to get a more reliable product to the market faster than their competitors, through to a military vehicle project manager. And everything in between. Because it's main focus is making you a better RAM engineer.

This course ties a lot of management and practitioner elements together. It combines the 16-hour Reliability Management Course (which introduces higher business and reliability concepts) with the 24-hour Reliability Practitioners Course (that focuses more on the application of the methods to link reliability with business).

What does this course look like?

The course is broken down into 10 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 engineering. This is only the start of your reliability and RAM learning process, but you will be able to go back to your workplaces armed with the ability to understand the value of reliability and how it helps your business. Which makes you a better engineer.

​Module 1 - Why is reliability valuable to you? Where we start to talk about the value of reliability engineering and how to work it out for your organization.

Module 2 - What is reliability to your organization? Which includes how we go about defining what we want to get in terms of RAM and the (high-level) approach to getting there.

Module 3 - How does your team make reliability happen? Where we talk about how your organization gets from where it is now to one that can create value from your reliability.


Module 4 - How do YOU make reliability a thing? Reliability happens at the point of decision - and by decision we mean something that influences the design or configuration of your thing. Which means you need to 'win friends' and value good behaviors. And lead.


Module 5 - 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 6 - 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 7 - 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 8 - 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 9 - 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 10 - 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 stuff for you below if you need a more formal understanding of how this course can help you.

Acuitas-WebsiteVisuals2024-02-12 at 2.31.34 PM 4.png
bottom of page