The way hardware and software goes through such rapid development, one = can only try and keep up wherever possible. We now have 23 nodes on = our system and have decided to move all of the software to version 6.3 = for all of our AW/AP's and WP's and the v2k_01 software version for all = of our controllers. So far, this release shows good stability and = should serve us for at least the next five years. Moving to this = release will eliminate your having to keep up with what software is on = what controller and which quick fixes need to be applied. Cost is a major factor in standardizing the rest of the hardware as far = as workstations and other Sun products. We have a pretty good mixture = of workstation hardware with 51B and 51D and 51E boxes. The = 'advantage' program allows an opportunity to get everything at the same = level but this advantage disappears each time Invensys/Foxboro follows = Sun into another box. All one can do is weigh the cost of training, = spare parts, and maintenance on older hardware against the cost to = upgrade. When these costs equal or surpass the 'latest and greatest', = look to the horizon to see if something new is coming out before you = jump onto the 'advantage' bandwagon. For example, right now might not = be a good time to start upgrading since Solaris 8 is on the verge of = being our new operating system for unix and that includes a NEW = workstation processor type. -----Original Message----- From: Eudilson N=FA=F1ez Cossio = [mailto:Eudilson.Nunez@xxxxxxxxxxxxxxxx] Sent: Friday, November 16, 2001 2:18 PM To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] The best of the Jungle! Hi List, We have several DCS Foxboro to make control in our petroleoum = refinery. Since Y2K remediation, the new projects suggest to install the last = vesion and now a day we have a jungle of version in software and hardware and several quick fixes required for each version too. My question is:=20 Based on your experiences what do you recommend to make a good administration and support about the upgrades for this kind of systems = in a big distributed application as in our case? Could you please suggest a good selection to standarize the system and reduce the knowledge, spare parts, etc required for at lease 5 years? For example we have (as a main description of our systems) the = following list: Foxboro I/A vesions 4.3, 6.1, 6.1.2, 6.2.1 CP 10, 30, 40B, 60 AW, AP, WP Series 50, 51, 70 styles A, B, B1, D, E Thank you very much for your concepts. Sincerly, Eudilson Nunez =20 =20 ___________________________________________________________________ This list is neither sponsored nor endorsed by The Foxboro Company. Use the information obtained here at your own risk. For disclaimer, see http://www.thecassandraproject.org/disclaimer.html#maillist list info: //www.freelists.org/list/foxboro subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave ___________________________________________________________________ This list is neither sponsored nor endorsed by The Foxboro Company. Use the information obtained here at your own risk. For disclaimer, see http://www.thecassandraproject.org/disclaimer.html#maillist list info: //www.freelists.org/list/foxboro subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave