Ted just an opinion use SOTD (Standard of the Day)you are bound to end up with both types as the size of the logical process unit is the likley driver another area to consider is the new gateway FBM's bringing your foreign devices (PLC's...) in below the CP rather than into their own station (gateway)this makes sense from a control and distribution point of view but makes the FCP's 2MB fieldbuss a bit of a bottleneck when compared to the ZCP's multiple fieldbuss capability a con for the FCP is you have to provide DC power and you probably would choose seperate power to the base plate power in my plant I am running CP60's each with 30 200 series FBM's spread over 5 base plates the CP's are not working very hard yet i am sitting at the FCP I/O limit in a nutshell the FCP's are my preference but my process will probably dictate ZCP on another note, all you UNIX users (and I am one) the reference to a P91 Host, check out PSS 21H-4U6 B4 and 21S-1B10 B3 the windoze version of IA has come a long way (on paper) Shaun NZ Steel -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Johnson, Theodore (Ted) S Sent: Wednesday, 8 March 2006 09:22 To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] Migration -- FCP vs. ZCP?=20 Hello everyone, =20 At our refinery we have been incrementally upgrading our relatively small 2 node I/A system as time/money/justification/projects/outages have allowed. In the last 2 years we have gone from v4.3 -> v7.1, 51B -> F, Legacy historian -> AIM*, CP30/40 -> CP60 (recently installed 200 series FBMs connected via FCM10s and fiber hubs), and soon DM -> FoxView. Next month we will be replacing our Carrierband LAN Interface modules with ATS and P91 (as boot host) and installing ethernet switch pairs in strategic locations. Therefore, soon we will have the basic Mesh infrastructure to build upon and migrate to over time. [At our next major outage opportunity (Turnaround 2009), we will consider adding the Solaris machines on the MESH or converting to Windows machines on the MESH, cp60 ->270, ICC -> IACC or?, etc...] The discussion we are having now is whether we should continue to install/upgrade centrally located CPs (ZCP270s) or migrate towards using remote mounted CPs in the field (i.e. FCP270s). =20 In addition to future upgrade considerations (2009), we have a more immediate new capital/expansion project (2007 start-up), the timing of which makes sense to install 270 controllers. The scope is adding 4 I/O cabinets in 3 different areas (requiring 4 pairs of FCPs or 2 pairs of ZCP w/FCM100). Besides purchase price, there are other considerations such as future CP upgrades (ability to combine/remove CPs), number of FBMs supported, peer-to-peer connections, engineering/maintenance training, spare parts, etc. [Note: currently 270s will support either 100 or 200 series I/O, but at some point in the near future they'll be able to support both types of FBMs at the same time.] At this time the project team is leaning towards using FCPs. =20 =20 Thinking more long term (depending on new project decision and future CP60 -> 270 upgrade path) we could eventually end up with either: =20 a) All ZCPs - Use ZCP on new project and upgrade existing CP60s to ZCP270s (in existing I/O cabinets change FCMs from 10 to 100),=20 =20 b) All FCP - Use FCP on new project and upgrade existing CP60 to FCP270s (use same fiber between control room and I/O cabinet but change FCM10/baseplate to FCP/baseplate); or =20 c) Mixed FCP/ZCP architecture - Use FCP on new projects and/or ZCP on future upgrades.=20 =20 I have begun listing the pros and cons of FCP vs. ZCP :=20 =20 FCP (reference PSS 21H 1B9 B3) =20 Pro: Hardware slightly cheaper No FCM required Less power consumption per module (8.5W vs 15W) Mounted remotely (puts more D in DCS?) Minimize/free up precious real estate in DCS cabinets in control room =20 Cons: =20 Supports only 32 series 200 FBMs or 64 100 series For equivalent I/O capacity, FCP software license slightly more expensive than ZCP license =20 ZCP (reference PSS 21H 1B10 B3) : Pros: Same form factor/layout as previous CPs Supports more FBMs (120) Easier to combine CPs (reduce overall number of CPs) on future upgrades (CP60-> ZCP)=20 More controls in fewer number of CPs resulting in fewer (potential) peer to peer connections=20 Cons: Additional hardware components required (FCM100, 1x8 mounting structure) vs FCP Overall hardware cost appears to be slightly more expensive =20 What are other pros and cons regarding FCP vs ZCP? Architecturally, is one better? Technically, is one superior? Long term which will be the least expensive solution? Will one be better supported by Invensys Foxboro (preferred product/architecture)? How does this compare with competitive DCS manufacturers architecture direction (FCP more like Delta V)? Which way would you go (FCP or ZCP) and why? =20 Any other thoughts, comments, concerns, etc. would be greatly appreciated... Regards, =20 Ted Johnson Instrument and Control Engineer Tesoro Alaska PO Box 3369 54741 Tesoro Rd Kenai, AK 99611 Direct: (907) 776-3568 Cell (907) 398-8710 Fax: (907) 776-3863 Email: tsjohnson@xxxxxxxxxxx <BLOCKED::mailto:tsjohnson@xxxxxxxxxxx> =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: //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: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave