• Not Answered

Requirements to change the System ID


We originally had one DeltaV system covering the entire plant. Today there are three systems each covering a different zone of the plant. The original system had enough licenses to cover the entire plant. We have the changed the licensing on paper but not in the system. Coinciding with our upgrade to version 12 I would like to correct the issue. This means removing all the licenses and installing the new ones which will have a new System ID number. I would like to know the requirements to complete this work smoothly. I have done something similar but it  has been a long time and there likely have been changes to what I need to do. I want to make sure I have all the questions answered in the procedure before I start.

BC

3 Replies

  • Can you help provide insight on this inquiry?

    Best Regards,

    Rachelle McWright: Business Development Manager, Dynamic Simulation: U.S. Gulf Coast

  • In reply to Rachelle McWright:

    BC, I would recommend that you work with your Emerson Local Business Partner(LBP). There is a process they need to implement to get this to happen, a lot of steps, and some cost associate to this change. If your are breaking up your 1 system to many smaller systems, they will need generate many system dongles for you and make new Pro+ systems. It is much easier if you are consolidating from many systems to one large one. In any case, you might want to get Technical support on this since it requires many things to happen before you can get to your final destination.

    I see you are going to DeltaV v12.3.1, put a big note to yourself there are licenses changes. You maybe gaining dst licenses do to these changes but it will required that your database goes to Emerson GSC/Product Engineering so they can decode these licenses for you. If you don't, you will lose them and it is not reversible.
  • In reply to Tinh Phan:

    The LBP is involved but more input to catch issues never hurts. We are not breaking up the systems, that is already done. The second two zones have been running for years, we just need to change the licenses on the initial Zone. We do not own the "extra" licenses on the original system, removing them is one of the purposes of the changes. Thanks for the reminder about the licenses changes in v12.3.1.

    BC