One AMS ServerPlus for two DeltaV systems

Hi,

 

We are planning to have two DeltaV systems on two domains. These two domains will be child domains of a parent domain.

We would like to have one central AMS server for the two systems, preferably residing in the parent domain, and several AMS clients installed on some DeltaV workstations.

How easy is it to do it? Would you recommend against it?

I suppose you cannot just simply add two DeltaV networks in AMS Network Configuration and then add the clients in Station Configuration.

Thank you,

 

Istvan

  • YES – you can install the Server Plus on the parent domain and have the Client SC stations on the two child domains.

     A few reminders when deploying this way:

    • Each DeltaV Pro Plus should have AMS Client SC installed and licensed. If other DeltaV stations will require AMS Device Manager functions, then additional Client SC licenses should be purchased and installed to them
    • Full version of SQL Server is highly recommended if total tag count will be more than 3,000 tags for optimal performance
    • KBA: NA-0800-0113 should be taken into consideration as well

     For more details, we highly suggest that you check our System Planning Guide that can be found at this link (https://psgext.emersonprocess.com/sites/pss/platforms/AO/Guides%20and%20Manuals/amsdm_ru_planguide12.pdf). This architecture is best depicted by the image in page 30 - Architecture A3: Single AMS Device Manager Distributed Network that Supports Multiple DeltaV Control Networks with or without Zones.

    Should you have further concerns or questions, please let me know. Thank you!

  • YES – you can install the Server Plus on the parent domain and have the Client SC stations on the two child domains.

    A few reminders when deploying this way:

    ◦Each DeltaV Pro Plus should have AMS Client SC installed and licensed. If other DeltaV stations will require AMS Device Manager functions, then additional Client SC licenses should be purchased and installed to them

    ◦Full version of SQL Server is highly recommended if total tag count will be more than 3,000 tags for optimal performance

    ◦KBA: NA-0800-0113 should be taken into consideration as well

    For more details, we highly suggest that you check our System Planning Guide that can be found at this link (psgext.emersonprocess.com/.../amsdm_ru_planguide12.pdf). This architecture is best depicted by the image in page 30 - Architecture A3: Single AMS Device Manager Distributed Network that Supports Multiple DeltaV Control Networks with or without Zones.

    Should you have further concerns or questions, please let me know. Thank you!

  • In reply to Abby Eugenio:

    Hello Abby,

    Your attached link is not working.

    Regards,
  • In reply to Ev15:

    Some additional info:
    When installing on Domains, make sure you install all AMS clients prior to installing AMS ServerPlus. This will creat trusts between the clients and ServerPlus. I believe this is called out in the installation guide but want to make sure you are aware of it. I know quite a few installations that did not follow this and had a lot of issues later.

    Another recommendation, make sure all your instruments has unique tag names for both systems. This will prevent confusion which system the device belong to.

    Lastly, try googling this System Planning Guide for your version of AMS.