[foxboro] IEE Strategy Naming Conventions
- From: "Horlacher, Don" <DHorlacher@xxxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 6 Dec 2011 14:26:23 -0700
List,
My company will be upgrading from an old UNIX version (4.3) of I/A to
version 8.6 on the mesh, using Foxview/Foxdraw, Wonderware Historian, and the
IEE (now Foxboro Control Software 3.0) configurator. Invensys will be
performing the conversion of systems, except for the screens, which I will
re-create on the Foxdraw. I found out at the recent OpsManage conference in
Nashville that the conversion into IEE is made much easier if the LOOPID
parameter in the blocks is filled in. All of our existing blocks have blanks in
the LOOPID parameter.
My plan is to fill in the LOOPID parameters before Invensys starts the
conversion. I'm thinking of using the main control block tagname (eg. The PIDA
control block) for each loop, maybe appending the CP and compound name onto it.
However, for cascade loops, I am unsure of what to do. I am thinking of just
naming each loop within a cascade and let the strategies then point or connect
to each other. I am not up to speed yet on IEE. My question is, what are solid
naming conventions for strategies and LOOPID parameters, and how are more
complex relationships handled?
Regards,
Don Horlacher
Electrical/Control Engineer
ASARCO Hayden
520-356-3500
Email: DHorlacher@xxxxxxxxxx
_______________________________________________________________________
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:
- » [foxboro] IEE Strategy Naming Conventions - Horlacher, Don
