{"id":6958,"date":"2016-07-15T12:41:52","date_gmt":"2016-07-15T17:41:52","guid":{"rendered":"http:\/\/www.livingreliability.com\/en\/?p=6958"},"modified":"2025-11-08T16:14:21","modified_gmt":"2025-11-08T21:14:21","slug":"lrcm-reliability-analyst-survey-results","status":"publish","type":"post","link":"https:\/\/www.livingreliability.com\/en\/posts\/lrcm-reliability-analyst-survey-results\/","title":{"rendered":"LRCM reliability analyst survey results"},"content":{"rendered":"\n
\n
\n
\n
    \n
  1. How does LRCM speed<\/em><\/strong> of failure mode instance selection compare with the pick list method on the legacy work order entry form.<\/span> (10=vastly superior, 1=same or worse).\n
      \n
    1. 7<\/li>\n\n\n\n
    2. 10<\/li>\n\n\n\n
    3. 1 [1<\/a>]<\/sup><\/li>\n\n\n\n
    4. 8<\/li>\n\n\n\n
    5. 8<\/li>\n\n\n\n
    6. 8<\/li>\n<\/ol>\n<\/li>\n\n\n\n
    7. How does the LRCM work order \u201ctreeview\u201d structure compare to previous (drop-down lists) with regard to the quality<\/em><\/strong> of information entered on the work order?<\/span> (10=vastly superior, 1=same or worse).\n
        \n
      1. 7<\/li>\n\n\n\n
      2. 8<\/li>\n\n\n\n
      3. 1<\/li>\n\n\n\n
      4. 8<\/li>\n\n\n\n
      5. 8<\/li>\n\n\n\n
      6. 9<\/li>\n<\/ol>\n<\/li>\n\n\n\n
      7. How does LRCM ease<\/em><\/strong> of failure mode selection compare with the legacy EAM work order entry form.<\/span> (10=vastly superior, 1=same or worse).\n
          \n
        1. 7<\/li>\n\n\n\n
        2. 9<\/li>\n\n\n\n
        3. 1<\/li>\n\n\n\n
        4. 8<\/li>\n\n\n\n
        5. 9<\/li>\n\n\n\n
        6. 9<\/li>\n<\/ol>\n<\/li>\n\n\n\n
        7. What is still missing that would improve the quality of information needed for the reliability analysis of your fleet\u2019s failure modes?<\/span>\n
            \n
          1. Improve the EAM\u2019s response time. Mesh often has to wait for the EAM. Reports (such as the Qlik dashboard) that would allow us to better monitor the quality of the data entered via the work order.<\/li>\n\n\n\n
          2. The technician is the best information source. But since he is providing that information via the dispatcher by radio, there is loss of precision. Improve dispatcher competency.<\/li>\n\n\n\n
          3. We have lost 10 years of valuable information by switching to Mesh.<\/li>\n\n\n\n
          4. Update the feedback suggestions in the RCM knowledge base more frequently.<\/li>\n\n\n\n
          5. Syncronization between the EAM codes and the RCM knowledge base should be executed more frequently. There are orphan codes on both the EAM and Mesh ends.<\/li>\n\n\n\n
          6. When a dispatcher is replaced the new dispatcher\u2019s lack of familiarity with the RCM hierarchy results in incorrectly selected failure modes. Direct access by the technicians using a tablet or smart phone would improve this situation.<\/li>\n<\/ol>\n<\/li>\n\n\n\n
          7. What benefits have you obtained by having better quality work order data?<\/span>\n
              \n
            1. I have identified opportunites for improving maintenance policies for mitigating the consequences of specific failure modes.<\/li>\n\n\n\n
            2. I reduced the time I use to perform analysis.<\/li>\n\n\n\n
            3. I still need to do too much data cleaning due to errors.<\/li>\n\n\n\n
            4. The RCM knowledge base is still quite out of date in many areas.<\/li>\n\n\n\n
            5. We managed to slightly improve the quality of information. According to records, in 2015, we have a 35% dispersion of data that are incorrectly assigned to a component or system. Previously we were between 50-55% of dispersion. I hope to see more of an improvement to 80% error free or more.<\/li>\n\n\n\n
            6. The quality of the analysis is improved substantially. The analysis time has been reduced since the information is complete and we can get it in a single report.<\/li>\n<\/ol>\n<\/li>\n\n\n\n
            7. Assess your ability to perform effective reliability analysis before the implementation of Mesh.<\/span> (10=Excellent, 1=ineffective).\n
                \n
              1. 3<\/li>\n\n\n\n
              2. 5<\/li>\n\n\n\n
              3. 10<\/li>\n\n\n\n
              4. 6<\/li>\n\n\n\n
              5. 9<\/li>\n\n\n\n
              6. 2<\/li>\n<\/ol>\n<\/li>\n\n\n\n
              7. How would you rate your reliability analysis effectiveness after the implementation of Mesh.<\/span> (10=Excellent, 1=ineffective).\n
                  \n
                1. 7<\/li>\n\n\n\n
                2. 8<\/li>\n\n\n\n
                3. 1<\/li>\n\n\n\n
                4. 7<\/li>\n\n\n\n
                5. 7<\/li>\n\n\n\n
                6. 9<\/li>\n<\/ol>\n<\/li>\n\n\n\n
                7. How is your ability to evaluate and optimize maintenance strategies now in comparison to the time prior to Mesh.<\/span> (10=vastly superior, 1=same or worse)\n
                    \n
                  1. 7<\/li>\n\n\n\n
                  2. 6<\/li>\n\n\n\n
                  3. 1<\/li>\n\n\n\n
                  4. 7<\/li>\n\n\n\n
                  5. 9<\/li>\n\n\n\n
                  6. 7<\/li>\n<\/ol>\n<\/li>\n\n\n\n
                  7. What more is needed to improve your analysis capabilities?<\/span>\n
                      \n
                    1. We still need cleaner information. The dispatcher who is actually entering the data in mesh must become expert in the subject to avoid mis-communication and so that he can support the technician over the radio in selecting the right failure modes and event types. The EAM should also be faster (IT project under study) so that he dispatcher has enough time to record the data properly.<\/li>\n\n\n\n
                    2. Greater focus by the dispatcher in the reliability and precision of the information transmitted by the technician and recorded in Mesh.<\/li>\n\n\n\n
                    3. Go back to RCMCost. At least that worked.<\/li>\n\n\n\n
                    4. Reports are required with correct information.<\/li>\n\n\n\n
                    5. Modify or create new failure modes, via the feedback system, using names or components and parts that the technicians use. This will speed up the location of the right leaf in the knowledge hierarchy when completing the work order. These anomalies are causing \u201cblanks\u201d in the reports.<\/li>\n\n\n\n
                    6. You can still find a lot of work orders that are filled without using (by-passing) the Mesh knowledge hierarchy. There are many failure modes where the cause is specified as \u201cunknown\u201d.<\/li>\n<\/ol>\n<\/li>\n\n\n\n
                    7. What tools do you currently use for analysis<\/span>?<\/span>\n
                        \n
                      1. Minitab, @risk, Excel, SuperSmith, Exakt, among others.<\/span><\/li>\n\n\n\n
                      2. Spreadsheets and pivot tables<\/li>\n\n\n\n
                      3. Pivot tables<\/li>\n\n\n\n
                      4. Pareto, DOFA<\/li>\n\n\n\n
                      5. Excel: Filters and pivot tables<\/li>\n\n\n\n
                      6. Super Smith<\/li>\n<\/ol>\n<\/li>\n\n\n\n
                      7. Do you consider that the suggestion feedback system in Mesh helps improve the RCM knowledge base?<\/span> (10=completely agree, 1=completely disagree)\n
                          \n
                        1. 6<\/li>\n\n\n\n
                        2. 8<\/li>\n\n\n\n
                        3. 1<\/li>\n\n\n\n
                        4. 9<\/li>\n\n\n\n
                        5. 10<\/li>\n\n\n\n
                        6. 8<\/li>\n<\/ol>\n<\/li>\n\n\n\n
                        7. To what extent does the image gallery associated with a failure mode add value to the knowledge base, and to the quality of work order data entry?<\/span> (10=immense value, 1 little or no value)\n
                            \n
                          1. 3<\/li>\n\n\n\n
                          2. 5<\/li>\n\n\n\n
                          3. 1<\/li>\n\n\n\n
                          4. 8<\/li>\n\n\n\n
                          5. 2<\/li>\n\n\n\n
                          6. 8<\/li>\n<\/ol>\n<\/li>\n\n\n\n
                          7. How much value does the failure mode instance count (of failed and potentially failed parts) in the work order RCM tree add to your understanding of the asset’s reliability and failure consequence mitigating policies?<\/span> (10=immense value, 1 little or no value).\n
                              \n
                            1. 8<\/li>\n\n\n\n
                            2. 5<\/li>\n\n\n\n
                            3. 1<\/li>\n\n\n\n
                            4. 8<\/li>\n\n\n\n
                            5. 1<\/li>\n\n\n\n
                            6. 8<\/li>\n<\/ol>\n<\/li>\n\n\n\n
                            7. List the principal advantages of the Mesh tool set?<\/span>\n
                                \n
                              1. Help to improve the quality of information on the work order. Forces the work orders to relate to the RCM knowledge base. Helps identify the failure and apply the correct failure modes affecting the equipment.<\/li>\n\n\n\n
                              2. Documenting work orders is faster and less prone to error. Also updating the RCM knowledge base is more practical.<\/li>\n\n\n\n
                              3. \u00a0<\/li>\n\n\n\n
                              4. Getting to the root causes of the failures that most affect the fleet.<\/li>\n\n\n\n
                              5. Correct allocation of failure modes to the right systems and components. Ease In modifying the knowledge base using the suggestion feedback system. Control Of the changes made to the knowledge base. Agility To include failure modes that apply to other systems (Copy-Paste).<\/li>\n\n\n\n
                              6. “Easy to manage failure modes and see their relationship to equipment functions. Easy to maintain and updated fleet RCM knowledge.<\/li>\n<\/ol>\n<\/li>\n\n\n\n
                              7. List the principal disadvantages of the Mesh tool set?<\/span>\n
                                  \n
                                1. The underlying EAM platform is too slow (true even before Mesh). The competency of the personnel who record the information in Mesh on behalf of the technicians needs to be upgraded. In my opinion these should be skilled technicians or engineers.<\/li>\n\n\n\n
                                2. In practice, we cannot always identify the failure mode. We know only the symptom at the time of execution of the work. The actual failure mode may be known only when the replaced component is overhauled in the rebuild shop. And the rebuild shop is not using Mesh to close the work order.<\/li>\n\n\n\n
                                3. Everything. Particularly the slowness.<\/li>\n\n\n\n
                                4. Missing information.<\/li>\n\n\n\n
                                5. There have been problems with synchronization of EAM failure codes and failure modes in the RCM knowledge base. It’s taking too many seconds between clicking on the Event and acceptance into the EAM.<\/li>\n\n\n\n
                                6. No direct connection from Mesh to the reliability analysis tools.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/div>\n\n\n\n
                                  \n

                                  ## Post Tree Navigation<\/h2>\n\n\n\n

                                  LRCM<\/h3>\n\n\n