[foxboro] Question to Gaylon (was 3rd Party products on windows)

Re: because we don't use the CRTs as our primary operator interface

What do you use for your primary interface if not the WP?



Regards,
 
Alex Johnson
Invensys Systems, Inc.
10707 Haddington
Houston, TX 77043
713.722.2859 (voice)
713.722.2700 (operator)
713.932.0222 (fax)
ajohnson@xxxxxxxxxxx
For the latest information on ArchestrA, go to
http://www.invensys.com/Archestra.html.
 

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Hicks, Gaylon F.
Sent: Wednesday, August 25, 2004 11:40 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] 3rd Party products on windows.

Since this is Soapbox Day on the list server, move over David. My turn.

We are in the design part of the process of installing a lot of new
ZCP270/200 series hardware here on BFN Unit 1, FAT (hopefully) spring
2005.  The target I/A version is 8.0.  During initial discussions with
Foxboro I really pushed for a Sun/Unix AW on this system.  To make a
long story short, 8.0 will not support the 50 series boxes.  So, like it
or not (NOT!), I'm going to be the proud owner of an AW70.  The WP70s I
mind much less, because we don't use the CRTs as our primary operator
interface.  I really think we aren't far from a Windows Only I/A future.


The "I don't like Windows" viewpoint has been expressed at the Users
Groups meetings before, but we should be sure to do it this year also
(Remember the Alamo!). =20

I realize that the preceding mini-diatribe added nothing useful what so
ever to the world, but I feel better.

Gaylon Hicks=20



-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of David Johnson
Sent: Wednesday, August 25, 2004 9:17 AM
To: Foxboro@xxxxxxxxxxxxx
Subject: [foxboro] 3rd Party products on windows.


I have been very quiet on the Foxboro bashing for a very long time.  But
I=20
cannot let some of the recent threads go without weighing in.

There are problems that are inherent to windows, and there are problems=20
that are due to poor implementation, or obsolete third party products.
I=20
have heard Foxboro salespeople try to justify these as problems due to
the=20
frequency of product updates for windows, or the amount of testing
required=20
for each service pack etc. Where was Windows 2000? Not on I/A.  I have
also=20
had a salesman tell me that all these problems would be solved if we
(the=20
people who did not ask for the windows product to begin with) were
willing=20
to pay more (remember Windows =3D lower cost of ownership) so that they
(the=20
people selling the product) could do adequate testing to keep products
and=20
licenses up to date. That's crazy.

If Foxboro wants me to make the move to windows (without screaming about

it), they must at least base load a version, like XP, with the current
and=20
tested third party tools.  Security has to be a priority, not an=20
afterthought.  No longer should we accept products that are not up to
date,=20
or even supported on the OS that is being shipped coming from Foxboro.
MKS=20
toolkit was not up to date.  Exceed was not up to date. Installing other

applications (and that's why we are demanding windows right?) can have=20
disastrous DLL and/or registry conflicts.  Some of these issues may be=20
fixed in the newest release, I don't know.  I do know Foxboro,
Wonderware,=20
Rockwell Automation (kind of), Yokogawa and Emerson are all advising=20
against installing XP SP2 until further notice. So it appears that
Foxboro=20
is not alone with these issues. Of course, some of these problems occur
on=20
Solaris too, but the operating system releases are less frequent, third=20
party applications are fewer, and virus risks are fewer (but still
there).

If I'm going to commit to a windows based future, The vendors need to=20
commit to a high quality, robust system that has components that have
been=20
tested together.

David Johnson








"Quote me as saying I was misquoted."
Groucho Marx=20

=20
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
=20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: