Abstract: A system (10) and method (200) for managing components in a control system can include a plurality of devices (150) operably coupled to a processing system (125) for controlling a process run by the processing system. A server (100) is in communication with the plurality of devices. A client (20) is in communication with the server (100), wherein the client (20) or an instance between the client and the server, such as controller (15), is operable to identify at least one relevant item associated with the plurality of devices (150). The at least one relevant item is one of a plurality of items to be added to a group, an inactive one of the plurality of items of the group being activated or one of the plurality of items of the group wherein the group is being activated.

Abstract: A system (10) and method (200) for managing components in a control system can include a plurality of devices (150) operably coupled to a processing system (125) for controlling a process run by the processing system. A server (100) is in communication with the plurality of devices. A client (20) is in communication with the server (100), wherein the client (20) or an instance between the client and the server, such as controller (15), is operable to identify at least one relevant item associated with the plurality of devices (150). The at least one relevant item is one of a plurality of items to be added to a group, an inactive one of the plurality of items of the group being activated or one of the plurality of items of the group wherein the group is being activated.

Abstract: An OPC redirection manager maintains the information necessary for taking appropriate action when the target OPC server fails and for ensuring that no bad status is returned to the client. Any existing OPC client needing seamless failover between target OPC data access and/or alarm and event servers will connect to a uniquely configured instance of the redirection manager instead of connecting to the primary server. The client application continues to perform OPC related tasks as usual. Because each client connection is unique, the redirection manager itself is not a single point of failure. Each configured redirection manager instance monitors the health of the target server mode and the target server itself by subscribing to failure events.

Abstract: An OPC redirection manager maintains the information necessary for taking appropriate action when the target OPC server fails and for ensuring that no bad status is returned to the client. Any existing OPC client needing seamless failover between target OPC data access and/or alarm and event servers will connect to a uniquely configured instance of the redirection manager instead of connecting to the primary server. The client application continues to perform OPC related tasks as usual. Because each client connection is unique, the redirection manager itself is not a single point of failure. Each configured redirection manager instance monitors the health of the target server mode and the target server itself by subscribing to failure events.

Abstract: An OPC redirection manager maintains the information necessary for taking appropriate action when the target OPC server fails and for ensuring that no bad status is returned to the client. Any existing OPC client needing seamless failover between target OPC data access and/or alarm and event servers will connect to a uniquely configured instance of the redirection manager instead of connecting to the primary server. The client application continues to perform OPC related tasks as usual. Because each client connection is unique, the redirection manager itself is not a single point of failure. Each configured redirection manager instance monitors the health of the target server mode and the target server itself by subscribing to failure events.