Hi Don, Finally I see a mail regarding IEE. Ok. Now the process is something like this. While converting to IEE the CP saveall will be used. The CP saveall is imported into an object called BulkData in the IEE. During import it will ask you options for naming the strategies and other things. This is where Loopid helps you. What I can suggest is, for simple loops, jus give the loopid as the transmitter name without the "I" or "T", like 801F1001. Here 801 is the unit name, F stands for flow and 1001 is the numbers from the tagname. For the cascade loops you can use the name of the Master transmitter. Hope this helps. Thank you, Regards, Srikanth.P Invensys India Private Ltd Mail: Srikanth.Pisipati@xxxxxxxxxxxx H.P: +966 (0)568854702 -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Horlacher, Don Sent: Wednesday, December 07, 2011 12:26 AM To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] IEE Strategy Naming Conventions 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 *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail reception@xxxxxxxxxxxxx This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). _______________________________________________________________________ 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