Re: [foxboro] Documentation of a Foxboro I/A system

  • From: "Jim Mowrey" <jmowrey@xxxxxxxxxxxxx>
  • To: <foxboro@xxxxxxxxxxxxx>
  • Date: Thu, 8 Jun 2006 16:04:41 -0400

Concur.  We are doing a big backdoc job right now with it.  

Jim

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Troy L Brazell
Sent: Thursday, June 08, 2006 3:02 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Documentation of a Foxboro I/A system


Anton,
Even knowing that Foxboro wants to do away with CAE, like UNIX, they will
"pry it from my cold dead hands". Like Mr. Burbach said it will do what you
want. Has some quirks, but over all is one of the more useful tools that I
use.

Troy L. Brazell
Duke Energy Field Services
Sr. Process Control Analyst
ISA CCST
Phone (405) 263 4130
Cell    (405) 301 2994
Okarche Plant
Route 3 Box 95
Okarche, OK. 73762
*****************************
MS Windoze the cure for Insomnia
*****************************


                                                                           
             "Burbach,                                                     
             Norbert"                                                      
             <norbert.burbach@                                          To 
             ips.invensys.com>         foxboro@xxxxxxxxxxxxx               
             Sent by:                                                   cc 
             foxboro-bounce@fr                                             
             eelists.org                                           Subject 
                                       Re: [foxboro] Documentation of a    
                                       Foxboro I/A system                  
             06/08/2006 01:18                                              
             PM                                                            
                                                                           
                                                                           
             Please respond to                                             
             foxboro@freelists                                             
                   .org                                                    
                                                                           
                                                                           




Anton,
I'd say use FoxCAE if just want to back document your system.
It's fast and can handle all your nodes.

Norbert

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Prinsloo, Anton
Sent: Wednesday, June 07, 2006 4:58 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Documentation of a Foxboro I/A system

Dear All,
I would like to ask some input as to the best possible way to document
my system. I do require a method to back document a virtually
undocumented system and it MUST include the ability to generate loop
drawings, using data sucked from a running system.

I have a 3 node Unix system that has recently been upgraded from 51D to
P81 servers/workstations, SunOS 5.8, IA version 7.1.1.

I am leaning towards the use of FoxCae, but I have been informed that it
is not the preferred tool, is no longer supported, and that IACC is the
way to go.

I have a very negative view of IACC in its current format/version - it
is laden with bugs, it is not robust, it is seriously restrictive in its
operation,  is not intuitive and I will need serious convincing before I
would consider using it.

What are users out there doing right now?

Hope to hear from you soon,
Kind regards

> Anton Prinsloo
> Control System Superintendent
> Zinifex Century Mine
> Tel: +61 (07) 4769 5762
> Mob: +61 (0) 423 608 734
> Fax: +61 (07) 4769 5764
> Email: anton.prinsloo@xxxxxxxxxxx
>
>



_______________________________________________________________________
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: