{"id":3974,"date":"2014-10-19T12:05:31","date_gmt":"2014-10-19T17:05:31","guid":{"rendered":"http:\/\/www.livingreliability.com\/en\/?p=3974"},"modified":"2014-12-28T18:09:03","modified_gmt":"2014-12-28T23:09:03","slug":"mesh-use-cases-knowledge-builder","status":"publish","type":"post","link":"https:\/\/www.livingreliability.com\/en\/posts\/mesh-use-cases-knowledge-builder\/","title":{"rendered":"MESH Use Cases – Knowledge Builder"},"content":{"rendered":"

Glossary<\/h2>\n

Tree, hierarchy, knowledge base:<\/strong> The expandable list representing an Equipment type or Fleet and its Systems, Subsystems, Components, Functions, Failures, and Failure Modes. The elements: \u00a0Components, Subsystems, or Systems elements may be excluded from any branch of the tree.<\/p>\n

Equipment, fleet:<\/strong> The highest element in a heirarchy. Represents a type of equipment. For example Hitachi Electric Truck 320T.<\/p>\n

Knowledge element, element:<\/strong> A node on the tree representing one of: Equipment, System, Subsystem, Component, or Failure mode.<\/p>\n

Consequences:<\/strong> The reason why the failure matters. The choices are:<\/p>\n

    \n
  1. Hidden<\/li>\n
  2. Safety, Health, Environmental<\/li>\n
  3. Operational<\/li>\n
  4. Non-operational<\/li>\n<\/ol>\n

    Mitigation Task:<\/strong> An activity that must be done pro-actively to avoid or reduce the consequences of faillure. The choices are:<\/p>\n

      \n
    1. Time (age) based maintenance.<\/li>\n
    2. Condition based maintenance.<\/li>\n
    3. No maintenance, allow function to fail and then repair<\/li>\n
    4. Inspection (Failure Finding) to see if a function has failed.<\/li>\n
    5. Redesign – a one time change in the asset, its operation or manitenance procedures, or associated training.<\/li>\n<\/ol>\n

      Corrective Task:<\/strong> A reactive activity that must be done following a failure.<\/p>\n

      Use Cases for MESH Knowledge Builder<\/h2>\n

      Objective:<\/strong> Create and update the RCM knowledge base using MESH Knowledge Builder<\/p>\n

      Actor(s):<\/strong> Reliability Analyst<\/p>\n

      Activities:<\/strong><\/p>\n

        \n
      1. Create a new fleet<\/li>\n
      2. Edit fleet information<\/li>\n
      3. Access the fleet hierarchy<\/li>\n
      4. Add a knowledge element\n
          \n
        1. An element other than a failure mode<\/li>\n
        2. A failure mode<\/li>\n<\/ol>\n<\/li>\n
        3. Modify a knowledge element\n
            \n
          1. An element other than a failure mode<\/li>\n
          2. A failure mode<\/li>\n<\/ol>\n<\/li>\n
          3. Move an element up or down in the tree<\/li>\n
          4. Copy an element and paste in another another location<\/li>\n
          5. Delete an element<\/li>\n
          6. View a Failure mode<\/li>\n<\/ol>\n\n\n\n
            Activity 1. Create a new Fleet<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

            User Action:<\/strong>\u00a01. Start MESH in web browser
            \nSystem response:<\/strong>\u00a0Knowledge Base – Fleet Administration main display
            \n\"MESH<\/a><\/p>\n

            User Action:<\/strong>\u00a0Hit the +Add button<\/p>\n

            \"KB<\/a>
            \nSystem response:<\/strong>\u00a02. Input fleet data dialog            \"KB<\/a><\/p>\n

            User Action:<\/strong>\u00a03. Enter data, Save\"KB<\/a>
            \nActivity succeeds:<\/strong>\u00a0Dialog closes. List displays with new equipment added            \"KB<\/a><\/p>\n\n\n\n
            Activity 2. Edit equipment information<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

            User Action:<\/strong>\u00a02.1 Hit Edit fleet information icon\"KB<\/a>System response:<\/strong>\u00a0Same dialog as Activity 1 User action 3<\/p>\n

            User Action:<\/strong>\u00a02.2 Edit data. Save
            \nActivity succeeds:<\/strong> Dialog closes<\/p>\n\n\n\n
            Activity 3.\u00a0Access the fleet knowledge base<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

            User Action:<\/strong>\u00a03.1\u00a0Hit the Build Knowledge icon\"KB<\/a>Activity succeeds:<\/strong>\u00a0Tree view of knowledge base appears\"KB<\/a><\/p>\n\n\n\n
            Activity 4A.\u00a0Add a new knowledge element (other than a failure mode)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

            User Action:<\/strong>\u00a04.1\u00a0Right click the element below which you wish to add a new element. Select Append. Select the Element type you wish to add.\"KB<\/a>
            \nSystem response:\u00a0<\/strong>Append new element dialog appears            \"KB<\/a><\/p>\n

            User Action:<\/strong>\u00a04.2 Edit information. Hit Accept\"KB<\/a>Activity succeeds:\u00a0<\/strong>New element appears in tree view. Hit Save to accept\"KB<\/a><\/p>\n

            Repeat this activity to\u00a0append\u00a0additional\u00a0elements to the equipment tree. For example add a Component, a Function, and a Functional Failure so that the tree view now looks similar to\u00a0this:\u00a0\"KB<\/a><\/p>\n\n\n\n
            Activity 4B.\u00a0Add a \u00a0failure mode<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

            User Action:<\/strong>\u00a05.1 Right click a Functional failure and select Append and Failure Mode from the context menu.<\/p>\n

            \"KB<\/a><\/p>\n

            System response:<\/strong> The Append new element (Failure Mode) dialog displays:\"KB<\/a><\/p>\n

            User Action:<\/strong>\u00a05.2 Complete the Failure Mode (Basic) information as shown:<\/p>\n

            \"KB<\/a><\/p>\n

            User Action:<\/strong>\u00a05.3 Hit the Tasks tab, the add icon and select\u00a0a mitigation task type.<\/p>\n

            \"KB<\/a><\/p>\n

            User Action:<\/strong>\u00a05.4 Enter the Description, Interval, and select a Skill:<\/p>\n

            \"KB<\/a><\/p>\n

            User Action:<\/strong>\u00a05.5 Hit the Images tab and upload an image (if required) to illustrate the Failure Mode’s Failure, Potential Failure, or Suspension states.\"KB<\/a><\/p>\n

            System response:<\/strong>\u00a0System uploads \u00a0and displays in the dialog the selected image file.\u00a0\"KB<\/a><\/p>\n

            User Action:<\/strong>\u00a05.6 Hit the Risks tab. And select a grid square corresponding to the probability and severity of the Failure mode.<\/p>\n

            \"KB<\/a><\/p>\n

            User Action:<\/strong>\u00a05.7 Select the Reputation, then the Environmental tabs making respective severity and probability selections. Hit Accept:\"KB<\/a><\/p>\n

            Activity succeeds:<\/strong> System closes dialog and displays tree view with new Failure Mode appended onto the tree.<\/p>\n

            \"KB<\/a><\/p>\n

             <\/p>\n\n\n\n
            Activities\u00a05 to 9.\u00a0Modify, copy, and move elements.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

            User Action:<\/strong> 1. Right click an element in the tree and select the desired context menu activity choice.\u00a0\"KB<\/a><\/p>\n

            Follow similar\u00a0procedures to those in Activities 1 to 4B above to complete the required action.<\/p>\n

            Activities succeed:<\/strong>\u00a0Hit Save. The system displays success message.\u00a0\"KB<\/a><\/p>\n

             <\/p>\n\n","protected":false},"excerpt":{"rendered":"

            Glossary Tree, hierarchy, knowledge base: The expandable list representing an Equipment type or Fleet and its Systems, Subsystems, Components, Functions, Failures, and Failure Modes. The elements: \u00a0Components, Subsystems, or Systems elements may be excluded from any branch of the tree. Equipment, fleet: The highest element in a heirarchy. Represents a type of equipment. For example […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6,5],"tags":[],"class_list":["post-3974","post","type-post","status-publish","format-standard","hentry","category-lrcm","category-rcm"],"_links":{"self":[{"href":"https:\/\/www.livingreliability.com\/en\/wp-json\/wp\/v2\/posts\/3974","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=3974"}],"version-history":[{"count":0,"href":"https:\/\/www.livingreliability.com\/en\/wp-json\/wp\/v2\/posts\/3974\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.livingreliability.com\/en\/wp-json\/wp\/v2\/media?parent=3974"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.livingreliability.com\/en\/wp-json\/wp\/v2\/categories?post=3974"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.livingreliability.com\/en\/wp-json\/wp\/v2\/tags?post=3974"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}