{"id":5501,"date":"2015-10-16T12:28:45","date_gmt":"2015-10-16T17:28:45","guid":{"rendered":"http:\/\/www.livingreliability.com\/en\/?p=5501"},"modified":"2025-11-06T05:13:28","modified_gmt":"2025-11-06T10:13:28","slug":"mesh-rcm-knowledge-continuous-improvement","status":"publish","type":"post","link":"https:\/\/www.livingreliability.com\/en\/posts\/mesh-rcm-knowledge-continuous-improvement\/","title":{"rendered":"MESH &#8211; RCM knowledge continuous improvement"},"content":{"rendered":"<p><em>What befalls the RCM analysis once it is completed and the ensuing PM program uploaded into the EAM? Too often it gathers dust, and fades eventually into distant memory. Only a pale reflection of the intensive mental energy expended in creating the knowledge rich RCM analysis remains in the form of EAM failure codes<\/em><sup>[<a href=\"#mesh-rcm-knowledge-continuous-improvement-n-1\" class=\"footnoted\" id=\"to-mesh-rcm-knowledge-continuous-improvement-n-1\">1<\/a>]<\/sup><em>. What of daily new experiences, observations, and insights? How can the RCM analysis dynamically incorporate knowledge as it emerges?<\/em><\/p>\n<p>MESH, a software enabler for the Living RCM (LRCM) process, solves the continuous knowledge drain problem. The following exercise demonstrates how updates may be integrated naturally into the work order process.<\/p>\n<h3>Step 1<\/h3>\n<ul>\n<li><a href=\"http:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshCreateEquipment.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignright size-full wp-image-5502\" src=\"http:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshCreateEquipment.jpg\" alt=\"MeshCreateEquipment\" width=\"376\" height=\"226\" srcset=\"https:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshCreateEquipment.jpg 376w, https:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshCreateEquipment-300x180.jpg 300w\" sizes=\"auto, (max-width: 376px) 100vw, 376px\" \/><\/a>In the &#8220;Equipment Manager&#8221; tab I created a specific instance of the fleet &#8220;Fire Hydrant System&#8221; called &#8220;FireHydSys1&#8221;. (In practice the equipment would already exist.)<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h3>Step 2<\/h3>\n<ul>\n<li><a href=\"http:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshAddWorkOrder.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignright size-full wp-image-5503\" src=\"http:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshAddWorkOrder.jpg\" alt=\"MeshAddWorkOrder\" width=\"426\" height=\"378\" srcset=\"https:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshAddWorkOrder.jpg 426w, https:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshAddWorkOrder-300x266.jpg 300w\" sizes=\"auto, (max-width: 426px) 100vw, 426px\" \/><\/a>In the DAS<sup>[<a href=\"#mesh-rcm-knowledge-continuous-improvement-n-2\" class=\"footnoted\" id=\"to-mesh-rcm-knowledge-continuous-improvement-n-2\">2<\/a>]<\/sup> tab I created a &#8220;dummy&#8221; work order for FireHydSys1 called, for example, &#8220;MWsug1&#8221;. (In practice the work order would already exist.)<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h3>Step 3<\/h3>\n<ul>\n<li><a href=\"http:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshLrcmFeedback.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignright size-full wp-image-5504\" src=\"http:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshLrcmFeedback.jpg\" alt=\"MeshLrcmFeedback\" width=\"340\" height=\"140\" srcset=\"https:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshLrcmFeedback.jpg 340w, https:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshLrcmFeedback-300x124.jpg 300w\" sizes=\"auto, (max-width: 340px) 100vw, 340px\" \/><\/a> From that work order on the refreshed DAS list hit the &#8220;LRCM analysis&#8221; tree icon.<sup>[<a href=\"#mesh-rcm-knowledge-continuous-improvement-n-3\" class=\"footnoted\" id=\"to-mesh-rcm-knowledge-continuous-improvement-n-3\">3<\/a>]<\/sup><\/li>\n<li>The work order will display the reliability performance of the equipment in a granular way by providing a <a href=\"http:\/\/www.livingreliability.com\/en\/posts\/mesh-basic-reliability-analysis-on-the-work-order\/\" target=\"_blank\">failure instance count <\/a>associated with each node of the RCM tree view.<\/li>\n<li>Right click an element in the RCM knowledge tree.<\/li>\n<li>Hit &#8220;Feedback | Modify&#8221;<\/li>\n<\/ul>\n<h3>Step 4<\/h3>\n<ul>\n<li><a href=\"http:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshLrcmFeedbackModifyElement.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignright size-full wp-image-5505\" src=\"http:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshLrcmFeedbackModifyElement.jpg\" alt=\"MeshLrcmFeedbackModifyElement\" width=\"350\" height=\"152\" srcset=\"https:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshLrcmFeedbackModifyElement.jpg 350w, https:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshLrcmFeedbackModifyElement-300x130.jpg 300w\" sizes=\"auto, (max-width: 350px) 100vw, 350px\" \/><\/a>Make and submit a suggestion simply by editing the text. (The original text appears below the text box for reference.) Add your justification for the update and hit save.<\/li>\n<\/ul>\n<h3>Step 5<\/h3>\n<p>Typically at the subsequent RCM review meeting the facilitator and the group would review feedback suggestions by the SMEs between meetings, and edit, accept or reject them.<\/p>\n<ul>\n<li><a href=\"http:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshFeedbackManagerViewJustification.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignright wp-image-5509\" src=\"http:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshFeedbackManagerViewJustification.jpg\" alt=\"MeshFeedbackManagerViewJustification\" width=\"367\" height=\"263\" srcset=\"https:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshFeedbackManagerViewJustification.jpg 565w, https:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshFeedbackManagerViewJustification-300x215.jpg 300w\" sizes=\"auto, (max-width: 367px) 100vw, 367px\" \/><\/a>Hit Feedback Manager tab<\/li>\n<li>Select the Fleet e.g. &#8220;Fire Hydrant System&#8221;<\/li>\n<li>Hit &#8220;Start Session&#8221;<\/li>\n<li>Hit the &#8220;Process Feedback&#8221; icon for a feedback suggestion<\/li>\n<li>Review the justification<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h3>Step 6<\/h3>\n<ul>\n<li><a href=\"http:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshFeedbackManagerApproveReject.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignright wp-image-5510\" src=\"http:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshFeedbackManagerApproveReject.jpg\" alt=\"MeshFeedbackManagerApproveReject\" width=\"368\" height=\"264\" srcset=\"https:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshFeedbackManagerApproveReject.jpg 559w, https:\/\/www.livingreliability.com\/en\/wp-content\/uploads\/2015\/10\/MeshFeedbackManagerApproveReject-300x215.jpg 300w\" sizes=\"auto, (max-width: 368px) 100vw, 368px\" \/><\/a>Review, edit, accept, or reject<\/li>\n<li>Hit &#8220;Finish Session&#8221;<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>If the suggestion is accepted, the knowledge base will be updated automatically with the revised text. If a suggestion \/ justification includes changes to the mitigating task, the facilitator could open the knowledge base manually and update it accordingly.<\/p>\n<p>The feedback system is meant to be used primarily by the technicians after executing a work order in order to continuously improve the RCM knowledge. But it can be used by anyone to contribute to the RCM knowledge base<sup>[<a href=\"#mesh-rcm-knowledge-continuous-improvement-n-4\" class=\"footnoted\" id=\"to-mesh-rcm-knowledge-continuous-improvement-n-4\">4<\/a>]<\/sup>. For example, the RCM auditor, prior to signing off on the analysis, can pose a series of questions and make comments or suggestions using the feedback system in the same way as outlined here.<span style=\"color: #888888;\"><br \/>\n<\/span><\/p>\n\n<ol class=\"footnotes\">\n\t<li class=\"footnote\" id=\"mesh-rcm-knowledge-continuous-improvement-n-1\"><strong><sup>[1]<\/sup><\/strong>The SAP catalogs, the Maximo failure code hierarchy, the Ellipse codes.<a class=\"note-return\" href=\"#to-mesh-rcm-knowledge-continuous-improvement-n-1\">&#x21A9;<\/a><\/li>\n\t<li class=\"footnote\" id=\"mesh-rcm-knowledge-continuous-improvement-n-2\"><strong><sup>[2]<\/sup><\/strong>DAS is a legacy acronym for &#8220;Downtime Administration System&#8221;. It is simply a list of active work orders and some related operations.<a class=\"note-return\" href=\"#to-mesh-rcm-knowledge-continuous-improvement-n-2\">&#x21A9;<\/a><\/li>\n\t<li class=\"footnote\" id=\"mesh-rcm-knowledge-continuous-improvement-n-3\"><strong><sup>[3]<\/sup><\/strong>LRCM is an alternate user interface for completing and closing a work order by communicating via the EAM&#8217;s API.<a class=\"note-return\" href=\"#to-mesh-rcm-knowledge-continuous-improvement-n-3\">&#x21A9;<\/a><\/li>\n\t<li class=\"footnote\" id=\"mesh-rcm-knowledge-continuous-improvement-n-4\"><strong><sup>[4]<\/sup><\/strong>which, arguably, is the maintenance department&#8217;s most valuable intellectual asset<a class=\"note-return\" href=\"#to-mesh-rcm-knowledge-continuous-improvement-n-4\">&#x21A9;<\/a><\/li><\/ol>\n","protected":false},"excerpt":{"rendered":"<p>What befalls the RCM analysis once it is completed and the ensuing PM program uploaded into the EAM? Too often it gathers dust, and fades eventually into distant memory. Only a pale reflection of the intensive mental energy expended in creating the knowledge rich RCM analysis remains in the form of EAM failure codes. What [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[87],"tags":[35,112],"class_list":["post-5501","post","type-post","status-publish","format-standard","hentry","category-managing-lrcm","tag-continuous-improvement","tag-lrcm"],"_links":{"self":[{"href":"https:\/\/www.livingreliability.com\/en\/wp-json\/wp\/v2\/posts\/5501","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.livingreliability.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.livingreliability.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.livingreliability.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.livingreliability.com\/en\/wp-json\/wp\/v2\/comments?post=5501"}],"version-history":[{"count":1,"href":"https:\/\/www.livingreliability.com\/en\/wp-json\/wp\/v2\/posts\/5501\/revisions"}],"predecessor-version":[{"id":6003,"href":"https:\/\/www.livingreliability.com\/en\/wp-json\/wp\/v2\/posts\/5501\/revisions\/6003"}],"wp:attachment":[{"href":"https:\/\/www.livingreliability.com\/en\/wp-json\/wp\/v2\/media?parent=5501"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.livingreliability.com\/en\/wp-json\/wp\/v2\/categories?post=5501"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.livingreliability.com\/en\/wp-json\/wp\/v2\/tags?post=5501"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}