{"id":2306,"date":"2010-11-24T09:00:29","date_gmt":"2010-11-24T01:00:29","guid":{"rendered":"http:\/\/www.sivecochina.com\/en\/?p=2306"},"modified":"2014-10-22T09:27:53","modified_gmt":"2014-10-22T09:27:53","slug":"coswin-tips-tricks-repairable-standby-equipment","status":"publish","type":"post","link":"https:\/\/newsletter.bluebeecloud.com\/en\/tips-tricks\/coswin-tips-tricks-repairable-standby-equipment\/","title":{"rendered":"COSWIN: Repairable & standby equipment"},"content":{"rendered":"
A common problem in maintenance is replacing equipment from production, let us say a motor, repairing or refurbishing it (either on- or offsite) and then storing the repaired motor for the next time it is needed. There are two ways to do this:<\/div>\n

 <\/p>\n

A. Replacing equipment<\/strong><\/div>\n

 <\/p>\n

\u2460 With the Move command in COSWIN equipment file the equipment A along with all its history is moved to the Zone Repairables (or Refurbishment or Workshop or \u2026) \u2461 There it will stay until moved somewhere else. All its history, work orders etc follow with it. \u2462 Again, with the Move command, replacement motor B which has been refurbished is moved to the location and zone of A.<\/div>\n

 <\/p>\n

<\/div>\n

 <\/p>\n

The second method is elegant and comprehensive but requires more information:<\/div>\n

 <\/p>\n

B. Equipment & Stock items managed by serial number<\/strong><\/div>\n

 <\/p>\n

\u2460 Create an equipment, say a motor \u2461 Create & connect a part, say a motor \u2462 Declare the part a repairable equipment COSWIN will now know what to do in the future operations.<\/div>\n

 <\/p>\n

<\/div>\n

 <\/p>\n

\u2463 A work order is created, say, Unfitting of equipment A. Replace S-1 with S-2, another repairable with a serial number in stock \u2464 The WO is presented to stores, S-2 is issued for exchange. Note that COSWIN is aware of the transaction, because the WO number shows that this transaction is for a refurbishment or a repair of a repairable \u2465 The repairable S-2 is issued on the WO number 0043 and will replace S-1.<\/div>\n

 <\/p>\n

<\/div>\n

 <\/p>\n

\u2466 On the same Work order the damaged S-1 motor is returned to COSWIN Stock \u2467 COSWIN now proposes that a sibling WO is created that will track the costs of the repairs to S-1 \u2468 S-1 is now repaired internally or via the COSWIN Stock functionality quotations for repair are requested \u2469 A quotation is accepted, the repair is carried out \u25cb11 S-1 returns to stock with the costs of repair recorded \u25cb12.<\/div>\n

 <\/p>\n

<\/div>\n

 <\/p>\n\n\n\n
COSWIN shows all of the above transactions. From the above it follows that:<\/strong>
 
\n  In the history of the equipment A, there will be a full log of all the motors or repairables that have been attached or removed.
\n  In Stock there will be a history with costs of all repairables that have been issued and received into stores.
 \n <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"
A common problem in maintenance is replacing equipment from production, let us say a motor, repairing or refurbishing it (either on- or offsite) and then storing the repaired motor for the next time it is needed. There are two ways to do this:<\/div>\n

 <\/p>\n

A. Replacing equipment<\/strong><\/div>\n

 <\/p>\n

\u2460 With the Move command in COSWIN equipment file the equipment A along with all its history is moved to the Zone Repairables (or Refurbishment or Workshop or \u2026) \u2461 There it will stay until moved somewhere else. All its history, work orders etc follow with it. \u2462 Again, with the Move command, replacement motor B which has been refurbished is moved to the location and zone of A.<\/div>\n

 <\/p>\n

<\/div>\n

 <\/p>\n

The second method is elegant and comprehensive but requires more information:<\/div>\n

 <\/p>\n

B. Equipment & Stock items managed by serial number<\/strong><\/div>\n

 <\/p>\n

\u2460 Create an equipment, say a motor \u2461 Create & connect a part, say a motor \u2462 Declare the part a repairable equipment COSWIN will now know what to do in the future operations.<\/div>\n

 <\/p>\n

<\/div>\n

 <\/p>\n

\u2463 A work order is created, say, Unfitting of equipment A. Replace S-1 with S-2, another repairable with a serial number in stock \u2464 The WO is presented to stores, S-2 is issued for exchange. Note that COSWIN is aware of the transaction, because the WO number shows that this transaction is for a refurbishment or a repair of a repairable \u2465 The repairable S-2 is issued on the WO number 0043 and will replace S-1.<\/div>\n

 <\/p>\n

<\/div>\n

 <\/p>\n

\u2466 On the same Work order the damaged S-1 motor is returned to COSWIN Stock \u2467 COSWIN now proposes that a sibling WO is created that will track the costs of the repairs to S-1 \u2468 S-1 is now repaired internally or via the COSWIN Stock functionality quotations for repair are requested \u2469 A quotation is accepted, the repair is carried out \u25cb11 S-1 returns to stock with the costs of repair recorded \u25cb12.<\/div>\n

 <\/p>\n

<\/div>\n

 <\/p>\n\n\n\n
COSWIN shows all of the above transactions. From the above it follows that:<\/strong>
 
\n  In the history of the equipment A, there will be a full log of all the motors or repairables that have been attached or removed.
\n  In Stock there will be a history with costs of all repairables that have been issued and received into stores.
 \n <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"author":1,"featured_media":8356,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17,259],"tags":[4,78,79],"_links":{"self":[{"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/posts\/2306"}],"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=2306"}],"version-history":[{"count":2,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/posts\/2306\/revisions"}],"predecessor-version":[{"id":8556,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/posts\/2306\/revisions\/8556"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/media\/8356"}],"wp:attachment":[{"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/media?parent=2306"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/categories?post=2306"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/tags?post=2306"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}