Recent Control & Safety Systems Discussions
Similar Posts
how do implement having two proplus from two delta V system but I want to have just one delta V network for two proplus and the two different delta V system.
Establishing Pi Historian Communication with DeltaV
Establishing a communication netTAP NT 100 from Hilscher with DeltaV
How to establish communication with a OPC Client software on NON DeltaV remote PC via cisco firewall?
Network Architecture Considerations in Ovation Control Systems
Share

Delta v network establishment for system

dear all,

I have to ask about the network establishment of delta v network, I have four section of plant each section have 4 controller and controlling the dedicated part and having its own station for each control section. Now I want to make a network such that to bring these all four controller on one server and want to manage and create database on that server, how will i establish the network which setting will be required on this server i need help to establish this network so every section of four can send its data to server and main database will establish there. I need information of network configuration and also software setting of deltav.

Second thing that these each of four station have assign as a proplus, but when I centralize the system how one proplus station setting will be done, as each delta v system have only one proplus so what would be status of each station when we combine all of them how we change the setting for bringing them to one system.

Thank you

regards

K.Jadoon

Yawar Khan
  • wtelkins
    If I'm reading this correctly you have 4 distinct DeltaV systems with 4 Proplus stations and 4 system ids.
    A DeltaV system can only have one Proplus and one system ID so to integrate the 4 into one system is completely doable but you will have to choose which existing Proplus will be the one you keep.
    The other stations can be converted to Engineering stations on the new integrated system.
    Logistically you will have to setup a network infrastructure that will allow you to combine all the switches into one big DeltaV network with the ProPlus you have chosen and then there's going to be a whole lot of minor steps around decommissioning/recommissioning controllers onto the new network, exporting databases and importing/integrating them into the primary Proplus etc. I would strongly suggest using your local DeltaV service contacts to perform this.
  • depthcharge623

    In reply to wtelkins:

    I just finished doing something very similar to this and it is no easy task. Something else you will have to consider is licensing. Specific licenses (controller redundancy, workstations, DSTs, etc) are associated with system IDs. So to combine systems you will have to make sure the ProPlus you keep has enough licenses. If you don't have enough, you will need to purchase more. You can speak to your LBP to see if it will be possible to dissolve the three other system IDs and move them all onto the system that will remain.
  • ELvin John
    Based on my experience of doing 3 merger projects, I'll like to bring to your attention that such projects are not easy. There are a lot of considerations that need to be taken into account before which you can go ahead and merge.

    I assume that these 4 systems which you mention would be at different software versions. You will need to bring them to a common DeltaV version and then proceed to evaluate the software elements that would eventually be common, for eg., alarm priorities, alarm types, engg units, user access settings, class based definitions, security definitions in terms of parameter security, function security etc.. You will also need to evaluate from the graphics point of view, the dynamos that are defined, the colour animations, any special .fxg files, schedulers, etc..

    You will also need to ensure that all the hardware is compatible and can be upgraded to your target revision. You will also need to consolidate all the licenses for having a single system. You will need to approach you local Emerson support centre to help you with that. You will need to create a redundant network for all nodes to reside upon.

    You will also need to consider the effects of the merger on historical data, event data and how you would want this to work after the merge.

    Once you have evaluated all this and realized the enormity of the task of merging systems, you may be overwhelmed and scared. Document all that needs changing, to make it uniform across all systems and then you are ready to do this on a test system, which is really important.

    I highly recommend that you get your local Emerson support team involved in this project to ensure that all aspects are completely covered and that you have expert help at all times.
  • Yawar Khan

    In reply to wtelkins:

    Yes 4 proplus station for now, but after internal checking i will make a network and bring to one server which will be proplus but i required the steps with out disturbing the process. These controller which are commissioned and in running state i wan to bring on one proplus server and change these four station to engineering with out disturbing the process.
  • Yawar Khan

    In reply to ELvin John:

    thanks for your reply, but i am working on same versions but yet network is not established there for testing purposes i have to assign different proplus to each station after it i have to bring all these controller to one network with one proplus server without disturbing the process and these station will become the engineering stations, but i want network establishment with out disturbing the process.
  • depthcharge623

    In reply to Yawar Khan:

    This cannot be done. It will require a shutdown of at least the three areas controlled with the three systems that are being moved.
  • Yawar Khan

    In reply to ELvin John:

    this thing was done due to client push because we have to check them the logic on live system but at that time network was not establish but after some time this network will establish and we have to bring all 4 section to one server so then these 4 proplus will become engineering station and one server for them as proplus and rest of four engineering, but i need steps to make this system with out distubing the process.
  • MichaelP
    Hallo K.Jadoon,

    The task is not easy. It is not quick.
    You will need to stop the operation of the physical equipment and disturb the physical hardware.
    This is clear. No question on this.
    The configuration should remain functionally the same. So in this way there is no 'disturbance'.
    There are good posts by other contributors on this subject (e.g. Elvin). Take their advice and get in touch with local support.
    Sound like you need expert help.
    With the initial investigations (by the expert) you can advise the client from a more informed position.
    It will be interesting project.
    You will learn a lot.
    Good luck.
  • Andre Dicaire

    In reply to ELvin John:

    Khan, to perform this without disturbing the processes requires that all four systems were implemented from the beginning with this end in mind. Specifically, the network addressing on all these systems must not overlap. If these systems were configured independently, the addressing will certainly overlap. In that case, you will have to decommission those controllers and bring them back on new addresses in the main system. If this is the case, those processes cannot be moved while running.

    If all the systems were developed with meticulous attention to consistency and with appropriate unique addressing, your desire is possible, but as Elvin points out, there are significant execution challenges that need to be considered. What you are attempting is simply not a supported capability. Doing this offline greatly simplifies the process, but there are still serious challenges that require planning and testing.

    On the addressing topic, the Pro Plus will be at 10.4.0.6 on all the systems, and that's ok. duplication of Workstation Addresses is minor, as these can change. But if the controller nodes, or IO nodes use the same addresses in different systems, those controllers cannot be moved over without decommissioning. That is definitely a show stopper for those nodes.

    Bottom line, you should absolutely get help from your Emerson service provider and ensure this is done by someone who has done this before, and knows all the issues and challenges. Having compatible addressing is only the first step. The next one should be to get help.

    Andre Dicaire

This is the official online community site of the Emerson Global Users Exchange, a forum for the free exchange of non-proprietary information among the global user community of all Emerson Automation Solution's products and services. Our goal is to improve the efficiency and use of automation systems and solutions employed at members’ facilities by sharing our knowledge, experiences, and application information.

User Groups | World Areas | Community Guidelines | Legal Information | Privacy Policy | Contact Community Manager

Website translation provided by Website Translator

© 2015-2022 Emerson Global Users Exchange. All rights reserved.