Re: [foxboro] Emergency Shutdown testing
- From: "Johnson, Alex P (IPS)" <alex.johnson@xxxxxxxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Mon, 13 Mar 2006 12:46:41 -0500
Commercial issues need to be handled with your Account Representative.
Separately, I'll try to get him/her involved.
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 Pat Martens
Sent: Monday, March 13, 2006 11:20 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Emergency Shutdown testing
We were actually considering duplicate hardware.
For the costs of FSIM (which I understood runs only on solaris) you can buy
quite a number of FCP270 and (as I also understood) the block license for
these would be inexpensive as licensing is calculated based on the number of
connected I/O which is none!
Please correct me if I made the wrong assumptions!
Is there somewhere a document that explains the control block licensing
concepts?
We used to have block-equivalentes, then it became value points but for
FCP270 I'am a bit lost.
Regards,
P. Martens
Process Automation Specialist
Total Raff. Ned. N.V.
----- Original Message -----
From: "Johnson, Alex P (IPS)" <alex.johnson@xxxxxxxxxxxxxxxx>
To: <foxboro@xxxxxxxxxxxxx>
Sent: Friday, March 10, 2006 6:38 PM
Subject: Re: [foxboro] Emergency Shutdown testing
Some folks use FSIM to do this sort of testing. See this for a general
overview of our offerings
http://www.simsci-esscor.com/us/eng/services/operatortraining/default.htm
And
http://www.simsci-esscor.com/us/eng/products/productlist/fsimplus/FSIM+Plus.
htm for FSIM particularly.
FSIM runs the CP code so that you can be sure that what you see is what you
will get.
Alternatively, you can buy duplicate hardware. :)
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 brad.s.wilson@xxxxxxxxxxxxxx
Sent: Friday, March 10, 2006 12:29 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Emergency Shutdown testing
Although this doesn't directly relate to DCS, I'm curious how sites handle
testing of their ESD systems. Since we have nothing considered critical,
we do not have a standalone system like Triconex, but rather we've written
sequence code that directly toggles motors & valves and safes control
loops, in addition to using EXC blocks to handle DEP block shutdowns. Our
problem is that our reliability engineer wants to test those ESD programs
by turning on ALL the motors and then verifying that they all stop when the
code is run. I don't like to idea of having everything running dry &
deadheaded. If you test your ESD systems, how do you ensure that it will
actually do everything that you want it to do?
Brad Wilson
Process Control Engineer
ExxonMobil Chemical Co
Edison Synthetics Plant
732-321-6115
732-321-6177 fax
Brad.S.Wilson@xxxxxxxxxxxxxx
_______________________________________________________________________
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: //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: //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: //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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
