Python in Process Control?

[Carlos Ribeiro]

On Tue, 05 Oct 2004 06:10:17 GMT, Andrea Griffini <agriff at tin.it> wrote:
> In this field seems to me that really people try to
> get above by standing on each other feet instead than
> on each other shoulders; but this doesn't look to me
> like just a software problem.

Nice definition.
 
> ... (I can't think to a customer
> even *wanting* to change the library version in a NC
> machine he bought, often the investments are rather
> high and the approach I see is "if it works just don't
> dare to think about touching it") 

I think you've nailed the root of the problem (or at least one of the
roots). For the most part, customers tend to be careful, and they
approach solutions in this area as true 'black boxes'. It may be
because they're afraid of the unknown, or because bugs in control
software can be really costly, and they don't want to be held liable
for it (at least they can say, "I never messed with it, if it's
broken, it's not my fault").

Put in other words: In many cases (not all, of course), the people who
buy this stuff are not engineers -- who in some cases are not even
involved with the process --, but the money guys. It's expensive, it
will save the company money, so the money guys sign the bill... but
only if someone else (the vendor) takes full responsibility for it.
It's a recipe for close solutions, in my opinion. The money guys also
tend to buy the same stuff other companies bought, which makes this
behavior self-sustaining, in a way.

Keeping with the same reasoning line, why don't the engineers that
work in the company take more responsibility? Because they were never
in such a position. They don't have a choice. They have to keep things
running, period. The one who messes up with stuff is fired. And doing
development is not their company business, anyway. Want to do it? Go
working for a vendor.

BTW, this kind of behaviour can't last forever. It's inefficient, and
it's doomed to death, sooner or later.

-- 
Carlos Ribeiro
Consultoria em Projetos
blog: http://rascunhosrotos.blogspot.com
blog: http://pythonnotes.blogspot.com
mail: carribeiro at gmail.com
mail: carribeiro at yahoo.com