Deactivating Local HMI on Primary Server and Service Engine Continuity on Secondary Server

Deactivating Local HMI on Primary Server and Service Engine Continuity on Secondary Server

Hello,

We are in the midst of a project in v10 that uses a dominant scheme for two redundant servers communicating with IEDs, along with a standalone HMI client. The primary server operates within a virtual environment, while the secondary server acts as both the backup server and local HMI.

I am seeking some guidance on the following points:

  1. Primary Server: Given that the primary server is situated in a virtualized setting and isn't directly accessible to the operator, is it feasible to disable the local HMI? Just to clarify, even with the local HMI disabled, we want to ensure the driver continues to fetch data from the IEDs, the historian still logs events and alarms, and the server consistently provides OPC information to the client HMIs.

  2. Secondary Server: In case the operator close the HMI application, can we ensure that the server component keeps functioning on the service engine?

Your input would be greatly appreciated.

Thank you,


Abdallah