Vman
Senior Member
If it ain't broke, don't fix it
Posts: 460
Gender:
|
I can also see how for companies that use Advanced Manufacturing where they may want to keep track of labor and resources that are being committed for repairs rather than normal production. In some company's, your repair section is pretty self-contained, in others, some repair has to be sent out to the factory floor (for example, replacement of a surface-mount IC may be done at the one station that has the equipment, which may not be in the repair section), or to an outside vendor. I would think that you would want to be able to differentiate between warranty and customer-paid for service or repair. My main experience with repair is from my time in the military, where I was in maintenance units. One thing that might also be useful would be to assign some sort of status code to a repair (either the S/O or W/O). If your company does a lot of repairs, or this is its primary business, then you would want to run reports that tell you what's up with an item. For example, an item may go from w/shop, to w/customer authorization for repair, to w/parts (if required) to in shop, to Q/C, and finally to shipping. Of course, all this could turn a really good, simple module in to a pretty complicated mess.
|