The Cyber-Spy.Com Usenet Archive Feeds Directly
From The Open And Publicly Available Newsgroup
This Group And Thousands Of Others Are Available
On Most IS NNTP News Servers On Port 119.
Cyber-Spy.Com Is NOT Responsible For Any Topic,
Opinions Or Content Posted To This Or Any Other
Newsgroup. This Web Archive Of The Newsgroup And
Posts Are For Informational Purposes Only.
From: firstname.lastname@example.org (bob peterson)
Subject: Re: Avoiding PLCs
Date: 14 Oct 2002 07:09:55 -0700
References: <0Qhq9.email@example.com> <firstname.lastname@example.org>
NNTP-Posting-Date: 14 Oct 2002 14:09:56 GMT
email@example.com (Steve Cothran) wrote in message news:<firstname.lastname@example.org>...
> >> "JohnS" wrote in message
> Unfortunately every customer then seems to insist that we
> >> > build using the make of controller already in use by them.
> That is an unfortunate fact of life, and I'll bet money that it's not
> gonna change anytime soon. Since I started my company, we started with
> 1 brand of PLC, and we now support 6. The bill each year for all the
> software service contracts/upgrades/replacements/licenses is
> breathtaking. You just have to charge the client a rate commensurate
> with your costs.
> Some of your customers will not understand, and you will have to look
> for others. Last month, a customer wanted me to program a machine
> (medium press, poorly built electronics) based on a Basic Stamp, (on a
> kludge-board) that someone had thrown together. I refused the job for
> liability reasons, now the customer is pissed at me. But it's much
> better to have him pissed than a workmen's comp judge.
Smart move, but the workman's comp issue is not the problem. In most
states workman's comp only applies to the company that the worker is
employed by. Venders can and are sued on a regular basis. Its why
you have professional liability insurance. Your company does have
liability insurance, right?
> If you design and implement your own controller, you better have deep
> pockets or good insurance...because much more than a scratch on a user
> that can be attributed to your controller, and you're dog meat.
OTOH - the main issue is not so much the liability issue as can you
make money working on some oddball thing thought up in someones garage
and do it safely.
Go Back To The Cyber-Spy.Com
Usenet Web Archive Index Of
The sci.electronics.design Newsgroup