Re: [foxboro] Conectivity between nodes

Sadly, there are slips between implementation and design. A CAR should be
entered and worked since it clearly violates the design goals of the HMI.

BTW, the issue that Duc sees is not "CSA", but rather the way it is being
improperly used by the trend areas in a display. The mistake is in the
client not CSA itself. The client should not depend on CSA for normal
operation.

Regards,
 
Alex Johnson
Invensys Systems, Inc.
10900 Equity Drive
Houston, TX 77041
713.329.8472 (voice)
713.329.1700 (fax)
713.329.1600 (switchboard)
alex.johnson@xxxxxxxxxxxxxxxx

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of duc.do@xxxxxxxxxxxxxx
Sent: Friday, February 24, 2006 2:59 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Conectivity between nodes

>But, it doesn't change the design goal of CSA, i.e., that the loss=20
>of CSA does not impair operation of the plant and that you can=20
>schedule access to CSA for your convenience.

I beg to differ. When half of the available screens in a control room
are locked up due to a dead CSA, I'd say that pretty much impairs
operation.

Yeah, Alex, I know you said that it shouldn't happen, but watching it
happen for daily for a week convinced me that screen lock-up *does*
happen when CSA died.

(And I can't blame human nature to want to see if happens again on
another screen when the first one is locked up. Now you got two screens
at are out of commission for 5-6 minutes!)

My problem with a CSA hang-up is still there -- I just get better at
mitigating the symptoms when it happens.

Duc

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Johnson, Alex P (IPS)
Sent: Friday, February 24, 2006 3:44 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Conectivity between nodes

I don't know if they need it or not.

But, it doesn't change the design goal of CSA, i.e., that the loss of
CSA
does not impair operation of the plant and that you can schedule access
to
CSA for your convenience.

Regards,
=20
Alex Johnson
Invensys Systems, Inc.
10900 Equity Drive
Houston, TX 77041
713.329.8472 (voice)
713.329.1700 (fax)
713.329.1600 (switchboard)
alex.johnson@xxxxxxxxxxxxxxxx

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On
Behalf Of Weiss, Andreas
Sent: Friday, February 24, 2006 10:50 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Conectivity between nodes

> The theory behind CSA is that it is needed only for=3D20
> configuration and that
> maintenance can be scheduled around that activity. Taking it down is
> supposed to have no impact on operations.
>=3D20

We run scripts every night. These scripts use iccprt and other iccdrvtsk
functionalities to extract the control station database and export it
into other formats.

I think that these tools didn't work without an CSA. I've never checked
it should I?

Regards,
Andreas
=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: