Re: [foxboro] FXBAIS vs PI OPC Interface
- From: "Toecker, Michael" <mtoecker@xxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 24 Jun 2008 15:10:31 -0500
Extra loading from business systems is not an issue that can be taken
lightly. At the Hatch Nuclear plant in Georgia, a rebooted business
system that was requesting data from the process network triggered an
emergency shutdown of the plant (48 hours long). It would appear likely
that the external system had either write capability to tags, or the
volume of tags caused the process to be interrupted due to bad tag
quality.
The safety systems interpreted the condition as a massive drop in the
amount of water being used to cool the reactor, triggering a shutdown
(as the system was designed to do).
The takeway is this: Be aware of the interaction you allow to your
systems, and how effects from the business network can translate back
into your process network. There was no mention of the type or
manufacturer of the control system in use at Hatch.
http://www.washingtonpost.com/wp-dyn/content/article/2008/06/05/AR200806
0501958.html
Sincerely,
=20
Michael Toecker
Burns and McDonnell Engineering
Control System Security Group
mtoecker@xxxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Jack.Easley@xxxxxxxxxxxx
Sent: Tuesday, June 24, 2008 2:39 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FXBAIS vs PI OPC Interface
Yes, PI fxbais can be setup to be read-only. Sadly, in our case it is
not. So use of PI read-only from the MESH with a good Firewall is
relatively secure.
However, even if PI access is set up read-only, you should not forget
the matter of additional loading of your control system when PI tags are
added by the PI administrator. We experienced problems with this when at
Version 6.12 NODEBUS with loaded CP30/40s and Integrator 30s.
I don't think AIM is involved with the PI fxbais Interface, only FoxAPI.
Jack Easley
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Johnson, Alex P (IPS)
Sent: Tuesday, June 24, 2008 1:05 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FXBAIS vs PI OPC Interface
Re: Read-only and FoxAPI (and AIM*API for that matter)
It is possible to configure read-only access using FoxAPI. This
configuration is done in the /opt/fox/ais/bin/an_init.tcp file on the
machine running the netFoxAPI Server (an_server).
If this is set, it does not matter what PI is configured to do, the data
will not be written.
For AIM*API, the file is /opt/aim/bin/an_init.tcp.
Confidentiality Notice: This email message, including any attachments,
=3D0A=3D
contains or may contain confidential information intended only for the
=3D0A=3D
addressee. If you are not an intended recipient of this message, be =
=3D0A=3D
advised that any reading, dissemination, forwarding, printing,
copying=3D0A=3D
or other use of this message or its attachments is strictly prohibited.
If=3D
=3D0A=3D
you have received this message in error, please notify the sender =
=3D0A=3D
immediately by reply message and delete this email message and =
any=3D0A=3D
attachments from your system.=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
- References:
- Re: [foxboro] FXBAIS vs PI OPC Interface
- From: Jack.Easley
Other related posts:
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- Re: [foxboro] FXBAIS vs PI OPC Interface
- From: Jack.Easley