From: Luke Graham <spoooq@...>
Date: 2005-03-10T08:41:35+09:00
Subject: Re: scada: killer app for ruby

I think gnu scada systems are unlikely for a few reasons.
Customers want support more than anything, costs for
a broken scada can be calculated in wheelbarrows of
cash per minute. Scada is boring. Scada is hard.
The cost of integration can be more than the cost of
the software anyway. Finally, anyone who knows
anything about it is probably already doing it for a living.
Would you run your control systems on some kids
part-time experiment?

One last thing.. ruby is fine for the windows end, all the
protocols can be implemented.. but its just not going
to work on the embedded end.


On Wed, 9 Mar 2005 21:31:11 +0900, Jason Sweat <jason.sweat@gmail.com> wrote:
> On Wed, 9 Mar 2005 21:17:58 +0900, Simon Strandgaard <neoneye@gmail.com> wrote:
> > On Wed, 9 Mar 2005 20:51:29 +0900, "Pe�a, Botp" <botp@delmonte-phil.com> wrote:
> > > In searchning for scada systems on the net, i noticed that they are usually
> > > written in c/c++/c# and most of the systems are proprietary (eg, citect,
> > > rockwell) and worst, a lot are running in windows system. There are gnu
> > > scada systems sprouting but are very very alpha.
> >
> > what is scada ?
> >
> > --
> > Simon Strandgaard
> 
> From way back when I worked in Industrial Control, an achronym for:
> Supervisory Control And Data Acquisition.
> 
> Basically a system to montor PLCs (Programmable Logic Controllers,
> special purpose computers, usually wired up to machines in plants)
> that both capture data about what is happening on the system (from
> sensors wired to the PLC) and can send setpoint information to the
> PLCs (which they use via actuators again wired to the PLC).  There
> usually is some PC software which displays all of this graphically.
> 
> HTH
> 
> Regards,
> Jason
> http://blog.casey-sweat.us/
> 
> 


-- 
spooq