800xA use the control network for a Client
We have a 800xA system on our field - the field include 01 WHP and 01 FPSO.
The Servers are located on FPSO.
The WHP is "unmanned" but we intend to install a HMI operator station (client) on WHP for the well service activities.
The FPSO ICSS is connected to the PM866 on WHP through a fiber optic network and there is no spare cores for future expantion.
There is no client-server connected to WHP, there is 01 redunance control network from FPSO to WHP only. How can we connect the new client on WHP to the Server on FPSO without adding a client-server network?
There exist something called "collapsed networks" in the System Guide.
I.e. all nodes share same LAN. This is recommended/possible for smaller networks.
When using a switched network and industrial graded equipment I see no real problems with having a client or two on the control network as their "heavier" traffic is solely unicasted (=will not be seen by peer nodes on a switched network). However it must be tested if a client on control network is accepted by the aspect server (as of 5.1 "node up" by RNRP is required before connection is activated) - without this "node up" the client addition will seem to work from the wizard, but the client itself will never be able to launch a workplace.
Alternatively, using VLAN technology the client/server network could be brought to the WHP.
IMPORTANT: network separation and isolation will be reduced from using a collapsed or VLAN segmented network. Multicast storms and other malicious stuff is more likely to occur on networks with IT/office equipment compared to a "clean" control network.
A broadcast storm might (will) affect all VLANs on a trunced link.
Is your customer prepared to run with less isolation (=protection) than what a traditional control network offers?
Storms and malicious activities could be reduced (not prevented) by using a firewall and port rate limiters.
The newly released ABB NE870/871 RNRP router can do both of these plus act as a RNRP Area Router, i.e. replace the traditional Connectivity Server as router or act as control network area divider, e.g you could define the WHP control network area with a different RNRP Area number and let the NE87x limit the number of nodes able to communicate across the FPSO / WHP border.
Area 1: FPSO client server network
Area 20: FPSO control network
Area 21: WHP control network (20 and 21 interconnected with a NE870)