Data routing using Layer-3 switch for 800xA verison 6.x
We are engineering a new project with 800xA version 6.0-3. In this project there are two platform. Platform NFA is existing platform running 800xA 5.1 with Infi-90 DCS. Platform WHP#3 is new greenfield platform to be engineered in 800xA 6.0-3-1 with AC800M and AC800M HI.
The final project scope is to operate the new platform completely (as the new platform will be unmanned) from existing platform using PLC connect.
Attached is the proposed network configuration. The communication between NFA and WHP#3 platform involves 4 levels of redundancy. Switch A (Fiber Optic and Wireless) and Switch B (Fiber Optic and Wireless). In this configuration the Wireless is using Layer-3 protocol via firewall for communication. Thus we are bound to use Layer-3 switch and have separate networks in WHP#3 and NFA platforms.
In this configuration I would like your advice about the overall system performance of 800xA considering the new platform will be completely operated from existing platform via PLC connect.
Request any kind of support or wayforward in this regards.
I realize this isn't exactly the point of your questions but using the PLC Connect product to connect to another 800xA system sounds like it would be...frustrating. No faceplates, no remote troubleshooting, etc.
There is a product called 800xA Multisystem Integration which might be helpful. I have zero experience with it so it might not work between versions.
The nicest option in my opinion would be to extend the existing 800xA v5.1 system to the new greenfield installation. This might require upgrading to v6.0.3 on the existing system but would have many benefits.
After that is complete you would have a pair of harmony connect servers, a pair of 800M connect servers and maybe an additional aspect server at the remote location (extra redundancy).
A lot of the ready made graphics, etc. go lost when using PLC Connect to interface an AC 800M. It sounds like a lot of work to gain a little, which still will be less than using AC 800 Connect and an O&G function library like REUSE.
I must agree, this sounds like a job for Multisystem Integration.
Are you sure 6.0.3 cannot interface with 5.1 over MI?
How fast and reliable is the link between NFA and WHP#3?
MI, RDP and to some degree MMS are not very resource intensive and could run on less bandwidth and higher latency. While on the other hand 800xA client server traffic is "heavier" and has more problems with latency and poor bandwidth.
About L3 routing, as far as I can tell PLC Connect remote OPC connection does not mind being routed over L3 network. MMS and IAC does not mind L3 routing either.
However, 800xA clients and servers *need* to be joined by a RNRP network. But even RNRP support L3 if you put Tunnel Area Border nodes on each side of the L3 network, e.g. using ABB NE87x RNRP Routers as the Layer-3 switches in the images. Also a PC with RNRP can act as TABN.
1. I suggest using MI in the first place.
2. You can also use Remote Desktop Protocol and run operator workplaces in virtual clients or Terminal Servers put on WHP#3 along with some aspect and connectivity servers there.
3. The whole HMI including OPC servers can be placed on NFA, only having the controllers on WHP#3 and accessed over FO/wireless, with or without RNRP (with is of course suggested for failover and link supervision). When staff is present on the unmanned platform they could use RDP back to NFA to do maintenanc/engineering.