Category: Reliability

ICML 55 – the revolution in the lubrication sector

ICML 55 – the revolution in the lubrication sector

What is ICML 55? ICML 55 is revolutionizing the lubrication industry! It is so exciting to be around at this time when it has... ...
5 Habits of an Extraordinary Reliability Engineer – My review

5 Habits of an Extraordinary Reliability Engineer – My review

Peter Horsburgh has essentially captured the 5 Habits of an Extraordinary Reliability Engineer in his book! His style of writing appeals to engineers as he keeps... ...


Root Cause Analysis has always been dear to my heart. The procedure involved in finding the root causes and addressing them have intrigued me greatly... ...

ICML 55 – the revolution in the lubrication sector


What is ICML 55?

ICML 55 is revolutionizing the lubrication industry! It is so exciting to be around at this time when it has started its implementation. For those who aren’t aware of ICML 55, here are a couple of notes on it.

ICML 55 was born out of ISO 55000 which speaks to Asset Management. From this standard, 3 standards were developed to guide the lubrication industry since no previous standards existed within the lubrication industry.

  • ICML 55.1 - Requirements for the Optimized Lubrication of Mechanical Physical Assets
  • ICML 55.2 - Guideline for the Optimized Lubrication of Mechanical Physical Assets
  • ICML 55.3 - Auditors' Standard Practice and Policies Manual

ICML 55.1 has already been completed, while 55.2 should be done at the end of this year and 55.3 scheduled for 2020.

These are exciting times!

Here’s the official press release:

While ICML 55.1 was only launched in April of this year, it is a standard that the lubrication industry has been in need of for several years. It addresses the “Requirements for the Optimized Lubrication of Mechanical Physical Assets”.

What exactly are the assets covered? Here they are:

  • Rotating & Reciprocating Machines, Powertrains, Hydraulic Systems and lubricated subcomponents
  • Assets with lubricants that reduce friction, wear, corrosion, heat generation or facilitate transfer of energy
  • Finished products from API categories I-V
  • Non Machinery support assets (Personnel, policies, procedures, storage facilities and management)


Photo Credit:
Photo Credit:

ICML 55.1 speaks to the “Requirements for the Optimized Lubrication of Mechanical Physical Assets” it also describes and defines 12 interrelated areas that can be incorporated in a lubrication program. This has never been officially documented before, nor has any standard been published as a guideline for lubrication programs.

The 12 areas are outlined below:

  1. SKILLS: Job Task, Training, and Competency
  2. MACHINE: Machine Lubrication and Condition Monitoring Readiness
  3. LUBRICANT: Lubricant System Design and Selection
  4. LUBRICATION: Planned and Corrective Maintenance Tasks
  5. TOOLS: Lubrication Support Facilities and Tools
  6. INSPECTION: Machine and Lubricant Inspection
  7. LUBRICANT ANALYSIS: Condition Monitoring and Lubrication Analysis
  8. TROUBLESHOOT: Fault/Failure Troubleshooting and RCA
  9. WASTE: Lubricant Waste Handling and Management
  10. ENERGY: Energy Conservation and Environmental Impact
  11. RECLAIM: Oil Reclamation and System Decontamination
  12. MANAGEMENT: Program Management and Metrics

As per ICML's website, here's a list of people that the new standard can benefit:

Photo Credit:


Check out the ICML 55 standards today and apply it to your organization!

5 Habits of an Extraordinary Reliability Engineer – My review

Peter Horsburgh has essentially captured the 5 Habits of an Extraordinary Reliability Engineer in his book! His style of writing appeals to engineers as he keeps the content directly on point and provides case studies to each of his chapters. Most engineers aren’t big readers (except for manuals and when absolutely necessary) but the conversational tone in which Peter explains some of his revelations about the industry ideally captures the attention of reader. I couldn’t put the book down once I started reading it!

What I really love about this book is that it was holistically designed for engineers. The book is small allowing persons to carry it around anywhere and it isn’t too thick to daunt the reader into thinking that they need to allocate a couple of days to reading it. Peter has kept the chapters short, driving the various points home and has even provided summaries for each section of the book. This makes it super easy when trying to relate to an issue that he has discussed. Peter has also done an excellent job with the illustrations in the book to keep the reader’s attention and provide for some light amusement to keep the book as a guide that engineers want to return to time and time again

Additionally, an extra step was taken to ensure that the book has some durability built into it. The pages aren’t the ordinary soft paper, rather the pages have a bit of a card stock finish. This was my first light bulb moment after opening the book (there were tonnes more light bulb moments while reading it!). Obviously the pages had to be durable! This book was meant to be in the workshop with the engineers becoming part of their manuals! I can clearly see engineers rushing back to this book during the course of the day to get back to a particular chapter or case study that can assist them in some issue of the day.

I definitely enjoyed this book! Peter first introduces the reader to the 5 Don’ts of Reliability Engineering. I hadn’t realized until then that the “Don’ts” that were covered form critical parts of any Reliability Engineers’ day! The manner in which he introduces these stood out for me, as he brought in case studies to demonstrate instances where he dealt with some of these “Don’ts” or even performed them himself. It is with these case studies that I appreciated that some of the situations that I face daily may receive a “Don’t” when it shouldn’t. With Peter’s story telling ability, he was able to truly relate to the readers the practical examples of things that should and shouldn’t be done. Unlike other books, he demonstrates the impacts (and throws some financials in there as well, which helps us to actually quantify what we’re looking at) of particular “Don’ts”.

Right after the “Don’ts” section, he launches into the “5 Habits” which are each covered in their own Chapters. While he explains the habits in this section, he then further dedicates each Habit to a Section (not just a Chapter) where he mixes in his real life experiences as his Case Studies while providing introductory information on the habits and their impacts on the plant and its reliability. Quite skilfully, afterwards he dedicates a Section to “Applying the habits”. This is in keeping with the conciseness of the book!  

I would highly recommend that all Reliability Engineers add this book to their library! It’s a book that gets all the lightbulbs blinking in your head from the moment that you begin reading it. However, it is not a book to be read just once, it needs to form part of your routine (either weekly or monthly). After reading this book, I can almost guarantee that the week that you spend in work afterwards will be nothing short of interesting as you may find yourself thinking… “Peter covered this in his book…let me just look back and verify if this can be dealt with in another way”. That being said, I believe that any engineer will make it part of their “consultation” guide especially during brainstorming sessions. It was indeed a pleasure reading this book! 

Check out his website for more info on getting this amazing book!


Root Cause Analysis has always been dear to my heart. The procedure involved in finding the root causes and addressing them have intrigued me greatly as it involves using all your data gathering and cognitive skills. In the past, it was a bit difficult to properly perform RCAs since it usually meant jumping around different types of software. For instance, depending on the type of analysis that I wanted carry out, I would either use a Fish Bone Diagram or Cause and Effect Logic Tree. Depending on the type that I needed to use, I would have to switch programs just to get these generated. Then, there’s the issue of writing the final report and utilizing my expert copy and paste skills with Microsoft word while toggling excel worksheets to determine the costs attached to the failure.

Needless to say, I was very impressed when introduced to the PROACT software. It has an extremely friendly user interface (in some cases, I can even use drag and drop options!) which is very easy to navigate even for a beginner like me at the time. What I really love about the software is that it bridges the gaps and guides users (both for beginners and experts) on the RCA process. By allowing users to follow a step a by step process it ensures that users don’t forget vital pieces of information that are absolutely critical to the RCA.

If you are familiar with RCA, you will be aware that the basis of any RCA is properly establishing the Severity of the failures. As such, the first step when the user enters the software, is the assigning of the Severity of the failure with the Severity Calculator. This calculator can even be customized for varying applications! Afterwards, the profile of the failure is then defined. This profile allows the user to identify elements that may have been forgotten if the RCA was being done from scratch. The Severity Calculator also allows users to determine the type of analysis that is fit for the severity index. Depending on the severity, the user can be guided to use either; 5 Whys, Fish Bone Diagrams or Cause and Effect Logic Trees. This is definitely one key advantage since it allows for different forms of analysis based on the severity.

Next the Critical Success Factors are inserted. The strategic placement for the input of these factors at this point in the analysis is purely genius! It forces the user to determine which factors directly impact them and these are usually placed on the final report. These CSFs start shaping the pending RCA into the mould that we need. Once these CSFs are established, then the objectives need to be defined. These help the analyst in guiding their RCA and ensuring that it is kept focused. It is easy to become distracted when performing these types of analyses since users are presented with an abundance of information. The definition of these aspects help the analyst to keep on track.

As with any RCA, there must be a team involved. The PROACT software allows users to delegate different tasks to different team members! It can even track the status of these events. Instead of sending long reminder emails (which tend to choke one’s inbox and can be easily missed), it is essentially easier to view the status of the assigned tasks using the PROACT software. This is a definite advantage of the software!

Now to the core of the software, the development of the RCA! Users are allowed to define the event that lead to the failure. Here’s where the software gets very interesting!!! Users can pull from existing templates dependent on the type of failure! This is the highlight of the PROACT software for a user like myself! It is very interesting to view templates (there are over 300 templates) of common failures and compare these to what the user has actually experienced. It allows the user to be able to access years of experience of a consultant at their fingertips! The team at Reliability Center Inc have definitely put a lot of work into developing these templates and have drawn upon their actual field experience for the past30+ years! This is the absolute game changer for the software!

During the building (or growing) of the Cause and Effect Tree, the user is allowed to authenticate their hypotheses and can attach pictures from the failure as verification for ruling out or accepting that mode as one of the root causes. These pictures can then be input into the final report without the need for cropping, cutting and pasting and all the exciting formatting issues that tend to occur when trying to include pictures in the final report.

PROACT also allows for users to input financial data. Another game changer for me! Users can define the costs associated with the downtime for particular failures, repair costs or even manpower costs. These all help to put a financial value on the cost of the failure being investigated. This neat trick is crucial for the review by upper management! Additionally, the final steps in any of the RCAs is to determine recommendations for the latent causes that were determined. These will be the courses of action to be taken to prevent failures of this nature from occurring in the future.

Overall, the PROACT software is indeed a time saver, keeps excellent track of the findings and collections of the investigation at hand and produces a very succinct, detailed report that anyone from upper management to the engineers can clearly understand. I love working with this software and my clients are always very impressed that this type of software actually exists and is so easy to use! I would highly recommend any user (novice or expert) in the reliability field to use the software in their everyday tasks and realize the impact that it has on increasing the efficiency of RCAs and their ROIs to their organizations.

More information can be found at