Thanks for sharing your SAP journey with us @Hadwll When you train your staff make sure you do not just train your staff in SAP transactions, but that you train them in the business process so they understand what they're being asked to do, how to do it and why.

Sorry @Raul Martins and @Herr Schneider missed this topic. I do not have direct experience with what is referred to as Risk Based Work Selection, but I have been actively involved in scope reviews for major turnarounds and these were very much risk based. And very similar to what is described for RBWS in the Becht article in that it was a facilitated review of all turnaround scope with all technical experts in the room and consisted of a risk review of doing the scope in the outage, or not. What worries me in the article by Becht is that they look at benefits vs costs, but very often in heavy industry the turnaround scopes are around addressing integrity and process safety risks which can be hard to express in monetary benefits or people often find themselves risk assessing these risks away because the chance of them happening is so remote. Instead I would simply use a 'standard' 5x5 risk assessment matrix and look at the risk reduction achieved by executing the scope during the outage and then qualitatively compare that against the incurred cost. And then look at the scenario where the scope is not executed in the outage.  

Hi all, In May this year we discussed about a topic named "Using Time Based Maintenance (TBM) to Prevent Failures" (link here). Also, Erik is releasing a course and he sent a few emails last week discussing about how to increase your plant's reliability, in which he talked about the Condition Based Maintenance (CBM) approach on one of these emails. Personally, I am a big fan of this topic and would like to know your thoughts about it this week! Okay, but what is this "Condition Based Maintence"? For those who didn't get a chance to read his email, I will briefly explain here what that is: Differently from TBM, in which you change out parts based on a determined interval for their age-related failure nature, the CBM will change them out based on its condition. In other words, you will only replace your item if it displays signals of damage and a failure is likely to occur prior to your next opportunity (eg.: prior to the next outage). If such item does not show any damage signals or only minor signals that are likely to last until your next shut, then you simply keep it as is and start planning its replacement (more inspections might also be an option). When to use it? On his email, Erik gave an interesting example: "An example of condition based maintenance would be the brake pads we talked about in one of the earlier emails - you regularly check the remaining thickness and once the pads start to get thin you replace them." Basically, the brake pads are not overdue in 12, 24, or 36 months. However, their life is related to the way and how often we use them. In other words, if you brake abruptly you will see a faster wear behaviour, as well as if you drive 2,000km per month instead of 300km, you will also notice more wear. This causes a not age-related failure, but something more random. In this situation, having a 12 monthly plan to replace them would not be as cost effective and would not necessarily increase your car's reliability. An option here would be inspecting the brake pads every X months or Y mileage and replacing it once it reachs is minimum thickness. For random failures, the Condition Based Maintence is a more appropriate approach than TBM. Is Inspecting the only option? No. There are many options that can help you achieve a reliable CBM strategy. They can be inspections as mentioned, but also vibration analsys, oil analysis, ultrasounds and the list goes on and on.   How about you? Do you use CBM on your plant? Have you noticed an better outcomes since using such strategy?   Regards, Raul Martins

Hi @Herr Schneider, To be honest, it is something that I have heard of, but never really worked with. A quick search on Google brought me the links below: https://becht.com/becht-blog/entry/risk-based-work-selection-a-process-focusing-on-turnaround-excellence/; https://roconsulting.biz/wp-content/uploads/2017/06/ROCo-RBWS.pdf; https://www.bicmagazine.com/magazine/risk-based-work-selection-pros-and-cons/ http://www.bakerobrien.com/bakerobrien2/assets/File/APO - RAM Presentation 20081015.pdf   Hope this helps you. If you find something, feel free to share here with us as well.   @Erik Hupje, do you have any experiences using RBWS?   Regards, Raul Martins

I am personally a big fan of using such tools on my daily routine. Usually, I use the Eisenhower Matrix for the tasks that I need to perform when planning my rosters. While Pareto on a more macro level, such as which projects will be prioritized.