Re: [foxboro] Emergency Shutdown testing
- From: "Pat Martens" <foxpat@xxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Fri, 10 Mar 2006 19:18:17 +0100
Another approach could be to perform an individual I/O test for the loops
conserned just like you would do during a looptest/commissioning phase.
This would involve manual manipulation of the outputs concerned one by one.
You could then load your application in an offline system and use something
like VPlink to simulate motor/valve feedback signals.
This should prove that your application is ok.
Once you have your simpel process simulation available in (something like)
VPlink you can re-use it any time you want. Very handy if you did some
drastic changes to your applic. and you want to make sure you have not
changed anything you did not intend to change!
VPlink works o.k. for us for our I/A DCS and our SMS safety PLC's
Regards,
Patrick Martens
Total Raff. Ned. N.V.
----- Original Message -----
From: <brad.s.wilson@xxxxxxxxxxxxxx>
To: <foxboro@xxxxxxxxxxxxx>
Sent: Friday, March 10, 2006 6:28 PM
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
Other related posts:
