{"id":2074,"date":"2010-10-29T08:45:13","date_gmt":"2010-10-29T00:45:13","guid":{"rendered":"http:\/\/www.sivecochina.com\/en\/?p=2074"},"modified":"2014-10-22T09:28:05","modified_gmt":"2014-10-22T09:28:05","slug":"coswin-tips-tricks-quick-benefits-from-underutilized-coswin-functionalities-hazard-report","status":"publish","type":"post","link":"https:\/\/newsletter.bluebeecloud.com\/en\/tips-tricks\/coswin-tips-tricks-quick-benefits-from-underutilized-coswin-functionalities-hazard-report\/","title":{"rendered":"Quick benefits from underutilized COSWIN functionalities: Hazard Report"},"content":{"rendered":"
This article is the third in a series aimed at familiarizing our readers with lesser-known COSWIN functionalities, which can easily be configured by customers themselves to bring immediate benefits. Previous issues covered Contract Management<\/a> and Work Permits<\/a>. <\/div>\n

 <\/p>\n

The Hazard Report is perhaps one of the most interesting COSWIN features, as it essentially links operations to maintenance, in more ways than the name \u201cHazard\u201d seem to indicate (implying a reference to safety). This article will explain the basics of the Hazard Report functionality, elaborate some of its real-life implementations and present a example (application to quality at cable manufacturer Acome Xintai).<\/div>\n

 <\/p>\n

Hazard Report<\/strong><\/div>\n

 <\/p>\n

The hazard report is available for managing incidents or events that require attention. Its purpose is to lead to an action plan so that the incident does not repeat. The module is used to manage the complete cycle of a hazard report: create, update, delete, the effects, the recommended actions, and the follow up. Hazard reports are created against equipments (but this is not mandatory) and COSWIN stores all hazard report details. It also keeps a list of recommended actions and follow-up actions. \u2460 An incident is noted \u2461 A hazard report is created with various fields indicated below \u2462 The hazard report can generate various documents or transactions: Job Requests, Work Oder(s) or Purchase Order(s) to COSWIN Stock & Purchasing.<\/div>\n

 <\/p>\n

<\/div>\n

 <\/p>\n

\u201cHazard\u201d? What\u2019s in a name.<\/strong><\/div>\n

 <\/p>\n

Two things that should never be forgotten with CMMS and COSWIN in particular:<\/div>\n

<\/p>\n\n\n\n\n
 <\/td>\n(1)<\/td>\nThe people who developed the system had to choose names for the software functionalities (menus, screens, fields, etc.). While a generic name may cover all possible user of the functionality, it may not sound meaningful to users. On the other hand, a meaningful name may restrict the way people understand the functionality. COSWIN\u2019s Hazard Report is a perfect example of that.<\/td>\n<\/tr>\n
 <\/td>\n(2)<\/td>\nUsing COSWIN Resource Editor, any name in the system can be changed, in less than a minute.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
For example, the \u201cHazard Report\u201d can be changed to \u201cShift Report\u201d, \u201cQuality Report\u201d, \u201cOperation Report\u201d or anything else.<\/div>\n

 <\/p>\n

The choice of \u201cHazard Report\u201d highlights the possibility to use the functionality to report safety issues and launch corrective actions, in the form for example of a Job Request to the technical department, a direct Work Order or even a Purchase Request.<\/div>\n

 <\/p>\n

The same exact functionality could also be used for what is commonly called \u201cShift Reports\u201d or \u201cShift Log\u201d: during or at the end of a working shift, the shift leader reports what has happened. The purpose is to inform the next shift or launch actions by maintenance or other departments.<\/div>\n

 <\/p>\n

The same principle could be applied for reporting quality problems by production, through \u201cQuality Reports\u201d or \u201cDefect Reports\u201d: production logs quality problems and suggests or requests actions to be taken.<\/div>\n

 <\/p>\n

You can imagine other applications. In all cases, the \u201cHazard Report\u201d functionality \u2013 under this or another name of your choosing \u2013 ensures traceability: the incident (a production event, a quality problem, a safety risk etc.) is reported (who, what, when) and linked to an action (JR, WO or PR). It can then be followed up, measured and traced back to the initial event. <\/div>\n

 <\/p>\n

This process may or may not even be related to the maintenance department. It doesn\u2019t matter, it can still be managed in COSWIN.<\/div>\n

 <\/p>\n

As readers will have understood, we have just described a very important business process that ties together technical events and their consequences: an essential element of regulatory compliance and business management, usually not managed in the CMMS. <\/div>\n

 <\/p>\n

An example of application: quality management in Acome Xintai<\/strong><\/div>\n

 <\/p>\n

Acome Xintai Cable Co., Ltd. is a producer of RF cables (used in antennas), located in Shandong province. The semi-continuous manufacturing process requires a strong involvement from the maintenance team. During the initial audit conducted by Siveco at the beginning of the project, important savings opportunities were identified in using COSWIN to support Acome’s technical team for the resolution of quality problems.<\/div>\n

 <\/p>\n

In order to carry a given signal properly, the cables have to respond specifically to certain frequencies: may the cable be too thick or too thin (a few micrometers) at some point, the frequency response will show a peak out of the specified range and the whole batch will have to be scrapped.<\/div>\n

 <\/p>\n

When such defect is detected, a Hazard Report is raised in COSWIN, containing all related information such as the peak value in MHz. An inspection is then carried out on the production line, involving a number of tests: standard exchanges of bearings or gear-boxes, tightening of bolts, adjustment of speed control. For each such modification, a test is conducted, until the cause of the defect is identified. The challenging part of this procedure is that each modification can itself generate more defects – the entire process is very closely managed using Work Orders, one for each modification, all linked to the initial Hazard Report.<\/div>\n

 <\/p>\n


Example of Hazard Report at Acome Xintai<\/em><\/span><\/div>\n

 <\/p>\n

A given peak (identified by its MHz value) for a given production line is linked to a unique cause, which makes the historical record an extremely powerful tool to identify the cause of a defect, bringing a costly investigation from 2-3 days down to a few hours. This approach has resulted in important downtime reductions at Acome Xintai, as well as significant direct savings in raw material, energy, etc. In addition the perceived value of the maintenance team in the overall plant performance has been significantly improved!<\/div>\n

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

This article is the third in a series aimed at familiarizing our readers with lesser-known COSWIN functionalities, which can easily be configured by customers themselves to bring immediate benefits. Previous issues covered Contract Management<\/a> and Work Permits<\/a>. <\/div>\n

 <\/p>\n

The Hazard Report is perhaps one of the most interesting COSWIN features, as it essentially links operations to maintenance, in more ways than the name \u201cHazard\u201d seem to indicate (implying a reference to safety). This article will explain the basics of the Hazard Report functionality, elaborate some of its real-life implementations and present a example (application to quality at cable manufacturer Acome Xintai).<\/div>\n

 <\/p>\n

Hazard Report<\/strong><\/div>\n

 <\/p>\n

The hazard report is available for managing incidents or events that require attention. Its purpose is to lead to an action plan so that the incident does not repeat. The module is used to manage the complete cycle of a hazard report: create, update, delete, the effects, the recommended actions, and the follow up. Hazard reports are created against equipments (but this is not mandatory) and COSWIN stores all hazard report details. It also keeps a list of recommended actions and follow-up actions. \u2460 An incident is noted \u2461 A hazard report is created with various fields indicated below \u2462 The hazard report can generate various documents or transactions: Job Requests, Work Oder(s) or Purchase Order(s) to COSWIN Stock & Purchasing.<\/div>\n

 <\/p>\n

<\/div>\n

 <\/p>\n

\u201cHazard\u201d? What\u2019s in a name.<\/strong><\/div>\n

 <\/p>\n

Two things that should never be forgotten with CMMS and COSWIN in particular:<\/div>\n

<\/p>\n\n\n\n\n
 <\/td>\n(1)<\/td>\nThe people who developed the system had to choose names for the software functionalities (menus, screens, fields, etc.). While a generic name may cover all possible user of the functionality, it may not sound meaningful to users. On the other hand, a meaningful name may restrict the way people understand the functionality. COSWIN\u2019s Hazard Report is a perfect example of that.<\/td>\n<\/tr>\n
 <\/td>\n(2)<\/td>\nUsing COSWIN Resource Editor, any name in the system can be changed, in less than a minute.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
For example, the \u201cHazard Report\u201d can be changed to \u201cShift Report\u201d, \u201cQuality Report\u201d, \u201cOperation Report\u201d or anything else.<\/div>\n

 <\/p>\n

The choice of \u201cHazard Report\u201d highlights the possibility to use the functionality to report safety issues and launch corrective actions, in the form for example of a Job Request to the technical department, a direct Work Order or even a Purchase Request.<\/div>\n

 <\/p>\n

The same exact functionality could also be used for what is commonly called \u201cShift Reports\u201d or \u201cShift Log\u201d: during or at the end of a working shift, the shift leader reports what has happened. The purpose is to inform the next shift or launch actions by maintenance or other departments.<\/div>\n

 <\/p>\n

The same principle could be applied for reporting quality problems by production, through \u201cQuality Reports\u201d or \u201cDefect Reports\u201d: production logs quality problems and suggests or requests actions to be taken.<\/div>\n

 <\/p>\n

You can imagine other applications. In all cases, the \u201cHazard Report\u201d functionality \u2013 under this or another name of your choosing \u2013 ensures traceability: the incident (a production event, a quality problem, a safety risk etc.) is reported (who, what, when) and linked to an action (JR, WO or PR). It can then be followed up, measured and traced back to the initial event. <\/div>\n

 <\/p>\n

This process may or may not even be related to the maintenance department. It doesn\u2019t matter, it can still be managed in COSWIN.<\/div>\n

 <\/p>\n

As readers will have understood, we have just described a very important business process that ties together technical events and their consequences: an essential element of regulatory compliance and business management, usually not managed in the CMMS. <\/div>\n

 <\/p>\n

An example of application: quality management in Acome Xintai<\/strong><\/div>\n

 <\/p>\n

Acome Xintai Cable Co., Ltd. is a producer of RF cables (used in antennas), located in Shandong province. The semi-continuous manufacturing process requires a strong involvement from the maintenance team. During the initial audit conducted by Siveco at the beginning of the project, important savings opportunities were identified in using COSWIN to support Acome’s technical team for the resolution of quality problems.<\/div>\n

 <\/p>\n

In order to carry a given signal properly, the cables have to respond specifically to certain frequencies: may the cable be too thick or too thin (a few micrometers) at some point, the frequency response will show a peak out of the specified range and the whole batch will have to be scrapped.<\/div>\n

 <\/p>\n

When such defect is detected, a Hazard Report is raised in COSWIN, containing all related information such as the peak value in MHz. An inspection is then carried out on the production line, involving a number of tests: standard exchanges of bearings or gear-boxes, tightening of bolts, adjustment of speed control. For each such modification, a test is conducted, until the cause of the defect is identified. The challenging part of this procedure is that each modification can itself generate more defects – the entire process is very closely managed using Work Orders, one for each modification, all linked to the initial Hazard Report.<\/div>\n

 <\/p>\n


Example of Hazard Report at Acome Xintai<\/em><\/span><\/div>\n

 <\/p>\n

A given peak (identified by its MHz value) for a given production line is linked to a unique cause, which makes the historical record an extremely powerful tool to identify the cause of a defect, bringing a costly investigation from 2-3 days down to a few hours. This approach has resulted in important downtime reductions at Acome Xintai, as well as significant direct savings in raw material, energy, etc. In addition the perceived value of the maintenance team in the overall plant performance has been significantly improved!<\/div>\n

 <\/p>\n","protected":false},"author":1,"featured_media":8339,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17,259],"tags":[4,11,76,77],"_links":{"self":[{"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/posts\/2074"}],"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=2074"}],"version-history":[{"count":4,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/posts\/2074\/revisions"}],"predecessor-version":[{"id":8557,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/posts\/2074\/revisions\/8557"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/media\/8339"}],"wp:attachment":[{"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/media?parent=2074"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/categories?post=2074"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/tags?post=2074"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}