{"id":11138,"date":"2022-11-30T09:40:19","date_gmt":"2022-11-30T01:40:19","guid":{"rendered":"https:\/\/newsletter.bluebeecloud.com\/en\/?p=11138"},"modified":"2023-02-15T16:21:16","modified_gmt":"2023-02-15T08:21:16","slug":"integrating-fmeca-in-your-maintenance-system","status":"publish","type":"post","link":"https:\/\/newsletter.bluebeecloud.com\/en\/reliability\/integrating-fmeca-in-your-maintenance-system\/","title":{"rendered":"Integrating FMECA in your Maintenance System"},"content":{"rendered":"
Introduction of FMECA<\/strong><\/div>\n

 <\/br><\/p>\n

Most companies have a Preventive Maintenance plan in place, which incorporates regulatory demands (such as mandatory checks), suppliers\u2019 recommendations (from the equipment O&M manuals) and best practices accumulated in the organization (similar plants in the group, experience of the maintenance teams).<\/div>\n

 <\/br><\/p>\n

Developing a Preventive Maintenance Plan from scratch or optimizing the existing Preventive Maintenance Plan is a challenging task, which requires identifying potential problems, estimating their impact and designing actions to prevent their occurrence. A systematic approach is required, the best-known approach being \u201cFailure Modes, Effects and Criticality Analysis\u201d (or FMECA)<\/strong> or sometimes simply FMEA.<\/div>\n

 <\/br><\/p>\n

The FMECA is a tool used to systematically analyze potential component failures, identify their causes and effects, so as to define the necessary preventive actions to improve the reliability of facilities, the quality of outputs, the safety of operations, etc.<\/div>\n

 <\/br><\/p>\n

This article will show, through a practical example of a client project, how FMECA can and should be integrated into the overall maintenance system and its supporting IT system (the CMMS or Asset Management System).<\/div>\n

 <\/br><\/p>\n

Implementation steps<\/strong><\/div>\n

 <\/br><\/p>\n

In this article we take the FMECA management module built into the Baosteel Gases EMM system (Coswin 8i) as an example to introduce the application of FMECA in the actual enterprise quality management system in detail. The FMECA module is fully integrated in Coswin 8i, making use of all existing functionality of the system, such as equipment structures, technical data, failure history, preventive maintenance plans, etc.<\/div>\n

 <\/br><\/p>\n

\n
1.<\/div>\n
First in the module’s basic data, are defined the severity, probability and degree of detectability of potential failure modes in the system, in order to facilitate the comprehensive analysis and evaluation of failure modes. This is shown below:<\/div>\n

 <\/br>\n<\/div>\n

Severity SEV:<\/div>\n

 <\/br><\/p>\n

\"\"<\/div>\n

 <\/br><\/p>\n

Occurrence probability OCC:<\/div>\n

 <\/br><\/p>\n

\"\"<\/div>\n

 <\/br><\/p>\n

Degree of detectability DET:<\/div>\n

 <\/br><\/p>\n

\"\"<\/div>\n

 <\/br><\/p>\n

\n
2.<\/div>\n
The module then supports the FMECA process, allowing users to list all potential failure modes, consequences and causes of failure for key parts of the equipment, then to determine the severity, occurrence probability and degree of detectability of each failure mode.<\/div>\n

 <\/br>\n<\/div>\n

The following figure shows the analysis for an air filter system with three main parts: <\/div>\n

 <\/br><\/p>\n

\"\"<\/div>\n

 <\/br><\/p>\n

Select a part, double-click to open, you can see the details of this FMECA:<\/div>\n

 <\/br><\/p>\n

\"\"<\/div>\n

 <\/br><\/p>\n

You can also click the \u201c \u201d button to add a new part in the FMECA for failure mode and consequences analysis:<\/div>\n

 <\/br><\/p>\n

\"\"<\/div>\n

 <\/br><\/p>\n

Since the module is fully integrated in Coswin 8i, equipment parts can be directly selected from parts in the equipment database.<\/div>\n

 <\/br><\/p>\n

\"\"<\/div>\n

 <\/br><\/p>\n

In the FMECA module, information is added pertaining to failure modes, consequences, cause, the current control mode, the severity, occurrence probability and degree of detectability as shown below:<\/div>\n

 <\/br><\/p>\n

\"\"<\/div>\n

 <\/br><\/p>\n

\n
3.<\/div>\n
Based on the FMECA analysis, the corresponding preventive maintenance plan can then be formulated. For example, the self-cleaning filter is routinely checked with a frequency of one month:<\/div>\n

 <\/br>\n<\/div>\n

\"\"<\/div>\n

 <\/br><\/p>\n

The work code is associated with FMECA to facilitate following up preventive maintenance. Since all data is interlinked in the system, advanced analysis is possible, so as to support a continuous improvement process (RCM or equivalent) based on a FMECA fed by systematic feedback from the field.<\/div>\n

 <\/br><\/p>\n

\"\"<\/div>\n

 <\/br><\/p>\n

The resulting preventive maintenance plan will automatically trigger the generation of maintenance work orders in the Coswin 8i system, execution is then performed with support from the bluebee\u00ae mobile solution, ultimately reducing the occurrence of equipment failure, thus achieving the purpose of preventive maintenance.<\/div>\n

 <\/br><\/p>\n

Why integrating FMECA inside the Maintenance system?<\/strong><\/div>\n

 <\/br><\/p>\n

Quoting from above: \u201cSince all data is interlinked in the system, advanced analysis is possible, so as to support a continuous improvement process (RCM or equivalent) based on a FMECA fed by systematic feedback from the field.\u201d<\/div>\n

 <\/br><\/p>\n

Indeed, more often than not, companies use Excel sheets or paper forms to support the FMECA process. FMECA however requires a relational database, considering the complexity of inter-related data and the sheer amount of technical data in large plants.<\/div>\n

 <\/br><\/p>\n

Some companies chose to implement a separate specialized FMECA tool, which often prove too complicated (such tools are designed for aerospace or military applications of FMECA, or for product-FMECA which is a similar yet different process than manufacturers apply to products, not production equipment). They are not integrated with the CMMS or rely of importing history files: there is no proper feedback loop from operation.<\/div>\n

 <\/br><\/p>\n

Instead, the Siveco approach of an integrated FMECA module described above is compliant with continuous improvement and the feedback loop philosophy of modern management systems (such as ISO 55000 Asset Management \u2013 now also a Chinese standard under the name GB\/T 33172\u8d44\u4ea7\u7ba1\u7406\u7efc\u8ff0\u3001\u539f\u5219\u548c\u672f\u8bed).<\/div>\n

 <\/br><\/p>\n

This is made possible by flexible Coswin technology: the FMECA module does not require any software development, it is a standard Coswin 8i \u201cfree module\u201d adapted to the specific needs of clients. For more on Coswin flexible configuration, see this article<\/a>. Another example of application of Coswin free module was for WCM\/TPM, as shown in this article<\/a>.<\/div>\n

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

Introduction of FMECA<\/strong><\/div>\n

 <\/br><\/p>\n

Most companies have a Preventive Maintenance plan in place, which incorporates regulatory demands (such as mandatory checks), suppliers\u2019 recommendations (from the equipment O&M manuals) and best practices accumulated in the organization (similar plants in the group, experience of the maintenance teams).<\/div>\n

 <\/br><\/p>\n

Developing a Preventive Maintenance Plan from scratch or optimizing the existing Preventive Maintenance Plan is a challenging task, which requires identifying potential problems, estimating their impact and designing actions to prevent their occurrence. A systematic approach is required, the best-known approach being \u201cFailure Modes, Effects and Criticality Analysis\u201d (or FMECA)<\/strong> or sometimes simply FMEA.<\/div>\n

 <\/br><\/p>\n

The FMECA is a tool used to systematically analyze potential component failures, identify their causes and effects, so as to define the necessary preventive actions to improve the reliability of facilities, the quality of outputs, the safety of operations, etc.<\/div>\n

 <\/br><\/p>\n

This article will show, through a practical example of a client project, how FMECA can and should be integrated into the overall maintenance system and its supporting IT system (the CMMS or Asset Management System).<\/div>\n

 <\/br><\/p>\n

Implementation steps<\/strong><\/div>\n

 <\/br><\/p>\n

In this article we take the FMECA management module built into the Baosteel Gases EMM system (Coswin 8i) as an example to introduce the application of FMECA in the actual enterprise quality management system in detail. The FMECA module is fully integrated in Coswin 8i, making use of all existing functionality of the system, such as equipment structures, technical data, failure history, preventive maintenance plans, etc.<\/div>\n

 <\/br><\/p>\n

\n
1.<\/div>\n
First in the module’s basic data, are defined the severity, probability and degree of detectability of potential failure modes in the system, in order to facilitate the comprehensive analysis and evaluation of failure modes. This is shown below:<\/div>\n

 <\/br>\n<\/div>\n

Severity SEV:<\/div>\n

 <\/br><\/p>\n

\"\"<\/div>\n

 <\/br><\/p>\n

Occurrence probability OCC:<\/div>\n

 <\/br><\/p>\n

\"\"<\/div>\n

 <\/br><\/p>\n

Degree of detectability DET:<\/div>\n

 <\/br><\/p>\n

\"\"<\/div>\n

 <\/br><\/p>\n

\n
2.<\/div>\n
The module then supports the FMECA process, allowing users to list all potential failure modes, consequences and causes of failure for key parts of the equipment, then to determine the severity, occurrence probability and degree of detectability of each failure mode.<\/div>\n

 <\/br>\n<\/div>\n

The following figure shows the analysis for an air filter system with three main parts: <\/div>\n

 <\/br><\/p>\n

\"\"<\/div>\n

 <\/br><\/p>\n

Select a part, double-click to open, you can see the details of this FMECA:<\/div>\n

 <\/br><\/p>\n

\"\"<\/div>\n

 <\/br><\/p>\n

You can also click the \u201c \u201d button to add a new part in the FMECA for failure mode and consequences analysis:<\/div>\n

 <\/br><\/p>\n

\"\"<\/div>\n

 <\/br><\/p>\n

Since the module is fully integrated in Coswin 8i, equipment parts can be directly selected from parts in the equipment database.<\/div>\n

 <\/br><\/p>\n

\"\"<\/div>\n

 <\/br><\/p>\n

In the FMECA module, information is added pertaining to failure modes, consequences, cause, the current control mode, the severity, occurrence probability and degree of detectability as shown below:<\/div>\n

 <\/br><\/p>\n

\"\"<\/div>\n

 <\/br><\/p>\n

\n
3.<\/div>\n
Based on the FMECA analysis, the corresponding preventive maintenance plan can then be formulated. For example, the self-cleaning filter is routinely checked with a frequency of one month:<\/div>\n

 <\/br>\n<\/div>\n

\"\"<\/div>\n

 <\/br><\/p>\n

The work code is associated with FMECA to facilitate following up preventive maintenance. Since all data is interlinked in the system, advanced analysis is possible, so as to support a continuous improvement process (RCM or equivalent) based on a FMECA fed by systematic feedback from the field.<\/div>\n

 <\/br><\/p>\n

\"\"<\/div>\n

 <\/br><\/p>\n

The resulting preventive maintenance plan will automatically trigger the generation of maintenance work orders in the Coswin 8i system, execution is then performed with support from the bluebee\u00ae mobile solution, ultimately reducing the occurrence of equipment failure, thus achieving the purpose of preventive maintenance.<\/div>\n

 <\/br><\/p>\n

Why integrating FMECA inside the Maintenance system?<\/strong><\/div>\n

 <\/br><\/p>\n

Quoting from above: \u201cSince all data is interlinked in the system, advanced analysis is possible, so as to support a continuous improvement process (RCM or equivalent) based on a FMECA fed by systematic feedback from the field.\u201d<\/div>\n

 <\/br><\/p>\n

Indeed, more often than not, companies use Excel sheets or paper forms to support the FMECA process. FMECA however requires a relational database, considering the complexity of inter-related data and the sheer amount of technical data in large plants.<\/div>\n

 <\/br><\/p>\n

Some companies chose to implement a separate specialized FMECA tool, which often prove too complicated (such tools are designed for aerospace or military applications of FMECA, or for product-FMECA which is a similar yet different process than manufacturers apply to products, not production equipment). They are not integrated with the CMMS or rely of importing history files: there is no proper feedback loop from operation.<\/div>\n

 <\/br><\/p>\n

Instead, the Siveco approach of an integrated FMECA module described above is compliant with continuous improvement and the feedback loop philosophy of modern management systems (such as ISO 55000 Asset Management \u2013 now also a Chinese standard under the name GB\/T 33172\u8d44\u4ea7\u7ba1\u7406\u7efc\u8ff0\u3001\u539f\u5219\u548c\u672f\u8bed).<\/div>\n

 <\/br><\/p>\n

This is made possible by flexible Coswin technology: the FMECA module does not require any software development, it is a standard Coswin 8i \u201cfree module\u201d adapted to the specific needs of clients. For more on Coswin flexible configuration, see this article<\/a>. Another example of application of Coswin free module was for WCM\/TPM, as shown in this article<\/a>.<\/div>\n

 <\/br><\/p>\n","protected":false},"author":1,"featured_media":11155,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[266,296,346,380],"_links":{"self":[{"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/posts\/11138"}],"collection":[{"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/comments?post=11138"}],"version-history":[{"count":15,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/posts\/11138\/revisions"}],"predecessor-version":[{"id":13286,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/posts\/11138\/revisions\/13286"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/media\/11155"}],"wp:attachment":[{"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/media?parent=11138"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/categories?post=11138"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/tags?post=11138"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}