Centralized management of a software defined automation system

Patent metadata

Field	Value
Publication number	US-11953890-B2
Application number	US-202117390841-A
Country	US
Kind code	B2
Filing date	Jul 30, 2021
Priority date	Oct 13, 2015
Publication date	Apr 9, 2024
Grant date	Apr 9, 2024

Abstract

Embodiments of system and methods for providing centralized management of a software defined automation (“SDA”) system are disclosed. The SDA system comprises of a collection of controller nodes and logically centralized and yet physically distributed collection of compute nodes by monitoring activities of the compute nodes. In accordance with some embodiments, one or more components of the system monitor execution, network and security environments of the system to detect an event in a first environment. In response to the detected event, at least one component in the first environment is remediated, the remediation of the first environment creating a trigger to cause remediation of at least one component in each of a second and third environments.

First claim

What is claimed is:

1. A method of selecting a compute resource for deploying a guest comprising:
identifying compute resources in an automation system that are available to potentially receive deployment of a guest, at least two of the compute resources having different attributes from one another in the automation system;
assessing constraints of the guest against a set of operational parameters to select a type of host for the guest;
selecting a type of host for the guest based on the assessing;
selecting, based on the type of host selected, the assessing, and attributes of the compute resources that are available, a compute resource for the guest; and
deploying a host of the type selected that is configured with the guest and associated virtual network on the selected compute resource, the associated virtual network connecting the guest to other guests configured on other hosts, the selected compute resource connected to and managed by a fog controller, the fog controller interconnected to other compute resources in the automation system.

2. The method of claim 1 , wherein the compute resources that are available are physically distributed but monitored by a system controller of the automation system.

3. The method of claim 1 , wherein the operational parameters include at least two of: process critical level, a time sensitive level, a cost of execution, a proximity critical level and cost performance.

4. The method of claim 1 , wherein deploying the host configured with the guest on the selected compute resource is in response to a fault event, a maintenance event, a process event or a request to provision the guest on a compute resource.

5. The method of claim 4 , wherein the fault event is triggered by failure of a compute resource on which the guest was deployed.

6. The method of claim 4 , wherein the process event is triggered by a process variable running out of bounds.

7. The method of claim 1 , wherein the compute resources include at least one of: a server machine, a personal computer, a smart connected device, a human machine interface (HMI) module or an industrial controller.

8. The method of claim 1 , wherein the attributes of the compute resources include at least two of: processing power, memory size, processor chip technology, operating system or CPU utilization level.

9. The method of claim 1 , wherein the type of host is one of at least two of the following: a virtual machine, a container or a bare metal.

10. The method of claim 4 , further comprising monitoring the automation system to detect the fault event, the maintenance event or the process event.

11. An automation system comprising:
a system controller or redundant system controllers in communication with a plurality of compute resources, the system controller or redundant system controllers being implemented on one or more machines, and being configured to:
identify compute resources from the plurality of compute resources that are available to potentially receive deployment of a guest, at least two of the compute resources having different attributes from one another in the automation system;
assess constraints of the guest against a set of operational parameters to select a type of host for the guest;
select a type of host for the guest based on the assessing;
select, based on the type of host selected, the assessing, and attributes of the compute resources that are available, a compute resource for the guest; and
deploy a host of the type selected that is configured with the guest and associated virtual network on the selected compute resource, the associated virtual network connecting the guest to other guests configured on other hosts, the selected compute resource connected to and managed by the system controller, the system controller interconnected to other compute resources in the automation system.

12. The system of claim 11 , wherein the compute resources that are available are physically distributed but monitored by the system controller.

13. The system of claim 11 , wherein the operational parameters include at least two of: process critical level, a time sensitive level, a cost of execution, a proximity critical level and cost performance.

14. The system of claim 11 , wherein the host configured with the guest is deployed on the selected compute resource in response to a fault event, a maintenance event, a process event or a request to provision the guest on a compute resource.

15. The system of claim 14 , wherein the fault event is triggered by failure of a compute resource on which the guest was deployed.

16. The system of claim 14 , wherein the process event is triggered by a process variable running out of bounds.

17. The system of claim 11 , wherein the compute resources include at least one of: a server machine, a personal computer, a smart connected device, a human machine interface (HMI) module or an industrial controller.

18. The system of claim 11 , wherein the attributes of the compute resources include at least two of: processing power, memory size, processor chip technology, operating system or CPU utilization level.

19. The system of claim 11 , wherein the type of host is one of at least two of the following: a virtual machine, a container or a bare metal.

20. The system of claim 14 , the system controller is further configured to monitor the automation system to detect the fault event, the maintenance event or the process event.

21. The system of claim 11 , wherein the system controller and the plurality of compute resources reside in a customer premise equipment server or redundant customer premise equipment servers.

22. A non-transitory machine-readable storage medium storing instructions that, when executed by a machine, causes it to perform a method comprising:
identifying compute resources in an automation system that are available to potentially receive deployment of a guest, at least two of the compute resources having different attributes from one another in the automation system;
assessing constraints of the guest against a set of operational parameters to select a type of host for the guest;
selecting a type of host for the guest based on the assessing;
selecting, based on the type of host selected, the assessing, and attributes of the compute resources that are available, a compute resource for the guest; and
deploying a host of the type selected that is configured with the guest and associated virtual network on the selected compute resource, the associated virtual network connecting the guest to other guests configured on other hosts, the selected compute resource connected to and managed by a fog controller, the fog controller interconnected to other compute resources in the automation system.

Assignees

• Schneider Electric Ind Sas

Inventors

• Chauvet Antonio
• Wilhelm Philippe
• Harriman Merrill
• Alfano Eric
• Mehmedagic Alen
• Kling Andrew Lee David
• Doggett David
• Vallala Vijay

Classifications

• G06F9/45558

  Hypervisor-specific management and integration aspects · CPC title

• H04L41/0806

  for initial configuration or provisioning, e.g. plug-and-play · CPC title

• H04L41/08

  Configuration management of networks or network elements (address allocation H04L61/50) · CPC title

• H04L63/20

  for managing network security; network security policies in general (filtering policies H04L63/0227) · CPC title

• G06F2009/45595

  Network integration; Enabling network access in virtual machine instances · CPC title