[EAS] Reuse and Recycle...

[Mike McCarthy]

I tend to agree with Gary. In a true management assessment, what does 
the repair buy?  If it keeps an old machine with old, but tested and 
reliable software running a few more years compared to a $10K capital, 
software upgrades, and associated headaches, then the $200 per machine 
repair is very well spent.

We had office and automation computers starting to fail one right after 
the other. A little digging revealed all the mother board caps had 
failed. So we shot gunned all of them in one round. Took a few days, but 
we simply moved stations around repaired machines and loaded logs into 
them as needed during transitions. Offices were done over the weekend.

Since the automation system was running Win2K and we'd have needed to 
upgrade to XP, we saved no less than $10K in capital. Add another $25K 
in software upgrades to not only the OS, but also the automation system 
as well as integration time.  That $2000 project paid a 35:1 cost to 
value payoff and bought us two more (and ongoing) years of use.

I apprecaite the fact some things require replacement and there is a 
point of diminishing returns.  But when the cost to value ratio is so 
lopsided, I'm also just sayin...

MM

On 7/13/2012 5:53 PM, Gary Glaenzer wrote:
>         >  I have to factor in true man hours cost vs. other projects that
> need the talent of my people vs. the replacement costs.  Much as I hate that
> technique, I>have to agree with Clay (Which I usually do anyway).
>
> One must also factor ( in the negative ) the man -hours that would be spent
> re-loading all programs and files from the old to the new box, if the box
> were replaced.
>
> I would venture that time shot doing such tasks far exceeds the time he
> spent replacing capacitors.
>
> Just sayin'
>
> Gary
>